Engine AD evidence
PT6A CT blade and vane pairing evidence review
owners, operators, Aircraft records teams use this page when PT6A overhaul or aircraft sale puts the Engine AD status line under review. The work traces Engine AD status line and CT blade removal and installation records to Shop visit build record, Authorized release certificate, current status data, and supplied acceptance criteria. Findings identify missing source pages, unsupported applicability, serial or location conflicts, and open corrective evidence. The buyer receives a cited register, evidence map, request list, and closure plan.
When this review is needed
- A PT6A overhaul or aircraft sale is approaching and the records owner needs a page-level proof set.
- The summary status uses shorthand that cannot be defended without the underlying task, release, or configuration record.
- A counterparty has asked which exceptions are true blockers and which are retrieval issues.
The problem
Engine AD status line evidence often looks complete until the reviewer asks which page proves the actual aircraft, engine, component, or location. The review focuses on those trace points instead of accepting inherited status language.
What gets reviewed
- Trace each affected CT blade to the shop event where it was removed, inspected, replaced, or retained.
- Compare vane ring configuration notes with the blade combination claimed in the status line.
- Check that release certificates identify the installed parts and the engine serial number.
- Review the logbook entry for date, time, cycles, and maintenance release reference.
- Separate compliance evidence from ordinary overhaul work scope notes.
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 blade serial, vane reference, engine serial, and release record all point to the same event.
- Fail when a shop package lists replaced blades but omits the matching vane combination evidence.
- Pass when the AD status line cites a source page rather than a summary inherited from a prior owner.
- Fail when a component certificate exists but cannot be tied to the engine installation record.
Evidence normally required
- engine AD status extract
- shop visit work package
- blade and vane serial number list
- authorized release certificates
- logbook installation entries
- life-limited part records
Common discrepancies
- Blade replacement noted in the work scope but missing serial numbers.
- Vane configuration carried forward without the source inspection sheet.
- Release certificate filed with purchase paperwork rather than the engine build package.
- Status list closed with a shop visit date that does not match the logbook release.
What is at stake
If the gap survives to closing or delivery, the next owner may inherit a disputed status line and a harder retrieval problem. Schedule, reserve, or acceptance decisions can then rest on assumptions instead of records.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Frame 2022 Pt6a
Confirm the exact event, affected file set, buyer role, and decision standard before any engine ad status line is treated as sufficient.
Trace Replacement Evidence
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 Vane Pairing
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Compressor Turbine
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
- Engine AD evidence discrepancy log with source-page citations
- Evidence map for accepted, rejected, and unresolved lines
- Targeted retrieval list for records owners
- Closure brief for technical and commercial decision makers
Who uses the output
- Director of maintenance uses the register to decide which lines can be accepted or escalated.
- Powerplant engineer uses the evidence map to request missing technical records.
- Technical records manager uses the closure plan for transaction, audit, or delivery decisions.
How the work fits into the transaction or program
AD 2022-08-13 applies to all P&WC PT6A-34, -34B, -34AG, -114, and -114A engines, requiring replacement of certain compressor turbine vanes and removal of CT blades operated with those vanes, following low-time CT blade fractures tied to specific blade and vane repair combinations; reconstruct which blade and vane part numbers, including repaired vanes, were installed together and for how long, because compliance depends on the combination history rather than a single part. The evidence set centers on engine AD status extract, shop visit work package, blade and vane serial number list, and authorized release certificates. The likely weak points are overhaul records that list assemblies without vane repair provenance, hot section inspections that changed parts without recording the pairing, and utility operators' fragmented logbooks breaking the operating-hours calculation. Handoff: director of maintenance, PT6A overhaul or aircraft sale, PT6A CT blade and vane pairing.
Jurisdiction-specific considerations
FAA and TCCA 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
This work is an evidence review only. It does not approve a repair, modification, inspection, manual revision, aircraft, engine, appliance, or part, and it does not replace the regulator, authorized release personnel, operator, or maintenance organization.
What this review does not cover
- Physical inspection or borescope work outside the records set
- Engineering approval of repairs or alternate methods
- Commercial negotiation of credits or reserves
Specific to this review
- For this review, combination-history evidence matters because the AD closure depends on what blade and vane hardware was together, not solely on whether parts were replaced.
- A recurring records trap is that pT6A records often split useful evidence across engine logbooks, shop traveler pages, and component certificates.
- A sale file can show a compliant current build while leaving the historical pairing basis unproved.
- The scope uses the 2022 Pt6a Blade Replacement question as the control point, so the review stays tied to PT6A overhaul or aircraft sale and the buyer decision behind it.
- The evidence starts with Engine AD status line and follows Evidence Review Vane Pairing 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 Director of maintenance: 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 Engine Compressor Turbine Blades questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Engine AD evidence discrepancy log with source-page citations; 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 CT blade and vane combination history under the PT6A CT blade AD..
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 2022 pt6a blade replacement and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block pt6a overhaul or aircraft sale or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is engine 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 director of maintenance 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.