ARC evidence at handback
Airworthiness review records traced through the redelivery binder source set
An airworthiness review file arriving in a redelivery binder should let the reader reconstruct each review: who performed it, what it found, and how the findings were closed. This check traces the file through the binder's indexes, discrepancy registers, and acceptance notes to confirm that reconstruction is possible. Lessors commission it when taking an aircraft back, and operators run it on themselves before the lessor's inspector does. It returns a finding-level account of the review history with each unevidenced closure or undischarged item listed for the acceptance file.
When this review is needed
- The current ARC was granted on a recommendation and the recommendation report is nowhere in the binder.
- Review findings from the last physical survey reference corrective actions that still need locating in the records.
- The ARC has been extended in consecutive years and the return falls near the point where a full review becomes due.
- The aircraft is leaving an EASA registry and the incoming operator must judge how much of the review history it can rely on.
The problem
The ARC on the flight deck is one page, while the history behind it spreads across review reports, recommendation files, and finding closures split between the CAMO and the operator. Binder compilers file the certificates and stop, because certificates are easy to find. At acceptance the questions are about substance: what the last review found, whether the closures are real, and whether the extension chain rested on a genuinely controlled environment.
What gets reviewed
- ARC issue and extension chronology reconstructed and checked for continuity across the lease
- Each review report located, with its aircraft survey and records review portions present
- Findings from each review traced to corrective action and closure evidence in the binder
- Recommendation reports checked where the ARC was issued by the competent authority on recommendation
- Open items referenced by the latest review reconciled against discrepancy registers and acceptance notes
- Reviewer authorizations and CAMO details checked for consistency with the certificates issued
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 ARC and extension in the chronology exists as a document, with no gaps between validity periods
- Findings enumerated in review reports each have a closure record, a due disposition, or an explicit carry-forward
- The physical survey portion of each review is evidenced and its date is consistent with the aircraft's location and check history
- Extensions were granted within a controlled environment consistent with the continuing-airworthiness records for that period
- Items the latest review left open appear on the redelivery acceptance notes rather than only inside the review report
Evidence normally required
- All ARCs and extensions issued during the lease
- Airworthiness review reports and any recommendation reports
- Finding and corrective-action records from the CAMO
- The binder's discrepancy registers and acceptance notes
- Continuing-airworthiness records covering each extension period
Common discrepancies
- An extension chain valid on paper while records for the same period show lapses that question the controlled environment
- Review findings closed in the CAMO's tracking system with no closure evidence filed into the binder
- A recommendation report absent because it stayed with the reviewing organization when the CAMO changed
- The latest review's open items missing from the acceptance notes, leaving the return negotiation working from an incomplete picture
What is at stake
A review file that cannot show finding closure invites the acceptance team to treat those findings as open, which widens the return workscope. An incoming CAMO that cannot rely on the history budgets for its own full review with a physical survey, and that cost, plus the hangar slot it requires, gets argued straight into the return negotiation.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the chronology
Lay out every review, ARC, and extension across the lease and identify the documents each event requires.
Locate the substance
Pull review reports, recommendation files, and finding records into the chronology.
Trace finding closures
Follow each finding to its corrective action and confirm the closure evidence sits in the binder.
Report reliance and gaps
Deliver the chronology, the finding table, and the reliance assessment for acceptance.
What the buyer receives
- A review-history chronology with every certificate, report, and extension evidenced or flagged
- A finding-closure table for the acceptance file listing each unevidenced closure
- An assessment note on which parts of the review history the incoming CAMO can rely on
Who uses the output
- Lessor technical teams deciding what the review history is worth at acceptance
- The incoming operator's CAMO scoping its own review and survey needs
- The returning operator's records staff recovering closure evidence before handback
How the work fits into the transaction or program
The review file connects the binder's certificates to its maintenance evidence, so it is read alongside the AD and deferral sections that review findings usually point into. Exceptions from this check land in the acceptance discussion and shape whether the next registry entry needs a fresh full review or can build on the existing history.
Jurisdiction-specific considerations
The ARC construct belongs to the EASA system under Part-M and Part-CAMO. An aircraft heading to the FAA registry does not carry an ARC forward, yet the review history still matters as evidence of continuing-airworthiness control, and FAA inspection-record requirements under 14 CFR 91.417 take over on arrival. Moves in the other direction raise a sharper question: whether the inherited records will support a first ARC on the new registry without a full independent review.
Regulatory limits
This check does not perform an airworthiness review, issue or extend an ARC, or make any airworthiness determination. It reports whether the review records in the binder are complete and internally supported, and leaves regulatory judgments to the CAMO and the competent authority.
What this review does not cover
- Conducting the physical survey or records review an actual airworthiness review requires
- Interacting with the competent authority about ARC validity
- Closing review findings by performing or certifying maintenance
Specific to this review
- Two consecutive ARC extensions force a full review the following year, so a return date near that boundary decides whether the lessor inherits a fresh review or an imminent one.
- Recommendation reports are the documents most often missing from ARC files, because they belong to the reviewing organization's process and binder compilers stop at the certificate.
- Extension validity depends on the aircraft having stayed in a controlled environment, which makes the extension evidence only as strong as the continuing-airworthiness records for those same months.
- Review findings are a leading indicator for the rest of the binder: a review that struggled to close findings usually signals thin evidence in the AD and component sections too.
- A well-evidenced review history retains value even where the certificate does not transfer, because the incoming CAMO can credit it in scoping its own review effort.
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 ARC on board is valid. Why would acceptance still question the review history?
Validity and evidential completeness are different tests. The certificate shows a review concluded; the acceptance team wants to see what it found and how the findings closed, because open or unevidenced findings translate directly into return workscope. A valid ARC over a thin file protects the operator in service and still costs money at handback.
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.