Skip to content

Airworthiness review

LEAP engine airworthiness-review evidence records review

This review looks behind an airworthiness review certificate on a LEAP engine to confirm the CAMO evidence supports it. It works through the airworthiness review file, the certificate and its recommendation basis, the open-finding log, and the continued-airworthiness status reports, testing whether each rests on a source record. It is run for a party relying on the certificate to price, transfer, or continue managing the engine. You receive a supported exception list against the review evidence, a source map, and a closure plan for findings that are still open or thinly documented.

When this review is needed

  • A buyer is pricing a LEAP engine on the strength of a recent airworthiness review and wants the underlying file confirmed.
  • The review certificate is near expiry and the open findings behind it have to be resolved before renewal.
  • A CAMO handover is underway and the incoming manager needs to inherit a verified review file, not just a certificate.
  • Continued-airworthiness status reports feed a transaction and their basis has not been independently checked.

The problem

An airworthiness review certificate is a conclusion, and a conclusion is only as sound as the file under it. The review file for a LEAP engine may cite status reports and finding closures that themselves lean on records held elsewhere, so a certificate can read clean while a finding it depended on was closed without accomplishment evidence. The reader trusting the certificate rarely sees whether its recommendation basis was built or assumed.

What gets reviewed

  • The airworthiness review certificate and the recommendation that supports it
  • The open-finding log with each finding's current state and closure evidence
  • CAMO records that fed the review reconciled to their source documents
  • Continued-airworthiness status reports checked for currency and support
  • Findings closed during the review traced to the record that resolved them
  • The review's scope confirmed against the engine's actual status coverage

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

  • The review certificate's recommendation basis reconciles to the status reports it cites
  • Each finding shown as closed carries a record that documents the resolution
  • Open findings on the log are tracked to a current state, not left dormant
  • Continued-airworthiness status reports reflect the engine's present position, not a stale snapshot
  • The review's declared scope covers the status areas a buyer or renewal would test

Evidence normally required

  • The airworthiness review file and the review certificate
  • The open-finding log and any finding-closure records
  • CAMO status reports and continued-airworthiness summaries relied on by the review
  • Source records behind the cited status: AD, LLP, configuration, and shop evidence
  • Any prior review recommendations or authority correspondence

Common discrepancies

  • A finding recorded as closed with no resolution record behind the closure
  • A recommendation basis that cites a status report the file does not contain
  • A continued-airworthiness summary that lags the engine's current AD or LLP position
  • An open finding left dormant on the log with no current tracking state

What is at stake

Relying on a certificate whose file does not hold up means inheriting open findings dressed as closed, or a recommendation basis that cannot be reproduced. That weakens the price a buyer should pay, complicates the next review, and puts the CAMO taking over in the position of defending conclusions it cannot trace, usually right as a renewal or transaction forces the question.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Read the certificate basis

Pull the review certificate and the recommendation basis it rests on for the engine.

02

Test the findings

Trace each closed finding to its resolution record and confirm open findings carry a current state.

03

Reconcile the status reports

Check the continued-airworthiness summaries against the AD, LLP, and configuration source records.

04

Flag the exceptions

List thinly supported conclusions and plan the closures the next review cycle will require.

What the buyer receives

  • A supported exception list against the airworthiness review evidence
  • A source map linking review conclusions to the records beneath them
  • A closure plan for findings still open or documented too thinly to rely on

Who uses the output

  • Asset managers pricing an engine on the strength of its review certificate
  • Incoming CAMO managers inheriting the review file at a handover
  • Records teams preparing the file to survive a renewal or a buyer's check

How the work fits into the transaction or program

The airworthiness review sits on top of the engine's status records and feeds the certificate a transaction or renewal relies on. Confirming the evidence beneath the certificate means the conclusion can be defended, and its exception list drives the finding closures that have to clear before the next review cycle.

Aircraft-specific considerations

A LEAP engine's relatively short service life means its review file leans heavily on current configuration, shop-visit release evidence, and LLP status rather than a long maintenance history. The review confirms those current-status pillars are documented to review grade, because on a young engine a thinly supported finding closure stands out more than it would on an asset with decades of accumulated paper.

Jurisdiction-specific considerations

The airworthiness review concept and its certificate sit under the EASA continuing-airworthiness framework, while an FAA-registered engine reaches an equivalent conclusion through different recordkeeping. When an engine has moved between the two, the review notes where a finding or status report was framed under one system and now has to satisfy the other's expectations.

Regulatory limits

The review confirms the evidence behind the airworthiness review is present and consistent. It does not issue or extend an airworthiness review certificate, act as the CAMO of record, or make an airworthiness determination on the engine.

What this review does not cover

Specific to this review

  • A review certificate can be technically valid while a finding it relied on was closed without the accomplishment record that would prove the resolution.
  • The recommendation basis is where a review file most often thins out, because it summarizes status that lives in reports the file may only reference rather than contain.
  • On a young engine, a dormant open finding is more revealing than on an older one, since there is less history to explain why it was never worked.

Sources

Frequently asked questions

We already hold a valid review certificate. What does checking the file add?

The certificate states a conclusion; the file is what defends it. If a finding was closed without a resolution record, or the recommendation cites a report the file lacks, that surfaces at renewal or in a buyer's diligence. The review confirms the conclusion can be traced before someone else tests it.

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.