GTF maintenance program
Geared turbofan engine maintenance-program records review
This review confirms that the maintenance program recorded against a geared turbofan engine matches the approved program the operator is actually working to. It is run when a team is buying, transferring, or holding a GTF asset and the program status has to be trusted before the next milestone. It checks approved program revisions, task escalations, bridging analyses, and the source documents each interval traces to. You receive an exception list, a map from each program line to its source, and a closure plan scoped to the serial number under review.
When this review is needed
- A GTF engine is changing hands and the buyer needs the working program confirmed before pricing.
- The operator has escalated task intervals and the escalation basis has to be shown in the records.
- A program revision was issued and no one has verified the fleet is tracking to the current one.
- An engine is bridging from one operator's program to another and the intervals must reconcile.
The problem
The geared turbofan is a high-change powerplant, so its program has moved through several revisions in a short service life. Task escalations, fleet campaigns, and bridging analyses accumulate faster than the status list is updated, and the interval a tracking system shows may reflect a program revision the engine was never actually moved onto. The record that proves which program applies is often buried in a revision transmittal nobody kept.
What gets reviewed
- Approved program revision in force for the serial number against the revision the records track to
- Task escalations with the analysis and approval that permit the extended interval
- Bridging analyses where the engine moved between operator programs
- Source-document references behind each program task and interval
- Program status reconciled to the utilization and maintenance history on file
- Open program items carried as tracked exceptions with their basis stated
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 program revision the records track to is the one approved for this serial number, not a superseded transmittal
- Each escalated interval traces to an escalation analysis and its approval, not to a status-list edit
- A bridging analysis exists where task history crossed between two operator programs
- Program tasks reference the source instruction they derive from, with the correct revision
- Recorded program status agrees with the utilization figures in the logbooks and status lists
Evidence normally required
- The current approved maintenance program and its revision history for the serial number
- Task escalation analyses and their approvals
- Any bridging analysis from a prior operator program
- The program status list or tracking export for the engine
- Utilization and maintenance history to reconcile intervals against
Common discrepancies
- An interval tracked to a program revision the engine was never formally moved onto
- An escalated task with no escalation analysis behind the extended interval
- A bridging analysis missing where the engine changed operator programs
- A program task referencing a superseded revision of its source instruction
What is at stake
An engine tracked to the wrong program revision can carry a task that is overdue against the applicable interval or one that was escalated without the analysis to support it. Either finding surfaces at induction or a shop visit, when the cost of proving the correct basis is highest and the schedule has already been built on the wrong one.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the applicable revision
Establish which approved program revision governs this serial number and pull its transmittal history.
Test the intervals
Check each task interval and escalation against its analysis and approval, module by module.
Reconcile the bridge
Confirm any move between operator programs carries a bridging analysis and the receiving approval.
List and sequence
Record the unsupported program lines and order the evidence needed to close them.
What the buyer receives
- An exception list of program lines whose basis or revision cannot be supported
- A source map tying each program task and interval to the document behind it
- A closure plan sequencing the missing program evidence for the serial number
Who uses the output
- Asset managers pricing a GTF engine against the program it is actually maintained to
- Continuing-airworthiness teams confirming the engine tracks the approved revision
- Records teams closing program-evidence gaps before induction or shop visit
How the work fits into the transaction or program
The program review sets the interval framework every other GTF record is measured against. Once the applicable revision and its escalations are confirmed, task-card completeness, non-routine closure, and shop evidence can be read against a program that is known to be the right one rather than one assumed from a tracking export.
Aircraft-specific considerations
Geared turbofan programs revise often because the type is young and fleet experience is still reshaping intervals. Module-level task structure and the gearbox-driven inspection set mean an escalation on one module does not carry to another, so the review confirms the revision and escalation basis module by module rather than at the engine level.
Jurisdiction-specific considerations
An FAA-tracked GTF program and an EASA continuing-airworthiness program express intervals and approvals differently, so an engine moving between the two systems needs the bridging analysis and the receiving approval both present in the records. The review notes where a program line was approved under one system and has no equivalent basis in the other.
Regulatory limits
The review reads the program records and reconciles them to source. It does not approve a maintenance program, authorize an interval escalation, or make an airworthiness determination on the engine.
What this review does not cover
- Authoring or approving the maintenance program or any escalation
- Performing the tasks the program calls for
- Any airworthiness determination on the engine or its modules
Specific to this review
- The document that proves which program revision applies is usually a revision transmittal, which is the item operators most often fail to retain.
- An escalation approved for one engine module does not transfer to another, so escalation evidence has to be checked per module.
- On a young high-change type, the gap between the revision a tracking system shows and the one the engine was moved onto is where program findings concentrate.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
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 aircraft operation, including maintenance program and recordkeeping expectations.
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
How is this different from a task-card review of the same engine?
This review works at the program level: which revision applies, whether intervals were legitimately escalated, and how a bridge between operator programs was justified. A task-card review checks that the individual accomplishments under that program were signed off with the right data. The program review sets the framework the task-card review then measures against.
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.