Repair approval gaps
Missing repair-approval data in aircraft records
Missing repair-approval data is the case where a logbook entry records a repair and cites an approval, but the approved or acceptable data that approval rests on is not in the records. It matters most for lessors, airlines, and the receiving MRO during a purchase, a redelivery, or a re-lease. The review reads the repair entries, the cited approval references, the substantiation, and the release paperwork, then isolates which repairs have no retrievable basis. You receive a register of unsupported repairs, the data to be recovered for each, and a recommended path to close or reconstruct the basis.
When this review is needed
- Diligence has turned up repairs that cite an approval number with no document attached.
- A redelivery condition requires every repair to rest on approved or acceptable data and several entries cannot be matched to a file.
- An aircraft is moving registries and the receiving authority wants the approval basis for repairs done abroad.
- A repair was carried out under a field approval years ago and only the reference survives in the logbook.
The problem
The logbook entry looks complete because it names a drawing, a repair scheme, or an 8110-3 reference, so a status list reads the repair as closed. The document that reference points to is the part most likely to be absent, and without it the repair is a claim rather than a supported fact. Whoever holds the asset next inherits the duty to keep that repair under continued airworthiness while being unable to show what it was approved against.
What gets reviewed
- Every repair entry that cites an approval reference without an attached document
- The category of basis each repair claims, whether approved data, acceptable data, a field approval, or a design approval
- Cross-references from the entry to drawings, repair schemes, and engineering dispositions held elsewhere
- Release records that should accompany the repair at the time it was carried out
- Repairs done at a third-party shop or abroad whose approval path is unclear
- Recurring inspections or limitations the missing approval may have imposed on the repair
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 cited approval reference resolves to a document that is present and legible
- The document found matches the repair entry by date, location, and asset serial number
- A field-approved repair carries the approval form and the data the form approved, not the reference alone
- Acceptable-data repairs name the source they were accepted against and that source is identified
- Any recurring inspection or life limit the approval imposed is recorded and tracked
- Release paperwork for the repair names the correct configuration and approving organization
Evidence normally required
- Major repair and alteration records and any field approval forms
- Logbook entries citing the repair and its approval reference
- Drawings, repair schemes, and engineering dispositions held outside the logbooks
- Release certificates tied to each repair event
- Correspondence or work packages that may hold the original approved data
Common discrepancies
- A repair entry naming an 8110-3 or DOA reference whose document is nowhere in the file
- A field approval recorded by number with the approved data never filed alongside it
- A repair claiming acceptable data without identifying what data it was accepted against
- A recurring inspection imposed by the original approval that was never carried into tracking
- An overseas repair whose approval path cannot be reconstructed from what survives
What is at stake
An unsupported repair may have to be re-substantiated, re-approved, or in some cases removed before the asset can transfer or re-lease. On a structural repair near a load path, recovering the original approved data is far cheaper than reconstructing a substantiation from scratch, and surfacing the gap during diligence keeps the cost on the party that created it.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Isolate the unsupported repairs
Pull every repair entry that cites an approval reference and flag those with no document attached or retrievable.
Search for the original basis
Trace each reference into drawings, repair schemes, field approval files, and work packages held outside the logbooks.
Classify and register
Record each repair by the basis it claims and whether the original data was recovered, partial, or absent.
Plan recovery or reconstruction
Recommend who can supply the missing document or what reconstruction is required, and the order to work them in.
What the buyer receives
- A register of repairs whose approval data is missing, each with the basis it claims
- A per-repair recovery list naming the document to be located or the data to be reconstructed
- A recommended closure path identifying who can supply or re-create the basis
Who uses the output
- Records teams chasing the original approval documents before a deal closes
- Continuing-airworthiness staff who must carry recurring inspections the approval imposed
- Asset and acquisition teams pricing the cost of recovering or reconstructing each basis
How the work fits into the transaction or program
This sits inside a repair-history review and a wider records audit, narrowing the work to the specific repairs whose approval cannot be produced. It feeds the discrepancy register and the data room, and its recovery list drives the requests sent to the outgoing operator while there is still leverage to close them.
Aircraft-specific considerations
Which missing approvals are decisive depends on the structural repair manual and the principal structural element list for the type. A repair at a fatigue-critical location with no retrievable basis carries more weight than a minor skin repair, so the recovery effort is prioritized against the structural configuration of the specific aircraft.
Jurisdiction-specific considerations
A repair approved under one authority does not arrive approved under another. A field approval or a design organization approval has to be evaluated against what the receiving registry will accept, and a repair done abroad may need its basis reconstructed in a form the receiving authority recognizes before the aircraft can cross.
Regulatory limits
The review identifies which repairs lack a retrievable approval basis and what is needed to close each one. It does not re-approve a repair, issue an airworthiness determination, perform structural inspection, or guarantee that any authority will accept a reconstructed basis.
What this review does not cover
- Engineering re-substantiation or re-approval of a repair
- Physical inspection of the repair on the aircraft
- Any airworthiness determination or regulatory approval
Specific to this review
- The approval reference in a logbook entry is the most reliable thing in the record; the document it points to is the most frequently missing.
- Recovering original approved data is usually cheaper than building a fresh substantiation, so the first response is a recovery search rather than re-engineering.
- Approved data and acceptable data are tracked as separate gaps here, because the route to close each one differs.
- An approval that imposed a recurring inspection can leave a hidden tracking gap even when the repair document is later found.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
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
Does a missing approval document mean the repair is unairworthy?
No. It means the records do not yet support the repair. The review separates a documentation gap from an engineering problem and recommends recovering or reconstructing the basis so the repair stands behind the asset.
Can the original approved data usually be recovered?
Often, yes. Field approval files, design organization records, and the repair vendor's package frequently still hold the data even when the aircraft file does not, which is why the first step is a structured recovery search.
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.
Walk through your situation with an engineer who has done this work.