WorkflowFleet, Leasing & Asset Management

Aircraft Technical Records Audit

An aircraft records audit that proves every requirement with its page and finds the gaps a year before handback

Every records gap found a year before handback, each with the page the agent checked.

See one case, screen by screen ↓
demo41,286pagesin one A330's records set, read and indexed overnight in an audit run of 3 h 41 min
demo23gapsfound 214 days before the return, 5 critical, each with every page the agents checked
target100%of 14 CFR 121.380 status items linked to the page that proves them
target12monthsbefore handback, the gap list is complete — not at the lessor's records inspection
In short

What is Aircraft Technical Records Audit?

Aircraft Technical Records Audit is aircraft records audit software that checks a full aircraft records set against everything it must prove — for a lease return, a mid-term lease records inspection, an induction, a sale or an FAA records inspection — and lists the gaps for the records team. Seven agents read every page, write the requirements from the regulation, the lease, the records manual and the lessor's checklist, prove each with its page or list the gap with every page checked, and look for the missing proof in other record sets. The records specialist decides and signs.

How to choose AI for airlines: a buyer's guide to agentic AI solutions →

Updated

The problem

Why an aircraft records audit still takes months — and finds the gaps too late

An aircraft records audit has to prove everything before a leased aircraft goes back to its lessor, is sold, or comes in from another airline: the status of every airworthiness directive with its date, method and next action, the back-to-birth history of every life-limited part, a release certificate for every component fitted since delivery (an FAA Form 8130-3, with dual release when the lease asks for it), and every check and repair with its approved data. Records teams prove it by hand, binder by binder, across tens of thousands of scanned task cards, work packages, logbooks and shop reports.

Most gaps surface late, at the lessor's pre-redelivery records review a few months before the return, when every day of delay costs rent, storage and MRO slots. The proof that is missing is often somewhere the airline already has — a repair shop's scan box never indexed to a tail, a previous operator's archive, an attachment in the records mailbox — but nobody has time to read 40,000 pages to find one certificate. A part whose back-to-birth chain breaks is usually retired, whatever life it has left.

typical120+man-daysof records and technical work for one first-lease narrowbody return, a widebody more than double
typical$2Mper narrowbodytypical overspend on a return that misses its conditions
typical$4.5Mper widebodytypical overspend on a return that misses its conditions
Where a widebody return's records days goestimated
By hand135 days
With the solution22 days
  • Pulling and indexing the records from every system and archive15 → 1 d
  • Writing what the records must prove from the lease, regulation and lessor checklist10 → 2 d
  • Proving each requirement page by page60 → 4 d
  • Searching other record sets for the missing proof25 → 5 d
  • Records requests to shops, previous operators and lessors15 → 8 d
  • The lessor pack and answering the lessor's issues list10 → 2 d

Estimated split of records-team days for one widebody lease return, by hand and with the solution.

How it works

How a records set is audited

Seven agents read every page, write what the records must prove, prove it or list the gap, find the missing proof elsewhere and check each other; the records specialist decides.

What comes in
Records in9 places · scans, M&E system, mailbox, shops, lessors
Agents at work
Intake agentreads every page
Requirements agentwhat it must prove
Then
Audit agentproves or lists the gap
Then
Source finderother record sets
Check agentre-reads blind
Then
Request agentdrafts requests
Lessor pack agentlessor-ready status
A person decides
Records specialistconfirms, closes or escalates each gap with a reason code
What comes out
Every requirement proven with its page
Gap list with pages checked
Signed lessor-ready pack
One case, step by step

An aircraft records audit, one gap at a time

N806CV, a Corvane Airways A330-300, MSN 1486, goes back to Aldermoor Aviation Capital on May 17, 2027 — 214 days from today. The records pack is due 90 days before. Here is the morning after its second audit run, screen by screen, in the working solution.

  1. 01Thursday, 08:05

    The agents worked overnight; her morning starts with their briefing

    Alicia Romero · Technical records specialist

    Alicia owns the N806CV return records. Today shows 23 open gaps on N806CV, 5 critical — there were 61 in April — and 94% lessor-ready, 389 of 412 proven. Five things need her: the 23 gaps found overnight, with a likely match for the top one, G-04 where the agents ask her to decide, the engine lessor's reply with 23 files, two drafted records requests and a Kestrel scan box newly indexed.

    Audit agent: “Overnight I read N806CV’s full records set — 41,286 pages — against the 412 things it must prove for the return to Aldermoor.”

  2. 02Overnight · 3 h 41 min

    Every page read, every requirement tried, every result re-read blind

    The agents

    The intake agent pulled 41,286 pages in 3,912 documents from 9 places — the M&E system, the scanned task-card archive, the technical log, the records mailbox, the C-check package from Tallis Aero Services, Kestrel Accessory Repair's scan boxes and the engine lessor portal among them — and found a 2017 box filed under N807CV. The audit agent proved 391 requirements with their pages and listed 21 gaps — a records gap analysis with every page it checked. The check agent re-read 60 proven items and 17 suggestions without seeing the first answer and turned 2 proven items into gaps.

    The plan the audit agent wrote: “Prove each of the 412 requirements with a page; never mark proven without one.”

  3. 03What it must prove

    412 requirements from four sources, each one quoted

    Requirements agent

    The list comes from the regulation (205 items: 14 CFR 121.380, 91.417 and 43.9), lease ALD-330-1486 Schedule 6 Part C (114), Corvane's Technical Records Manual rev 14 (66) and Aldermoor's records checklist in ATA Spec 2500 index order (27). Where two sources ask for the same proof, the agent kept one requirement and quoted both. The records manager approves the list before it is used.

  4. 04The records shelf

    Ten binders; every hole in a spine is a gap

    Alicia Romero · Technical records specialist

    The technical records review starts at the shelf, where the tail's records stand as binders: certificates, ADs, bulletins and modifications, life-limited parts, components and release certificates, checks, repairs, alterations, engines and APU, logbooks. Each spine shows how much it has proven — Components 90 of 96 — and every gap is a numbered hole with its severity. Beside the shelf, the audit agent, the source finder and the check agent each say what they did.

    “each binder is something the records must prove · every hole is a gap”

  5. 05Gap G-01 · critical

    No release certificate for the APU starter fitted in 2019

    Audit agent

    The records must hold an authorized release certificate (FAA Form 8130-3, dual release) for every component fitted since delivery — quoted from lease ALD-330-1486, 14 CFR 121.380(a)(1) and the records manual. Work order WO-19-30418 fitted APU starter P/N 3605812-4, S/N SG21877 on June 12, 2019 at DEN and cites “8130-3 tracking 4471-0619”, but no certificate is in the component file. The agent lists where it looked: 1,184 pages in 6 places.

    “Where the agent looked — so you can trust that it is not there.”

  6. 06The likely source · 0.94

    The certificate was in a shop's scan box, page 214

    Source finder and check agent

    The source finder searched record sets never indexed to a tail and found Kestrel Accessory Repair's box KAR-BX-17, scanned in August 2024: page 214 is a Form 8130-3 with the same part number, serial and tracking number, Block 11 “Overhauled”, the dual release statement present and a date of Jun 4, 2019 — before the fit. The check agent read the page without the source finder's answer and agrees.

    Check agent: “I read KAR-BX-17 p. 214 without the source finder’s answer: part number, serial, tracking number and the dual release statement all agree with WO-19-30418.”

  7. 07Confirmed and signed

    She confirms the match; the shelf moves to 95%

    Alicia Romero · Technical records specialist

    Alicia confirms with reason code C1 — proof found and matches — and her e-signature. The certificate is linked to the requirement and the gap closes: 22 gaps, 390 of 412 proven, 95% lessor-ready. Because G-01 was critical, Grace Okafor, the Continuing Airworthiness Manager, countersigns. The source finder already points to the next one, G-03.

    “I confirm the match and close the gap as Alicia Romero, Records Specialist — e-signature.”

  8. 08Gap G-04 · below 0.85

    A repair approval for the wrong drawing revision is her call

    Alicia Romero and the check agent

    Repair R-2021-044 on the aft cargo door surround was beyond SRM limits. An email in the records mailbox carries the manufacturer's approval, but it applies to drawing revision B and the repair was done to revision C. The source finder's confidence is 0.72, below the 0.85 threshold, and the check agent disagrees, so Confirm the match is locked. Alicia escalates it to Grace Okafor for an airworthiness decision.

    Check agent: “I cannot confirm: the approval covers drawing revision B; the repair was done to revision C. Ask engineering whether revision C is covered.”

  9. 09A records request

    The letter for a missing birth record is drafted, not sent

    Request agent

    G-05: the nose gear drag brace, S/N MG2209, has no birth record before 2016 — it came from a gear exchange at the 2024 overhaul and its history starts with a 2016 overhaul sheet. The request agent drafts R-2 to Arden Gear Services for the 2011 certificate of conformity, saying why back-to-birth traceability is needed and what Corvane holds. Alicia reviews and sends it; the 10-business-day clock starts then.

    “Drafted by the request agent · nothing is sent until you send it.”

  10. 10Lessor-ready

    The pack stays blocked until the critical gaps are closed

    Lessor pack agent · for Martin Keane

    Martin Keane, the lease technical manager, sees N806CV at 95% with the pack due to Aldermoor on Feb 16, 2027, each binder in the lessor's index order and Aldermoor's issues list from its April mid-term records review, MI-1 to MI-6, mapped to the gaps that answer them. Release stays blocked while a critical gap is open; at the current pace that is early January, six weeks before the pack is due.

    Lessor pack agent: “The pack can go once the 4 critical gaps are closed.”

Who it’s for

Built for everyone who answers for a records set.

The same return, seen by the four people who carry it — what the work looked like, and what it looks like now.

AR
Alicia RomeroTechnical Records Specialist, DEN · owns the N806CV return records
Technical records specialist
Before
“I can't read 41,000 pages for one certificate — tell me which page is missing and where it might be.” Chases certificates from shops and answers the lessor's issues list by hand.
Now
Opens each gap with what is required, what was found, every page checked and a likely source; confirms, rejects, requests or escalates with a reason code and her e-signature.
DH
Devon HartleyTechnical Records Manager · runs 9 audits at once
Technical records manager
Before
“I need to know which return is at risk this week, not the week the lessor arrives.”
Now
Approves what the records must prove, compares every audit run with the last, sets the rules and signs the records pack before it goes to a lessor.
GO
Grace OkaforContinuing Airworthiness Manager · countersigns critical gaps
Continuing Airworthiness Manager
Before
“If a part can't be traced, I decide what it means — not a spreadsheet.”
Now
Gets every escalated or disputed gap — a repair approval for the wrong revision, a broken back-to-birth chain — and countersigns every critical closure.
MK
Martin KeaneLease Technical Manager · Aldermoor's counterpart for the return
Lease technical manager
Before
“Aldermoor will ask for the pack in February. I want to send it in January.”
Now
Sees lessor-ready status by binder, the date the pack can go and the lessor's issues list answered gap by gap; reviews and sends the reply.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents read every page, write what the records must prove, prove it or list the gap, find the missing proof elsewhere and check each other; the records specialist decides.

Intake agent

Pulls every record from the M&E system, scan archive, technical log, records mailbox, stores receiving, shop boxes and lessor portals; reads the scans; files each document to its binder in the lessor's ATA Spec 2500 index; flags illegible, duplicate and mis-filed pages.

  • Never edits or deletes a record
  • Duplicate pages are kept and marked, not discarded
Requirements agent

Writes what the records must prove — AD status records, LLP back-to-birth history, release certificates, checks and repairs — from 14 CFR 121.380 and 91.417, the lease's return schedule, the airline's technical records manual and the lessor's checklist, and quotes each source.

  • Never drops a requirement
  • A new list needs the records manager's approval
Audit agent

Reads the whole records set against each requirement; proves it with the page, or lists a gap with what was found and every place and page checked.

  • Never marks proven without a page
  • Never closes a gap
Source finder

Searches other record sets for the missing proof — shop scan boxes never indexed to a tail, previous operators' archives, the records mailbox, stores receiving — and proposes a match with a confidence.

  • Never attaches a match
  • Below 0.85 it is the person's call
Check agent

Re-reads every proposed closure and a 15% sample of proven items without seeing the first answer; a disagreement blocks the close and can turn a proven item into a gap.

  • Never sees the first answer before it finishes
Request agent

Drafts records requests to shops, previous operators, lessors and internal teams, tracks each clock, and reads the replies and proposes them as proof.

  • Never sends without a person
Lessor pack agent

Keeps the lessor-ready status, maps the lessor's issues list to gaps and proof, and assembles the records pack in the lessor's ATA Spec 2500 index order.

  • Never releases a pack; the records manager signs
Records specialist

Closes each gap; the Continuing Airworthiness Manager countersigns critical ones; the records manager releases the pack. The agents propose; a named person decides.

Ask in plain words

Ask the agents about any gap, page or return

Every screen carries its own conversation. Ask in plain words, or tell the agents what to do; answers cite their source, and nothing is closed, sent or released until a person says so.

What changed since April?

61 gaps in April, 23 now: 42 closed, 4 new from work done after April (G-12, G-14, G-20, G-23), 19 carried. Nothing reopened.

Why did the check agent add two gaps?

I re-read 60 proven items without seeing the audit agent's answer. Two did not hold: G-07, an AD done to bulletin Revision 01 when the AD names Revision 02, and G-16, engine 1's HP turbine disc, where the LLP sheet and the logbook differ by 12 cycles.

What did the engine lessor send?

23 monthly utilization reports from Saxby Airways for ESN 41733, March 2020 to January 2022, adding up to 1,964 cycles — the exact jump on the LLP sheet.

Which critical gap will take longest?

G-05, the nose gear drag brace: no record set we hold has its 2011 birth record, so it waits on Arden Gear Services' answer to R-2. If none comes, Grace Okafor decides between replacing the part and agreeing other proof with Aldermoor.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

TodayThe records specialist's morning: open gaps and lessor-ready status for the aircraft, audits open, the next return, what needs her and the agents' briefing.
The records shelfAn aircraft records audit as a shelf of ten binders: each spine shows what is proven, each hole is a numbered gap, with the agents' conversation beside it.
The audit runEach agent's step in the overnight audit run, the plan the audit agent wrote and every records source read, with its page count.
What the records must proveWhat the records must prove: 412 requirements from 14 CFR 121.380, 91.417 and 43.9, the lease's return conditions, the technical records manual and the lessor's ATA Spec 2500 checklist, each with its proof or gap.
One gap, in plain wordsA missing FAA Form 8130-3 release certificate: what the records must prove, what the agent found and every place and page it looked.
The suggested sourceThe candidate certificate from a shop's scan box beside the requirement — part number, serial, tracking number and dual release checked — and the check agent's blind read.
After the gap closesThe shelf after a confirmed match: 390 of 412 proven, 22 gaps, 95% lessor-ready, and the source finder's next suggestion.
A call below the thresholdA structural repair approval for the wrong drawing revision at confidence 0.72: the check agent disagrees, so confirming is locked and the gap goes to a person to escalate.
Records requestsRecords requests to shops, previous operators and internal teams with their clocks, and a drafted letter for a missing back-to-birth record.
This audit against the lastRepeat aircraft records audits compared: gaps by binder from April to now — 42 closed, 4 new from later work, 19 carried, none reopened.
Lessor-ready statusAn aircraft lease return records review by binder, in the lessor's ATA Spec 2500 index order: the lessor's mid-term issues list mapped to gaps, and the pack release blocked by critical gaps.
Audit trailEvery agent step and every person's decision, newest first, with reason codes and a chain value per entry that shows any change.
Your rulesConfidence threshold, blind check, CAM countersign, release block, request answer time, repeat audit schedule and the records pack date — all settings.
Governance

Built for airworthiness records: every page cited, every decision signed.

Proven means a pageEvery requirement quotes its source — the regulation, the lease, the records manual or the lessor's checklist — and every proven item links the page it sits on. Every gap lists the places and pages checked.
Two agents must agreeThe check agent re-reads every proposed closure and a sample of proven items blind. A disagreement blocks the close until a person settles it.
People close, countersign and releaseAgents read, propose and draft. The records specialist closes each gap with a reason code and an e-signature; below 0.85 confidence it is always the person's call.
Airworthiness decisions stay with the CAMCritical gaps need the Continuing Airworthiness Manager's countersign, escalated gaps go to her, and the records pack cannot be released while a critical gap is open.
Read-only to the systems of recordConnections to the M&E system, scan archive, technical log, mailbox and portals are read-only; the agents never edit or delete a record. A lessor's representative sees only released packs.
A hash-chained audit trailEvery agent step and every person's decision is recorded with who, what, when and the reason code, each entry chained to the one before, so a change anywhere shows. Rule changes are logged as rules.
Configuration

Your records standard, not ours

What the agents check against and when a person must decide are settings. A rule change needs the records manager's approval with a reason, and is logged.

SettingDefaultChoose from
Confidence threshold0.85A value you set; below it, a suggested source is the person's call
Check agent must agreeOnOn · Off
Critical gaps need the CAM's countersignOnOn · Off
No pack release with a critical gap openOnOn · Off
Check agent sample of proven items15%A percentage, re-read blind in every run
Records request answer time10 business daysBusiness days you set; a reminder is drafted 3 days before the clock ends
Repeat audits before a return18, 12, 6 and 3 months18, 12, 6 and 3 months · 12, 6 and 3 months · Monthly from 12 months
Records pack to the lessor90 days before the returnDays before the return date you set
Connections

Works with the records you already keep

M&E systemrecords, work orders, AD and LLP status, attachments
Scan archivescanned task cards, work packages and logbooks
Technical logthe electronic tech log and its defects
Records mailboxattachments from shops, engineering and lessors, indexed
Stores receivingthe receiving log and component release certificates
Shop, lessor and engine lessor portalsshop scan boxes, previous operators' records, the lessor's checklist
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

typical
$4.5M
typical widebody return overspend when return conditions are missed
Gaps found at the lessor's auditup to $4.5M
Gaps found a year aheadclosed in time
target
100%
of 14 CFR 121.380 status items proven with their page, before the lessor or the FAA asks
390 of 412 proven
N806CV, after the APU starter certificate is found
target
12months
before handback, the gap list is complete — not at the lessor's records inspection

“demo” = seen in the working solution, on its sample records set · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (IBA, Revisiting redeliveries — 120+ man-days of records and technical work per first-lease narrowbody return, about $2M per narrowbody and $4.5M per widebody overspent when return conditions are missed; Acumen on deeper records checks about 12 months before handback; 14 CFR 121.380 on the status records an operator keeps). People, airlines, lessors, shops, aircraft and part numbers named on this page are fictional — characters and sample data in the working solution.

Questions

What records teams and lease managers ask about an aircraft records audit.

What is Aircraft Technical Records Audit?

Aircraft Technical Records Audit is aircraft records audit software that checks a full aircraft records set against everything it must prove — for a lease return, a mid-term lease records inspection, an induction, a sale or an FAA records inspection — and lists the gaps for the records team. Seven agents read every page, write the requirements from the regulation, the lease, the records manual and the lessor's checklist, prove each with its page or list the gap with every page checked, and look for the missing proof in other record sets. The records specialist decides and signs.

What records are needed to return a leased aircraft?

The 14 CFR 121.380 maintenance records and the 91.417 records, plus whatever the lease's return conditions, the lessor's checklist and your technical records manual add: AD status with date, method and next action, back-to-birth records for every life-limited part, a release certificate for every component fitted since delivery, checks, repairs with their approved data, alterations, engine and APU records and logbooks. On the demo A330 that is 412 requirements in 10 binders.

How does it find a missing FAA Form 8130-3 release certificate?

The audit agent reads the work order that fitted the part and lists every place it searched. The source finder then searches record sets never indexed to the aircraft — shop scan boxes, previous operators' archives, the records mailbox, stores receiving — and proposes a page with a confidence. On the demo it found the APU starter's certificate in a shop scan box, page 214, at 0.94, with part number, serial, tracking number and dual release checked.

What is back-to-birth traceability, and does it check it?

Back-to-birth traceability is the unbroken history of a life-limited part from its manufacture to today, with every cycle recorded. Yes: life-limited parts are their own binder. A break in the history, a cycle count that differs between the LLP sheet and the logbook, or an unsigned LLP page becomes a gap, and the request agent drafts the letter to whoever holds the missing record, such as a previous operator or a gear exchange provider.

How early should records be reviewed before a lease return?

The solution is designed to have the gap list complete 12 months before handback, so the lessor's pre-redelivery records review is not the first time anyone sees a gap. Repeat audits run at 18, 12, 6 and 3 months before a return by default, and each run is compared with the last, showing what closed, what is new and what reopened.

Can AI audit aircraft technical records on its own?

AI agents do the reading, but people decide. Agents never mark a requirement proven without a page, never close a gap, never send a request and never release a pack. Below 0.85 confidence the person decides, the check agent must agree before a close, critical gaps need the Continuing Airworthiness Manager's countersign, and the records manager signs the pack.

Does it produce the records pack in ATA Spec 2500 order?

Yes. The intake agent files every document to its binder in the lessor's ATA Spec 2500 index, and the lessor pack agent assembles the pack in that order, keeps the lessor-ready status and maps the lessor's issues list to the gaps and proof that answer each item. The index of the ATA Spec 2500 records can be exported from the lessor-ready screen.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your technical records manual, a lease's return conditions, a lessor's checklist and a sample records set — and it goes live once every quality gate has passed. We will walk you through it on one of your own aircraft first.

See it on
your next return.

We'll run Aircraft Technical Records Audit on the records set of one of your own aircraft.