Repair file integrity
Reconciling an airline's structural repair file to source after re-indexing
When an airline migrates its maintenance system or digitizes legacy records, the structural repair map can survive while the dossiers behind it scatter. This reconciliation retraces every mapped repair to its damage report, accomplishment record, and approval data inside the post-migration archive. Continuing-airworthiness and records teams run it after the cutover settles and before the file faces an audit, a fleet transaction, or an authority review. It produces a proven map-to-dossier index, a register of repairs that no longer trace, and recovery actions ordered by airworthiness relevance.
When this review is needed
- A maintenance information system cutover moved repair records and the mapping has never been proven repair by repair.
- Legacy paper dossiers were scanned and the fleet's repair charts now reference digital objects of unknown quality.
- A continuing-airworthiness audit is scheduled and structural records are a likely sample.
- Aircraft are being marketed or returned off lease and the repair file must be transaction-grade.
The problem
Airline structural records span decades and formats: microfilmed dossiers, scanned heavy-check packages, and native entries in two or three successive systems. A migration carries the map forward as data while the substantiating documents travel separately as attachments, exports, or boxes. Afterward the map looks complete, and the team only learns which links died when someone pulls a specific repair under audit pressure.
What gets reviewed
- Every entry on each aircraft's repair map traced into the post-migration archive
- Damage reports and non-routine cards matched to their mapped repairs
- Approval data located and checked for coverage of the repair as recorded
- Repair-generated inspection requirements verified as still present in the maintenance program after cutover
- Legacy-format dossiers assessed for legibility and completeness after conversion
- Cross-fleet patterns in where the migration dropped or duplicated structural documents
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
- Each mapped repair opens to a complete dossier in the live system, not to a dead link or placeholder
- Dossier contents match the map entry: location, dimensions, and repair type agree
- Approval references inside dossiers resolve to documents that exist in the archive
- Repair-driven repetitive inspections survived the cutover into the current program build
- Scanned legacy dossiers remain readable at the level an auditor would require
Evidence normally required
- Current repair maps for the affected fleet
- The post-migration records archive and the migration mapping specification
- Pre-cutover exports, backups, or manifests where they exist
- Heavy-check and non-routine records for the migration-era period
- The current maintenance program build with repair-driven task listings
Common discrepancies
- Map entries whose attachments were dropped when file sizes exceeded a migration limit
- Dossiers split across the old and new systems with neither holding a complete set
- Repetitive inspections tied to repairs that lost their linkage during program conversion
- Duplicate map entries created by the migration that hide a single unsubstantiated original
What is at stake
A repair that cannot be traced to its approval data reopens as a question about the airplane, and under EASA continuing-airworthiness review or an FAA records inspection that question escalates quickly. Fleet transactions inherit the same weakness: every untraceable dossier found by a buyer's team during marketing costs more than finding it internally would have.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Recover the boundary
Assemble pre-cutover manifests and the migration specification to define what should exist.
Trace map to dossier
Open every mapped repair in the live archive and verify the dossier is complete and legible.
Restore program links
Confirm repair-driven inspections still run in the current maintenance program.
Register and generalize
Log untraceable repairs with recovery routes and report defect patterns for the next fleet's cutover.
What the buyer receives
- A map-to-dossier index proving traceability for every reconciled repair
- An untraceable-repairs register with recovery route and airworthiness relevance for each
- A migration-defect summary the airline can apply to remaining fleets before their cutover
Who uses the output
- CAMO and continuing-airworthiness leads answering authority reviews
- Records teams prioritizing dossier recovery across the fleet
- Fleet and asset managers preparing aircraft for lease return or sale
How the work fits into the transaction or program
The reconciliation belongs to post-migration assurance, alongside AD status and LLP verification. Its untraceable-repairs register feeds the airline's normal discrepancy process, and the proven index becomes the reference the next lease return or audit starts from instead of starting cold.
Jurisdiction-specific considerations
EASA operators face structural records questions through the airworthiness review cycle under Regulation 1321/2014, where a broken dossier link can hold up an ARC recommendation. FAA operators meet the same records through 14 CFR 91.417 inspections and transaction diligence. Fleets spanning both registries need the reconciled index to satisfy the more document-hungry of the two reviews.
Regulatory limits
The work restores and proves document traceability. It does not assess the repairs themselves, approve data, perform airworthiness reviews, or issue findings on the aircraft's condition. Any airworthiness question raised by an untraceable repair goes to the airline's engineering and its authority for disposition.
What this review does not cover
- Airframe inspection or repair condition assessment
- Development or approval of replacement repair data
- Execution of the records system migration itself
Specific to this review
- Attachment-size limits are a recurring silent killer in migrations: large scanned heavy-check dossiers fail to transfer while small ones succeed, skewing loss toward exactly the biggest repairs.
- Structural dossiers are the least standardized record class in an airline archive, which is why automated migration verification clears them at higher false-pass rates.
- Reconciling one fleet before migrating the next converts findings into prevention; the defect classes repeat almost exactly across cutovers.
- An untraceable repair on a leased aircraft is a lessor claim waiting for redelivery; the recovery window is widest while the airline still operates the aircraft.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Our migration vendor certified a 100 percent record count match. Is reconciliation still needed?
Count matches confirm objects moved, and say nothing about which object landed under which repair or whether attachments survived intact. Structural files fail on linkage and legibility, which only opening the dossiers repair by repair can prove.
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.