Narrowbody records
Leap 1a 1b durability upgrade records evidence review
The decision turns on on an early-build LEAP engine, determine which durability upgrades (HPT blade/shroud, combustor liner, reverse-bleed system) have actually been embodied and whether the records prove it, since early -1A/-1B engines came off wing early and were upgraded piecemeal at shop visits and this drives remaining time-on-wing and value. Read build configuration vs the current upgrade standard, SB incorporation records for the HPT and combustor campaigns, shop visit workscopes showing which hardware was cut in, first. Resolve an early engine marketed as upgraded when only some campaigns were embodied, -1A and -1B paperwork conflated on a mixed-fleet operator, and upgrade hardware fitted with the SB reference missing so the improved on-wing interval cannot be claimed.
When this review is needed
- The file is being prepared for early-build LEAP engine acquisition or lease return.
- The first evidence to test is build configuration vs the current upgrade standard.
- The open question is on an early-build LEAP engine, determine which durability upgrades (HPT blade/shroud, combustor liner, reverse-bleed system) have actually been embodied and whether the records prove it, since early -1A/-1B engines came off wing early and were upgraded piecemeal at shop visits and this drives remaining time-on-wing and value.
The problem
The difficult point is an early engine marketed as upgraded when only some campaigns were embodied, -1A and -1B paperwork conflated on a mixed-fleet operator, and upgrade hardware fitted with the SB reference missing so the improved on-wing interval cannot be claimed.
What gets reviewed
- Review the status claim and the specific documents named as support.
- Trace affected serial numbers, task references, release certificates, and configuration records.
- Check whether accepted evidence meets the buyer's stated criteria for the event.
- Document why each open item remains open and what evidence would close it.
- Produce a prioritized register for commercial and technical review.
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 page reference, asset identity, and status claim agree without unexplained gaps.
- Fail when a document proves work on a related item but not on the item being accepted.
- Flag any record whose approval basis or release status is unclear from the page supplied.
- Check that the final package distinguishes records gaps from physical work findings.
Evidence normally required
- AD and SB status list
- method-of-compliance records
- configuration status list
- approved modification data
- logbook entries with dates, times, and references
- release paperwork for affected parts
Common discrepancies
- A source page cited in the index but absent from the delivered folder.
- A task shown as complete with no release entry or inspection sign-off.
- Configuration status assumed from fleet practice rather than asset-specific evidence.
- Replacement evidence that closes part of the gap but leaves dates or serials unresolved.
What is at stake
If unresolved, an early engine marketed as upgraded when only some campaigns were embodied, -1A and -1B paperwork conflated on a mixed-fleet operator, and upgrade hardware fitted with the SB reference missing so the improved on-wing interval cannot be claimed changes the early-build LEAP engine acquisition or lease return position for Leap 1a 1b durability upgrade records.
How the work runs
Frame Leap Durability
Confirm the exact event, affected file set, buyer role, and decision standard before any ad and sb status list is treated as sufficient.
Trace Records Review
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 Narrowbody Early
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Config Embodiment
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 Leap 1a 1b durability upgrade records, split into supported, disputed, and missing evidence.
- Source map for build configuration vs the current upgrade standard 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 early-build LEAP engine acquisition or lease return.
Who uses the output
- Technical asset manager uses the register to decide what can be accepted, reserved, or escalated.
- Engine lead uses the register to decide what can be accepted, reserved, or escalated.
- Reliability engineer uses the register to decide what can be accepted, reserved, or escalated.
How the work fits into the transaction or program
On an early-build LEAP engine, determine which durability upgrades (HPT blade/shroud, combustor liner, reverse-bleed system) have actually been embodied and whether the records prove it, since early -1A/-1B engines came off wing early and were upgraded piecemeal at shop visits and this drives remaining time-on-wing and value. The evidence set centers on build configuration vs the current upgrade standard, SB incorporation records for the HPT and combustor campaigns, shop visit workscopes showing which hardware was cut in,. The likely weak points are an early engine marketed as upgraded when only some campaigns were embodied, -1A and -1B paperwork conflated on a mixed-fleet operator, and upgrade hardware fitted with the SB reference missing so the improved on-wing interval cannot be claimed. Handoff: technical asset manager, early-build LEAP engine acquisition or lease return, Leap 1a 1b durability upgrade records.
Start with a single asset
Organize records and a discrepancy register for diligence.
Aircraft-specific considerations
For Leap 1a 1b durability upgrade records, the records depend on on an early-build LEAP engine, determine which durability upgrades (HPT blade/shroud, combustor liner, reverse-bleed system) have actually been embodied and whether the records prove it, since early -1A/-1B engines came off wing early and were upgraded piecemeal at shop visits and this drives remaining time-on-wing and value.
Jurisdiction-specific considerations
For Leap 1a 1b durability upgrade records, FAA/EASA review starts with build configuration vs the current upgrade standard; the trigger is early-build LEAP engine acquisition or lease return.
Regulatory limits
The review stops at build configuration vs the current upgrade standard; release decisions stay with the authorized parties.
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
- Leap 1a 1b durability upgrade reviews work best when the acceptance standard is captured before evidence is judged.
- Some gaps need a corrected status line rather than another copy of the same weak record.
- A defensible file explains which evidence was used and which adjacent records were excluded.
- The final register should let a non-records stakeholder see the decision consequence quickly.
- The scope uses the Leap Durability Upgrade Records question as the control point, so the review stays tied to Early-build LEAP engine acquisition or lease return and the buyer decision behind it.
- The evidence starts with AD and SB status list and follows Review Evidence Narrowbody Early 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 Technical asset manager: 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 Build Config Embodiment Verify 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
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). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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 leap durability upgrade records and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block early-build leap engine acquisition or lease return or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad and sb status list, 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 technical asset manager 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.