AD evidence
AD 2022-27-04 PW1500G Dual Engine Shutdown records evidence
For airlines, lessors, Aircraft records teams, the trigger is a220 lease transition or engine swap. AD 2022-27-04 applies to all PW1500G-series engines after an uncommanded dual engine shutdown upon landing compromised braking capability on an A220, mandating corrective software and configuration actions. The review notes that decision: prove the required FADEC software standard and any hardware changes are embodied on each engine, with the installation records tied to engine serials rather than aircraft tails. EE checks current AD or SB status report, source accomplishment entry, applicability and configuration evidence against the current status claim and the acceptance criteria supplied for the review. The buyer receives a discrepancy.
What gets reviewed
- AD 2022-27-04 applies to all PW1500G-series engines after an uncommanded dual engine shutdown upon landing compromised braking capability on an A220, mandating corrective software and configuration actions.
- The review notes that decision: prove the required FADEC software standard and any hardware changes are embodied on each engine, with the installation records tied to engine serials rather than aircraft tails.
- 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 2022-27-04 pw1500g dual engine shutdown position when source evidence matches the summary claim and affected asset.
- Question the ad 2022-27-04 pw1500g dual engine shutdown position when a spreadsheet, index, or status flag is the only support.
- Escalate the ad 2022-27-04 pw1500g dual engine shutdown 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
- software loads recorded in aircraft logbooks but not engine files (or vice versa) so neither file alone proves compliance, engines swapped between tails carrying stale software status, and no record of the post-mod configuration check.
- A ad 2022-27-04 pw1500g dual engine shutdown 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
FADEC status source inventory
The review starts by listing the source records that actually name the engine-level software and configuration claim, with file location, revision date, and owner recorded before any status conclusion is made.
Dual shutdown applicability test
The next pass ties the corrective action evidence to serial, effectivity, configuration, and utilization data so the open item is not closed from a generic status line.
Software load exception split
The findings separate missing source evidence, conflicting entries, stale revision references, and unsupported dispositions because each class needs a different closure route.
A220 engine 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 2022-27-04 PW1500G Dual Engine Shutdown evidence map with source-page references
- AD 2022-27-04 PW1500G Dual Engine Shutdown discrepancy register sorted by blocker, reservation, and monitor item
- AD 2022-27-04 PW1500G Dual Engine Shutdown document request list naming the exact missing or corrected record
- The review notes that decision note for the a220 lease transition or engine swap team
How the work fits into the transaction or program
AD 2022-27-04 applies to all PW1500G-series engines after an uncommanded dual engine shutdown upon landing compromised braking capability on an A220, mandating corrective software and configuration actions; prove the required FADEC software standard and any hardware changes are embodied on each engine, with the installation records tied to engine serials rather than aircraft tails. 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 software loads recorded in aircraft logbooks but not engine files (or vice versa) so neither file alone proves compliance, engines swapped between tails carrying stale software status, and no record of the post-mod configuration check. Handoff: powerplant engineer, A220 lease transition or engine swap, AD 2022-27-04 PW1500G Dual Engine Shutdown records evidence.
Regulatory limits
This ad 2022-27-04 pw1500g dual engine shutdown 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 dual-shutdown review starts with FADEC software standard, engine serial, aircraft tail history, and any hardware change required to support the mandated configuration.
- The evidence must show the software load was embodied on each affected engine, because an aircraft log entry alone can miss engines later swapped between A220 tails.
- The landing-event risk behind the AD makes braking-capability context relevant, but the records task remains proving software and configuration status from source documents.
- The review compares engine files, airframe logbooks, software load records, configuration reports, and post-mod checks for the same serial and accomplishment date.
- The failure mode is a complete AD status line that cannot connect the FADEC load, hardware change, and post-mod verification to the engine currently installed.
- For lease transition or engine exchange, the handoff identifies whether missing evidence belongs to the operator, powerplant shop, software loader, or prior records holder.
- The output preserves separate lines for software status, hardware status, serial trace, and post-mod check so one supported claim does not hide another gap.
- The useful result is an engine-level evidence map for A220 records teams that need to prove the dual-shutdown corrective action after swaps or transitions.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
What makes this records review different from a general file audit?
The scope is tied to 2022 pw1500g dual shutdown 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 lease transition or engine swap 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 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.