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. None of these match each other when the flight crosses a zone boundary, and the only place the time zones are spelled out is in the IATA code printed next to each airport name.

This is a usability disaster, and it persists because the alternative — printing UTC, or printing both local times — would surface a different problem: most travelers cannot mentally convert their boarding time from UTC to "the time my watch will show when I need to be at the gate." The convention has been "show local times, no labels, trust the IATA codes" since the 1970s and it has not been seriously challenged since.

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.

The mistake this most often produces is missed connections. A traveler sees a 4-hour layover in Frankfurt and assumes that is plenty of buffer; the layover is in fact 4 hours of FRA-local time, which spans both arrival and departure events, and the actual gap between deplaning at one gate and being at the next gate may be 2:30 once you account for arrival hold patterns, immigration, and a Schengen-zone transit at FRA. Always check that printed connection times leave a buffer above the airline's posted minimum connection time (MCT) for that specific airport — and add 30 minutes on top of the MCT for any connection through ATL, LHR, CDG, FRA, or HKG.

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. STA is calculated months in advance from a baseline aircraft type, an average wind, an average ground time at the gate, and historical taxi-out and arrival-hold figures for the route. It is a planning estimate, not a prediction.

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 status the morning of, you are looking at ETA — which is why the answer "the website says 14:25" might be 30 minutes off the original ticketed time.

Actual time of arrival (ATA) is the timestamp recorded when the aircraft's parking brake is set at the gate. This is the time the U.S. Bureau of Transportation Statistics uses to compute on-time performance ^[1]. A flight is "on time" if ATA is within 15 minutes of STA — note: not within 15 minutes of ETA. A flight that touches down on time but waits 25 minutes for a gate counts as delayed.

The cheapest mental model: STA is the marketing time, ETA is the ground-crew time, ATA is the metric time. Three different audiences, three different answers, often three different numbers. 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 — is padded. Airlines have steadily increased block times since the early 2000s, partly because airport ground operations actually have gotten slower (more traffic, smaller margin for ATC delays), and partly because the U.S. DOT's on-time-performance metric is published per airline per route. A schedule that books 7:00 for a flight that physically takes 6:10 has a 50-minute pad: most days the airline arrives on time and posts a clean OTP number; the worst days, the pad absorbs a delay that would otherwise show up in the public data.

The result is the routine "we're arriving early" announcement on long-haul. The flight is not early in any physical sense — the pilots flew at the planned cruise speed, took the planned route, and burned the planned fuel. The aircraft physically arrived at the time the route actually takes, which is less than the time the airline scheduled. The most common pad sizes:

• Trans-Atlantic eastbound: 30–60 minutes of pad. Eastbound flights have stronger jet-stream tailwinds in winter and chronically arrive 20–40 minutes "early."
• Trans-Atlantic westbound: 15–30 minutes of pad. Headwinds eat the pad and these flights more often run late.
• Domestic U.S. east-west routes: 15–25 minutes of pad. Heavy congestion at JFK, LGA, EWR, ORD, ATL, LAX.
• Asia-Pacific long-haul: 30–60 minutes of pad. The tradewind structure and the sheer length of the routes (LAX-SYD, JFK-HKG) leave room for variation.

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, "early arrival" is approximately meaningless: their ground-side appearance is governed by gate availability, customs lines, and bag-claim time, and those don't move with the touchdown clock.

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 travel with you but never connect to cellular do not get the network time-zone broadcast. They keep whatever zone they were last set to. The OS-level "Set time zone automatically" toggle on iOS and macOS uses location services as a fallback, but the toggle is off by default on iPad and on every laptop, and many travelers leave it off because they want their work calendar to stay in their home zone. The result is a device that shows wrong local time at the destination — and worse, that schedules new calendar events in the wrong zone.

Border-region cell coverage. At airports near international borders, your phone may attach to a tower across the border and inherit that tower's time zone. This is most common at GVA (Geneva, Swiss/French border), DTW (Detroit, US/Canadian border), and at smaller European airports near multiple country boundaries. Restart cellular if your clock looks wrong on landing.

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 is the meridian at roughly 180° east-west where the calendar date changes ^[2]. It is not a straight line; it bends east around Kiribati, west around Samoa, and east around the Aleutians, so that all of each affected region 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, before you "left" in destination-local time. The flight still took nine hours; the calendar rotated 24 hours minus 19 hours of zone shift. This is the famous "arrive before you leave" effect. Concorde's transatlantic London-to-New York runs landed before they took off, in local time, by about 90 minutes — for the same reason, scaled down to a 3.5-hour eastbound flight across a 5-hour zone gap.

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. A 45-minute MCT at ATL means the airline believes a passenger can deplane, walk between concourses, and re-board within 45 minutes — and it will sell you the connection if your gap meets this. The MCT does not reflect what actually happens on the ground. It reflects the airline's contractual willingness to rebook you, free of charge, if you miss the connection because the inbound was late.

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: 30–45 minutes is genuinely enough at smaller hubs (DEN, MSP, CLT). At ATL, ORD, LAX, JFK in the afternoon thunderstorm window, add 30 minutes on top.

International-to-domestic in the U.S.: 90 minutes is the absolute floor. You will deplane, queue immigration (15–60 min depending on airport and time of day), claim and re-check your bag, clear customs, re-enter security, and walk to a domestic gate. ATL, MIA, JFK, SFO, and LAX during peak immigration windows can eat 2 hours by themselves. Book 2:30 minimum.

Schengen-to-non-Schengen connections in Europe: AMS and FRA are the most reliable for tight connections. CDG is the worst — the inter-terminal bus rides at peak can take 30 minutes by themselves. Avoid <90 minute CDG transfers between terminals 1 and 2. Eurocontrol publishes a Network Operations Plan annually that documents the worst chokepoints and gives prevailing delay statistics by airport ^[4].

Domestic-to-international in Asia: PEK, PVG, NRT, HND all have substantial inter-terminal transit. ICN is the cleanest. SIN is the cleanest worldwide for tight transit. HKG is fine if both flights are at the main terminal.

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 if both are with the same airline — the airline owes you nothing, and you will be standing at the rebook desk paying for a new flight. Self-connecting on separate tickets is a calculated risk; the airline industry's MCT does 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. The lack of a suffix means same calendar day in destination time — including eastbound long-haul that gains a day at the date line.

Block time is scheduled gate-to-gate minutes; air time is takeoff to touchdown. They differ by 25–45 minutes on a long-haul. 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].

For looking up the local zone at any airport on the network, the airport directory lists every IATA-coded airport with its current local time, IANA zone, and DST schedule. Individual airport pages such as JFK, LHR, and HND carry a live clock and a pointer to the city page where the arrival actually lands.

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 25–60 minutes longer than the air time, with the difference absorbing taxi, holds, and gate-arrival waits.

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 airline, per airport, per terminal, and per connection type (domestic-to-domestic, international-to-domestic, etc.). It is a contractual floor, not a recommendation, and real-world buffers should typically exceed it by 30 minutes or more for any international or congested-airport connection.

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 is the timestamp at which the parking brake is set at the destination gate, and is the value used for on-time-performance statistics. 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. Every commercial airport in the world has a unique IATA code. 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.