Cessna Citation Longitude engine shop-visit records review

When this review is needed

• An engine has just returned from a shop visit and its status must be reconciled into the aircraft records.
• A transaction is pricing the engine on post-shop-visit condition and needs the package verified.
• Parts moved between modules during the visit and the LLP status has not been reconciled.
• The shop report is on file but the test-cell data or build records that support it are missing.

The problem

An engine shop-visit package looks conclusive because it ends with a release, but the release only means what the build records, part list, and test-cell data behind it support. On a Citation Longitude engine, a module build can shift life-limited parts and change status in ways the summary does not spell out. If the build detail is thin, the aircraft carries an engine status that the shop-visit package cannot fully back.

What gets reviewed

• The shop report reconciled against the engine status the aircraft now records
• Module build records confirming the configuration returned from the visit
• Test-cell data supporting serviceability and any performance restoration claimed
• Life-limited part moves during the visit checked for continuous traceability
• The release certificate matched to the work and the parts it covers
• Both HTF7700L positions reconciled where more than one engine was worked

What gets validated

• Post-visit engine status on the aircraft reconciles with the shop report totals
• Module build records account for every part installed or transferred during the visit
• Test-cell data is present and supports the serviceability the release states
• Life-limited parts moved in the visit carry their history forward without a break
• The release certificate covers the actual work scope and the parts involved

Evidence normally required

• The engine shop-visit package including the shop report and workscope
• Module build records and the incoming and outgoing part lists
• Test-cell data and any performance-restoration results
• Release certificates for the engine and its life-limited parts
• The pre-visit and post-visit engine status for reconciliation

Common discrepancies

• Post-visit engine status on the aircraft that does not reconcile with the shop report
• A module build record that omits a part move, breaking an LLP trace
• A release on file without the test-cell data that should support serviceability
• A workscope in the report that the release certificate does not fully cover

What is at stake

An engine whose shop-visit status cannot be reconciled to its build records puts remaining life and next-due events in doubt, which directly affects value and dispatch planning. A part that moved between modules without its history following can break an LLP trace that took years to build. Discovering this after the engine is back on wing means unstitching a shop visit that everyone assumed was closed.

How the work runs

What the buyer receives

• An exception list of unreconciled status, undocumented part moves, and missing support data
• A source map linking the release and status to the build records and test-cell data behind them
• A closure plan identifying the shop-visit documents needed to complete the engine package

Who uses the output

• Asset managers pricing or trading the engine on post-shop-visit condition
• CAMO leads reconciling the shop visit into the aircraft's engine status
• Records teams protecting the LLP trace through a module build

How the work fits into the transaction or program

A shop visit is the point where engine records are most likely to detach from the aircraft file, because the work happens off-wing and comes back as a package. This review reconciles that package into the aircraft records before the status is trusted. It pairs closely with the LLP-trace review, since the same module builds drive both the engine status and the life-limited part history.

Aircraft-specific considerations

The Citation Longitude is powered by two HTF7700L engines, and because the type is young, early shop visits are often the first real test of how well the engine records integrate with the aircraft file. A visit on one position still has to reconcile against the other for a complete engine picture, and a module build on either engine can move life-limited parts that the aircraft's LLP status must then absorb.

Jurisdiction-specific considerations

The engine may return with an FAA Form 8130-3, an EASA Form 1, or a dual release depending on the shop and the operator. On a cross-border transfer the release basis has to match the receiving authority, since a shop visit released to one authority can require additional evidence before an operator on the other register accepts the engine status.

Regulatory limits

This review reports on whether the shop-visit records support the engine status and release. It does not certify the engine, approve its return to service, endorse the shop's release, or replace the operator responsible for the engine's continued airworthiness.

What this review does not cover

• Physical inspection or test of the engine
• Endorsement or reissue of the shop release certificate
• Reconstruction of shop-visit records held only by the overhaul facility

Specific to this review

• A shop-visit release is only as strong as the build records and test-cell data behind it, which the summary rarely spells out in full.
• Module builds move life-limited parts, so a shop visit is one of the few moments that can silently break an LLP trace.
• Post-visit engine status must reconcile back to the shop report, and a gap here puts remaining life and next-due events in doubt.
• Early Longitude shop visits are the first real integration test between the engine records and the aircraft file, so gaps tend to show up here first.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits