Repair-approval records for an operator AOC transfer

When this review is needed

• An aircraft is changing operator certificates and the receiving side will examine every structural repair and major alteration.
• A repair was embodied years ago and the approved data it was flown under is no longer with the record.
• A repair introduces recurring inspections and those tasks have to appear in the program the aircraft is bridging to.
• The transfer crosses authorities and a repair approved under one regime needs a basis the receiving side recognizes.

The problem

Repairs are the records that age worst. The work gets done, the aircraft returns to service, and over the years the approved data drifts away from the entry that describes the repair. At an operator transfer the receiving side does not accept the presence of a repair as proof it was approved. It asks for the data the repair was carried out against and the return-to-service that closed it, and structural repairs without that pairing are exactly what surface late.

What gets reviewed

• Each repair and major alteration matched to the approved data it was carried out against
• Damage reports and dispositions reconciled with the repair actually embodied
• Return-to-service entries confirmed for each repair on the airframe and components
• Recurring inspections introduced by repairs traced into the maintenance program
• Alterations checked for the approval and any effect on type design configuration
• The repair map ordered so the receiving side can review structural repairs first

What gets validated

• Every repair on the map has approved data identified and on file
• Each repair has a return-to-service entry consistent with the work described
• Repairs that impose recurring inspections have those tasks reflected in the program
• Alterations carry the approval basis and any configuration change they introduced
• Damage dispositions match the repair embodied rather than an earlier proposed scheme

Evidence normally required

• The repair map or structural repair and alteration index for the aircraft
• Approved data packages, repair drawings, and substantiation for each repair
• Return-to-service entries and work packages closing the repairs
• The maintenance program tasks carrying repair-driven recurring inspections
• Contact points at the organizations that engineered or embodied the repairs

Common discrepancies

• A structural repair on the airframe with no approved data left on file
• A repair introducing recurring inspections that never reached the maintenance program
• A return-to-service entry that does not match the repair the damage report describes
• An alteration whose approval basis cannot be identified from the records held

What is at stake

A repair the receiving operator cannot tie to approved data becomes an open question against the airframe, and an open structural repair can stall acceptance or force a re-evaluation of the affected area. Where a repair carries recurring inspections, a missing basis also puts the next-due tasks in doubt, which can pull the aircraft into an inspection the program did not plan for. Found in transfer week, none of this has schedule room to absorb it.

How the work runs

What the buyer receives

• A repair evidence map tying each repair to its approved data and return to service
• A gap list of repairs missing approval or continued-airworthiness data, ranked by structural weight
• A document request set for the substantiation and drawings the receiving side will require

Who uses the output

• Asset managers weighing the exposure of any repair without a filed basis
• Receiving-operator engineering staff reviewing repairs for acceptance
• Records leads assembling repair substantiation before the transfer window

How the work fits into the transaction or program

This review precedes the receiving operator's examination of the airframe's repair history. It substantiates the repairs most likely to draw questions and routes their recurring inspections into the bridging program, so the receiving side inherits a repair map that stands on its approved data.

Jurisdiction-specific considerations

A repair engineered and approved under FAA rules may need a basis the receiving side accepts when the aircraft moves to an EASA operator, or the reverse. The review identifies repairs whose approval crosses the authority line and flags where a recognized basis has to be confirmed, so a repair that was compliant at embodiment is not first challenged at acceptance.

Regulatory limits

The review reports what the repair records and their approved data support. It does not approve any repair or alteration, issue a return to service, evaluate the physical condition of a repaired area, and does not replace the receiving operator's or authority's acceptance of the repairs.

What this review does not cover

• Engineering or approving any repair or alteration
• Physical inspection of repaired structure
• Issuing a return-to-service for any repair

Specific to this review

• The presence of a repair proves only that work was done; acceptance needs the approved data and the return to service that closed it.
• Repairs that carry recurring inspections are the ones a missing basis hurts most, because the doubt spreads from the record into the next-due program tasks.
• Approved data drifts away from the repair entry over years of operation, which is why old structural repairs are where the transfer questions concentrate.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits