Audit readiness
Operator records-readiness checklist
This checklist gives an operator a structured self-check on its records before an authority audit, a customer audit, or a transaction, comparing tracking output to source records and testing AD status, LLP currency, and retention. Run it on a sampled set of tails first. You finish with a readiness score by record area, a sampled-finding list, and a remediation plan ordered by exposure.
When this review is needed
- An authority or customer audit is scheduled and the records need a dry run.
- A transaction is approaching and the operator wants findings before a third party raises them.
- The tracking system has been in use for years without a check back to source documents.
- A new quality lead wants a baseline read of where the records actually stand.
The problem
Maintenance tracking gives a confident-looking status, and that confidence is the problem. Years of entries summarize work that may or may not have a retrievable source record behind it. An AD shows as complied with, but the accomplishment evidence cannot be produced on demand. The operator only learns which lines are unsupported when an auditor or a buyer pulls them, by which point it is a finding rather than a fix.
What gets reviewed
- Tracking output sampled line by line against source records
- AD compliance status and the supporting accomplishment evidence
- Life-limited part currency and the trace behind the status list
- Records retention against the applicable retention requirement
- Repair and alteration records with their approval basis
- Retrievability of archived records under realistic audit timeframes
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- A sample of tracking entries traces to a matching source record
- Each AD shows accomplishment evidence and the method of compliance
- Life-limited part remaining life is supported by the underlying documents
- Records are retained for the required period and are retrievable on request
- Repairs and alterations show the approval basis behind each entry
Evidence normally required
Common discrepancies
- Tracking entries that summarize work without a retrievable source record behind them
- An AD shown as complied with where the accomplishment evidence cannot be produced
- LLP life remaining that is not supported when the source documents are pulled
- Records archived in a format or location that is slow to retrieve under audit
- A repair recorded with no approval basis attached
What is at stake
An unsupported status line found by an authority becomes a formal finding with a deadline; the same line found by a buyer becomes a price concession. Found internally on a sample first, it is just a remediation item the operator schedules on its own terms.
How the work runs
Pull the sample
Select a representative set of tails and record areas, and document the sample size and how it was chosen.
Trace to source
Test sampled tracking, AD, and LLP lines against the source records that should support them.
Score by area
Assign a readiness score per record area so the weakest areas are visible before anyone external looks.
Order remediation
Build a remediation plan ranked by audit and transaction exposure rather than by ease of fix.
What the buyer receives
- A readiness score by record area with the sample size noted
- A sampled-finding list with the source-record gap for each item
- A remediation plan ordered by audit and transaction exposure
Who uses the output
- Quality and compliance leads preparing for an audit
- Continuing-airworthiness management closing the highest-exposure gaps
- Asset management sizing records risk ahead of a transaction
How the work fits into the transaction or program
The checklist is a dry run before an external eye arrives. Where a tracking line fails the sample, the source-to-status reconciliation checklist takes that area to a full reconciliation, and findings feed a structured discrepancy register.
Regulatory limits
A readiness self-check confirms completeness and traceability on a sample. It is not an authority finding, does not predetermine an audit result, and does not make an airworthiness determination.
What this review does not cover
- Conducting the actual authority or customer audit
- Physical inspection of the aircraft
- Any airworthiness determination or regulatory approval
Specific to this review
- A readiness self-check confirms completeness and traceability; it is not an authority finding and does not predetermine an audit result.
- Sampling is the practical method, because checking every entry on a large fleet is rarely feasible before an audit date.
- Ordering remediation by exposure means an unsupported AD line is fixed ahead of a cosmetic gap, because the two carry very different audit weight.
Sources
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
Why sample instead of checking everything?
On a fleet of any size, full verification before a fixed audit date is rarely feasible. A documented sample gives a defensible read on where the records stand and points remediation at the weakest areas first.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Adapt the checklist to your asset, event, and jurisdiction.