Shop visit records
CFM56 HPT seal configuration and shop visit evidence
This review is for MROs, lessors, Aircraft records teams that need to defend Shop visit work scope during Engine shop visit or mid-lease inspection. It compares the status claim with Engine AD status line and HPT module build record, Shop visit work scope, Parts release certificate, release entries, and configuration or task-control records where supplied. The output shows which lines are supported, which need retrieval, and which require specialist disposition before acceptance.
When this review is needed
- The file contains a closed status line but the buyer cannot see the source record behind it.
- Aircraft, engine, component, or software configuration has changed since the last accepted status report.
- The review team needs an exception list before lease return, import, shop release, or sale close.
The problem
The hard part is not finding documents, it is deciding whether the right document supports the exact claim. Dates, serials, revisions, measured values, and release references are checked at the level needed for acceptance.
What gets reviewed
- Trace the HPT seal installed condition from shop teardown through final build.
- Check part and serial identifiers against release certificates and installation records.
- Review whether the work scope actually included the affected seal location.
- Compare engine logbook release wording with the shop visit status update.
- Identify records needed before an engine sale, lease return, or next shop visit.
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
- Pass when build sheets and certificates support the installed HPT seal condition.
- Fail when the work scope says replaced but the build sheet omits the part identity.
- Pass when the engine logbook references the same shop event used for AD closure.
- Fail when a certificate proves part eligibility but not installation on the engine.
Evidence normally required
- AD status report
- HPT module build sheets
- parts installation list
- authorized release certificates
- shop visit release statement
- powerplant logbook entries
Common discrepancies
- Seal part reference appears in material issue records but not in the final build record.
- AD status closed using a shop visit cover page only.
- Module paperwork separated from the main engine records file.
- Installation date in the tracking system differs from the shop release date.
What is at stake
Unresolved evidence can become a lease exception, audit finding, import question, or shop-release delay. The exposure is highest when missing records are discovered after leverage or access to the prior records owner has changed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Frame 2023 Cfm56
Confirm the exact event, affected file set, buyer role, and decision standard before any ad status line is treated as sufficient.
Trace Seal Replacement
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Review Configuration
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Visit Records
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- HPT seal evidence matrix
- Open discrepancy register grouped by aircraft, engine, component, or location
- Source-record request list with exact missing pages
- Acceptance notes for lines that are supported by the delivered file
Who uses the output
- Powerplant records analyst uses the register to decide which lines can be accepted or escalated.
- Powerplant engineer uses the evidence map to request missing technical records.
- Shop visit manager uses the closure plan for transaction, audit, or delivery decisions.
How the work fits into the transaction or program
AD 2023-05-05 superseded AD 2021-10-09 for CFM56-5B and -7B engines with certain HPT inner stationary seals, requiring removal, inspection, and replacement of affected seals after cracks were found in rotating air HPT front seals; verify from shop visit records which seal part and serial is installed and that removal deadlines tied to shop visit opportunities were met. The evidence set centers on AD status report, HPT module build sheets, parts installation list, and authorized release certificates. The likely weak points are seal part number never captured at the last performance restoration, compliance claimed at next shop visit that never arrived before the deadline, and supersedure differences (added part numbers, revised compliance windows) not reflected in the status list. Handoff: powerplant records analyst, engine shop visit or mid-lease inspection, CFM56 HPT seal configuration and shop visit evidence.
Jurisdiction-specific considerations
FAA references are used as evidence context for recordkeeping and compliance support. The review does not treat one authority's record format as automatic acceptance by another authority or by a counterparty.
Regulatory limits
The output supports records and transaction decisions. It does not make an airworthiness determination, issue a release to service, grant credit, or bind any authority, authorized person, operator, or counterparty.
What this review does not cover
- Creation of missing maintenance records
- Regulatory filings submitted for the owner or operator
- Legal interpretation of lease or purchase terms
Specific to this review
- For this review, hPT seal evidence depends on build configuration, so a purchase invoice or material issue alone is weak support.
- A recurring records trap is that shop packages can prove compliance only when final assembly records identify what stayed in the engine.
- Engine-level AD status should be checked against module records because modules may have independent work histories.
- The scope uses the 2023 Cfm56 Hpt Seal question as the control point, so the review stays tied to Engine shop visit or mid-lease inspection and the buyer decision behind it.
- The evidence starts with AD status line and follows Replacement Evidence Review Configuration references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for Powerplant records analyst: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Shop Visit Records Inner questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from HPT seal evidence matrix; it gives the next reviewer a precise map instead of another broad request for a better file.
- The source discipline is stricter on this page than on a general audit because the claim being tested is Verify HPT seal configuration and replacement evidence under AD 2023-05-05..
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Frequently asked questions
What makes this records review different from a general file audit?
The scope is tied to 2023 cfm56 hpt seal and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block engine shop visit or mid-lease inspection or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad status line, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives powerplant records analyst a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.