Modification status
Airbus A330 family modification and STC status records review
This review establishes what modifications and STCs a specific A330 airframe actually carries and whether each one is supported by approved data. A records specialist runs it for the party evaluating, transferring, or holding the asset, typically before a trade or a program transfer. It reconciles the modification status report against SB embodiment evidence, STC installation files, and the effectivity that applies to this manufacturer serial number. You receive an exception list keyed to each modification, a map to the source record, and a plan to close the gaps.
When this review is needed
- A buyer is pricing an A330 and needs the embodied modification standard confirmed before signing.
- An STC installed under one authority has to be shown acceptable to the receiving state of registry.
- A cabin reconfiguration was carried out and the approval trail behind it is unclear.
- The modification status report and the physical configuration have drifted apart over several operators.
The problem
The modification status report tells you what someone believes is installed, not what the release paperwork proves. On an A330 that has moved between operators, SBs get logged as embodied without the accomplishment record attached, and STCs carry into a new registry with no evidence the receiving authority ever accepted them. Sorting the supported entries from the assumed ones takes serial-level work against the source files.
What gets reviewed
- Modification status report reconciled line by line against SB embodiment evidence
- STC installation files checked for approved data and receiving-authority acceptance
- Effectivity confirmed against the manufacturer serial number rather than the fleet default
- Cabin and systems configuration changes matched to their governing approval
- Superseded or partially embodied SBs flagged where the record shows only the original issue
- Interaction between overlapping modifications reviewed for conflicting approvals
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
- Each SB marked embodied is backed by a dated accomplishment record, not the status list alone
- Every STC has approved data on file and evidence of acceptance on the registry the aircraft is moving to
- Effectivity for each modification covers this serial number and its build standard
- Configuration entries agree with the release documents raised at the time of installation
- Partial or optional embodiments are recorded as such rather than shown fully complete
Evidence normally required
- The current modification and STC status report for the serial number
- SB accomplishment records and the task cards that closed them
- STC certificates, approved data packages, and installation release paperwork
- The type design configuration and effectivity list for this build standard
- Prior operators' configuration histories where a change predates the current file
Common discrepancies
- SBs shown embodied with no accomplishment record behind the entry
- An STC installed abroad with no evidence the receiving authority accepted it
- A cabin change recorded in configuration but missing its approved data reference
- Effectivity applied from a fleet template that does not match this serial number
What is at stake
A modification taken on faith becomes the new owner's liability the day title moves. If an STC turns out to lack an acceptable basis on the target registry, the aircraft can be grounded pending substantiation, and cabin or systems changes without approved data force a costly reconstruction or removal at the worst possible moment.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the status baseline
Take the current modification and STC status report as the starting index and pin it to the serial number.
Trace each entry to evidence
Match every embodied SB and STC to its accomplishment record, approved data, and release paperwork.
Test acceptance and effectivity
Confirm effectivity for this build standard and check STC acceptance on the target registry.
Log exceptions and close-out
Record unsupported entries as exceptions and sequence the evidence needed to close each one.
What the buyer receives
- An exception list keyed to each modification and STC with its supporting status
- A source map showing which record proves each embodied change
- A closure plan sequencing the missing approvals and accomplishment evidence
Who uses the output
- Asset managers pricing the aircraft against a confirmed modification standard
- Records teams setting the configuration entry status for a new program
- Certification staff resolving STC acceptance on the receiving registry
How the work fits into the transaction or program
This review sits between diligence and program entry. It hands the buyer a verified modification standard to price against, gives the records team a configuration baseline to maintain, and flags the STC acceptance work the receiving authority will expect before the aircraft flies on its new registration.
Aircraft-specific considerations
A330 configuration history tends to concentrate around cabin reconfigurations, connectivity and IFE installations, and systems SBs tied to long-haul operation. A serial number that has served several operators accumulates layered modifications where a later change assumes an earlier one is present, so the review traces the dependency chain rather than checking each entry in isolation.
Jurisdiction-specific considerations
An A330 embodying STCs approved under one authority does not automatically carry those approvals onto another registry. The review notes where an FAA or EASA basis exists and where the receiving state will need to validate or reissue an approval, but it does not perform that validation.
Regulatory limits
The review reports what the modification and approval records support as of the review date. It does not issue an airworthiness determination, grant or transfer any approval, and does not substitute for the receiving authority's acceptance of the installed configuration.
What this review does not cover
- Physical inspection or teardown to confirm what is installed on the aircraft
- Generating approved data or securing an STC where one is absent
- Formal validation of a foreign STC by the receiving authority
Specific to this review
- An embodied SB entry means little without the accomplishment record; the status list is an index, not proof.
- STCs are the most common surprise on an A330 crossing registries because acceptance rarely travels with the paperwork.
- Layered cabin modifications can conflict when a later change silently assumes an earlier embodiment that was never completed.
- Effectivity copied from a fleet template is a frequent source of false positives on a single serial number.
- A partially embodied SB shown as complete hides the residual work that a later dependent change assumes is already done.
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
Why check STC acceptance separately from the STC certificate itself?
A certificate proves the modification was approved by the issuing authority, not that the registry the aircraft is moving to has accepted it. Acceptance is a separate step, and an aircraft can hold a valid STC that the receiving state still requires to be validated before the change is usable there.
What if an SB shows embodied but no accomplishment record exists?
It is treated as an exception, not a closed item. The embodiment is either reconstructed from work orders and installation records or logged as unsupported, so the buyer knows the configuration entry rests on an assumption rather than evidence.
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.