Cycles (Landing Cycles / Engine Cycles)

Aviation maintenance distinguishes between time and cycles because the stress mechanisms on different components are dominated by different operating phenomena. A turbine engine running at cruise produces relatively low stress on its hot-section parts compared to the thermal and mechanical shock of a single start, takeoff thrust application, climb, and shutdown. A landing gear and the surrounding fuselage structure absorb relatively low stress at altitude compared to the impact and ground loads of a single touchdown and rollout. Components dominated by start/stop loading are tracked by cycles; components dominated by running stress are tracked by hours.

For airframes, a cycle is most commonly defined as one takeoff and landing — the touchdown is the cycle event that imposes the dominant fatigue load on the gear, the wing-fuselage join, and the pressurization structure (one takeoff means one pressurization cycle, one landing means one depressurization cycle). Some manufacturers define cycles slightly differently for different structural items, which the Aircraft Maintenance Manual specifies precisely.

For engines, a cycle is the start-to-shutdown sequence with intermediate operation — typically one takeoff cycle counted plus any in-flight thrust excursions that the manufacturer's monitoring rules count as additional partial cycles. Turbine engines track cycles for their life-limited rotating parts (discs, shafts, certain blade rows) under the regulator's safe-life calculation. The Time Between Overhaul or TBO of a turbine engine is typically expressed in both hours and cycles, and the engine reaches the TBO threshold at whichever of the two limits is reached first.

For short-sector flight training operations, cycles dominate the maintenance schedule. A typical training profile of a Cessna 172 is approximately one hour per flight with several touch-and-goes per session — so the cycles-to-hours ratio is materially higher than the equivalent ratio for a long-cross-country profile. Schools that maintain their fleet against an AMP designed around longer-sector operating profiles silently over-fly cycle limits while staying under hour limits — eventually surfacing as airframe inspections coming due ahead of schedule.

For turbine flight training (multi-engine cadet training, regional turboprop type ratings), the cycle premium on engine TBO is operationally significant. An engine that would run 5,000 hours / 7,500 cycles to TBO under an airline operating profile may reach 7,500 cycles long before 5,000 hours under a training profile of three short sectors per hour. The economic implication is that engine-overhaul reserve calculations must use cycles-and-hours pacing in training operations, not hours alone.

Tracking cycles correctly is one of the most error-prone areas of small-fleet maintenance management. The cycle event is implicit — a touchdown happens, but it is not always recorded as a discrete cycle event in the way an engine start is recorded. Schools running a paper or spreadsheet maintenance regime sometimes count cycles by counting flights, which under-counts because a single training flight typically includes multiple touch-and-goes. Other schools count touch-and-goes as full cycles when manufacturer data may treat them as partial cycles. The variance is enough to mis-track fleet cycles by 10 to 20 percent, which propagates into AMP compliance and overhaul reserves.

For turbine operations, the cycle-tracking discipline is more consequential because the part costs are higher. A life-limited turbine disc that is removed at its cycle limit costs tens of thousands of dollars to replace; one that is allowed to run past the limit because of an undercount is a regulatory finding and a structural-integrity issue. Cycle counting for turbines should not be an estimate.

Aviatize tracks cycles per aircraft and per engine as a first-class data field, separate from flight hours and from Hobbs/tach time. The cycle count increments automatically against the rules configured for the operation: a fixed-wing training profile counts each landing as one airframe cycle; turbine engines count cycles per the manufacturer's definition with touch-and-goes counted appropriately; pressurized aircraft count pressurization cycles separately if the AMP requires it.

For LLPs and TBO-controlled components, the platform projects the next-due event in both hours and cycles and alerts on the limiting constraint. A turbine engine projected to reach 5,000 hours in 18 months but 7,500 cycles in 8 months is flagged on the cycles trajectory, with the maintenance-reserve dashboard showing the cycle-driven overhaul as the imminent capital event. For training operators specifically, the cycles-vs-hours separation makes the operational economics of short-sector training visible — an honest input to fleet-renewal and pricing decisions.