Major vs minor repair classification source evidence review

When this review is needed

• A current status line depends on earlier work, a replacement part, or a superseded requirement.
• The aircraft, engine, or component changed configuration after the original entry was made.
• A transition reviewer asks why inspections stopped, limits changed, or an N/A call was made.
• The team needs a clean bridge from old records to the current compliance position.

The problem

The hard cases are rarely blank files. They are files where the earlier evidence was real, then a later modification, AD revision, or component swap changed what must be proven now.

What gets reviewed

• Map the current configuration before accepting the status answer.
• Link superseded entries, prior inspections, replacements, and open corrective actions.
• Check repair entries, structural work descriptions against Appendix A categories, presence or absence of 337s against the active requirement.
• Identify status lines that need a revised basis rather than another copy of the same record.
• Document why each N/A, closed, or next-due position is defensible.

What gets validated

• Pass when old and current requirements are bridged without losing applicability.
• Fail when a stopped repetitive task lacks the modification or replacement record that allowed it to stop.
• Check replacement parts for serial continuity and release evidence.
• Reject any closure that cites an obsolete requirement without explaining the current one.

Evidence normally required

• repair entries
• structural work descriptions against Appendix A categories
• presence or absence of 337s
• approved data for each
• status list

Common discrepancies

• This file structural repairs signed off as minor with no substantiation.
• reviewers reclassifying repairs at pre-buy.
• generating instant findings.
• EASA transfer reviews rejecting minor-classified repairs that Appendix A calls major.

What is at stake

Unbridged configuration changes can make a closed line look current when it is stale. That creates audit findings, transition delays, and avoidable arguments over whether more inspections or documents are due.

How the work runs

What the buyer receives

• Configuration evidence matrix for major vs minor repair classification
• Supersedure bridge table for major vs minor repair classification
• Open correction tracker for major vs minor repair classification
• Acceptance risk summary for major vs minor repair classification

Who uses the output

• structures engineer uses the output to decide what can be accepted and what needs escalation.
• IA or inspector uses it to update status, request missing records, or brief the counterparty.
• records analyst uses it to close administrative items without losing technical reservations.

How the work fits into the transaction or program

The whether repairs in the records were correctly classified as major or minor under Part 43 Appendix A, because misclassification decides whether a 337 and approved data should exist; the repair entries, structural work descriptions against Appendix A categories, the presence or absence of 337s and approved data for each. The evidence set centers on the repair entries, structural work descriptions against Appendix A categories, the presence or absence of 337s and approved data for each. The likely weak points are major structural repairs signed off as minor with no substantiation, reviewers reclassifying repairs at pre-buy and generating instant findings, EASA transfer reviews rejecting minor-classified repairs that Appendix A calls major. Handoff: structures engineer, repair classification disputes during review, Major vs minor repair classification source.

Jurisdiction-specific considerations

Where FAA requirements interact, the output keeps each authority's evidence trail separate.

Regulatory limits

The review cannot replace an authority decision, approved maintenance program, engineering approval, or release certificate. It documents the evidence position so authorized teams can make their own determinations.

What this review does not cover

• Engineering redesign or new approval data
• Release to service or conformity sign-off
• Maintenance program approval changes

Specific to this review

• Supersedure errors often survive because the old AD line still looks closed.
• Configuration proof must travel with the affected asset, not solely with the operator's fleet file.
• A bridge table is usually clearer than a long narrative when several AD numbers or revisions are involved.
• The scope uses the Major Minor Repair Classification question as the control point, so the review stays tied to Repair classification disputes during review and the buyer decision behind it.
• The evidence starts with Major vs minor repair classification status entry and follows Records Review Source Evidence 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 structures engineer: 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 Part Appendix Behind Every questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
• The handoff value comes from Configuration evidence matrix for major vs minor repair classification; 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 Reassess major versus minor classification of recorded repairs and identify where required 337s and approved data are missing..

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits