Airbus A220 family structural repair records review

When this review is needed

• An A220 is being acquired and the buyer needs a located, data-backed record of every structural repair.
• A repair carries a recurring inspection and the operator must confirm it is captured in the program.
• A redelivery requires a complete structural repair map rather than scattered damage reports.
• Repairs done under different operators need consolidating into one supported history for the airframe.

The problem

Structural repairs accumulate one event at a time, each with its own damage report, its own approval basis, and sometimes its own recurring inspection, and they rarely arrive as a single map. A dent-and-blend done during a line check may sit in a work order that never made it into a repair register, and a repair approved under one operator's arrangement may reach the next owner without the data that substantiates it. The airframe carries repairs the records cannot fully locate or justify.

What gets reviewed

• Every structural repair placed on the airframe with its zone and location
• Each repair matched to its approval basis, whether SRM data or a specific approval
• Recurring inspections introduced by a repair checked against the maintenance program
• Damage reports reconciled to the repairs that closed them
• Repairs done under prior operators consolidated into one supported repair map
• Repairs without located data or an approval basis flagged for reconstruction

What gets validated

• Each repair has an approval basis, whether SRM referenced or a discrete approval document
• Every repair is located on the airframe by zone rather than described in the abstract
• Recurring inspections from repairs are carried into the maintenance program
• Damage reports each tie to the repair record that resolved them
• The consolidated repair map accounts for repairs recorded across all prior operators

Evidence normally required

• Structural repair records and any existing repair register or map
• Damage reports and the work orders that closed them
• The approval basis for each repair, including SRM references or discrete approvals
• The maintenance program tasks covering recurring inspections from repairs
• Logbook entries referencing structural work on the airframe

Common discrepancies

• A repair recorded without the approved data that substantiates it
• A repair carrying a recurring inspection that never entered the maintenance program
• A damage report with no repair record showing how it was resolved
• Repairs described in work orders but absent from any consolidated repair map

What is at stake

A repair without its approval data or its location on the airframe is a liability the operator cannot close on its own, and it forces a conservative assumption or an inspection to prove the structure. Worse, a repair that introduced a recurring inspection but never propagated into the maintenance program is an open airworthiness obligation running silently, which surfaces as a finding at the next audit or the next heavy check with no margin left to react.

How the work runs

What the buyer receives

• A structural repair map locating each repair on the airframe with its data status
• An exception list of repairs missing approval data, location, or a linked recurring inspection
• A source map and closure plan sequencing the reconstruction for this airframe

Who uses the output

• Asset managers who need a located, data-backed repair history to price or accept the aircraft
• CAMO and records teams confirming recurring inspections are captured in the program
• Structures engineers who need the repair basis settled before further work

How the work fits into the transaction or program

The structural repair review consolidates a scattered event history into a map downstream teams can act on. It hands the program owner the recurring inspections that repairs introduced, and it gives the acceptance team a repair history whose approval basis is settled rather than assumed.

Aircraft-specific considerations

The A220 is young enough that heavy structural damage history is usually limited, but composite and metallic repairs on this airframe still carry their own approval basis and, in some cases, a recurring inspection that must live in the program. Because the type has passed through fewer operators than an older aircraft, a review often turns on locating the data behind a small number of repairs rather than untangling decades of accumulated structural work.

Jurisdiction-specific considerations

A repair approved under an FAA basis and one accepted under EASA oversight can rest on different data and different continued-airworthiness handling, and a fleet crossing between them can carry repairs whose basis needs recognition on the receiving side. The review notes where a repair's approval will require a validated or recognized basis under the other authority.

Regulatory limits

The review reports what the structural repair records support. It does not issue an airworthiness determination, approve or design any repair, and does not replace an engineering assessment of the structure or the operator's acceptance.

What this review does not cover

• Physical inspection or non-destructive testing of any repair on the aircraft
• Design or engineering substantiation of a repair lacking approved data
• Approval of a repair or its recurring inspection interval

Specific to this review

• A repair that introduced a recurring inspection is an open obligation even when the physical work is sound, if the inspection never reached the program.
• On a young A220 the exposure is usually a handful of repairs missing data rather than a deep backlog of structural history.
• A dent-and-blend closed in a line-check work order is a common repair that never reaches a consolidated repair map.
• Locating a repair by zone matters as much as its data, because an unlocated repair cannot be reconciled against later inspection findings.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits