Configuration evidence
Airbus A220 family modification and STC status records review
This review confirms what modifications and STC installations a specific Airbus A220 actually carries and whether each is backed by approved data for that serial number. A records specialist runs it during diligence, a lease transition, or a configuration cleanup, working from the modification status report, SB embodiment records, and STC files. Each claimed change is matched to its approval basis, its effectivity, and the paperwork that shows it was worked. You receive an exception list of unsupported or ambiguous changes, a source map tying every entry to a document, and a closure plan scoped to this airframe.
When this review is needed
- A buyer is pricing an A220 and needs to know which modifications and STC installations the airframe genuinely carries.
- A lease is transitioning and the modification status report must line up with the physical configuration before acceptance.
- An operator inherited a fleet with inconsistent SB embodiment records and wants one supported configuration view per tail.
- A cabin or avionics STC is being added and the existing change history has to be settled first.
The problem
On a younger type like the A220 the modification history looks tidy until you try to trace a single STC back to its approval. The status report lists an embodiment, but the release paperwork, the effectivity note, and the installation record do not always agree, and an interior or connectivity STC installed under one operator may never have been carried cleanly into the next operator's summary. The list reads complete while the evidence behind it is thin in specific places.
What gets reviewed
- The modification status report reconciled against the SB embodiment records for this serial number
- Each STC installation matched to its approval and to the effectivity that makes it applicable to the airframe
- Manufacturer service bulletins recorded as embodied checked against the accomplishment paperwork
- Interior, avionics, and connectivity changes traced from work order to release document
- Configuration deviations between the recorded status and the installed standard flagged for closure
- Superseded or partially embodied modifications identified where the status list treats them as complete
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
- Every STC on the status report has an approval reference and applies to this serial number by effectivity
- Each SB recorded as embodied is supported by an accomplishment record, not just a status line
- Interior and cabin modifications trace to a release document rather than an operator-authored summary alone
- Modifications marked complete are not in fact partial embodiments awaiting a later step
- The recorded configuration matches the type design plus the approved changes for the airframe
Evidence normally required
- The current modification and STC status report for the airframe
- SB embodiment records and the manufacturer service bulletin references cited
- STC files including approval documents and installation instructions
- Work orders and release certificates for cabin, avionics, and structural changes
- The configuration or effectivity list delivered with the aircraft
Common discrepancies
- An STC recorded as embodied with no approval document tied to this serial number
- SB embodiment carried forward between operators without the underlying accomplishment record
- A cabin modification installed but never reflected in the configuration list
- A modification listed as complete that was only partially worked at the last check
What is at stake
A modification claimed but not supported becomes the next reviewer's problem, and on a transaction it either drops the price or stalls acceptance until someone reconstructs the approval trail. If an STC is recorded as embodied but the installation cannot be tied to approved data, the operator carries a configuration it cannot fully substantiate, which surfaces again at the next redelivery with less time to fix it.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the claimed configuration
Take the modification status report and STC list as the set of changes the airframe is said to carry.
Match each change to its basis
Tie every modification and STC to an approval, an effectivity, and the paperwork that shows it was worked.
Isolate the exceptions
Flag changes that are unsupported, partial, or recorded without approval for this serial number.
Scope the closure
Sequence the reconstruction by recoverability and hand over a supported change history.
What the buyer receives
- An exception list of unsupported, partial, or ambiguous modifications with the missing evidence named
- A source map linking each embodied change to its approval and installation paperwork
- A closure plan sequencing the reconstruction work for this specific airframe
Who uses the output
- Asset managers pricing or accepting the aircraft who need a supported configuration view
- Records teams reconciling the status report before a program or operator change
- Certification engineers confirming an STC basis before a further modification is added
How the work fits into the transaction or program
The modification review sits between the raw status report and any downstream decision that relies on configuration being settled. It hands a supported change history to the acceptance team on a transition, or to the engineering group planning the next STC, so neither has to rebuild the embodiment picture from scratch.
Aircraft-specific considerations
The A220 entered service recently enough that its delivery baseline is well documented, but its cabin and connectivity fit changes hands with the aircraft and the modification record is where operator transitions leave the most drift. Engine and avionics configuration on this type carries its own SB stream, so a review scopes to the actual embodiment history of the serial rather than assuming a young airframe has a clean sheet.
Jurisdiction-specific considerations
An A220 traded or operated across FAA and EASA oversight will carry STC approvals and SB references framed to whichever authority governed the installing operator. The review notes where a change was approved under one authority and needs a recognized basis under the other, so the receiving side knows what supporting documentation to expect.
Regulatory limits
The review reports what the modification and STC evidence supports for this airframe. It does not issue an airworthiness determination, approve or validate any STC, and does not substitute for the operator's or CAMO's acceptance of the configuration.
What this review does not cover
- Physical inspection or confirmation of the installed configuration on the aircraft
- Preparation or submission of any STC application or approval
- Engineering substantiation of a modification that lacks approved data
Specific to this review
- On the A220 the connectivity and cabin STC trail is the most likely place for embodiment to detach from approval, because that fit moves with operator preference.
- A modification status report can show a full embodiment count while individual entries lack the accomplishment record that closes them.
- Partial SB embodiments on this type are easy to miss because the status line reads complete once the first phase is worked.
- STC effectivity by serial number matters even within one family, so a change valid on a sister aircraft is not automatically supported here.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
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.
Frequently asked questions
The A220 is a young aircraft, so why would its modification records need a review?
Age reduces the volume of changes, not the risk that a specific one lacks a supported trail. The cabin, connectivity, and avionics fit on this type moves between operators, and it is exactly those changes where the status report and the approval paperwork drift apart on an otherwise clean airframe.
Does this confirm the modifications are physically installed?
No. The review works from records and confirms whether each claimed modification and STC is backed by approved data and installation paperwork for this serial number. Physical confirmation on the aircraft is a separate inspection activity outside this scope.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.