Dash 8 shop visits
De Havilland Dash 8 engine shop-visit records review
This review reconciles the engine shop-visit packages on a De Havilland Dash 8 into a supported account of what was done, what was replaced, and how the engine was released. It reads the shop reports, the module build records, the test-cell data, and the release certificates together, checking that the workscope, the parts fitted, and the returned status agree. A records specialist runs it before a transaction or an engine sale where shop-visit history drives value. You receive a supported exception list, a source map through each shop visit, and a closure plan for the packages that do not reconcile.
When this review is needed
- A Dash 8 engine is being sold separately and its shop-visit history sets the price.
- A buyer wants each shop visit reconciled before pricing the powerplant on the aircraft.
- Module builds across visits have to be tied together so LLP identity holds.
- A shop visit was done at a facility whose paperwork has to be confirmed for the receiving side.
The problem
An engine shop-visit package should tell one consistent story: what came in, what was inspected, what was replaced, what was built, and how it left. On a Dash 8 engine that has been through several shops on a high-cycle regional life, those packages arrive in different formats, and the build record, the parts list, and the test-cell data do not always agree with the release. A module build recorded without the disk sheet that supports it breaks the LLP trace that runs through it, and a workscope that does not match the returned status leaves the engine's real condition unclear.
What gets reviewed
- Each shop-visit package read as a set: incoming status, workscope, build, and release
- Module build records reconciled to the parts fitted and the disk sheets behind them
- Test-cell data checked against the workscope and the returned status
- Release certificates tied to the specific shop visit they close
- LLP identity carried through each build without a break between visits
- Workscope and returned status reconciled so the engine standard is clear
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 shop visit's incoming status, workscope, build, and release form a consistent set
- Module build records agree with the parts list and the disk sheets on file
- Test-cell data is present and consistent with the workscope performed
- The release certificate names the engine and workscope it is meant to close
- LLP identity carried through each build reconciles with the LLP status sheet
Evidence normally required
- The engine shop-visit packages for each visit on record
- Module build records and disk sheets from the shops
- Test-cell run data associated with each visit
- Release certificates issued at the close of each shop visit
- The engine LLP status sheet for build reconciliation
Common discrepancies
- A module build record with no disk sheet to support the parts it lists
- Test-cell data missing for a visit whose workscope required a run
- A release certificate whose workscope does not match the shop report
- An LLP whose identity cannot be carried cleanly through a build between visits
What is at stake
A shop visit that does not reconcile undermines the value a buyer will assign to the engine, because they cannot tell what standard it was returned to. A broken build record propagates into the LLP trace, forcing conservative life assumptions, and a release that does not match the workscope can be challenged at the next transaction long after the shop has moved on.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Order the visits
Arrange the shop-visit packages chronologically and identify what each visit was meant to accomplish.
Reconcile within each visit
Check that incoming status, workscope, build, and release agree inside every package.
Carry the builds forward
Tie module builds and LLP identity across visits so the trace holds.
Flag the gaps
Record visits that do not reconcile and the build, test, or release evidence needed to close them.
What the buyer receives
- A supported exception list of shop visits that do not reconcile
- A source map through each shop visit from incoming status to release
- A closure plan for recovering the missing build, test, or release evidence
Who uses the output
- Asset and trading teams pricing the engine on its shop-visit history
- Records teams tying build records into the LLP trace
- Buyers verifying the standard each engine was returned to
How the work fits into the transaction or program
Shop-visit reconciliation feeds the LLP trace and the powerplant value in the data room, since both depend on the build records being consistent. Its exception list drives evidence recovery from the engine shops while their retained copies are still reachable, before the engine's history has to hold up at a sale.
Aircraft-specific considerations
Dash 8 engines run high cycle counts on short sectors, so shop visits come around often and the build history is deeper than on a long-haul asset. Propeller overhaul packages sit alongside the engine shop visits on this family and are reconciled together, since a buyer prices the powerplant and propeller as one story.
Jurisdiction-specific considerations
A shop visit released under one authority may need its release confirmed as acceptable to another when the engine or aircraft changes register. The review notes where a visit's release will need a bridging basis for the receiving system.
Regulatory limits
The review reconciles the shop-visit records into a supported account. It does not certify the engine, set its returned status on a shop's behalf, or make an airworthiness determination on the powerplant.
What this review does not cover
- Physical inspection, test, or teardown of the engine
- Issuing or reissuing any shop-visit release certificate
- Any airworthiness determination on the powerplant
Specific to this review
- A shop-visit package is a set, not a document; the value is lost when the build, the test data, and the release do not agree with each other.
- A build record without its disk sheet breaks the LLP trace that runs through the engine, so it costs more than a missing standalone report.
- On a high-cycle Dash 8 engine the shop-visit history is deep enough that reconciling visit to visit is where most of the effort goes.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Why read the whole package instead of just checking the release certificate?
The release tells you the engine was signed off, not what it was signed off to. Reading the incoming status, workscope, build record, and test data together confirms the release actually reflects the work, and it carries the module builds and LLP identity that a buyer prices the engine on. A release that does not match the workscope is exactly what surfaces at the next sale.
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.