Review file integrity
Airworthiness review evidence inside a component-history source file
Past airworthiness reviews are third-party attestations sitting inside the records history, and this check verifies they hold together. Each airworthiness review file in the component-history source file is read for completeness, for the disposition of any open items it recorded, and for consistency between what the review attested and what the surrounding records show for the subject component. The check runs as part of a serialized-component trace review, since a review file that contradicts the trace weakens both. It delivers an integrity report listing undispositioned items and attestation conflicts.
When this review is needed
- A past airworthiness review recorded findings and the file shows no disposition for several of them.
- The trace claims a status for the component that the most recent review file appears to contradict.
- Review files from a prior CAMO arrived incomplete at transition and their gaps were never inventoried.
- A counterparty's checklist asks for the airworthiness review history alongside the component trace, and the two have never been read together.
The problem
An airworthiness review file is treated as a finished artifact the moment the certificate issues, and its contents stop being read. Open items noted by the reviewer pass into a follow-up list that dissolves at the next organizational change, and the review's recorded observations about the component sit unexamined next to a trace that may quietly disagree with them. When both documents reach a counterparty, the disagreement is theirs to find.
What gets reviewed
- Each airworthiness review file in the history checked for completeness against its own index
- Open items and observations recorded by past reviews extracted into a single register
- Dispositions located for each item in later records, or their absence documented
- Review attestations concerning the component compared with the source file's evidence
- Continuity between successive reviews examined, including items appearing and vanishing between cycles
- Reviewing organization and signatory authority recorded for each file
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 recorded by a past review has a locatable disposition or is flagged as outstanding
- Statements in each review file about the component agree with the movement, status, and release records
- No finding disappears between consecutive review cycles without a documented closure
- Each review file is complete against its own document index, with missing annexes identified
- Utilization and status figures quoted in review files reconcile with the trace's figures for the same dates
Evidence normally required
- The airworthiness review files held in the records history, with annexes
- The component-history source file, including status reports and movement records
- Follow-up or corrective-action logs from the periods after each review
- CAMO transition records where continuing-airworthiness management changed hands
- The current component trace draft the review files will accompany
Common discrepancies
- Review items marked for follow-up with no trace of closure in any later record
- A review file quoting component status that conflicts with the release and movement evidence
- Files missing annexes that their own index says should be present
- Findings recorded in one review cycle that simply never appear in the next
What is at stake
Undispositioned review items compound across review cycles: each new review either re-finds them, which documents persistent neglect, or misses them, which undermines the review chain itself. An attestation conflict between a review file and the component trace forces the reader to distrust one of them, and reviewers, auditors, and buyers resolve that doubt against the asset every time.
How the work runs
Inventory the files
Collect every airworthiness review file in the history and check each against its own index.
Register the items
Extract all open items and observations into one register across review cycles.
Chase dispositions
Locate closure evidence for each item in the later records or mark it outstanding.
Reconcile with the trace
Compare review attestations with the verified component trace and report conflicts.
What the buyer receives
- An integrity report per review file covering completeness, consistency, and open items
- A consolidated open-item register with disposition status for every recorded finding
- A conflict list where review attestations and the component trace diverge, with the stronger evidence identified
Who uses the output
- CAMO leads clearing inherited open items before the next review cycle
- Records leads aligning the component trace with the review history before either is released
- Auditors and counterparty reviewers who would otherwise find the conflicts themselves
How the work fits into the transaction or program
Review files are the only documents in the history where an independent party has already judged the records, so their agreement with the component trace carries weight beyond their content. This check runs last in the source review sequence, after the trace positions are verified, because a conflict can then be resolved on evidence rather than negotiated between two unverified documents.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
In the EASA system the airworthiness review is a defined Part-M and Part-CAMO process under Regulation 1321/2014, producing a certificate and a file the authority can inspect, which makes gaps in that file visible findings. FAA-managed history has no direct equivalent certificate, so records from annual or conformity-type reviews are weighed with 14 CFR 91.417 retention duties in mind, and ICAO Annex 8 gives the common frame when a history spans both systems.
Regulatory limits
This check evaluates records of past reviews; it is not itself an airworthiness review. It issues no airworthiness review certificate, does not extend or validate any certificate, and does not determine the aircraft's or component's present airworthiness; it reports on the documentary integrity of the review history.
What this review does not cover
- Performing or renewing an airworthiness review
- Physical survey activities associated with review recommendations
- Legal assessment of a reviewing organization's approvals or authority
Specific to this review
- CAMO transitions are where review follow-up lists die: the outgoing organization owns the items, the incoming one owns the aircraft, and the register between them transfers last or never.
- A finding that vanishes between review cycles is a stronger red flag than one that persists, because persistence at least shows the item was tracked.
- Review files gain evidentiary value with age: an old review that corroborates the trace is independent contemporaneous confirmation no reconstructed record can match.
- Reviewers quote figures as of the review date, so apparent conflicts with the trace sometimes dissolve once both are read at the same effective date, and the integrity report normalizes dates before declaring a conflict.
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 certificates were all issued, so the reviews passed. What is left to check?
Issuance shows the reviewer was satisfied on the review date, often subject to items expected to be closed afterward. The check verifies those closures happened and were documented, and that what the reviewer attested still agrees with the component's records as assembled today. Both can fail years after a certificate was validly issued.
Does a conflict between a review file and the trace mean one of them is wrong?
Frequently it means they speak as of different dates or from different source sets. The integrity report first normalizes effective dates, then weighs the underlying evidence for each position. Genuine conflicts do occur, and identifying which document the source evidence supports is exactly what a counterparty will expect to see resolved.
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.