AD evidence
AD 2025-04-13 PW1500G/PW1900G HPC 7th-Stage Rotor records evidence
For lessors, asset managers, and aircraft records teams, the trigger is A220 or E2 diligence or engine shop-visit planning. AD 2025-04-13 applies to certain PW1500G and PW1900G engines with an affected HPC 7th-stage axial rotor installed, extending powder-metal inspection requirements to these fleets. EE identifies the installed rotor serial from build, module, and shop records, checks the required inspection or removal evidence against the compliance window, and returns a discrepancy register, evidence map, and closure request list for diligence or planning.
What gets reviewed
- AD 2025-04-13 applies to certain PW1500G and PW1900G engines with a certain HPC 7th-stage axial rotor installed, extending powder-metal inspection requirements to the A220 and E2 engine fleets.
- The review notes that decision: identify the installed rotor serial from build records and prove the required inspection or removal happened within the compliance window.
- Tie every accepted line to the affected serial number, date, revision, or work package.
- Separate recoverable filing defects from issues that need technical disposition.
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
- Accept the ad 2025-04-13 pw1500g/pw1900g hpc 7th-stage rotor position when source evidence matches the summary claim and affected asset.
- Question the ad 2025-04-13 pw1500g/pw1900g hpc 7th-stage rotor position when a spreadsheet, index, or status flag is the only support.
- Escalate the ad 2025-04-13 pw1500g/pw1900g hpc 7th-stage rotor item when configuration, serial, approval, or repeat-task logic changes the outcome.
Evidence normally required
- current AD or SB status report
- source accomplishment entry
- applicability and configuration evidence
- inspection or repair report
- utilization snapshot at compliance
Common discrepancies
- rotor serial absent from delivery minipacks on younger engines, inspections planned at a forecast shop visit with no fallback before the deadline, and applicability denied on the basis of engine model rather than installed rotor part number.
- A ad 2025-04-13 pw1500g/pw1900g hpc 7th-stage rotor summary cites evidence that is missing, stale, or filed under another asset.
- The closure package omits the document that would let the next reviewer repeat the conclusion.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
HPC rotor source inventory
The review starts by listing the source records that actually name the installed 7th-stage rotor serial, with file location, revision date, and owner recorded before any status conclusion is made.
Powder-metal applicability test
The next pass ties the affected part claim to serial, effectivity, configuration, and utilization data so the open item is not closed from a generic status line.
Rotor status exception split
The findings separate missing source evidence, conflicting entries, stale revision references, and unsupported dispositions because each class needs a different closure route.
Diligence evidence handoff
The output names the exact record request, the accountable owner, and the decision that remains open for records, engineering, leasing, or maintenance control.
What the buyer receives
- AD 2025-04-13 PW1500G/PW1900G HPC 7th-Stage Rotor evidence map with source-page references
- AD 2025-04-13 PW1500G/PW1900G HPC 7th-Stage Rotor discrepancy register sorted by blocker, reservation, and monitor item
- AD 2025-04-13 PW1500G/PW1900G HPC 7th-Stage Rotor document request list naming the exact missing or corrected record
- The review notes that decision note for the a220 or e2 diligence, engine shop visit planning team
How the work fits into the transaction or program
AD 2025-04-13 applies to certain PW1500G and PW1900G engines with a certain HPC 7th-stage axial rotor installed, extending powder-metal inspection requirements to the A220 and E2 engine fleets; identify the installed rotor serial from build records and prove the required inspection or removal happened within the compliance window. The evidence set centers on current AD or SB status report, source accomplishment entry, applicability and configuration evidence, and inspection or repair report. The likely weak points are rotor serial absent from delivery minipacks on younger engines, inspections planned at a forecast shop visit with no fallback before the deadline, and applicability denied on the basis of engine model rather than installed rotor part number. Handoff: engine records analyst, A220 or E2 diligence, engine shop visit planning, AD 2025-04-13 PW1500G/PW1900G HPC 7th-Stage Rotor records evidence.
Regulatory limits
This ad 2025-04-13 pw1500g/pw1900g hpc 7th-stage rotor records review does not approve data, issue a release, determine airworthiness, or guarantee authority acceptance. Regulators, authorized persons, operators, and transaction parties make final decisions under their procedures.
Specific to this review
- The PW1500G and PW1900G review starts with the installed HPC 7th-stage axial rotor identity, because applicability depends on rotor serial evidence rather than aircraft family alone.
- The build record, module record, shop visit card, and parts release paperwork are compared so a rotor change is not missed when the engine file was reorganized.
- The powder-metal issue is handled as a part-specific exposure question, so the file must prove inspection or removal for the affected rotor, not a general engine check.
- The compliance window is tested against the rotor status and engine utilization, especially where shop planning assumes a future removal that has not yet happened.
- The review flags cases where an AD status sheet says complete but the source record only identifies the engine model and omits the HPC rotor serial.
- For A220 and E2 diligence, the handoff separates airframe records, engine records, and module records because the decisive rotor evidence may be outside the aircraft file.
- The output gives asset managers exact requests for build sheets, module movement records, inspection records, removal tags, and replacement release documents.
- The useful result is a rotor-specific evidence map that can support transfer, shop induction planning, or lease review without treating the whole engine as one status item.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
What makes this records review different from a general file audit?
The scope is tied to 2025 pw1500g hpc rotor and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block a220 or e2 diligence, engine shop visit planning 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 engine 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.