Time en route, block time and why they differ
Time en route is airborne time for the leg: distance divided by ground speed. Block time is the whole thing, chocks to chocks, and it is the number your flying school bills, your operator schedules against and your maintenance programme counts. The gap between them is taxi, run-up, holding, the climb and the descent — and on a short sector that gap can be half the block time.
The arithmetic is trivial because of the units. A knot is one nautical mile per hour by definition, so 250 NM at 125 kt is 2.0 hours with nothing to convert. In minutes, multiply by 60: ETE = 60 × d ÷ GS. That relationship is also why nautical miles survived: one nautical mile is one minute of latitude, so distance, time, speed and position all share the same arithmetic on a chart.
The estimate is only as good as the ground speed you feed it, and ground speed is the one number on a flight plan that depends on a forecast. A 10% error in the forecast wind on a long leg is an ordinary occurrence, and it moves your arrival by the same 10%. That is why this calculator shows the estimate at ±20% of your planned speed alongside the headline figure: the spread, not the point value, is what you should carry reserves against.
For the flight plan itself, ICAO item 16 wants total estimated elapsed time from take-off to the destination — airborne time, not block time — while your logbook and the billing system usually want block time. Getting the two the wrong way round is a common and expensive habit.
Working it in your head
Two mental methods cover almost everything. The first is the nautical-miles-per-minute trick: divide your ground speed by 60 and you get miles per minute. At 120 kt that is 2 NM per minute, so a 90 NM leg is 45 minutes. At 150 kt it is 2.5, at 180 kt it is 3, and at 480 kt it is 8. Most pilots memorise the one number for their aircraft and never do the division again.
The second is minutes per ten miles, which is 600 divided by ground speed: 5 minutes per 10 NM at 120 kt, 4 at 150 kt, 3 at 200 kt. This one is better for the descent and the approach, where you are working in tens of miles rather than hundreds.
Adding it to a clock time is where errors creep in, because clock arithmetic is base 60 crossing into base 24. Convert to minutes past midnight, add, then convert back: 1400Z is 840 minutes, plus 130 minutes of block time is 970, and 970 ÷ 60 is 16 remainder 10, so 1610Z. If the total exceeds 1440 you have crossed into the next UTC day, which matters on the flight plan date and matters even more when your local date and the UTC date disagree.
Two allowances are worth being deliberate about. The taxi allowance is ground time and belongs in block time and fuel, but not in the airborne estimate you file. The climb and descent allowance exists because your cruise ground speed does not describe the profile: you climb slower than you cruise and you descend faster, and on a short sector you may never reach cruise at all.
Worked example: 250 NM at 125 kt, off blocks at 1400Z
A typical cross-country in a light single. Track distance 250 NM, planned ground speed 125 kt after applying the forecast wind, ten minutes of taxi at a towered field, no separate profile allowance.
- Time en route in hours. 250 ÷ 125 = 2.00 hours.
- In minutes. 2.00 × 60 = 120 minutes, which is the figure for flight plan item 16 as 0200.
- Block time. 120 + 10 = 130 minutes, or 2.17 decimal hours for the logbook.
- Off blocks in minutes past midnight. 14 × 60 = 840.
- Arrival in minutes. 840 + 130 = 970.
- Back to clock time. 970 ÷ 60 = 16 remainder 10, so the ETA is 1610Z. At UTC−4 that is 1210 local.
Now test the estimate. If the wind is 20% worse than forecast and you make good 100 kt, the leg becomes 150 minutes and the arrival slips to 1640Z. If it is 20% better at 150 kt, you arrive at 1550Z. That fifty-minute spread is the real planning envelope, and your fuel reserve has to cover the slow end of it, not the middle.
What to do with the numbers
Time en route goes on the flight plan and into the fuel calculation. Take it to the fuel burn calculator with your fuel flow: the airborne time drives cruise fuel, and the taxi allowance is a separate item on top.
Decimal hours is what almost every logbook, rental agreement and maintenance record wants. Note that 45 minutes is 0.75 hours, not 0.45 — a mistake that compounds silently across a hundred entries. Hobbs meters read in decimal hours directly, which is why rental time and block time rarely match to the minute.
Block time is your schedule and your billing. It also sets crew duty accounting for commercial operations, where the difference between airborne and chocks-to-chocks over a day of short sectors is substantial.
The ETA matters beyond politeness. Filing an estimate and then failing to arrive or cancel triggers search and rescue procedures. If the leg is running slower than planned, revise the estimate with air traffic control or your flight-following service rather than hoping to make it up.
Finally, watch the spread in the sensitivity table. If a 10% ground speed error moves your arrival past sunset, past a curfew, or past your legal fuel reserve, the plan is not robust and the answer is more fuel or a fuel stop rather than a more precise forecast.
Time for a leg at common ground speeds
| Ground speed | NM per minute | Minutes per 10 NM | Time for 100 NM | Time for 250 NM |
|---|---|---|---|---|
| 80 kt | 1.33 | 7.5 | 75 min | 3 h 08 |
| 100 kt | 1.67 | 6.0 | 60 min | 2 h 30 |
| 120 kt | 2.00 | 5.0 | 50 min | 2 h 05 |
| 150 kt | 2.50 | 4.0 | 40 min | 1 h 40 |
| 200 kt | 3.33 | 3.0 | 30 min | 1 h 15 |
| 250 kt | 4.17 | 2.4 | 24 min | 1 h 00 |
| 400 kt | 6.67 | 1.5 | 15 min | 37 min |
| 480 kt | 8.00 | 1.25 | 12.5 min | 31 min |
Memorise the miles-per-minute figure for your aircraft's normal cruise and most en-route timing becomes mental arithmetic.
Where flight time estimates go wrong
- Using true airspeed instead of ground speed. The whole point of the wind triangle is that these differ. Compute ground speed first with the ground speed calculator.
- Using straight-line distance for a route with turns. Airways, terrain avoidance and departure procedures all add track miles. Sum the legs rather than measuring the great circle, unless you really are flying direct.
- Applying cruise ground speed to the climb. A light single climbing at 80 kt indicated for fifteen minutes has covered far fewer miles than a cruise estimate suggests. That is what the profile allowance is for.
- Converting minutes to decimal hours by moving the decimal point. Forty-five minutes is 0.75 hours. Divide by 60, always.
- Forgetting the date change. An evening departure with a long leg lands on the next UTC day, and your flight plan carries a date as well as a time.
- Mixing local and UTC. Aviation runs on UTC. Do the arithmetic in UTC and convert at the very end, not in the middle.
- Planning to the point estimate. The forecast wind is a forecast. If a 10% miss breaks the plan, the plan is too tight.
Where this sits in flight planning
Flight planning runs in a fixed order and this calculator is the third step. First get the distance: for short legs read it off the chart, for long ones use the great circle distance calculator. Second get the ground speed: convert indicated to true airspeed, then apply the forecast wind with the ground speed calculator or the wind correction angle calculator. Third, this page. Fourth, fuel — take the time to the fuel burn and reserve calculator.
For multi-leg routes, work each leg separately and sum the times. The wind is different on each leg because the course is different, and averaging courses before applying the wind gives an answer that can be several minutes out over a few hundred miles. The same applies to the descent: if you are planning an arrival, the top of descent calculator tells you where the cruise segment ends.
A note on the clock. Aviation uses UTC — Zulu — everywhere except the terminal area procedures that quote local time, precisely to avoid the ambiguity of time zones and daylight saving on a flight that crosses both. Filed estimates, METAR and TAF validity, NOTAM windows and flight plan dates are all UTC. Convert to local for the passengers, not for the plan.
This tool gives planning estimates. Regulatory fuel and reserve requirements, and any operator's own scheduling rules, take precedence over anything computed here.