Hours to Months

The Hour Meter Says 180, the Calendar Says It Is Due Anyway

Almost every maintenance schedule worth reading is written with two numbers and the phrase "whichever comes first". Change the oil at 250 running hours or at six months. Inspect at 100 hours or at twelve months. The two limits are counting completely different things — one measures wear, the other measures decay — and a planner's job is to work out which of them is going to fire, on which machine, before the machine tells them the hard way.

Conversion factor: the month here is a fixed 730.485 h (30.436 875 days, one twelfth of a Gregorian year), so divide hours by 730.485. A 250-hour service limit is 0.342 months of actual running, while the six-month limit printed next to it spans 4 382.91 hours of elapsed time — the two only meet at about 41.7 running hours a month.

Two Clocks Running at Once

The hour meter counts duty

Running hours track what actually wears: bearing revolutions, thermal cycles, oil shear, filter loading. On a machine in daily use this is the limit that arrives first and the one the interval was really designed around.

The calendar counts decay

Oil oxidises and picks up moisture whether or not the shaft turns, batteries self-discharge, seals harden, treated fuel goes off. Nothing on the hour meter records any of it, which is why a second limit exists at all.

Low utilisation flips which one governs

A standby generator that runs 50 hours a year will never reach a 250-hour limit inside six months; the calendar triggers every single service. The same interval on a rental unit working 200 hours a month is purely an hours rule.

Aviation writes it down most explicitly

Approved schedules routinely pair a flight-hour figure with a calendar one — 50 hours or 4 months for an oil change, 2 000 hours or 72 months for a component — and compliance is against whichever arrives sooner in that operator's pattern of use.

Reading a Dual-Limit Interval Off the Hour Meter

The useful comparison is not hours against hours but running time against elapsed time, and getting there takes both directions of this converter.

Put the hour limit in and see how little running it is

Type 250, 500 or 2 000 into the left field. Spaces used as thousands separators are ignored and a comma works as a decimal point, so a figure copied from a manual goes straight in. A 500-hour interval turns out to be 0.684 months of continuous operation.

Swap to expand the calendar limit into hours

Press the swap button (↔) for mo → h and enter 6 or 12. Six months is 4 382.91 elapsed hours and twelve is 8 765.82 — the size of the window your running hours have to accumulate inside.

Find the utilisation where the two limits meet

Divide the hour limit by the number of calendar months beside it: 250 ÷ 6 is 41.7 running hours a month, 50 ÷ 4 is 12.5, 600 ÷ 6 is 100. Run above that rate and the hour meter governs; run below it and the calendar does, every time.

Copy the bare figure into the asset record

The copy control on each field returns digits alone, no unit and no separators, which is what a maintenance system's interval field or a fleet spreadsheet expects. Ctrl + C inside a field does the same.

This month is a fixed length: 730.485 hours every time, because the unit is defined as one twelfth of a 365.2425-day year. A real January runs 744 hours and a February 672, so when a due date has to land on an exact day, work in days and read the calendar rather than converting through months.

Dual-Limit Intervals and Which Clock Fires First

Typical published intervals with both limits translated into the other unit: the hour limit as months of pure running, and the calendar limit as the elapsed hours it spans. The final column reflects how the equipment is normally used, not a rule.

Asset and task	Hour limit	As months of running	Calendar limit	As elapsed hours	Usually fires first
Piston aircraft — engine oil and filter	50 h	0.068 mo	4 months	2 921.94 h	Calendar, for owners flying under 150 h a year
Aircraft for hire — 100-hour inspection	100 h	0.137 mo	—	—	Hours, no calendar limit exists
Light aircraft — annual inspection	—	—	12 months	8 765.82 h	Calendar, whatever the utilisation
Standby diesel generator — minor service	250 h	0.342 mo	6 months	4 382.91 h	Calendar, standby sets run tens of hours a year
Excavator — engine oil and filters	500 h	0.684 mo	12 months	8 765.82 h	Hours, on any working site
Airliner — A-check	600 h	0.821 mo	6 months	4 382.91 h	Hours, at 250–300 flight hours a month
Life-limited component — overhaul	2 000 h	2.738 mo	72 months	52 594.92 h	Calendar, on lightly flown airframes

The third column is the one that surprises people: a 2 000-hour overhaul limit is under three months of continuous operation, yet the calendar limit sitting beside it covers six years. An airframe that reaches both limits together is running for under 4 % of the elapsed time, and very few do — which is why calendar triggers dominate the workshop diary even though every interval is written hours-first.

Working Both Limits From One Screen

Both limits end up in one unit

Type in either field and the other keeps pace, so an hours limit and a calendar limit can be put on the same scale while you are still reading the manual page.

Calendar limits expand backwards

Swapping the pair gives mo → h, turning a 6- or 12-month rule into the elapsed hours a machine's running time has to fit inside.

Short intervals in days or weeks

The searchable dropdowns carry every time unit here, so a 50-hour task can be read in days and a quarterly inspection in weeks without leaving the page.

Fleet totals stay readable

Thousands are spaced apart and up to eight decimals are kept, so 52 594.92 hours and 0.06844768 months are both legible at a glance.

Questions From the Maintenance Planner

Which limit will fire first on a machine that barely runs?

Work out the crossover rate and compare it with your actual utilisation. Divide the hour limit by the calendar months beside it: a 250-hour or 6-month interval crosses over at 41.7 running hours a month, which is 500 a year. Anything running less than that will hit the calendar every cycle. A standby generator exercised weekly might log 50 hours a year, a tenth of the crossover, so its hour meter is effectively decorative — the service is a calendar event and should be scheduled as one.

Why service equipment at all if the hour meter has hardly moved?

Because the failure modes that idle machines suffer from are not wear-related. Oil oxidises and absorbs water from the air in the crankcase, acids from the last combustion cycle sit on bearing surfaces, starter batteries lose charge and sulphate, diesel grows microbial contamination, rubber seals take a set and coolant inhibitors deplete. None of it registers on a running-hours counter. The bitter irony of standby plant is that the equipment kept for emergencies is exactly the equipment most likely to fail when called, and calendar servicing is the only defence against it.

The mechanical hour meter and the engine controller disagree — which one counts?

Whichever one the manufacturer's schedule refers to, and they genuinely do differ. Some meters run only when oil pressure or an alternator signal is present, some count key-on time, and some controllers log engine hours weighted by load so that an hour at full power counts for more than an hour idling. A unit that idles a great deal can show a controller reading well above the mechanical count. Record which source governs the interval in the asset record, and never mix readings between the two when calculating what is due.

Is the month used here the same as the month on a service sticker?

Not exactly, and the difference is worth knowing. This converter uses a fixed month of 730.485 hours — one twelfth of a 365.2425-day year — while a sticker means a calendar month, which runs from 672 hours in February to 744 in a 31-day month. Over a six-month interval the fixed figure can sit up to about a day and a half either side of the true elapsed time. That is irrelevant when you are sizing an interval or comparing two limits, and it matters a great deal when a regulator wants compliance on a named date, so take the due date from the calendar.

How do I plan a fleet where every unit runs at a different rate?

Give every asset both triggers in the maintenance system and let whichever arrives first raise the work order — a single-trigger schedule will always miss something. Then sort the fleet by monthly running hours against the crossover rate, because that split tells you which machines need meter readings collected and which can simply be diaried. On a mixed fleet with a 500-hour or 12-month interval, the units above 41.7 hours a month generate hour-driven work that clusters unpredictably, while everything below it produces a steady, forecastable calendar load you can staff for a year ahead.