Why Flight Times Are Always Local, Not UTC

Flight times local time confusion usually starts at the same moment: a boarding pass shows a departure time and an arrival time, they are hours apart, and the flight duration printed next to them does not seem to add up. Nothing is wrong with the ticket. Both times are correct, and they are simply not measured on the same clock. Once that rule is in front of you, the confusing cases stop being confusing.

Every time on a ticket is local to the airport it names

The rule is short: a departure time is local to the departure airport, and an arrival time is local to the arrival airport. Neither is converted to your home time zone, and neither is Greenwich or Coordinated Universal Time (UTC), the reference clock the aviation industry actually runs on behind the scenes. The Standard Schedules Information Manual, the IATA reference document airlines and their systems use to exchange schedule data, carries a dedicated appendix for exactly this: UTC-to-local-time comparisons across every country and its daylight-saving rules, because two airlines in two countries need one shared way to translate a local time back to the same underlying moment.

That single rule explains almost everything that looks strange on a schedule. A flight that departs at 22:40 and arrives at 06:15 is not a five-and-a-half-hour flight with bad arithmetic. It is a flight of whatever duration the airline actually flies, with the departure clock reading one zone and the arrival clock reading another, and the difference between the two zones baked invisibly into the two printed times.

Two clocks, one flight

Picture a long westbound route where the departure city and the arrival city sit several hours apart on the clock, such as Singapore to London. Singapore Changi Airport sits eight hours ahead of UTC year-round. London sits either on UTC or one hour ahead, depending on the season. A flight that leaves Singapore in the late evening, local Singapore time, and spends the whole night in the air lands in London in the local afternoon, because the clock in London has been running hours behind the clock in Singapore the entire time the aircraft was airborne. Nothing about the flight changed; the reference clock did.

The same shape shows up on Shanghai to Frankfurt, a similarly long westbound route between two cities with a wide time-zone gap. A flight leaving Shanghai in the morning can land in Frankfurt on the same local afternoon it left, purely because Frankfurt's clock started that many hours behind Shanghai's before the aircraft ever took off. Read the two departure and arrival times as two separate, unrelated clocks, each doing its own job, and the schedule stops looking like it is lying to you.

Eastbound flights work the same rule in the opposite direction: the arrival clock jumps ahead of the departure clock, so a short flight can appear to eat far more clock-hours than it actually flies. The rule never changes. Only which direction it pushes the visible gap does.

When an overnight flight seems to land before it left

The case that actually confuses people, more than the hours, is the date. An overnight flight can show an arrival date one day later than its departure date, the same day, or, on the most extreme routes, appear to land before it took off by the calendar. None of that is an error in the schedule. It is the local-time rule plus the International Date Line, the reference line running roughly along the 180th meridian where the calendar date changes by a full day as you cross it.

Wikipedia's summary of the mechanics states the rule plainly: crossing the date line eastbound moves the calendar date back by one day, and crossing it westbound moves the calendar date forward by one day. A flight that departs late at night, local time, from a city just west of the line and lands in the morning, local time, in a city just east of it can show an arrival date that reads earlier than the departure date on the ticket, even though the aircraft was in the air for the number of hours everyone would expect. It has not travelled through time. It has crossed into a zone where the calendar had not yet turned over.

The date-line effect is separate from the ordinary time-zone effect described above, and the two stack on the longest routes. A flight can lose or gain hours from the time-zone difference and lose or gain a full calendar day from the date line, on the same ticket, and the two effects do not cancel each other out just because they point in opposite directions.

Reading a route page without losing a day

Three habits fix almost every case of this confusion, and none of them require converting anything by hand.

First, treat the departure time and the arrival time as belonging to two different, self-contained clocks, and never subtract one from the other to get a flight duration. The flight duration is its own separate figure, published alongside the two times precisely because the times themselves cannot be used to calculate it.

Second, when a flight lands the next calendar day, or the same day, or, rarely, the previous one, read that as the local-time and date-line rules doing their job, not as a scheduling mistake. If the date looks wrong, check which side of the date line each airport sits on before assuming an error.

Third, when you are meeting someone off a long flight, plan around the arrival airport's local date and time only. Converting the arrival time into your own time zone is useful for knowing when to expect a call, but it is not the number the airport, the airline or anyone on the ground is using to run the arrival.

How TrackMyWings helps

TrackMyWings™ is a live flight-tracking platform in development. A private beta shipped on 2026-08-24, Android only, on the Play internal testing track, and public launch has no fixed date. Once it launches, a live map and a shared view for the person waiting are planned features, built around exactly this kind of confusion: telling you plainly what time and what date a flight actually lands in, rather than leaving you to do the time-zone arithmetic yourself.

Questions people ask

Are flight times shown in local time or UTC? Local time. A departure time is local to the departure airport and an arrival time is local to the arrival airport. Neither is converted to UTC or to your own time zone; UTC is the reference clock the industry uses behind the scenes to keep every local time consistent.

Why does my flight arrival date look wrong? It usually is not wrong. An overnight flight can land the next calendar day, the same day, or, when it crosses the International Date Line, appear to land a day earlier than it left. Check which side of the date line the departure and arrival airports sit on before assuming an error.

Can a flight really land before it takes off, by the calendar? By the printed calendar date, yes, on certain date-line crossings, even though the flight has not travelled backward through time. The effect comes from crossing into a zone where the date has not yet advanced to match the zone the flight left from, not from anything unusual about the flight itself.

Sources

• IATA, Standard Schedules Information Manual (SSIM) overview, https://www.iata.org/en/publications/manuals/standard-schedules-information/ (captured 2026-09-23)
• Wikipedia, "International Date Line," https://en.wikipedia.org/wiki/International_Date_Line (captured 2026-09-23)
• timeanddate.com, "Can a Flight Land Before It Takes Off?" https://www.timeanddate.com/time/flights-land-before-leave.html (captured 2026-09-23)