Repair approval data
Geared turbofan engine repair approval data records review
This review confirms that the repairs and alterations recorded on a geared turbofan rest on approved data. It works through the damage reports, the disposition for each repair, the approved data that authorizes it, and the return-to-service entries that close it, testing whether the approval basis exists rather than is assumed. It is run for a party whose valuation or transfer depends on repairs being substantiated. You receive a supported repair exception list, a source map from each repair to its approved data, and a closure plan for repairs whose basis cannot be shown.
When this review is needed
- A geared turbofan is being valued and its repair history has to be confirmed as resting on approved data.
- A shop visit dispositioned damage and the approval basis behind each repair has not been checked.
- A buyer requires every non-standard repair mapped to its approved data before pricing.
- A repair disposition is recorded without the return-to-service entry that should close it.
The problem
A repair is only as durable as the approved data behind it. On a geared turbofan, damage gets dispositioned across shops, and a repair map can carry entries where the disposition is recorded but the approved data that authorizes it was never captured, or where a return-to-service entry closes a repair whose basis is a shop assumption rather than an approved document. The engine reads as repaired and released until each repair is matched to the data that justifies it.
What gets reviewed
- Each recorded repair matched to the approved data that authorizes it
- Damage reports reconciled to the disposition taken for each finding
- Return-to-service entries confirmed to close a repair with a documented basis
- Alterations checked for approval data appropriate to the change and the engine
- Non-standard repairs mapped to their specific approval source
- Repairs whose approval basis cannot be shown identified explicitly
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 repair carries approved data appropriate to the damage and the part repaired
- A damage report ties to the disposition and the repair that resolved it
- The return-to-service entry follows from a repair with a documented approval basis
- An alteration carries approval data suited to the change rather than a routine sign-off
- A repair with no traceable approved data is flagged against its disposition
Evidence normally required
- The repair and alteration records and the repair map
- Damage reports and the disposition for each finding
- Approved data references authorizing the repairs
- Return-to-service entries closing the repairs
- Shop reports where the repairs were performed
Common discrepancies
- A repair disposition recorded with no approved data reference behind it
- A return-to-service entry closing a repair whose basis is a shop assumption
- An alteration signed off as routine that needed approval data for the change
- A damage report with no clear link to the repair that resolved it
What is at stake
A repair without traceable approved data may have to be re-substantiated or reworked, which on an engine part is expensive and slow, and a buyer who cannot see the basis will price the risk down or refuse the part. A return-to-service entry that closes a repair with no approval behind it weakens every status built on top of it, and the correction usually lands under the pressure of a transaction.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the repair map
List the recorded repairs and alterations with their damage reports and dispositions.
Match to approved data
Confirm each repair references approval data appropriate to the damage and the part.
Close the loop
Verify the return-to-service entry follows from a repair with a documented basis.
Flag the unsupported
Identify repairs with no traceable approval and plan the re-substantiation or recovery.
What the buyer receives
- A supported repair exception list against the approved data
- A source map from each repair to its approval basis
- A closure plan for repairs whose basis cannot be shown
Who uses the output
- Asset managers pricing the repair exposure on a geared turbofan
- Engineering deciding how to treat a repair with no traceable approval
- Records teams recovering approved-data references before a transfer
How the work fits into the transaction or program
Repair approval sits alongside the release and configuration records as the evidence that a part was properly restored, not merely refitted. Confirming each repair's basis means the engine's condition can be defended at valuation, and the exception list drives the re-substantiation or data recovery that has to close before a buyer requiring approved data will accept the repair history.
Aircraft-specific considerations
A geared turbofan's high rate of shop activity produces a dense repair history dispositioned across multiple facilities, so the approved-data references are the records most likely to be scattered or assumed. The review maps each non-standard repair to its specific approval source, because on this engine family the gap is rarely the repair itself but the approved data that was applied in the shop and never filed with the engine records.
Jurisdiction-specific considerations
What counts as approved data differs between the FAA and EASA systems, and a repair authorized under one may need a matching basis to be relied on under the other. For an engine that has been repaired across the boundary, the review confirms the approval basis holds under the authority governing the current registration and flags repairs whose data will need restating for the receiving system.
Regulatory limits
The review reports whether recorded repairs and alterations rest on traceable approved data. It does not approve a repair, develop or approve repair data, or make an airworthiness determination on the engine or its parts.
What this review does not cover
- Performing, reworking, or signing off any repair
- Developing or approving repair or alteration data
- Any airworthiness determination on the engine
Specific to this review
- The common gap in a repair file is not the repair but its approved data, which was applied in the shop and never filed with the engine records.
- A return-to-service entry can close a repair whose basis is a shop assumption, so the entry proves the work happened without proving it was authorized.
- An alteration signed off as routine maintenance is easy to miss, because it needed approval data the routine sign-off never captured.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The repairs were released to service by the shop. Why check the approved data?
A return-to-service entry proves the work was done, not that it was authorized by approved data. A repair whose basis is a shop assumption may have to be re-substantiated or reworked, and a buyer who requires the approval source will discount the part. The review confirms each repair traces to data that justifies 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.