Records problem
Maintenance-tracking mismatch with source records
A maintenance-tracking mismatch is when the status produced by a tracking system disagrees with the source documents it is meant to summarize, so the list a buyer or lessee reads is not supported by what is in the records. This page is for lessors, airlines, and maintenance organizations that suspect their tracking output and the underlying evidence have drifted apart. The reconciliation compares the tracking status for ADs, life-limited parts, components, and inspections against accomplishment evidence, release paperwork, and logbook entries, line by line. You receive a reconciliation register showing each disagreement, its source, and the correction needed.
When this review is needed
- A tracking report and the logbooks state different times, cycles, or due values for the same item.
- Data was migrated between tracking systems and the new status was never checked against source documents.
- A status list will be relied on for a return or sale and no one has confirmed it traces to evidence.
- An item shows as complied with in tracking while the accomplishment record cannot be found.
The problem
A tracking system reports status, but it only reflects what was entered into it, which is rarely re-verified against the documents underneath. Initial loads carry forward prior assumptions, manual updates introduce transcription errors, and a program revision can shift due values without the source records moving with them. The output looks authoritative on a single page, so it gets relied on for forecasting, returns, and transactions while the disagreements with the actual evidence stay buried until someone checks.
What gets reviewed
- AD and SB status in the tracking system checked against accomplishment evidence and effectivity
- Life-limited-part life remaining compared to release paperwork and recorded accumulation
- Hard-time and on-condition component status against the entries and certificates behind them
- Inspection and check due values reconciled to the last accomplishment in the records
- Time and cycle datums in the tracking setup compared to the logbook accumulation
- Program revisions and escalations applied in tracking versus what the source records support
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 AD shown as complied with in tracking has accomplishment evidence with a matching method and date
- Life-limited-part life remaining in tracking matches the release paperwork and recorded cycles for the part
- Component due values trace to the last recorded accomplishment rather than an unverified initial entry
- Inspection intervals and last-done dates agree between the tracking report and the logbooks
- Aircraft time and cycle datums in tracking match the accumulated totals in the records
- Program escalations or revisions reflected in tracking are supported by approved program data
Evidence normally required
- Current maintenance-tracking status export for the aircraft and engines
- AD and SB accomplishment records with dates and methods
- Life-limited-part status list and the release certificates behind each part
- Airframe, engine, and component logbooks or digital records
- The applicable maintenance program revision and any escalation approvals
Common discrepancies
- An AD shown complied with in tracking whose accomplishment evidence is missing from the records
- Life remaining on a part that disagrees with the cycles recorded in the logbooks
- A due value driven by an initial load assumption rather than a real last-done date
- Time and cycle datums in tracking that do not match the accumulated totals in the records
- A program revision applied to tracking that the source records do not yet reflect
- Items present in the records that were never set up in the tracking system at all
What is at stake
A status list that overstates remaining life or understates what is due can drive the wrong maintenance plan, misprice an asset, or fail at a return when the evidence is finally pulled. Correcting it late, after a forecast or a deal has been built on it, costs far more than reconciling the status to source before it is relied on.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Export the tracking status
Pull the current tracking status for ADs, life-limited parts, components, and inspections across the aircraft and engines.
Pull the source evidence
Locate the accomplishment records, release paperwork, and logbook entries that each tracking item is meant to reflect.
Compare line by line
Set each tracking value against its source value and record every disagreement with the document behind it.
Specify corrections
State what each item should read and the evidence supporting it, and deliver a status that traces back to source.
What the buyer receives
- A reconciliation register listing each disagreement, the tracking value, the source value, and the gap
- A correction list specifying what each tracking item should read and the evidence that supports it
- A reconciled status view that ties the tracking output back to the source records it summarizes
Who uses the output
- Continuing-airworthiness staff correcting the tracking setup
- Records teams preparing a status list that can be relied on for a transaction or return
- Fleet and planning teams whose forecasts depend on accurate due values
How the work fits into the transaction or program
Reconciliation turns a tracking report into a status that traces to evidence, which is the baseline a return, a sale, or a planning forecast can stand on. It runs alongside an AD status review and a life-limited-part trace, and it depends on a continuous logbook history, so it is often paired with a gap analysis where the records have breaks.
Aircraft-specific considerations
Tracking setups differ by aircraft and engine type in their task structure, life limits, and program references, so the reconciliation is scoped to the specific configuration rather than applied with one generic template across a mixed fleet.
Regulatory limits
This reconciliation confirms whether tracking output agrees with the source records and identifies the corrections needed. It does not make the tracking system the record of compliance, certify the status, or issue any airworthiness determination on the operator's or authority's behalf.
What this review does not cover
- Operating or administering the customer's tracking system on their behalf
- Closure of the underlying maintenance tasks themselves
- Any airworthiness determination or regulatory sign-off on the corrected status
Specific to this review
- A tracking system reflects only what was entered, so its status is a claim about the records rather than the record itself.
- Initial data loads frequently carry forward last-done assumptions that were never tied to a source document, and those drive due values for years.
- A program revision can move due values inside the tracking system without the source records changing, creating a mismatch that looks like normal output.
- The reconciliation treats the source documents as authoritative and the tracking report as the thing to be proven against them.
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.
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). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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
Is the tracking system or the logbook the real record?
The source documents are the record. A tracking system summarizes them and is only as accurate as its inputs. The reconciliation proves the tracking status against those documents and flags every place the two have drifted apart.
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.
Walk through your situation with an engineer who has done this work.