Narrowbody records
131-9 APU shop visit records evidence review
The decision turns on accept a 131-9A/-9B APU shop visit package or exchange unit, in the highest-volume APU aftermarket where units rotate through exchange pools. Read shop visit report and workscope, LCF-limited part status for turbine hardware, 8130-3/Form 1 for the assembled unit and replaced parts, serial provenance across pool exchanges, hours/cycles reconciliation with host aircraft logs first. Resolve exchange unit delivered with a summary sheet but no piece-part LCF history, APU hours diverging from host aircraft usage logs, borescope-driven repairs undocumented between shop visits.
When this review is needed
- The next decision is APU shop visit / exchange.
- The first evidence to test is shop visit report.
- The open question is accept a 131-9A/-9B APU shop visit package or exchange unit, in the highest-volume APU aftermarket where units rotate through exchange pools.
The problem
The difficult point is exchange unit delivered with a summary sheet but no piece-part LCF history, APU hours diverging from host aircraft usage logs, borescope-driven repairs undocumented between shop visits.
What gets reviewed
- Reconcile the claimed 131-9 apu shop visit status to source documents by item, serial number, and date.
- Check that the latest status report agrees with logbook entries and task-card evidence.
- Review release paperwork for parts or assemblies that affect the stated configuration.
- Identify open items whose closure depends on outside records or revised statements.
- Map each discrepancy to the party best placed to answer it.
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 the source page supports the same part, serial, date, and status shown in the summary.
- Fail when a spreadsheet line has no matching log entry or certificate in the delivered file.
- Pass when repetitive tasks show a traceable last-done and next-due basis.
- Fail when configuration claims rely on inherited wording without supporting embodiment evidence.
Evidence normally required
- shop visit report
- module or assembly records
- logbook entries with dates, times, and references
- release paperwork for affected parts
- task cards and non-routine records
- current status report from the operator or CAMO
Common discrepancies
- Status carried forward from a prior operator with no source-page reference.
- Cycle, hour, or calendar values that diverge between the tracking export and the log entry.
- Release paperwork filed under a related assembly rather than the affected serial.
- A closure note that describes work performed but omits the document needed to prove it.
What is at stake
If unresolved, exchange unit delivered with a summary sheet but no piece-part LCF history, APU hours diverging from host aircraft usage logs, borescope-driven repairs undocumented between shop visits changes the APU shop visit / exchange position for 131-9 APU shop visit records.
How the work runs
Frame 131 APU
Confirm the exact event, affected file set, buyer role, and decision standard before any shop visit report is treated as sufficient.
Trace Visit Records
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 Evidence Narrowbody
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package A320 737
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
- Decision register for 131-9 APU shop visit records, split into supported, disputed, and missing evidence.
- Source map for shop visit report tied to the controlling status records.
- Owner action list for document retrieval, data correction, technical disposition, or acceptance decision.
- Briefing note tying the open items to APU shop visit / exchange.
Who uses the output
- powerplant engineer uses the register to decide what can be accepted, reserved, or escalated.
- records lead uses the register to decide what can be accepted, reserved, or escalated.
- asset manager uses the register to decide what can be accepted, reserved, or escalated.
How the work fits into the transaction or program
Accept a 131-9A/-9B APU shop visit package or exchange unit, in the highest-volume APU aftermarket where units rotate through exchange pools. The evidence set centers on shop visit report and workscope, LCF-limited part status for turbine hardware, 8130-3/Form 1 for the assembled unit and replaced parts, serial provenance across pool exchanges, hours/cycles reconciliation with host aircraft logs. The likely weak points are exchange unit delivered with a summary sheet but no piece-part LCF history, APU hours diverging from host aircraft usage logs, borescope-driven repairs undocumented between shop visits. Handoff: powerplant engineer, APU shop visit / exchange, 131-9 APU shop visit records.
Start with a single asset
Prove the review on a single tail, then scale across the fleet.
Aircraft-specific considerations
For 131-9 APU shop visit records, the records depend on accept a 131-9A/-9B APU shop visit package or exchange unit, in the highest-volume APU aftermarket where units rotate through exchange pools.
Jurisdiction-specific considerations
For 131-9 APU shop visit records, FAA/EASA review starts with shop visit report; the trigger is APU shop visit / exchange.
Regulatory limits
The file can show what shop visit report supports, while airworthiness decisions stay outside scope.
What this review does not cover
- Physical inspection findings outside the records package
- Negotiation of commercial credits or reserves
- Regulatory submissions made on behalf of the applicant
Specific to this review
- 131 9 apu exchange pool provenance changes which documents deserve first review because the highest-risk lines are seldom the newest pages.
- A clean index can still hide a weak position if the page reference points to a summary rather than primary evidence.
- Serial-number continuity matters as much as task completion for this review because assemblies move between assets.
- The most useful output is a decision register that separates accepted evidence, disputed evidence, and missing evidence.
- The scope uses the 131 APU Shop Visit question as the control point, so the review stays tied to APU shop visit / exchange and the buyer decision behind it.
- The evidence starts with Shop visit report and follows Records Review Evidence Narrowbody 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 engineer: 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 Exchange A320 737 Fleets questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Page-referenced discrepancy register with affected assets and closure owner; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What makes this aircraft review different from a general file audit?
The scope is tied to 131 apu shop visit and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block apu shop visit / exchange or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is shop visit report, 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 engineer 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.