Conversion AD evidence
767 conversion pitot static inspection evidence review
For lessors, operators, Aircraft records teams, the trigger is 767 freighter delivery or pre-purchase review where a closed status line must be proven from source evidence. The review checks Conversion STC records and Pitot static inspection record against Approved modification data reference, Inspection task card, maintenance release data, and any contract or audit request. Unsupported claims, timing conflicts, and missing closure records are separated into a register with evidence references and next actions.
When this review is needed
- A record line affects value, acceptance, next-due control, or delivery timing.
- The delivered file proves part of the story but leaves a date, serial, location, revision, or release gap.
- The team needs a narrow records review rather than a full maintenance program audit.
The problem
A clean index can hide weak evidence if the cited page is only adjacent to the required proof. This review keeps administrative completeness separate from a supported technical records position.
What gets reviewed
- Tie the pitot static inspection requirement to the conversion configuration installed on the aircraft.
- Check inspection cards for affected ports, lines, routing, and corrective actions.
- Review approved data references without treating them as proof that work was accomplished.
- The review notes that confirm return-to-service entries identify the converted aircraft and work package.
- Separate delivery punch items from compliance evidence needed for the AD status.
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 converted configuration, inspection card, corrective action, and release entry all agree.
- Fail when a conversion certificate is supplied without the pitot static inspection source record.
- Pass when corrective work is closed against the same affected area identified by the inspection.
- Fail when the delivery file relies on a generic STC reference with no aircraft-level accomplishment evidence.
Evidence normally required
- conversion work package
- pitot static inspection cards
- corrective action records
- approved data references
- aircraft logbook release
- delivery configuration statement
Common discrepancies
- Pitot static inspection evidence missing from the conversion closeout binder.
- Corrective action recorded as a non-routine without reference from the AD status line.
- Approved data index supplied without the aircraft task card.
- Delivery configuration statement not updated after rework.
What is at stake
Poor traceability can reduce confidence in the status report and slow the surrounding transaction. A cited exception list lets the team address the record defect before it becomes a broader dispute.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Frame 2025 767
The review notes that confirm the exact event, affected file set, buyer role, and decision standard before any conversion stc records is treated as sufficient.
Trace Conversion Pitot
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 Review
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package 300 Proving
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
- ad-2025-18-05-767f-conversion-pitot-static-proof evidence register
- Source-page index for each supported compliance or records claim
- Unresolved item list with impact and next action
- Closeout package for the buyer, CAMO, operator, or lessor representative
Who uses the output
- Aircraft records analyst uses the register to decide which lines can be accepted or escalated.
- Conversion program engineer uses the evidence map to request missing technical records.
- Asset manager uses the closure plan for transaction, audit, or delivery decisions.
How the work fits into the transaction or program
AD 2025-18-05 (Amendment 39-23132, effective October 23, 2025) applies to Boeing 767-300 airplanes converted to special freighter under STC ST02040SE and requires a visual inspection of certain first-officer pitot-static rigid tubes and flexible hoses for low points, with corrective action, after conversions installed the tubing incorrectly. The evidence set centers on conversion work package, pitot static inspection cards, corrective action records, and approved data references. The likely weak points are applicability tied to base model rather than the specific conversion STC and service bulletin effectivity, an inspection logged without distinguishing the converted first-officer system, and corrective re-routing closed without the conversion-related substantiation. Handoff: aircraft records analyst, 767 freighter delivery or pre-purchase review, 767 conversion pitot static inspection.
Jurisdiction-specific considerations
FAA 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 is not an approval service or a release function. Final airworthiness, compliance, import, and acceptance decisions remain with the regulator, authorized persons, the operator, maintenance organization, and transaction parties.
What this review does not cover
- On-aircraft troubleshooting
- New design data, repair data, or modification approval
- Signature of maintenance releases or certificates
Specific to this review
- For this review, for converted freighters, the compliance question is tied to the post-conversion configuration, not the passenger baseline.
- A recurring records trap is that an STC reference identifies the design basis but does not by itself prove the aircraft inspection was completed.
- The useful finding set separates missing conversion records from missing maintenance release evidence.
- The scope uses the 2025 767 Freighter Conversion question as the control point, so the review stays tied to 767 freighter delivery or pre-purchase review and the buyer decision behind it.
- The evidence starts with Conversion STC records and follows Pitot Static Evidence Review 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 Aircraft records analyst: 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 Inspection 300 Proving STC questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from ad-2025-18-05-767f-conversion-pitot-static-proof evidence register; 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 the conversion-STC pitot-static inspection and corrective evidence for the 767-300 special freighter AD..
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
Frequently asked questions
What makes this records review different from a general file audit?
The scope is tied to 2025 767 freighter conversion and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block 767 freighter delivery or pre-purchase review or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is conversion stc records, 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 aircraft 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.