Review-file evidence
Airworthiness review records check within an import and export records package
An airworthiness review records check reads the airworthiness review file that travels with an import, export, or registry change and asks whether the surrounding package can support it. Review reports, recommendation documents, and certificate copies are compared against status summaries, registry correspondence, and the supporting records. Transition and acquisition teams commission it before the file goes to a receiving CAMO or authority. What comes back is a list of the review items whose evidence is missing or inconsistent, written so the transition lead can slot it straight into the authority-response file.
When this review is needed
- An aircraft is moving onto an EASA registry and the receiving CAMO will rely on the airworthiness review file.
- The current review certificate was granted with findings whose closure evidence has never been assembled in one place.
- A registry change is timed close to the review's expiry and any gap could force a fresh full review.
- The buyer's technical team has asked how the last review's open items were dispositioned and the answer is scattered.
The problem
A review file often records that findings existed without carrying the evidence that closed them. During a registry change, the receiving CAMO or authority reads that file line by line, and every disposition that points to a document held somewhere else becomes a question the seller's team has to run down. The people who closed those items may have left, and the closing records may sit in a system the transition team cannot reach.
What gets reviewed
- The most recent airworthiness review report and its findings, traced item by item to closure evidence
- Certificate copies and their validity dates set against the registry-change timeline
- Recommendation documents checked against the status the source records actually show
- Dispositions that reference external records confirmed to exist inside the package
- Continuity between successive reviews, so no finding disappears between reports without a recorded close
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
- Every open item in the review report has a disposition, and every disposition has a document behind it
- Certificate validity covers the registry-change dates the transaction assumes
- Statements in the recommendation match the AD, maintenance, and deferral status the package supports
- No review finding is closed by reference to a record that turns out to be absent from the package
- The chain of successive reviews is unbroken, with each report accounting for its predecessor's open items
Evidence normally required
- The airworthiness review file: reports, recommendations, and certificate copies
- Status summaries current to the review date and to the planned transfer date
- Registry-change correspondence and any receiving-authority requests
- The supporting records the review dispositions cite
Common discrepancies
- A finding marked closed against a work order the package does not contain
- Certificate validity that lapses inside the planned transfer window
- A recommendation whose stated deferral position no longer matches the current status list
- Open items carried silently between successive reviews with no disposition recorded for either
What is at stake
If the review file cannot demonstrate its own dispositions, the receiving side may decline to rely on it, which can push the aircraft into a fresh airworthiness review at the worst possible point in the transaction. That adds weeks, invites new findings, and hands the counterparty leverage on price and conditions that a complete file would have avoided.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Reconstruct the review trail
Assemble reports, recommendations, and certificates into a dated sequence and note every finding raised.
Trace dispositions to evidence
Follow each closure statement to the record that proves it, inside the package or beyond it.
Test the timeline
Set certificate validity against the registry-change dates and flag any interaction.
Deliver the exception file
Hand over item-level exceptions, the retrieval list, and the timeline note.
What the buyer receives
- An item-level exception list for the airworthiness review file, keyed to missing or inconsistent evidence
- A validity and timeline note showing where review dates and transfer dates interact
- A retrieval list naming each absent document and its most likely holder
Who uses the output
- Transition leads answering the receiving CAMO or authority
- Records staff pulling the closure evidence the exceptions identify
- Acquisition teams judging whether to rely on the existing review or plan a new one
How the work fits into the transaction or program
This check runs alongside the wider import and export package review, focused on the one file a receiving CAMO scrutinizes hardest. Its exception list feeds the same authority-response evidence file as the rest of the package work, and its timeline note often decides whether the transfer schedule holds.
Jurisdiction-specific considerations
Practice around airworthiness reviews differs between the FAA and EASA systems. On the EASA side the review and its certificate are formal Part-M and Part-CAMO instruments with defined validity, while an FAA-registered aircraft carries no direct equivalent, so a westbound or eastbound transfer changes what the file must prove. The check is framed around the receiving system's expectations, since that is who reads the file next.
Regulatory limits
The check evaluates documentation only. It does not perform an airworthiness review, does not extend or issue any certificate, and does not decide whether the receiving authority or CAMO will accept the existing review. Those judgments stay with the approved organizations and authorities that hold them.
What this review does not cover
- Conducting a new airworthiness review or physical survey
- Acting as the CAMO of record for either party
- Advising on the commercial terms of the registry change
Specific to this review
- A review certificate's remaining validity is a transaction asset; losing it to a documentation gap can cost weeks at closing.
- Dispositions that cite records by reference are the most common failure point, because the reference survives while the record gets archived out of reach.
- Receiving CAMOs often re-perform sampling on the review file, so an exception list prepared in advance predicts most of their questions.
- A registry change close to review expiry leaves no slack: a single unresolved finding can force the full review to be repeated under the new system.
- Successive review reports that disagree about an open item signal a records-control problem larger than the item itself.
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
The aircraft has a valid review certificate. Why would anyone re-check the file behind it?
Validity and demonstrability are different things. The certificate shows a review happened; the receiving side still reads the file to decide how much weight to give it, and gaps in the file transfer as risk to the buyer.
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.