Engine shop visits
Bombardier Global 7500 engine shop-visit records review
A Global 7500 engine shop-visit records review verifies that a shop-visit package tells one consistent story from induction through test to release. It is run for a lessor, operator, or management provider assessing an engine's documented status on a specific tail. It reads the shop report, the module build records, the test-cell data, and the release certificate together, then reconciles them against the life-limited part trace carried into and out of the visit. You receive a supported exception list, a source map linking each claim to its evidence, and a closure plan for the engine under review.
When this review is needed
- An engine on a Global 7500 came back from a shop visit and its package has to be verified before it drives a valuation.
- A life-limited disk was replaced at a module build and the new part's trace has to link to the release paperwork.
- A prospective buyer wants the shop-visit history reconciled before pricing the powerplant.
- An engine is being separated for its own sale and the package must stand on its own away from the airframe.
The problem
An engine shop-visit package is thick and easy to accept on its cover sheet. The trap is that the test-cell numbers, the module build sheet, and the release certificate can each be individually complete while disagreeing on which parts left the shop in which position. A life-limited disk swapped during the visit has to carry its own trace from origin, not just appear on the outgoing status, and that link is where packages most often fail on close reading.
What gets reviewed
- The shop report read against the work scope the visit was inducted to accomplish
- Module build records checked for the parts installed and their recorded positions
- Test-cell data confirmed to support the performance and the release the engine left on
- Release certificate verified for the right form, authority, and scope of the visit
- Life-limited parts entering and leaving the build reconciled to their trace and remaining life
- The outgoing engine status cross-checked against the build and the release evidence
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
- The parts on the module build sheet match those on the release certificate and the outgoing status
- Each life-limited part carried through the build has trace to its required origin, not the status list alone
- Test-cell results support the standard the engine was released to
- The release certificate is the correct form for the work and the jurisdiction of the shop
- The work actually performed matches the scope the visit report claims
Evidence normally required
- The complete engine shop-visit package, including shop report and work scope
- Module build records and the disk sheets for life-limited parts
- Test-cell data from the visit
- The release certificate issued at the end of the visit
- The engine life-limited part status before and after the visit
Common discrepancies
- A life-limited disk installed at the build whose trace stops short of its required origin
- A module build sheet that lists a part position the release certificate does not confirm
- Test-cell data that does not clearly support the release standard claimed
- A release certificate whose scope is narrower than the work the shop report describes
What is at stake
An engine whose shop-visit package does not reconcile carries a discount until it does, because a buyer prices the risk that a disk position or a build standard cannot be proven. If a life-limited part entered the build without full back-to-birth trace, its remaining life may have to be treated conservatively, which directly reduces what the engine is worth. Reassembling this trace after the shop has moved on is slow and sometimes impossible.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Frame the visit
Establish the inducted work scope and the standard the engine was meant to leave on.
Reconcile the build
Match the module build sheet, disk sheets, and release certificate for parts and positions.
Trace the life-limited parts
Confirm every life-limited part in the build has trace to its required origin and correct remaining life.
Settle the status
Cross-check the outgoing status against the evidence and list what does not reconcile.
What the buyer receives
- A supported exception list flagging each place the package does not reconcile
- A source map linking the shop report, build records, test data, and release certificate to the outgoing status
- A closure plan naming the trace or evidence each open item needs
Who uses the output
- Asset managers valuing the powerplant on documented, reconciled status
- Records teams assembling an engine package that stands on its own for a separate sale
- Continuing-airworthiness leads confirming the outgoing status the tail will carry forward
How the work fits into the transaction or program
The shop-visit review anchors the engine status that logbook continuity and life-limited part tracking both draw on, so a reconciled package keeps the whole engine file consistent. Its exception list feeds remediation before the shop's records grow cold, and the settled package becomes the engine's evidence in the next lease return or sale.
Aircraft-specific considerations
The Global 7500 uses a purpose-built long-range powerplant whose early shop visits are still comparatively rare, so a single visit carries outsized weight in the engine's documented history. Because many of these aircraft sit under a management provider, the shop-visit package may have been received and filed by a party that no longer holds the tail, which is where continuity of the engine file breaks. The APU release evidence is reviewed alongside the engine where the shop visit touched it.
Regulatory limits
The review confirms the shop-visit package is internally consistent and supported by the release evidence and life-limited part trace. It does not approve the shop's work, issue or validate a release certificate, or make an airworthiness determination on the engine.
What this review does not cover
- Physical inspection, borescope, or test of the engine
- Re-issuing or validating any release certificate
- Any airworthiness or serviceability determination on the powerplant
Specific to this review
- A shop-visit package can be complete on its face and still fail to reconcile, because the build sheet and the release list the same parts in different positions.
- A life-limited disk installed during the visit is the highest-stakes trace in the package, since a break there caps the remaining life the whole engine can claim.
- Test-cell data is often the last document assembled and the first to go missing, which weakens proof of the release standard.
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 does the life-limited part trace matter more than the rest of the package?
Because it sets the engine's remaining life, which drives its value. A disk with a broken trace may have to be treated as if it had less life than the paperwork claims, and no other document in the package can restore that trace once the shop records are gone.
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.