Airworthiness reviews
Airworthiness review evidence read against the modification baseline
Airworthiness review files record what a reviewer examined, what was found, and how findings were closed before the certificate was recommended or issued. Read against a modification baseline, they are both evidence and test: the file's sampled records should agree with the baseline, and its open items should have dispositions the source package can produce. This review performs that reading during a configuration baseline effort, item by item across each review file in the aircraft's history. The configuration manager receives an exception list covering undispositioned findings, sampling mismatches, and gaps between successive reviews, formatted for the configuration support package.
When this review is needed
- Successive review files reference findings whose dispositions never made it into the aircraft's records.
- A review file's sampled modification records disagree with what the baseline now shows, and one of them is wrong.
- The aircraft is moving toward an EASA registry and its historical review files will be read during induction.
- Certificates were extended rather than renewed for several cycles and the underlying file depth is unknown.
The problem
Review files are written for the moment of certificate issue, then filed and forgotten. Findings raised during a review are often dispositioned through channels that never write back to the file: the mod record gets corrected, the missing document turns up, and the file still shows an open item with no resolution attached. Years later a reader cannot tell closed-and-undocumented from genuinely unresolved, and each successive review file references its predecessors, so one silent gap echoes through every file after it.
What gets reviewed
- Every airworthiness review file available in the aircraft's history, in sequence
- Findings and observations in each file, traced to a documented disposition
- Records sampled by each reviewer, re-checked against the current verified baseline
- Continuity between successive reviews: carried items, extensions, and renewal depth
- References from review files to modification, AD, and repair records in the source package
- The physical-survey remarks in each file, compared with configuration claims of the same date
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 finding in a review file resolves to closure evidence somewhere in the source package, or is confirmed still open
- Sampled record extracts quoted in the file match the corresponding records as they exist today
- Items carried between reviews appear in both files with consistent identity and status
- Extension decisions are documented with the basis the applicable rules require
- Survey remarks about configuration agree with the modification status verified for that date
Evidence normally required
- All available airworthiness review files and associated certificates
- The verified modification baseline and status report
- Disposition records for findings: corrected documents, recovered evidence, or corrective-action records
- AD and repair records the review files reference
- Registry and operator history to place each review in its regulatory context
Common discrepancies
- A finding about a missing SB record that was recovered a month later, with the recovery never noted against the review file
- Sampled extracts that no longer match the record, indicating the record changed after the review without an audit trail
- Consecutive extensions where the rules anticipated a full renewal, leaving years without deep review evidence
- Survey remarks describing equipment the modification records say was removed before the review date
What is at stake
A review file with unresolved findings undercuts the very instrument it supported: a counterparty can argue the certificate was recommended over open issues, and the burden of disproving that lands on the current owner. Where a file's sampled records contradict the baseline, the contradiction has to be run to ground before either document can be trusted, and doing that under transaction pressure is the expensive version.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Sequence the files
Order every review file and certificate event on a timeline, noting registry context and extension patterns.
Chase the findings
Trace each documented finding to closure evidence in the source package or confirm it as open.
Re-run the samples
Compare each file's sampled extracts against the corresponding records and the verified baseline.
Reconcile and report
Issue the exception list, continuity timeline, and conflict reconciliations for the support package.
What the buyer receives
- An exception list of undispositioned findings and sampling mismatches per review file
- A review-continuity timeline showing renewals, extensions, and depth across the aircraft's history
- A reconciliation note where review evidence and the baseline conflict, with a reasoned view on which record is defective
Who uses the output
- Configuration managers resolving conflicts between review files and the baseline
- CAMO teams preparing the next airworthiness review with a clean inheritance
- Buyers and lessors evaluating the depth behind the aircraft's certificate history
How the work fits into the transaction or program
This strand acts as an independent audit of the whole modification-baseline effort: reviewers in past years sampled the same records the baseline now rests on, and disagreement in either direction is diagnostic. It runs near the end of the sequence so the baseline it tests against is already verified, making every mismatch attributable rather than ambiguous.
Jurisdiction-specific considerations
The airworthiness review as a formal instrument belongs to the EASA system, defined in Regulation 1321/2014 and executed by CAMO or review staff, so its files exist only for the EASA-registered portions of an aircraft's life. FAA-registered periods produce different artifacts under 14 CFR 91.417, and ICAO Annex 8 supplies the continuity concept across the gap. A cross-registry aircraft is therefore reviewed era by era, and the absence of review files for FAA years is expected rather than exceptional.
Regulatory limits
This work audits documentation around past reviews; it is not itself an airworthiness review. It cannot issue, extend, or recommend a certificate, makes no airworthiness determination, and does not substitute for the review the current CAMO must perform on its own authority.
What this review does not cover
- Performing a new airworthiness review or physical survey
- Certificate applications, extensions, or authority liaison
- Re-adjudicating whether past reviewers should have issued their recommendations
Specific to this review
- Review files are the only records in the source package written by an examiner with a duty to sample skeptically, which is what makes their mismatches against the baseline so informative.
- Findings closed outside the file are far more common than genuinely open findings; the review's main work is converting the first kind into documented closures.
- A run of extensions is legitimate under the rules but thins the evidence trail, and sophisticated buyers now ask specifically about renewal depth.
- When a sampled extract disagrees with today's record, the defect is as likely in the record's later handling as in the original review, so the reconciliation cannot assume either side is right.
Sources
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
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.
Frequently asked questions
Do old review findings still matter once later certificates were issued?
Yes, because each certificate rests on the file behind it. A later issue does not retroactively close an earlier finding; it may simply mean the finding escaped the next reviewer's sample. Documented closure is what removes a finding from the aircraft's story, and this review either locates that documentation or lists the item as open inheritance for the current CAMO.
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.