Skip to content

GTF airworthiness review

Geared turbofan engine airworthiness-review records review

This review examines the airworthiness-review evidence held for a geared turbofan engine and confirms it stands on retrievable source. It is run for a lessor, operator, or asset manager checking a GTF asset before a transfer, a program change, or a review-certificate renewal. The work covers the review file, the continuing-airworthiness records the CAMO relied on, the open-finding log, and the status reports that sit behind the certificate. You get an exception list tied to each questionable line, a source map, and a closure plan scoped to the serial number in front of you.

When this review is needed

  • A GTF engine is changing hands and the buyer wants the review file confirmed before the certificate is relied on.
  • A CAMO is preparing to recommend a review-certificate renewal and needs the supporting evidence checked first.
  • An open-finding log has carried items across more than one review cycle and no one has cleared them.
  • The engine is moving between operators whose continuing-airworthiness records do not follow the same structure.

The problem

An airworthiness-review certificate is only as good as the file behind it, and on a GTF that file is assembled from status reports, CAMO summaries, and finding logs that were each produced at a different moment. When the review was signed against a summary rather than the underlying accomplishment record, the certificate looks settled while the evidence one layer down does not hold. The reader inherits that gap the moment the asset transfers.

What gets reviewed

  • The current airworthiness-review file and the certificate it supports
  • CAMO continuing-airworthiness records referenced during the last review
  • The open-finding log and the closure evidence claimed against each item
  • Continued-airworthiness status reports for time, cycles, and applicable directives
  • The review-recommendation trail and the data each recommendation rested on
  • Consistency between the review scope stated and the records actually held

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

  • Each line the review certificate rests on traces to a retrievable status report, not a summary alone
  • Open findings marked closed carry accomplishment evidence an auditor would accept on its face
  • The continuing-airworthiness records the CAMO cited match the effectivity for this engine serial number
  • Directive status carried into the review agrees with the accomplishment records on file
  • The review scope stated on the certificate matches the documents actually present in the file

Evidence normally required

  • The airworthiness-review file and the issued review certificate
  • The CAMO's continuing-airworthiness records for the engine
  • The open-finding or deferred-item log with claimed closures
  • Current time, cycle, and directive status reports
  • Any prior review recommendations and their supporting data

Common discrepancies

  • A review certificate signed against a status summary whose source report cannot be located
  • An open finding carried across two review cycles with no closure evidence attached
  • Directive status in the review file that disagrees with the accomplishment records
  • CAMO records cited by reference that were never delivered into the file

What is at stake

A review certificate resting on unverified status leaves the next holder unable to show what the last review actually examined. If a finding was carried but never closed, it resurfaces at the next cycle with the original evidence harder to reach and the responsible parties gone. That turns a clerical gap into a substantiation problem the owner pays to reconstruct.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Anchor to the certificate

Pull the current review file and list every status line the certificate depends on.

02

Trace to source

Follow each line down to the accomplishment record or status report that supports it.

03

Test the finding log

Check that closed findings carry evidence and carried items still have a path to close.

04

Map and sequence

Deliver the source map and a closure plan ordered by what the next event needs first.

What the buyer receives

  • An exception list tying each unsupported review line to its missing evidence
  • A source map linking the certificate back to the records that support it
  • A closure plan sequencing the open and carried findings for this serial number

Who uses the output

  • Asset managers confirming the review file before a GTF engine transfers
  • CAMO leads deciding whether the evidence supports a review-certificate recommendation
  • Records teams clearing carried findings before the next review cycle opens

How the work fits into the transaction or program

The review sits between the last airworthiness review and the next event that will test the engine's paperwork, whether a sale, a lease return, or a certificate renewal. Its exception list feeds the remediation that has to close before the CAMO can stand behind the file again.

Aircraft-specific considerations

A geared turbofan runs a high rate of module change, service-bulletin embodiment, and shop activity, so the airworthiness-review file carries more moving parts than a mature engine of the same thrust. The review pays attention to whether the last review actually reached the module and LLP evidence or stopped at the status layer above it, because that is where a GTF file most often looks complete while the trace underneath has broken.

Jurisdiction-specific considerations

An FAA-registered operator and an EASA CAMO structure the review evidence differently, so an engine that has crossed systems can carry two review histories that do not line up. The review notes where the file will need rework to satisfy the system the asset is heading into rather than the one it came from.

Regulatory limits

The review checks that the airworthiness-review evidence is present, consistent, and traceable. It does not conduct an airworthiness review, issue or renew a review certificate, or make any airworthiness determination on the engine.

What this review does not cover

  • Performing the airworthiness review or recommending the certificate
  • Return-to-service action on any component behind a finding
  • Any airworthiness determination on the engine

Specific to this review

  • On a GTF the review file most often looks complete at the status layer while the module and LLP trace one level down has quietly broken.
  • A finding carried across two review cycles usually costs more to close on the third pass because the original evidence has moved further out of reach.
  • A review certificate signed against a summary is defensible only if the summary's own source report can still be produced.
  • Directive status pulled into the review file at one date can drift out of agreement with the accomplishment records by the next cycle if the engine kept flying.
  • CAMO records cited by reference rather than filed are a frequent gap, because the reference survives the transfer but the underlying document does not.

Sources

Frequently asked questions

Does this replace the airworthiness review itself?

No. It checks that the evidence behind the review file is present and traceable so the CAMO can rely on it. The review and any certificate remain the CAMO's and the authority's to sign.

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.