Repair approval data review for MRO teams supporting an aircraft acquisition

When this review is needed

• A customer buying an aircraft has asked its MRO partner to read the repair file before terms are set.
• The shop will bid the aircraft's first heavy check and needs the repair population understood before pricing the workscope.
• The repair map in the data room disagrees on its face with the dent-and-buckle chart beside it.
• The candidate carries composite or fuselage repairs whose data packages will govern how adjacent work is done for years.

The problem

Repair records written for a past return-to-service read differently when the question becomes future maintenance. A shop inheriting an aircraft needs each repair's data package to plan inspections around it, disposition new damage near it, and answer the structures questions a heavy check raises. Data rooms present repair files as history, and history with gaps becomes tomorrow's engineering delay, discovered with the aircraft open and the check clock running.

What gets reviewed

• A census of repairs and alterations built from the repair map, chart, damage reports, and logbook entries
• Approved data located and attached for each repair: SRM basis, engineering package, or authority-approved deviation
• Alteration records checked for STC data, embodiment evidence, and ICA carried into the program
• Repair locations assessed for interaction with upcoming structural inspections and the planned heavy-check workscope
• Return-to-service documentation verified for each repair event
• Data recoverability judged per item, with the holding organization identified

What gets validated

• The repair census accounts for every damage report, with unrepaired or accepted damage explicitly dispositioned
• Cited SRM repairs fall within the referenced section's limits at the revision in force when performed
• Engineering-approved repairs carry the actual data package, and a reference number alone is logged as a gap
• Alterations feed their ICA into the maintenance program rather than existing only as embodiment records
• Repairs in zones touched by the planned heavy-check workscope are flagged for data completeness first

Evidence normally required

• The repair map, dent-and-buckle chart, and structural file from the data room
• Damage reports, dispositions, and engineering correspondence available from the seller
• The planned or bid heavy-check workscope, where the shop is pricing one
• Logbooks and work orders covering repair return-to-service entries
• STC and alteration documentation for embodied modifications

Common discrepancies

• Repairs referenced by engineering-order number where the order itself never made it into the records
• A repair map current to the previous heavy check with several years of line-station repairs unmapped
• Accepted damage carried without the periodic inspection its acceptance was conditioned on
• An STC removed mid-life whose de-modification left orphaned ICA tasks in the program

What is at stake

Undocumented repairs found during a heavy check stop work at that zone until data is recovered or recreated, and engineering turnaround mid-check is measured in weeks. For the buyer that means unplanned downtime and cost; for the shop, a schedule blown by a problem visible in the data room months earlier. Repairs lacking substantiation can also cap what alterations or subsequent repairs the location will support, narrowing options permanently.

How the work runs

What the buyer receives

• A repair census reconciling the map, the chart, and the damage history into one authoritative list
• A data-gap register with a recoverability judgment and holding organization per item
• A heavy-check impact note translating documentation gaps into workscope and turnaround risk

Who uses the output

• The buyer's deal team, which prices documentation gaps alongside the physical survey
• MRO program management planning the induction and first-check workscope
• Quality and records control, who will field structures questions once the aircraft is in the hangar

How the work fits into the transaction or program

This review connects transaction diligence to maintenance planning. It runs while the seller can still supply data, borrows findings from the buyer's other records workstreams, and its census becomes the structures baseline the shop works from at induction, first check, and every disposition after.

Jurisdiction-specific considerations

Whether repair data is approved, or merely acceptable, follows the aircraft's registry, and FAA and EASA frameworks split that line differently. An aircraft changing registry at purchase may carry repairs whose basis satisfied the old authority and needs re-examination under the new one, and the review marks those items before they surface as heavy-check questions.

Regulatory limits

The review evaluates the documentation trail. It does not perform structural engineering, approve or generate repair data, or determine that any repair or the aircraft is airworthy.

What this review does not cover

• NDT or physical inspection of repair sites
• Creating substantiation data for undocumented repairs
• Commercial negotiation of the purchase on the buyer's behalf

Specific to this review

• A repair file's usefulness to a shop is set by findability as much as completeness: fifty well-substantiated repairs indexed by zone beat the same fifty scattered through chronological logbook entries.
• Line-station repairs from the years between heavy checks are the most commonly unmapped population, because map updates cluster at check exit and drift in between.
• Accepted damage is a live obligation, and its conditional inspections are the item most often lost when an aircraft changes hands, since they lived in the previous operator's tracking rather than the structural file.
• Recovering an engineering package costs little while the authoring organization retains it and approaches impossible after retention periods lapse, so the recoverability judgment drives the request sequence more than repair size does.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits