Boeing 747 non-routines
Boeing 747 family non-routine card records review
This review follows the non-routine cards raised during a Boeing 747's checks from the reported defect through to a final sign-off. It is run for the party evaluating the asset when the way findings were dispositioned tells the real story of a check. The work reads defect cards, engineering dispositions, corrective-action entries, and the closure that released each item. You receive an exception list of non-routines that do not close, a source map tracing each defect to its disposition and sign-off, and a closure plan for the findings whose resolution is unclear.
When this review is needed
- A heavy check turned up structural findings and the buyer wants to see how each was dispositioned.
- A non-routine register lists open items the redelivery accepted and someone has to clear them.
- A finding was dispositioned by an engineering call and the approved data behind it needs checking.
- A corrective action was carried out but the card that should close it cannot be found.
The problem
Non-routines are where a 747 check gets interesting, because they capture what was actually wrong with the airframe. A defect card raised, an engineering disposition applied, a repair carried out, then a sign-off that closes the loop, but any one of those steps can be missing. A finding dispositioned on an engineering call without the approved data to back it, or a corrective action with no closing card, leaves the register saying the item is handled when the file cannot prove it.
What gets reviewed
- The non-routine register reconciled to the cards actually raised during the check
- Each defect card matched to its engineering disposition
- Corrective-action entries confirmed against the disposition they implement
- Approved data checked where a disposition authorized a repair or alteration
- Final sign-offs confirmed for every card the register lists as closed
- Structural findings cross-checked against the repair map and program
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
- Every defect card carries an engineering disposition appropriate to the finding
- Corrective actions match the disposition and are recorded against the card
- Dispositions that authorize a repair reference approved or acceptable data
- Each card the register calls closed has a final sign-off releasing it
- Structural findings are reflected in the repair map and any program task they trigger
Evidence normally required
- The non-routine register for the check under review
- The defect cards raised during the check
- Engineering dispositions and any approved data they cite
- Corrective-action entries and final sign-offs
- The repair map and program the structural findings feed
Common discrepancies
- A defect card with a corrective action but no final sign-off closing it
- A disposition that authorized a repair without an approved-data reference
- A structural finding that never made it onto the repair map
- An open non-routine carried from a prior check and never resolved
What is at stake
An open non-routine that was never closed becomes an inherited liability the current owner carries into the next transaction. A disposition without approved data behind it can force re-substantiation of a repair, and a corrective action with no closing sign-off cannot be shown to have released the aircraft from the defect at all.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Reconcile the register
Match the non-routine register to the cards actually raised during the check.
Trace each finding
Follow every defect card to its disposition and corrective action.
Check the basis
Confirm approved data where a disposition authorized a repair, and a final sign-off where the register claims closure.
List the open items
Flag the findings that do not close and plan their resolution.
What the buyer receives
- An exception list of non-routines that do not trace to closure
- A source map from each defect through disposition to final sign-off
- A closure plan for the open findings and unsupported dispositions
Who uses the output
- Asset managers reading the airframe's real condition history from its findings
- Records teams clearing open non-routines before a redelivery or sale
- Engineering confirming a disposition rests on data before it is relied on
How the work fits into the transaction or program
The review runs after a check produces its findings and before the register is relied on at redelivery or sale. Its exception list drives closure of the open items and recovery of the missing dispositions, and the traced register becomes the record of how the airframe's defects were actually resolved.
Aircraft-specific considerations
A 747's age and structure mean heavy checks routinely surface significant findings, so the non-routine register is dense and its structural entries carry the most weight. Freighter conversions concentrate findings around the main-deck floor and door structure, so the review reads those areas against the conversion and repair history for the serial number.
Jurisdiction-specific considerations
The approved-data path an engineering disposition can rely on differs between an FAA and an EASA system, so a disposition accepted under one register may need re-examination for the other. The review notes where a finding's disposition will require attention for the receiving authority.
Regulatory limits
The review traces each finding to its recorded closure and reports what is supported. It does not disposition a defect, approve a repair, or determine that the aircraft is airworthy.
What this review does not cover
- Dispositioning any finding or performing any corrective action
- Developing or approving the data behind a disposition
- Any airworthiness determination on the aircraft
Specific to this review
- The non-routine register is the truest record of a 747's condition, because it captures what was actually found wrong rather than what was scheduled.
- A finding closed by an engineering disposition is only defensible if the approved data it cites is in the file, and that data is the piece most often missing.
- A structural non-routine has to appear on the repair map as well as in the register, so a finding present in one and absent from the other signals a broken link.
Sources
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. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
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
How is this different from reviewing the routine task cards?
Routine cards show the scheduled work was done. Non-routine cards show what the check found and how it was resolved, which is where the airframe's real condition and the engineering judgment behind each fix are recorded. The two reviews complement each other and are often run together.
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.