Airworthiness review records inside the engine-module file

When this review is needed

• A records transfer is approaching and the receiving CAMO will read the airworthiness review file line by line.
• The last review carried open items and nobody can point to where their dispositions were filed.
• A shop visit changed the module configuration after the review was completed, and the file must still tell one coherent story.
• A lessor is preparing an engine for the next placement and wants the review evidence proven rather than assumed.

The problem

Airworthiness reviews get done under their own calendar, while the engine records file grows under the maintenance calendar. Between the two, an item raised at review time gets dispositioned in a work order, a shop report, or an email thread, and the review file is never updated to point at the evidence. Months later the file says an item was open, the engine says it was fixed, and the document connecting the two is somewhere in a package nobody has indexed.

What gets reviewed

• Each item raised in the airworthiness review traced to a dispositioning document in the engine-module file
• Review-period status claims checked against LLP status pages and disk sheets current at the review date
• Shop findings from visits inside the review period reconciled with what the review recorded
• Installation history verified so the review's subject configuration matches the modules actually fitted
• Test-cell evidence located for any performance or condition statement the review relied on
• Open items from prior reviews followed forward to a filed closure or flagged as still open

What gets validated

• Every open item in the review file has either a dispositioning document or an entry on the exception list
• Status figures quoted at review time match the LLP pages and disk sheets that were current on that date
• The module serials the review describes are the serials the installation history shows fitted
• Dispositions cite documents that exist in the file, at the location the index says they are
• No review item was closed by reference to a document that itself references nothing

Evidence normally required

• The airworthiness review file with its open-item and disposition records
• The engine-module records file including build sheets and shop-visit packages
• LLP status pages and disk sheets covering the review period
• Installation and removal history for the engine and its modules
• Test-cell records referenced by or relevant to the review

Common discrepancies

• A review item dispositioned in a work order that was archived with the shop package instead of the review file
• A status figure at review time that disagrees with the disk sheet by one shop visit's worth of cycles
• A prior review's open item that simply stopped appearing without any filed closure
• A disposition that cites a document reference no longer valid after the file was reindexed

What is at stake

When the receiving organization finds a review item without a filed disposition, it treats the item as open. That reading is conservative and expensive: it can trigger repeat inspections, hold a transfer, or push a due date forward on the assumption the work was never done. Every such episode also erodes confidence in the rest of the file, inviting deeper sampling than the transfer schedule can absorb.

How the work runs

What the buyer receives

• An exception list of review items whose disposition the source file cannot evidence
• A mapping of each supported item to the document and file location that carries it
• A recovery note per exception naming the likely holder of the missing evidence

Who uses the output

• CAMO leads answering the receiving organization's questions during a transfer
• Engine records staff filing the recovered dispositions where the next reader will find them
• Lessor technical managers deciding whether the file is placement-ready

How the work fits into the transaction or program

This check runs after the airworthiness review itself and before anyone outside the organization reads the file. It complements a redelivery or transfer audit by going one layer deeper on a single evidence type, and its exception list feeds directly into records-gap remediation if closures have to be recovered from shops or prior operators.

Jurisdiction-specific considerations

Under EASA, Part-CAMO and Part-M put the airworthiness review and its supporting records inside a defined organizational system, so the check reads the file against that system's own cross-references. FAA-managed engines lack a direct equivalent of the airworthiness review certificate, and the records that stand in for it under 14 CFR 91.417 are looser in form. Files that have crossed between the two systems tend to carry both conventions at once, which is precisely where dispositions go missing.

Regulatory limits

The check verifies whether documents support the review records. It does not perform an airworthiness review, does not issue or extend any certificate, and does not determine the airworthiness of the engine or its modules. Findings are documentary exceptions for the responsible organization to resolve within its own approvals.

What this review does not cover

• Conducting or renewing the airworthiness review itself
• Assessment of the CAMO's procedures or organizational approval
• Borescope, hardware, or any physical condition assessment

Specific to this review

• Review items are usually dispositioned in maintenance paperwork, so the closure evidence lands in the shop package by default and reaches the review file only if someone copies it across.
• A reindexing of the records file silently breaks dispositions that cite page or binder references instead of document identities.
• Receiving CAMOs sample prior reviews first because an unsupported open item is the cheapest defect for them to find and the most expensive for the sender to argue.
• The gap between the review calendar and the shop-visit calendar means the freshest configuration change is the most likely one to be missing from the review's story.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits