CAMO file reviews
Airworthiness Directive status review against the CAMO source file
This review reads an AD status list line by line against the continuing-airworthiness file that is supposed to stand behind it: CAMO status reports, airworthiness-review notes, maintenance-program references, and open-item logs. It is run for CAMO managers and fleet teams when an airworthiness status baseline is being set or challenged, typically ahead of an airworthiness review, an operator transfer, or a lease event. Each closed directive is matched to its accomplishment record, method of compliance, and any repetitive interval it carries. Directives whose closure the file cannot support come back as a dated exception list.
When this review is needed
- An airworthiness review is due and the signatory wants the AD baseline tested before the physical part starts.
- The aircraft is changing CAMO providers and the incoming organization will inherit the status list as written.
- An authority finding or audit observation has cast doubt on how directives were closed historically.
- A lease event will put the AD list in front of a counterparty whose reviewers work from source evidence.
The problem
An AD status list accumulates entries from years of engineers, software migrations, and inherited data, and each closure carries an implicit promise that a record exists somewhere. The CAMO file is where that promise is supposed to be kept, but status codes migrate cleanly while the evidence behind them often does not. Whoever signs the next airworthiness review inherits every optimistic closure made before their time.
What gets reviewed
- Every closed AD on the status list against accomplishment evidence in the CAMO file
- Method of compliance cited for each closure, including AMOC approvals where used
- Repetitive AD intervals against the maintenance-program references that schedule them
- Superseded and revised directives, checking each status line reflects the current issue
- Applicability decisions recorded for ADs marked not applicable
- Open-item logs for directives parked as deferred or in progress
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
- Each closed entry cites a work record, and that record exists in the file with the right aircraft, date, and hours or cycles
- The method of compliance on the record matches an option the directive actually permits
- Repetitive directives show a next-due point consistent with the last accomplishment and current utilization figures
- Not-applicable calls are backed by a configuration or effectivity rationale, and that rationale still holds
- AD revisions issued after closure have been assessed rather than silently carried under the old status
Evidence normally required
- The current AD status list with closure references
- The CAMO file: status reports, airworthiness-review notes, and open-item logs
- Accomplishment records for targeted closures, including task cards and release documents
- Current utilization figures for hours and cycles
- AMOC approvals and applicability assessments where the list relies on them
Common discrepancies
- Closures citing a work order number that no surviving record carries
- Repetitive ADs whose next-due date was computed from an accomplishment the file cannot produce
- Not-applicable determinations made against a configuration the aircraft no longer has
- Directives closed by SB reference where the SB record shows partial embodiment
What is at stake
A directive that cannot be shown as accomplished is, for review purposes, open. Discovering that during an airworthiness review or a redelivery inspection converts a paperwork gap into a grounded-aircraft problem, with the search for decades-old work records running against a live deadline.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Freeze the baseline
Fix the AD status list version under review and inventory the CAMO file material it will be read against.
Trace closures to evidence
Match each closed directive to its accomplishment record and confirm aircraft identity, dates, and utilization figures line up.
Test intervals and applicability
Recompute repetitive due points from the evidenced accomplishments and re-examine every not-applicable determination against current configuration.
Issue the exception list
Report unsupported closures with the specific gap and the likeliest retrieval source for each missing record.
What the buyer receives
- A directive-level exception list stating the evidence gap for each unsupported closure
- A supported-status view of the AD list showing which lines stand on file evidence
- A retrieval plan naming the likely source for each missing record
Who uses the output
- CAMO managers setting or defending the airworthiness status baseline
- Airworthiness-review staff scoping the document portion of the review
- Fleet and asset teams preparing an AD list for a lease or sale counterparty
How the work fits into the transaction or program
AD status is usually the first list a counterparty or reviewer attacks, so this review often anchors a wider CAMO-file program that goes on to LLP trace, release documents, and repair data. Its exception list feeds the operator's records-gap remediation, and its supported-status view gives the airworthiness review a tested starting point.
Jurisdiction-specific considerations
14 CFR Part 39 makes each AD a regulation in its own right, and 14 CFR 91.417 requires the current status of applicable ADs, with method of compliance and recurring times, to be kept and to transfer with the aircraft. EASA operators carry equivalent duties under Regulation (EU) 1321/2014, where the CAMO holds the status and the airworthiness review checks it. The review is built to those record requirements; it does not reinterpret the directives themselves.
Regulatory limits
The review states which closures the file supports and which it does not. It does not declare the aircraft airworthy or unairworthy, does not approve methods of compliance, and does not substitute for the airworthiness review or any authority action.
What this review does not cover
- Engineering assessment of alternative methods of compliance
- Performing or certifying the airworthiness review itself
- Physical inspection to confirm embodiment on the aircraft
Specific to this review
- Status-system migrations are the classic point where closure evidence detaches from the list: the code moves, the attachment does not.
- A single unsupported repetitive AD invalidates its whole downstream due chain, because every later due date inherits the unproven anchor point.
- Not-applicable is the least-audited status code and the one most likely to be wrong after a modification changed the configuration.
- Retrieving a twenty-year-old accomplishment record from a defunct MRO can take longer than re-performing the inspection, which is why exceptions are ranked by retrievability.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Is this the same as the document portion of an airworthiness review?
It covers similar ground but runs independently of the review signatory, earlier, and deeper on the AD list specifically. Many CAMOs use it to clear exceptions before the formal review so the certificate decision does not stall on record retrievals.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.