Flight-hours discrepancy
Inconsistent time-since-new (TSN) data
Inconsistent time-since-new data means the recorded flight hours for an aircraft, engine, or component disagree across logbooks, status lists, and the maintenance-tracking system. It is a problem for lessors, airlines, and MROs before a return, an induction, or an hours-based inspection falls due. The check reconciles total time in service against utilization history, logbook running totals, and the tracking baseline. You receive the points where the hours diverge, the corrected running total the evidence supports, and the effect on every hours-driven task.
When this review is needed
- A return condition is stated in hours and the recorded total time does not agree across the logbooks and the status list.
- An hours-based inspection or overhaul is approaching and the figure used to schedule it cannot be confirmed.
- An aircraft moved between tracking systems and the migrated total time does not match the source logbooks.
- A component carries a time-since-new that conflicts with the airframe history it was installed against.
The problem
Total time in service drives a large part of the maintenance program, yet it is carried in several places at once and they drift apart. A logbook running total, a status-list figure, and the number in the tracking system can each differ by tens or hundreds of hours after a data migration, a manual entry, or a period of estimated utilization. The figure looks authoritative wherever it appears, but the question of which one is correct is rarely settled until something forces it.
What gets reviewed
- Recorded total time in service for the airframe, engines, APU, and time-controlled components
- Logbook running totals reconciled against the utilization and flight-log history
- The maintenance-tracking baseline and any migration that reset or carried the figure forward
- Periods of estimated or averaged utilization where actual hours were not recorded
- Hours-based tasks, inspections, and overhauls scheduled from the disputed figure
- Component time-since-new against the airframe history it accumulated on
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
- Total time in service agrees across logbooks, status lists, and the tracking system
- The logbook running total reconciles with the sum of recorded utilization
- A tracking-system migration preserved the figure that the source logbooks support
- Estimated-utilization periods are identified and bounded rather than treated as exact
- Component time-since-new is consistent with the time accumulated on its host
- Hours-based task due points are recalculated against the reconciled figure
Evidence normally required
- Airframe, engine, and APU logbooks or their digital equivalents
- Utilization and flight-log history covering the recorded life
- Status lists stating total time in service for each item
- The maintenance-tracking baseline and any migration records
- Last shop-visit or inspection report stating the hours at the event
Common discrepancies
- A logbook running total that does not match the sum of recorded flight hours
- A tracking-system figure that drifted from the logbooks at a data migration
- A period of estimated utilization carried forward as if it were actual
- A component time-since-new that exceeds the airframe time it was fitted to
- An hours-based task scheduled from a figure the source records do not support
What is at stake
An overstated total time can pull inspections forward and waste life, while an understated total can let a task run past its interval, which is the more serious failure. At a return, an hours figure that cannot be reconciled to source undermines confidence in the whole status, and the discrepancy has to be resolved before the maintenance program can be relied on by the next operator.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Gather the figures
Collect total time in service from the logbooks, the status lists, and the tracking system for each item.
Reconcile to utilization
Test each running total against the recorded flight-log history and identify where the figures diverge.
Establish the supported total
Determine the figure the source evidence supports and bound any period of estimated utilization.
Recalculate dependents
Recompute the due points for hours-based tasks that were scheduled from the disputed figure.
What the buyer receives
- A reconciliation showing where the hours diverge and by how much
- The corrected total time in service that the source evidence supports, with the basis stated
- The recalculated due points for hours-based tasks affected by the correction
Who uses the output
- Records and continuing-airworthiness teams correcting the maintenance program baseline
- Fleet planners rescheduling hours-based tasks against the reconciled figure
- Asset teams confirming the status before a return or transaction
How the work fits into the transaction or program
The review settles the hours figure before it is relied on for scheduling or acceptance, so the rest of a records audit works from a baseline that the source evidence supports. It pairs with the cycles reconciliation, since many tasks are governed by whichever limit, hours or cycles, comes first.
Regulatory limits
The review reconciles recorded time in service against the source evidence and recalculates the figures that depend on it. It does not approve a maintenance program, sign off an inspection, make an airworthiness determination, or set the corrected figure on the operator's behalf.
What this review does not cover
- Physical inspection or any return-to-service action
- Approval or revision of the maintenance program itself
- Any airworthiness determination or regulatory approval
Specific to this review
- An understated total time is the more dangerous error, because it can let an hours-based task run past its interval rather than merely waste life.
- Data migrations between tracking systems are a frequent origin of hours drift, since the carried-forward total is rarely re-reconciled to the logbooks after the move.
- Periods of estimated utilization are bounded as a range rather than corrected to a single number, because the actual hours were never recorded.
- The reconciliation states the basis for the corrected figure, since an unsupported correction is no more defensible than the discrepancy it replaces.
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.
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). Air carrier maintenance recordkeeping and retention requirements under Part 121.
Frequently asked questions
Which figure is correct when the logbook and the tracking system disagree?
Neither is correct by default. The review reconciles both against the recorded utilization and the source records, and the supported figure is the one the underlying evidence actually carries, not the one that appears most often.
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.