Repair and alteration records reviewed for a registry change

When this review is needed

• The repair map includes entries substantiated by field approvals or designee-approved data and the aircraft is leaving that system.
• Major alterations such as interior or avionics changes were embodied under STCs whose standing on the destination registry is unconfirmed.
• The importing authority's checklist asks for repair data by category and the package holds it as an undifferentiated pile.
• A prior transition accepted repairs without their data, and this move is where the gap surfaces.

The problem

A repair's approval basis is invisible on the airframe and nearly invisible in the records: a work order references data, the data references an approval, and the approval lives in a designee's file or an authority archive from fifteen years ago. Domestic operation never tests the chain. A registry change reads every link under the destination system's rules and asks for categories the exporting records were never organized around.

What gets reviewed

• The repair map reconciled against the package's work orders, damage records, and heavy-check findings
• Substantiating data located for each mapped repair: the drawing, analysis, or manual reference it was embodied under
• Approval bases classified by instrument: manual limits, designee approvals, field approvals, STCs, and design organization approvals
• Transferability of each basis assessed under the importing registry's acceptance framework
• Major and minor classifications reviewed where the two systems draw the line differently
• Alterations checked for their supplement documentation, including flight manual supplements and ICA where applicable

What gets validated

• Each map entry names its substantiating data, and that data is physically in the package rather than referenced into a void
• Cited approvals are complete instruments: signed, dated, applicable to this serial number, and covering the repair as embodied
• STC-based alterations include evidence of applicability and, where the destination requires it, validation or acceptance on that registry
• Repairs classified minor under the exporting system are re-examined where the importing system would classify them major
• ICA and flight manual supplements for alterations are present at revisions consistent with the installed configuration

Evidence normally required

• The repair map or damage chart and the alteration list
• Substantiating data packages: drawings, analyses, and approval documents
• STC certificates and their supplements for embodied alterations
• The importing authority's requirements for repair and alteration data
• Work orders and check packages that embodied the mapped items

Common discrepancies

• A structural repair embodied under a designee approval whose signed form never entered the operator's records
• An STC valid on the exporting registry with no validation history on the importing one
• Alterations present on the aircraft, visible in photographs and wiring, that appear on no list in the package
• Substantiating data held as a reference number to an engineering system no current party can access

What is at stake

A repair whose basis cannot be shown gets treated as unapproved by the importing side, and the cure options, re-substantiation by a design organization or removal and re-repair, are both engineering projects running on transaction timelines. Alterations without transferable approvals can block the delivery configuration itself, forcing removal of equipment the buyer expected to keep.

How the work runs

What the buyer receives

• An entry-by-entry disposition of the repair map and alteration list for the registry change
• A transferability assessment identifying which approval bases need importing-side acceptance and by what route
• An exception register for the authority response, with a proposed recovery owner for each missing data package

Who uses the output

• Transition leads scoping what must be cured before the import proceeds
• Design and engineering organizations engaged to re-substantiate or validate specific items
• The receiving operator's CAMO establishing the repair and alteration baseline it will manage

How the work fits into the transaction or program

This review closes the loop the structural and release-document reviews open: they establish what was done and released, and this one establishes whether the design basis behind it survives the move. Its dispositions drive the engineering workstream of the transition, which has the longest lead time of any cure and therefore needs the earliest start.

Jurisdiction-specific considerations

The FAA and EASA systems approve repair data through different instruments, and bilateral agreements define which approvals cross automatically, which need validation, and which do not travel at all. A field approval, for example, is an FAA-domestic instrument, so an EASA-bound aircraft carrying repairs on that basis needs each one read individually. The review applies the destination framework, since that is the standard the aircraft must meet on arrival.

Regulatory limits

The review does not approve repair data, reclassify repairs, validate STCs, or make findings on behalf of any authority. It reports the documentary condition and transferability question for each entry; the engineering and regulatory resolutions belong to approved organizations and the authorities.

What this review does not cover

• Engineering re-substantiation or new repair design
• STC validation applications to the importing authority
• Physical survey of the airframe to find undocumented repairs, though findings from such surveys are incorporated when supplied

Specific to this review

• Approval-basis problems concentrate in the middle of an aircraft's life: early repairs tend to sit inside manual limits and recent ones inside current processes, while mid-life entries carry retired instruments and dissolved organizations.
• Bilateral acceptance of repair data has changed over time, so the date a repair was approved can matter as much as the instrument that approved it.
• Cabin and connectivity alterations generate the most undocumented entries, because they were driven by commercial teams on lease timelines rather than through the operator's engineering process.
• Re-substantiating one representative repair sometimes clears a family of similar entries, so grouping findings by repair type before engaging engineering cuts the cure cost materially.
• Undocumented alterations surface faster by comparing photographs and wiring diagrams against the alteration list than by reading the list itself, because the list only knows what was reported.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits