Airports and arrival times: how flight schedules really work

What the times on a boarding pass actually mean

Every line on a boarding pass that has a time on it is in local time at one specific airport, with no time-zone label. The departure time is in the departure airport's zone. The arrival time is in the arrival airport's zone. Boarding time, gate-closing time, and any check-in deadline are in the departure airport's zone. When the flight crosses a zone boundary these times are in different zones, and usually nothing on the pass says so; the airport codes are the only clue.

The convention is a reasonable one: what you need at each airport is the time on the local clocks. Printing UTC instead would force every traveller to convert. But it means the printed times cannot be compared directly.

The practical consequence is that you cannot subtract the printed times to get the flight duration. A 23:55 JFK → 11:35 LHR ticket prints as a 11:40 trip but is in fact about 6:40, because the eastbound zone shift adds five hours that disappear into the gap between the two printed numbers. To check the actual block time you have to either look at the airline's published schedule explicitly (most airline websites will show "Duration: 6h 40m" once you click into the leg), or convert one of the times into the other airport's zone using a time zone converter before doing the subtraction.

Connections are a separate trap. Both times of a layover are printed in the connecting airport's local time, so the layover itself is easy to read, but its usable length is shorter than it looks once you allow for a late arrival, the walk between gates, and any passport or security checks. Compare it with the airline's minimum connection time (MCT) for that airport, and leave a margin above it at large or busy hubs.

Scheduled vs estimated vs actual: three different times

Three distinct timestamps describe a flight's arrival, and they are not interchangeable.

Scheduled time of arrival (STA) is the time the airline filed when it published the schedule. STA is the contracted time. It is what shows on your ticket, on the airline's website until the day of departure, and on the airport's monitor when you arrive to pick someone up an hour before. Airlines set it months in advance from historical flight, taxi and delay data for the route and season. It is a planning figure, not a prediction for your particular day.

Estimated time of arrival (ETA) is the airline's current best guess. ETA updates throughout the flight as ATC issues holds, as winds aloft change, and as the destination airport revises its arrival sequence. Flight-tracking apps like FlightAware, Flightradar24, and the airline's own status pages show ETA, not STA. Ground crews and gate agents work from ETA. When you check a flight's status on the day, you are usually looking at the ETA, which is why it can differ from the time on your ticket.

Actual time of arrival (ATA), for on-time statistics, is the time the aircraft arrives at the gate, not the touchdown time. The U.S. Bureau of Transportation Statistics counts a flight as delayed if it arrives at the gate 15 minutes or more after its scheduled time ^[1]. A flight that lands on time but then waits 25 minutes for a gate counts as late.

A simple way to remember it: STA is the timetable, ETA is today's forecast, ATA is the record. When you are picking someone up, watch ETA on the airport's website or on a flight tracker — not the printed schedule.

Block time padding and "early arrivals"

Block time, the scheduled minutes from gate to gate, usually includes a margin. Airlines have lengthened scheduled times on many routes over the past two decades, partly to reflect real congestion and partly because on-time performance is published and compared. A schedule that books 7:00 for a flight that typically takes 6:10 has a 50-minute margin: on most days the flight arrives on time or early, and on bad days the margin absorbs some of the delay.

That is why long-haul flights often announce an early arrival. Winds matter too: on transatlantic routes the jet stream usually speeds up eastbound flights and slows westbound ones, especially in winter, so eastbound flights arrive early more often.

When a flight arrives "early" and waits for a gate, that wait is part of block time too — it counts as on-time. ATA is gate-arrival, not touchdown. If you are picking someone up, an early landing may not mean an early meeting: gate availability, passport control and baggage claim decide when they come out.

Why your phone's clock can lie at the gate

Modern smartphones update the displayed time when they connect to a cellular tower in a new region. The tower broadcasts the network's time zone, the OS reads the broadcast, and the lock screen updates within a few seconds of network attachment. This works well in transit and almost everywhere in life. There are three places it can mislead you, and all three happen at airports.

Airplane mode in flight. Your phone never sees the destination cell tower until you land and re-enable cellular. If you check your phone in flight to see what time you'll land, the clock still shows the departure airport's zone. The fix is to manually set the destination zone before you board, or to look at the in-flight entertainment system (which carries a properly-zoned destination clock).

Wi-Fi-only devices. Tablets and laptops that never connect to a cellular network do not get the network's time-zone information. Their automatic time-zone setting relies on location services instead; if that setting or location access is turned off (some travellers turn it off deliberately to keep their work calendar in their home zone), the device keeps showing the old zone and can create new calendar events in the wrong zone.

Border-region cell coverage. Near a border between two time zones, such as Spain and Portugal, a phone may connect to the neighbouring country's network and take its time. If your clock looks wrong on landing, toggle airplane mode or check the time-zone setting.

The simplest defense is a hardware watch set to a known zone, plus a habit of checking your phone's clock against an unambiguous time source (the airport's own departure boards, the in-flight system, or the world clock widget on a Wi-Fi-connected device) before relying on it for departure or boarding decisions.

Crossing the date line: when calendars rotate under you

The International Date Line runs roughly along the 180° meridian, and the calendar date changes when you cross it ^[2]. It is not a straight line: it bends east around Kiribati and Samoa and west around the Aleutian Islands, so that each country keeps a single calendar day. For flights, the date line has two practical consequences.

Westbound (Asia-bound from the Americas), you skip a calendar day. A Tuesday-evening departure from Los Angeles bound for Sydney arrives Thursday morning. Wednesday is essentially erased from your calendar. If you booked the flight for Tuesday and your hotel for Wednesday, and you didn't notice the date line, you are arriving a day after your check-in. Reputable booking systems handle this correctly — your itinerary will show "Arrives Thursday" — but some calendar apps that store events as a single fixed offset will display the arrival in your home time zone on the wrong calendar day. Always verify the arrival date on your itinerary, not the calendar event your travel app exported.

Eastbound (Americas-bound from Asia), you gain a day. A Saturday-evening Tokyo departure arrives in Honolulu on Saturday morning, earlier by the local clock than it left. The flight takes about seven hours, but Honolulu is 19 hours behind Tokyo. This is the "arrive before you leave" effect. Concorde's westbound London-to-New York flights landed about 90 minutes "before" they took off for the same reason: about 3.5 hours in the air against a 5-hour time difference.

For a deeper treatment of why the date line zigzags and what the maximum 26-hour gap between Kiribati (UTC+14) and Baker Island (UTC-12) means in practice, see The International Date Line, explained.

The date-line bug that recurs in calendar software is the same bug that haunts every distributed-team scheduler: storing a flight as "20:00 LAX → 06:00 SYD" with no zone label, and letting the calendar guess. A correctly-modeled flight has both endpoints stored as IANA zone identifiers (`America/Los_Angeles` and `Australia/Sydney`), and the calendar computes the rendered local time at each end. A travel app that stores flights with fixed UTC offsets will display them wrongly the next time the relevant region changes its DST policy, and will display them wrongly even today across the date line if the offset math wraps the wrong way.

Layovers, MCT, and the buffer you actually need

Minimum connection time (MCT) is the airline-and-airport-specific minimum gap that the booking system will allow between an inbound arrival and an outbound departure on the same itinerary. If an airport's MCT for a domestic connection is 45 minutes, the airline will sell you a connection of 45 minutes or more on one ticket. The MCT is the shortest connection that can normally be made, not a comfortable one. If you miss a connection on a single ticket because the first flight was late, the airline normally rebooks you.

The MCT is a minimum, not a recommendation. Real-world buffer needs vary by airport, by terminal, by time of day, and by the type of connection (domestic-to-domestic, domestic-to-international, international-to-international, Schengen-to-non-Schengen).

Domestic to domestic, same terminal: the MCT is often enough at smaller airports. At large hubs, and in seasons with frequent thunderstorms or snow, more margin helps.

International to domestic in the U.S.: you clear immigration and customs at the first U.S. airport, usually collect and re-check your bag, and go through security again. Queues vary from minutes to well over an hour, so allow considerably more than the domestic MCT; two hours or more is a common rule of thumb at the largest gateways.

Within Europe, Schengen to non-Schengen (or the reverse): you pass passport control between the two areas, and at some airports a terminal change. Allow more time where a terminal change is needed. Eurocontrol's Network Operations Plan covers capacity and delay forecasts for the European network ^[4].

Elsewhere: check whether the connection needs a terminal change, a transit security screening, or a visa, and allow for each.

If the inbound is delayed and the connection is on the same itinerary (single ticket), the airline owes you a rebook. If the connection is on a separate ticket, even with the same airline, the second airline generally has no obligation to you if you miss it, and you may have to buy a new ticket. Self-connecting on separate tickets is a calculated risk; MCT rules do not protect you.

Time-zone idioms in airline data

A few idioms appear on tickets and operational dashboards and are worth recognizing.

LT ("ARR 11:35 LT") just means destination-airport local time, not GMT and not UTC. Z time is UTC, sometimes written "Zulu" in pilot speech — ATC clearances and flight plans are always in Z time, and a pilot's "scheduled into LHR at 1135 Zulu" is 11:35 UTC, which is 12:35 BST in summer and 11:35 GMT in winter. The boarding-pass time is in local civil time, often off by an hour from the Zulu time the pilot mentioned.

+1 / -1 on a schedule arrival means the arrival is one calendar day after (or before) the departure in the destination's local zone. "JFK 23:55 → LHR 11:35+1" departs JFK on the printed date and arrives LHR the next calendar day in London time. No suffix means the same calendar date. Eastbound flights across the date line often show no suffix or a −1, because they land on the same or the previous date.

Block time is scheduled gate-to-gate minutes; air time is takeoff to touchdown. The difference is the taxi time at each end, often 20 to 40 minutes in total. When comparing durations between two airlines, make sure both are quoting block, or both quoting air. The IATA Standard Schedules Information Manual is the source-of-truth for these conventions across the industry ^[3].

An airport keeps the local time of the city it serves, so look up the city: the world clock shows the current time in major cities, and the time zone converter turns a scheduled arrival into your own zone's time for that date.

Glossary

Block time

Scheduled gate-to-gate minutes for a flight, including taxi-out, air time, and taxi-in to the destination gate. Block time is what the airline files in the schedule and what is used to compute on-time performance. It is typically 20 to 60 minutes longer than the air time, the difference covering taxiing, holding and waiting for a gate.

Minimum connection time (MCT)

The shortest gap between an inbound arrival and an outbound departure that an airline's booking system will allow on a single itinerary. MCT is set per airport and often per airline, terminal and connection type (domestic to domestic, international to domestic, and so on). It is a floor, not a recommendation; for international connections and busy airports, more margin is wise.

STA, ETA, ATA

Scheduled, estimated, and actual time of arrival. STA is the time on the published schedule. ETA is the airline's current best guess based on the actual departure time and en-route conditions. ATA, for on-time statistics, is when the aircraft arrives at the gate. The three values can differ by 30 minutes or more.

Zulu time

Aviation-radio shorthand for Coordinated Universal Time (UTC). Air traffic control clearances, flight plans, and pilot communications are always in Zulu time to avoid the ambiguity of local zones. The boarding pass shows local time at each airport; the cockpit operates in Zulu.

IATA code

The three-letter airport identifier assigned by the International Air Transport Association — JFK, LHR, HND, SYD, etc. Most commercial airports have an IATA code, and each code identifies one airport (some codes cover a city's group of airports, such as LON for London). The code is the only piece of an itinerary that unambiguously identifies the airport, since city names can be ambiguous (London has six airports, Paris has three, Tokyo has two main passenger airports).

Date line crossing

A flight whose departure and arrival occur on different sides of the International Date Line, causing the calendar date to shift by one day. Westbound flights skip a day; eastbound flights gain a day. Booking systems handle the date arithmetic correctly, but consumer calendars that store events as fixed UTC offsets rather than IANA zone identifiers can display the arrival on the wrong calendar day.

Block time padding

Schedule margin built into block time to absorb routine delays and protect on-time-performance statistics. A flight scheduled at 7:00 may actually fly in 6:10, with the 50-minute difference absorbing taxi waits, holds, and gate-arrival queueing on average days. The padding is why long-haul flights routinely arrive "early" and then wait for a gate.