Cycle-count discrepancy
Inconsistent cycles-since-new (CSN) data
Inconsistent cycles-since-new data means the recorded flight cycles for an airframe, engine, or life-limited part disagree across logbooks, status lists, and the tracking system. It is a problem for lessors, airlines, and MROs because cycles drive life-limited part retirement and cycle-based limits. The check reconciles cycle counts against the flight-cycle history, the logbook totals, and the limits each part is held to. You receive the points where the cycles diverge, the supported count, and its effect on every cycle-limited part and inspection.
When this review is needed
- An engine or aircraft is being valued and the cycle count drives how much life-limited part life remains.
- A cycle-limited part is approaching retirement and the count used to schedule it cannot be confirmed.
- A status-list cycle figure disagrees with the shop report that recorded the count at the last visit.
- A part moved between assets and its cycles do not reconcile with the cycle history it accumulated on.
The problem
Cycles govern the retirement of life-limited parts, so a cycle discrepancy is not a scheduling nuisance but a question about how much value remains in the asset. A status list, a logbook total, and a shop report can each carry a different cycle figure after a count was estimated, a flight leg was logged as multiple cycles, or a migration rounded the number. The part that looks to have years of life left may have far fewer cycles to run once the count is reconciled to source.
What gets reviewed
- Recorded cycles-since-new for the airframe, engines, and life-limited parts
- Logbook cycle totals reconciled against the flight-cycle history
- Cycle counts at each shop visit against the status list life remaining
- Multi-cycle and touch-and-go counting where a flight leg accrues more than one cycle
- Cycle-limited inspections and airworthiness items scheduled from the disputed figure
- Life-limited part cycles against the cycle history of the engines they have been 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
- Cycles-since-new agrees across logbooks, status lists, and the tracking system
- The logbook cycle total reconciles with the recorded flight-cycle history
- Cycle counts at shop visits match the status-list life remaining carried forward
- Multi-cycle legs are counted consistently across the recorded life
- Life-limited part cycles are consistent with the engines they accumulated on
- Cycle-limited task and retirement due points are recalculated against the reconciled count
Evidence normally required
- Airframe and engine logbooks or their digital equivalents
- Flight-cycle and utilization history covering the recorded life
- Life-limited part status list stating cycles since new and life remaining
- Shop-visit reports stating the cycle count at each event
- The maintenance-tracking baseline and any migration records
Common discrepancies
- A status-list cycle count that disagrees with the last shop report
- A logbook cycle total that does not reconcile with the recorded flight legs
- Multi-cycle or training legs counted as single cycles in part of the history
- A life-limited part whose cycles exceed the engine history it was fitted to
- A migration that rounded or reset the cycle count without reconciliation
What is at stake
An understated cycle count can carry a life-limited part past the cycles it was actually entitled to, which is a serious airworthiness exposure. An overstated count retires a part early and destroys usable value. At a transaction, a cycle figure that cannot be tied to source undercuts the life-limited part valuation, and the gap is far cheaper to settle before the deal than after.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Collect the counts
Gather cycles-since-new from the logbooks, status lists, shop reports, and tracking system for each item.
Reconcile to flight history
Test each cycle total against the recorded flight-cycle history and check how multi-cycle legs were counted.
Establish the supported count
Determine the cycle figure the source evidence supports for the airframe, engines, and life-limited parts.
Recalculate life and limits
Recompute life remaining and due points for cycle-limited parts and inspections against the reconciled count.
What the buyer receives
- A reconciliation showing where the cycle counts diverge and by how much
- The supported cycles-since-new for each item, with the basis stated
- The recalculated life remaining and due points for cycle-limited parts and tasks
Who uses the output
- Asset and acquisition teams pricing life-limited part life into a transaction
- Continuing-airworthiness teams correcting the cycle baseline and retirement schedule
- Engineering deciding how to treat a part whose cycles cannot be reconciled
How the work fits into the transaction or program
The review settles the cycle count before life-limited part life is priced or scheduled, and it pairs with the traceability review, since a reconciled count is only useful if the chain behind it holds. It feeds the discrepancy register and the engine valuation that the transaction depends on.
Aircraft-specific considerations
Cycle counting conventions vary by engine and operation type. Short-haul and training operations accrue cycles fast and may log multi-cycle legs, so the reconciliation is read against how the asset was actually flown rather than a single assumed cycle-to-hour ratio.
Regulatory limits
The review reconciles recorded cycles against source evidence and recalculates the figures that depend on them. It does not retire or re-life a part, approve a maintenance program, make an airworthiness determination, or set the corrected count on the operator's behalf.
What this review does not cover
- Physical inspection or retirement of any part
- Approval or revision of the maintenance program itself
- Any airworthiness determination or regulatory approval
Specific to this review
- A cycle discrepancy is a valuation problem as much as a safety one, because cycles, not hours, retire most life-limited parts.
- Training and short-haul operations can log multi-cycle legs, so a flat cycle-to-hour ratio is treated as a red flag rather than a shortcut.
- An understated cycle count is the more serious failure, because it can carry a life-limited part beyond the cycles it was entitled to run.
- The reconciled count is stated with its basis, since the cycle figure directly sets the retirement point of a critical rotating part.
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. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
Frequently asked questions
Why do cycle discrepancies matter more than hour discrepancies?
Most life-limited parts are retired on cycles, so a cycle error changes how much certified life a part has left. An understated count can carry a part past its limit, and a transaction prices remaining life directly off the count.
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.