A220 assets
Airbus A220 records review
An Airbus A220 records review is for lessors, airlines, and acquisition teams moving a single-aisle A220 aircraft through a transition, return, or sale. The trigger is often an earlier-build aircraft whose modification embodiment and program revision need establishing. We check modification standards by build standard, AD and Service Bulletin status against the program's evolution, the maintenance-program revision the aircraft was maintained under, and life-limit traceability against source documents. You receive a discrepancy register, a modification embodiment and program-revision status view tied to source records, and the evidence each open item needs to close.
When this review is needed
- An earlier-build A220 is changing hands and its modification embodiment needs confirming.
- A buyer needs the AD and Service Bulletin status read against the program's evolution.
- Maintenance-program revisions need reconciling against what the aircraft actually accomplished.
- A return is offered and the lessor wants the early service history read independently.
The problem
The A220 program matured rapidly, so earlier-build aircraft carry modification standards and Service Bulletin embodiments that later aircraft incorporated in production. The maintenance program itself has been revised across the type's service life, and a review has to reconcile the revision the aircraft was maintained under against the current one. Modification embodiment the records do not clearly establish is a frequent point of uncertainty.
What gets reviewed
- AD and Service Bulletin status read against the program's evolution
- Embodiment status for the modification standards tied to the aircraft's build standard
- Maintenance-program revision history and the revision the aircraft was maintained under
- Life-limited part status with continuous traceability
- Authorized release certificates for installed and replaced components
- Status lists reconciled against the source documents behind them
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
- Embodiment of each modification standard is clearly established against the aircraft's build standard
- AD applicability reflects the embodied modification standards
- The maintenance-program revision is reconciled with what the aircraft accomplished
- Life-limited part status traces to release documentation with consistent histories
- Service Bulletin embodiments expected in production are confirmed on earlier-build aircraft
- Status lists reconcile against the underlying source documents
Evidence normally required
Common discrepancies
- Modification embodiment that the records do not clearly establish
- AD applicability that does not reflect the embodied modification standard
- A maintenance-program revision out of step with what was accomplished
- Release certificates absent for components installed during a modification
- Status lists that disagree with the source documents they summarize
What is at stake
Accepting an A220 with unclear modification embodiment or a maintenance program out of step with the current revision can leave the next operator unable to show its baseline. Re-establishing the modification standard after acceptance is slow and can hold up the next placement.
How the work runs
Establish the build standard
Determine the aircraft's build standard and the modification standards expected at that point in the program.
Reconcile embodiment and revision
Confirm modification embodiment against the build standard and the program revision against what was accomplished.
Register discrepancies
Record each finding with its source document, evidence trace, and effect on the build-standard baseline.
Map closure
Recommend a closure path and responsible party so the baseline can be relied on.
What the buyer receives
- A discrepancy register pairing each finding with its source document and evidence trace
- A modification embodiment and program-revision status view tied to source records
- A closure recommendation for each item with the responsible party named
- A confirmed build-standard baseline the next operator can maintain against
Who uses the output
- Asset managers and buyers pricing an earlier-build aircraft on a confirmed baseline
- Records teams establishing the build standard ahead of the next placement
- Operators reconciling the program revision at induction
How the work fits into the transaction or program
The review runs ahead of the next placement so embodiment and program-revision findings can be resolved while the early service history is still reachable. It feeds the build-standard baseline the receiving operator maintains against.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Earlier-build A220 aircraft carry modification standards that later aircraft incorporated in production, so embodiment status is checked against the specific build standard rather than assumed across the type. The maintenance program has been revised over the type's service life, so the review reconciles the revision the aircraft was maintained under against the current one.
Jurisdiction-specific considerations
Where an A220 moves between authorities, the embodiment record and program revision have to be expressed in terms the receiving authority recognizes, and component releases have to be acceptable under the registry the aircraft moves to.
Regulatory limits
This review confirms records completeness, consistency, and traceability against the established build standard. It does not determine applicability on the authority's behalf, issue an approval, or determine airworthiness.
What this review does not cover
- Physical inspection or configuration survey of the aircraft
- Re-approval of a modification standard
- Any airworthiness or acceptance determination
Specific to this review
- Earlier-build A220 aircraft carry modification standards that later aircraft incorporated in production, so embodiment status is checked against the specific build standard.
- The maintenance program has been revised over the type's service life, so the review reconciles the revision the aircraft was maintained under against the current one.
- A production-incorporated Service Bulletin can be assumed embodied on a later aircraft yet still need confirming on an earlier-build one, so embodiment is verified rather than inferred from the serial range.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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.
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Why does build standard matter on an A220?
The program matured quickly, so an earlier-build aircraft may need modifications that later aircraft received in production. The review establishes the build standard first, then confirms embodiment against it rather than assuming a modification is present from the serial range.
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.
Walk through your situation with an engineer who has done this work.