Engine shop visits
Bombardier CRJ family engine shop-visit records review
This review reads the engine shop-visit package on a Bombardier CRJ and tests whether the shop report, the module build records, the test-cell data, and the release certificate reconcile to each other and to the LLP status the visit set. It is run by or for the party buying, transferring, or remarketing the regional jet or its engines, before the shop-visit history is relied on. It covers the shop report, the module build records, the test-cell data, and the release certificate that closed the visit. You receive an exception list keyed to the shop-visit package, a source map behind each reconciliation, and a closure plan for the visits whose records do not tie together.
When this review is needed
- A CRJ engine is being sold and the buyer requires the shop-visit history reconciled to the module builds.
- The tail is changing hands and the engine records have to support the LLP status the shop visits set.
- A recent shop visit's build records have not been checked against the release certificate that closed it.
- A remarketing team needs the shop-visit package supported before the engine carries its status into a sale.
The problem
An engine shop-visit package is where the LLP status and the module configuration are set, and on a CRJ the visits pile up quickly in short-sector service. The shop report, the build records, the test-cell data, and the release certificate are generated by the shop as one event, but they can disagree once they land in the aircraft file: a module built to one part configuration while the release names another, or an LLP cycle position in the build record that the status sheet never picked up. Whoever relies on the engine at a sale inherits that reconciliation, and the shop that could resolve it may have moved on.
What gets reviewed
- The shop report reconciled to the module build records for the visit
- Module build configuration matched to the release certificate that closed the visit
- LLP cycle positions in the build records reconciled to the status sheet that followed
- Test-cell data checked for consistency with the build and the release
- Successive shop visits reconciled so the engine's configuration history is continuous
- The shop-visit package reconciled against the engine status the file asserts
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 module build records agree with the shop report for the same visit
- The release certificate names the module configuration the build records establish
- LLP cycle positions from the build carry into the status sheet without an unexplained shift
- Test-cell results are consistent with the build configuration and the release
- The configuration history across successive visits is continuous with no missing build
Evidence normally required
- The engine shop-visit package with shop report, build records, and release certificate
- Test-cell data from the visit
- The LLP status sheet the shop visit fed
- Prior shop-visit records for configuration continuity
- Any prior findings on the engine records for the tail
Common discrepancies
- A module built to a configuration the release certificate does not name
- An LLP cycle position in the build record that the status sheet never reflected
- Test-cell data inconsistent with the build the package claims
- A gap in the configuration history where a shop visit's build record is missing
What is at stake
A shop-visit package whose records do not tie together undermines the LLP status and the module configuration built on it. On an engine sold separately, an unreconciled build record can drop the price or stall the sale, and a release certificate that does not match the module it closed leaves the buyer unable to confirm what configuration the engine actually left the shop in, at a point when reconstructing the shop's own records is slow or impossible.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Open the package
Assemble the shop report, module build records, test-cell data, and release certificate for each visit.
Reconcile the build
Confirm the build records agree with the shop report and the release names the configuration built.
Carry the LLP status
Check that LLP cycle positions from the build carry into the status sheet without an unexplained shift.
Confirm continuity
Reconcile successive visits for a continuous configuration history and list the missing records.
What the buyer receives
- An exception list keyed to the shop-visit package, flagging the visits whose records do not reconcile
- A source map tying each build, test-cell result, and release to the visit it belongs to
- A closure plan for the visits needing record retrieval or reconciliation
Who uses the output
- Asset and remarketing teams pricing the engine on a reconciled shop-visit history
- Records teams retrieving the build or release documents each unreconciled visit requires
- Buyers confirming the engine's configuration and LLP status before they accept it
How the work fits into the transaction or program
The review runs before the engine's shop-visit history is relied on at a sale or a transfer, so unreconciled visits are found while the shops that performed them can still supply the missing build or release. Its closure plan drives the record retrieval and reconciliation that has to finish before the engine carries its LLP status and configuration into a separate sale or onto a new operator.
Aircraft-specific considerations
A CRJ's high-cycle regional service drives frequent engine shop visits, so the package history is long and the module configuration turns over often, which makes build-to-release reconciliation the point where the record most often breaks. Because the family changes operators, an engine's shop-visit package can span several holders, so successive visits are reconciled for a continuous configuration history rather than read one visit at a time.
Jurisdiction-specific considerations
A CRJ engine moving between an FAA and an EASA operator needs its shop-visit releases to satisfy the receiving register, so a release issued on an FAA basis may need a dual release or an EASA-acceptable equivalent before the engine's status transfers. The review flags the visits whose release evidence will need supplementing for the destination.
Regulatory limits
The review reconciles the shop-visit records so a buyer or operator can rely on the engine's configuration and LLP status. It does not release an engine, certify a module build, or make an airworthiness determination.
What this review does not cover
- Performing or re-performing any engine shop work
- Issuing or re-issuing an engine release certificate
- Any airworthiness determination on the engine or the aircraft
Specific to this review
- The point a CRJ shop-visit package most often breaks is build-to-release: the module is built to one configuration and the release names another.
- An LLP cycle position set in a build record can fail to carry into the status sheet, so the build records are reconciled to the sheet rather than assumed consistent.
- Because CRJ engines change operators, configuration history is reconciled across successive visits, since a single missing build record breaks the continuity a buyer relies on.
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
Each shop visit has a release certificate. Why reconcile the whole package?
The release certificate closes the visit, but it has to name the configuration the build records establish and carry the LLP positions into the status sheet. On a CRJ engine that changed operators, those pieces can disagree once they land in the file, and a buyer needs them reconciled to trust the engine's configuration and remaining life.
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.