Engine shop visits
Dassault Falcon 7X engine shop-visit records review
This review confirms that each engine shop visit on a Dassault Falcon 7X is documented from work scope through module build to release. It is run by or for a party pricing, transferring, or maintaining the aircraft, where an engine's records set its remaining value. It examines the shop reports, the module build records, the test-cell data, and the release certificates for each visit, checking that the build traces cleanly and the LLP disposition inside the shop is consistent. You receive an exception list of shop-visit gaps and broken build traces, a source map to the shop package, and a plan to recover the missing evidence per engine position.
When this review is needed
- A buyer is pricing engine value and needs each shop visit documented from scope to release.
- A module build record shows a part change but its release and LLP disposition are not on file.
- An engine came back from a shop visit and its test-cell acceptance data cannot be located.
- The shop-visit history has to be assembled per position before a transaction or a register change.
The problem
An engine's records carry as much of its value as its hardware, and the shop visit is where that record is made or broken. On a Falcon 7X the shop-visit package should trace the work scope into the module build and out through test-cell acceptance and release, but a build record that changed an LLP without carrying its trace forward, or a visit missing its test-cell data, leaves the engine supported only in part. Across three engines a small documentation gap repeats, and the value at stake is highest exactly where the records are thinnest.
What gets reviewed
- Shop reports for each visit reconciled to the recorded work scope
- Module build records traced through part changes and reassembly
- Test-cell acceptance data confirming post-visit engine status
- Release certificates covering the engine and its changed components
- LLP disposition inside each shop visit checked for continuity of trace
- Shop-visit history assembled and consistent across all three engine positions
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 has a package covering scope, build, test, and release
- Module build records trace every part change through to a release
- Test-cell data supports the engine's accepted status after the visit
- LLP trace holds across the shop visit rather than breaking at the module build
- The shop-visit history is complete and consistent for each of the three engine positions
Evidence normally required
- The engine shop-visit packages for each visit and position
- Shop reports and work-scope documentation
- Module build records and part-change lists
- Test-cell acceptance data
- Release certificates for the engines and changed components
Common discrepancies
- A module build that changed an LLP without carrying its trace forward through the visit
- A shop visit whose test-cell acceptance data cannot be located in the package
- A release certificate that does not cover a component changed during the build
- A shop-visit history complete on two engine positions but with a gap on the third
What is at stake
A shop visit without a complete package leaves the engine's post-visit status unproven, so a buyer prices it conservatively or discounts it until the record is rebuilt. A build that broke an LLP trace inside the shop can undermine the whole engine's life position, and reconstructing shop-visit evidence after the fact depends on a shop package that may already be dispersed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the visits
Collect the shop-visit packages for each engine position and reconcile them to the recorded work scope.
Trace the build
Follow each module build through its part changes and confirm the trace reaches a release.
Confirm test and release
Check test-cell acceptance data and release certificates for each visit and changed component.
Close per position
Flag the gaps and broken traces and plan recovery organized by engine position.
What the buyer receives
- An exception list of shop-visit gaps and broken build traces, ranked by value at risk
- A source map tying each visit to its shop report, build, test, and release evidence
- A recovery plan for the missing shop-visit evidence, organized per engine position
Who uses the output
- Asset managers pricing engine value against shop-visit records that actually hold together
- Records teams recovering shop packages before a transaction quotes the engine status
- Continuing-airworthiness staff confirming post-visit status across all three engines
How the work fits into the transaction or program
The shop-visit review connects to the LLP and release-document reviews on a Falcon 7X, because the module build is where life-limited parts change and where release evidence for the engine is generated. Its recovery plan closes the shop-visit gaps before the engine status feeds a transaction, an export package, or a redelivery binder.
Aircraft-specific considerations
The Falcon 7X carries three engines, so shop-visit records have to be complete per position and a gap on any one engine drags on the whole aircraft's value. Because the type operates internationally, its engine shop visits may occur under different authorities, so the release evidence in a package has to be checked for the form and recognition the aircraft's register expects.
Jurisdiction-specific considerations
An engine shop visit performed under one authority produces release evidence that the other recognizes only under the applicable bilateral terms, so a package assembled abroad may need its release checked against the aircraft's register. The review flags shop visits whose release evidence would need supplement for the operating or receiving authority.
Regulatory limits
The review confirms that each shop visit is documented and that build trace and release evidence hold. It does not certify the engine, set its post-visit status on an authority's behalf, or make an airworthiness determination on any engine.
What this review does not cover
- Performing or re-performing any engine maintenance or test
- Certifying an engine or setting its post-visit status
- Physical inspection or borescope of the engines
Specific to this review
- The module build is where an LLP trace most often breaks inside a shop visit, because a part can change without its history following it out of the shop.
- Test-cell acceptance data is what proves post-visit status, so a package missing it leaves the engine's return unsupported even when the build is documented.
- With three engines, a documentation gap on a single position discounts the whole aircraft, so shop-visit history is assembled per position rather than pooled.
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 review shop-visit records per engine position instead of for the aircraft as a whole?
The Falcon 7X has three engines, each with its own shop-visit history, module builds, and life-limited parts. A gap on a single position can break that engine's trace and discount the whole aircraft, so the review assembles and checks the history position by position rather than treating the engines as one record.
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.