Modification status
Modification and STC status verified inside the maintenance-control export
A modification status source review reads every line of the modification and STC status report back to the maintenance-control system data it was generated from. For each change shown as embodied, the review looks for the closing work order, the approved data or STC reference, and the effectivity that ties the change to this serial number. It is run for maintenance control or fleet management before an operator transfer, while work-order attachments can still be pulled. The result is a line-by-line exception list separating substantiated modifications from claims the source data cannot carry.
When this review is needed
- A receiving operator has asked for the substantiation behind every modification shown as embodied.
- The status report was regenerated after a system migration and lines no longer match the previous issue.
- Changes were embodied under an earlier operator and the current system data is the only accessible source for the work orders.
- An STC list taken from the aircraft specification disagrees with what the maintenance-control system carries.
The problem
A modification status report is a database query dressed as a compliance document. The embodiment flag on each line was set by whoever closed the work order, sometimes years ago, and nothing forces the approved data reference, the effectivity check, or the certificate copy to be attached before that flag is set. Ahead of a transfer the maintenance-control lead is asked to stand behind every line, and the distance between flag and evidence only becomes visible once the work orders are opened.
What gets reviewed
- Every status-report line traced to a closing work order in the maintenance-control data
- Effectivity confirmed for the airframe serial number on each modification and STC
- Approved data, engineering order, or STC certificate references resolved for each embodied change
- Multi-phase modifications checked so the recorded status matches the phases actually closed
- Removed or deactivated modifications reconciled against the current report
- Cross-references untangled where an SB was accomplished through a modification or the reverse
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 line shown as embodied has an accomplishment record in the system data, with dates that make sense against the fleet history
- Effectivity statements cover this serial number rather than the fleet or the type generally
- Approved-data and STC references on the report resolve to documents that exist in the export
- Partial embodiments carry a status that reflects which phases closed and which remain open
- No change appears twice under different identities, once as an SB and once as a modification
Evidence normally required
Common discrepancies
- A modification flagged embodied whose work order covers only part of the change
- An STC on the list with no effectivity statement or certificate copy for this serial number
- A change removed at a heavy check that still shows as active on the report
- The same alteration counted twice, once as an SB accomplishment and once as a modification line
What is at stake
Modifications that cannot be substantiated get priced by the counterparty at removal cost rather than claimed value, and an STC without effectivity for the serial number can stall configuration acceptance outright. Once the aircraft has transferred, retrieving embodiment evidence means negotiating with a former operator instead of querying your own system.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Freeze the report
Fix the status-report issue under review and align it with the date range of the system data.
Trace each line
Pull the closing work order, approved data reference, and effectivity for every embodied change.
Resolve collisions
Reconcile duplicate identities, partial embodiments, and removed changes against the current report.
Issue the exception list
Deliver annotated lines with a prioritized retrieval shortlist for the gaps worth closing before transfer.
What the buyer receives
- A line-by-line exception list separating substantiated changes from unsupported claims
- An annotated modification status report pointing each line to its source records
- A summary of open substantiation items for the operator-transfer status package
- A retrieval shortlist naming the work orders and certificates worth chasing first
Who uses the output
- Fleet management defending the modification list in transfer negotiations
- Maintenance-control teams closing substantiation gaps while system access holds
- The receiving operator's engineering group loading a configuration it can trust
How the work fits into the transaction or program
Modification status sits between the logbook continuity work and the configuration reviews in a maintenance-control export source review. Its exceptions feed the equipment-list and weight-and-balance checks directly, since an unsubstantiated modification usually drags questions about installed equipment and mass changes along with it.
Jurisdiction-specific considerations
On the FAA side, alterations rest on 14 CFR Part 43 recordkeeping and approved data, with STCs issued under Part 21 and AC 21-40 shaping the application file an operator should hold. EASA-registered aircraft carry changes approved under Regulation (EU) 748/2012, and the embodiment record expectations differ enough that a transfer across registries often reopens lines both sides had considered settled.
Regulatory limits
Nothing in this work approves a modification, extends an STC to a new serial number, or generates approved data. It measures the status report against existing evidence and leaves any engineering or certification action to the appropriate approval holder and authority.
What this review does not cover
- Obtaining or transferring STC rights and permissions
- Preparing new approved data or engineering dispositions for unsupported changes
- Physical conformity inspection of embodied modifications on the aircraft
Specific to this review
- Embodiment flags are set at work-order closure, but attachments are added later or never, so the flag and its evidence drift apart over years without anyone noticing.
- A fleet-level STC purchase does not demonstrate coverage of this airframe; effectivity is established per serial number or configuration, and that is the line item counterparties test.
- Multi-phase modifications routinely show phase one closure as full embodiment, which is exactly the kind of line a technical acceptance team samples first.
- Where an SB and a modification describe the same physical change, status reports tend to carry both, and reconciling them changes compliance counts on other documents.
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 status report comes straight from our maintenance-control system. Why would it be wrong?
The report faithfully reflects what was keyed into the system, which is a different thing from what the evidence supports. Flags set without attachments, migrations that dropped links, and changes recorded under two identities all survive inside a clean-looking report until someone reads the lines back to source.
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.