Modification & STC status
De Havilland Dash 8 modification and STC status records review
This review confirms that the modifications and STCs a Dash 8's records claim are embodied match the approval basis and the effectivity for the specific tail. It is run for a lessor, operator, or manager evaluating, transferring, or continuing to hold a Dash 8, usually ahead of a transaction or after modification history has built up across several operators. It walks each recorded change back to its SB reference, STC, or approved data, and checks the change was eligible for this serial number. You receive a supported exception list, a source map linking each modification to its evidence, and a closure plan for the entries that do not yet trace.
When this review is needed
- A Dash 8 has passed through more than one operator and its modification list has never been reconciled to source.
- A buyer needs the embodied configuration confirmed before pricing the airframe.
- An STC is claimed on the status report but no one has located the approval or its effectivity.
- A regional operator program is being bridged and the receiving side needs the change history verified.
The problem
On a Dash 8 that has served several regional operators, modification records tend to accumulate as loose SB embodiment notes, STC certificates filed apart from their installation records, and a status report that was retyped each time the aircraft changed hands. A change can be listed as embodied while the approved data behind it sits with a former operator, or an STC can be recorded against an effectivity that never applied to this serial number. The report reads clean until someone asks for the evidence.
What gets reviewed
- Embodied modifications and STCs listed for the serial number against their SB or approved-data references
- Effectivity of each recorded change confirmed against this aircraft's build and modification history
- The approval basis for each STC, including whether it was accepted for the register the aircraft sits on
- SB embodiment recorded with the correct revision and any alternative method of compliance
- Recorded configuration mapped against the type design and the operator's prior modification program
- Changes made under a former operator that never carried forward onto the current status report
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 claimed modification carries approved data appropriate to the installation and the jurisdiction the aircraft operates under
- STC effectivity matches this serial number rather than a range that excludes it
- SB embodiment references the revision actually accomplished, not a superseded issue
- Repairs or equipment changes that alter configuration are recorded as modifications where the type demands it
- The current status report reconciles with the underlying embodiment records and shows no orphaned entries
Evidence normally required
- The modification and STC status report as currently maintained
- STC certificates, approved data packages, and installation records on file
- SB status and embodiment evidence for the airframe, engines, and propellers
- The type design and configuration reference for the Dash 8 variant
- Any prior operator modification program documents that carried into the file
Common discrepancies
- An STC listed as embodied whose certificate and installation record cannot be located
- A modification recorded against effectivity that does not apply to this serial number
- An SB shown as complied by an alternative method with no supporting substantiation
- A cabin or avionics change treated as a routine swap where the type requires a tracked modification
What is at stake
A modification carried on the status report without a traceable basis can force removal or re-substantiation before a buyer or a receiving program will accept it, and that work costs far more than confirming the approval up front. An STC recorded against the wrong effectivity distorts every downstream check that assumes the configuration is settled, and the discrepancy usually surfaces during diligence when leverage has already shifted.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the claimed configuration
Pull the modification, STC, and SB embodiment the records assert for this serial number.
Confirm basis and effectivity
Match each change to its approval basis and check it was eligible for this tail.
Reconcile to type design
Map the recorded configuration against the type design and the prior operator program.
List the exceptions
Flag untraced or mis-recorded changes and set a closure sequence for each.
What the buyer receives
Who uses the output
- Asset managers pricing the configuration the records can actually support
- Records teams setting a modification baseline the rest of the file rests on
- Engineering deciding how to treat a change that has no traceable approval
How the work fits into the transaction or program
This review establishes the modification baseline that AD applicability, equipment status, and weight-and-balance amendments all build on. It usually runs alongside the configuration and equipment-list work on the same tail, so a change confirmed here does not have to be re-checked when the equipment records are reconciled next.
Aircraft-specific considerations
Dash 8 airframes in regional service accumulate cabin, avionics, and role-specific modifications faster than most turboprops, and propeller and engine changes often carry their own STC trail filed apart from the airframe status report. High-cycle operation and multiple prior operators mean effectivity errors and orphaned STC certificates are the recurring failure modes, so the review is scoped to this serial number's actual history rather than a variant-level template.
Jurisdiction-specific considerations
An STC accepted by the FAA is not automatically valid on an EASA register, so a Dash 8 that has moved between systems can carry modifications whose approval basis needs validation for the register it now sits on. The review flags where a recorded change will need a validated or supplemental approval before a receiving authority or operator relies on it.
Regulatory limits
The review confirms that recorded modifications are internally consistent and supported by an approval basis. It does not approve a modification, grant or validate an STC, or determine that the aircraft is in an airworthy configuration.
What this review does not cover
- A physical configuration survey of the aircraft
- Developing, approving, or validating new modification or STC data
- Any airworthiness determination on the installed configuration
Specific to this review
- Effectivity is where Dash 8 modification records break most often: an STC can be genuinely embodied yet recorded against a serial range that excludes this tail.
- STC certificates and their installation records tend to separate when an aircraft changes operators, so the certificate survives while the proof of installation does not.
- A modification accepted under one authority may need separate validation for the register the aircraft now operates on, which the status report rarely flags.
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
Does this confirm the modifications are physically installed?
The review works from the records and the approval basis, confirming that each recorded modification is eligible for this serial number and supported by traceable data. A physical configuration survey is a separate exercise that is often run alongside it.
What happens to an STC with no locatable approval?
It goes on the exception list with a closure path: recover the certificate and installation record from the source that held them, or, where the aircraft has changed registers, confirm whether the change needs validation for the current authority.
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.