Status integrity
Reconciling status lists with the records behind them
A status-to-source mismatch means the summary an MRO is working from, or about to hand back with the aircraft, disagrees with the documents underneath it. This remediation reconciles the two: each disputed status line is read against its source task card, log entry, or certificate, the correct value is established, and the status product is amended under change control. Quality leadership commissions it when sampling, a customer challenge, or an escape investigation exposes the disagreement. The output is a corrected status set with a documented basis for every change, plus a defect analysis showing where the mismatches came from.
When this review is needed
- A quality sample found status lines that contradict the task cards or certificates they summarize.
- A customer's records team challenged the status set delivered at check exit and the challenge held up.
- Induction planning worked from a customer-supplied status that the shop's own findings keep disproving.
- An escape investigation traced a missed task to a status entry that never matched its source.
The problem
Status lists are compiled artifacts, built by keying data from whatever arrived at induction: the customer's spreadsheet, a prior operator's export, a summary of a summary. Once inside the shop's planning system, those entries steer work scoping and get restated on exit documentation as if the shop had verified them. When a discrepancy surfaces, the quality team cannot tell how deep it runs, because a mismatch found by sampling implies others that sampling missed.
What gets reviewed
- Definition of the mismatch population: which status products, which record types, which aircraft or events
- Line-level reconciliation of disputed entries against task cards, log entries, and release certificates
- Extension sampling to estimate how far beyond the known mismatches the problem reaches
- Root-cause classification: keying error, stale source, wrong revision, or inherited defect from customer data
- Controlled correction of the status product with a change note per amended line
- Notification package for downstream holders of any status version already distributed
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 corrected line cites the specific source document that establishes the new value
- Source documents used for correction are themselves complete, signed, and applicable to the event
- Corrections preserve the prior value and its provenance rather than overwriting history
- Extension samples are drawn from batches compiled by the same process as the known failures
- Distributed copies of the status product are identified so no superseded version keeps circulating
Evidence normally required
- The disputed status products and their revision history
- The source records for the affected events: task cards, non-routines, certificates, log entries
- Induction data as received from the customer, kept distinct from shop-generated data
- The shop's compilation procedure and records of who keyed what
- Any customer challenge correspondence defining the known mismatches
Common discrepancies
- Entries keyed from a customer-supplied summary that the shop's own source documents contradict
- A status compiled against one revision of a requirement while the work was signed against another
- Corrections made informally in a working copy, creating two versions with no note explaining either
- Mismatches concentrated in one compilation batch, pointing at a single process failure rather than random error
What is at stake
A status product that leaves the shop wrong propagates the error into the customer's records system under the MRO's name, and the correction later arrives as a customer claim rather than an internal fix. Inside the shop, planning built on bad status either over-scopes work the records say is due or, worse, under-scopes work the summary wrongly shows accomplished.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Scope the population
Fix which status products and record types are implicated and freeze the affected versions.
Reconcile line by line
Establish the correct value for each disputed entry from its source document.
Sample outward
Test adjacent batches to bound how far the defect extends beyond the known cases.
Correct under control
Amend the status set with change notes, notify holders of superseded versions, and hand root causes to quality.
What the buyer receives
- A corrected status set with a change note and cited source for every amended line
- A reconciliation report quantifying mismatch rates by record type and compilation batch
- A root-cause summary the quality system can act on
- A superseded-version notice for every party holding an earlier copy
Who uses the output
- Quality leadership closing the finding and feeding the root cause into corrective action
- Records control issuing the corrected status product and retiring superseded versions
- Program managers answering the customer with evidence instead of assurances
How the work fits into the transaction or program
The remediation sits inside the MRO's quality loop: the finding triggers it, the corrected status product closes the immediate exposure, and the root-cause summary feeds corrective action so the next check does not rebuild the same defect. Where the aircraft has already departed, the notification package limits how far the wrong version travels.
Jurisdiction-specific considerations
Shops working under both FAA and EASA approvals often produce status documents shaped by each customer's regime, and the same underlying source record may be summarized differently for each. Reconciliation therefore anchors on the source document itself, with FAA guidance such as AC 43-9C and the operator's continuing-airworthiness obligations under Regulation (EU) No 1321/2014 framing what the summary is required to represent.
Regulatory limits
This engagement corrects the status product against source records. It certifies nothing, confers no approval, and leaves airworthiness and release decisions with the certificate holders involved; a corrected summary is a better summary, never a substitute for the source evidence.
What this review does not cover
- Re-performance or re-inspection of the maintenance the records describe
- Redesign of the shop's records or planning systems
- Arbitration of commercial liability between the MRO and its customer
Specific to this review
- Mismatches cluster where data was keyed from customer-supplied summaries, because those entries never passed through the shop's own verification.
- A status corrected without a change note simply creates a second conflicting version, and reviewers who find two versions trust neither.
- The urgency of a mismatch scales with distribution: an error in a working copy is a defect, the same error in a delivered status set is a customer notification event.
- Batch-level concentration is diagnostic gold; if failures share a compiler, a date, or a source file, one process fix closes the whole population.
Sources
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.
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.
Frequently asked questions
The status list came from the customer. Is the mismatch our problem?
Once the shop plans work from it or restates it on exit documentation, yes, at least partly. Reconciliation keeps the origins separate for exactly that reason: entries traced to customer data are corrected and flagged as inherited, entries the shop introduced are corrected and fed to internal corrective action, and the report gives both parties a factual basis for whatever commercial conversation follows.
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.