Landed Is Not Here: The Four Timestamps Behind Every Arrival

A flight marked Landed can be forty minutes away from producing a passenger at the curb. That is not a tracking failure. It is what happens when two people watch the same flight through different instruments, and it is the single most common reason an airport pickup goes wrong at O'Hare.

Somebody is waiting in a cell phone lot. Their app says Landed. They drive to the terminal, circle twice, get moved along by an officer, circle again. Eleven minutes later the passenger texts to say they have just reached baggage claim. Nobody did anything wrong. The app was telling the truth. It was answering a different question than the one the driver was asking.

The gap between those two questions has a name in aviation data, and once you can see it you can plan around it.

An arrival is four timestamps, not one

Airlines report flight movements as a sequence of four events, known in the industry as OOOI. The U.S. Bureau of Transportation Statistics and the FAA both collect them, and the entire national picture of airline punctuality is built from them.

• Gate-Out. The moment the aircraft leaves the departure gate, recorded when the pilot releases the parking brake after the doors are closed.
• Wheels-Off. Takeoff.
• Wheels-On. Touchdown on the destination runway.
• Gate-In. Arrival at the gate, recorded when the pilot sets the parking brake at the stand. If the brake is not set, the timestamp is taken from the opening of the passenger door.

Two of these get confused with each other constantly, and they are the two that matter to anyone meeting a passenger.

What Landed means on a consumer flight tracker

Most consumer-facing trackers flip a flight to Landed at Wheels-On. That is the earliest defensible moment to call a flight arrived, it is available from radar data in near real time, and it is genuinely useful if the question you are asking is whether the aircraft is down safely.

It is the wrong signal if the question you are asking is when a person will walk out of a door. At Wheels-On the passenger is strapped into a seat on a taxiway, phone still in airplane mode, potentially a long way from the terminal building.

Notice that the official statistics do not use Wheels-On either. When the Department of Transportation reports that a flight arrived on time, the arrival time it means is Gate-In. A flight that touches down early and then sits waiting for a stand can still be recorded as late, because the metric stops at the gate rather than the runway.

Taxi-in: the gap nobody sees

Taxi-in time is defined as Gate-In minus Wheels-On. It is the portion of your journey that happens after the flight is over and before the flight is over, depending on which definition you are using.

The FAA tracks it closely enough to publish it by airport and by carrier through its Aviation System Performance Metrics program, and the way that data is bucketed tells you something important. Arrivals are grouped into taxi-in bands of under 15 minutes, 15 to 29, 30 to 44, 45 to 59, 60 to 74, and 75 or more.

Read that last band again. A federal agency built a reporting category for arrivals that spend an hour and a quarter between touchdown and the gate. Categories like that do not get created for hypotheticals. They exist because the tail is real, and at a hub the size of O'Hare it is real more often than average.

What makes taxi-in long at ORD

Several things, most of them invisible from outside the aircraft:

• Runway to gate distance. O'Hare's runway layout means an aircraft can land at one edge of the field and be assigned a stand at the far side of a different terminal.
• Gate occupancy. If the previous aircraft has not pushed back, yours holds. This is the most common cause of a long hold and the least predictable.
• Remote stands. When no contact gate is available, an aircraft parks away from the building and passengers are bused in. This adds a full transfer to a journey that the tracker already called finished.
• Ground congestion. A bank of arrivals hitting at once puts aircraft in a queue on the taxiway, exactly as they queue for takeoff.
• Weather. Snow, low visibility, and ground stops all compress and then release traffic in waves, which is worse for taxi times than a steady flow.

The part no dataset measures at all

Here is the uncomfortable bit. Gate-In is where the official record stops, and it is still not the moment your passenger appears. Everything after the parking brake is unmeasured by any public dataset:

• Deplaning, which runs front to back and takes longer the further back you sat and the fuller the aircraft is
• The walk from the gate to baggage claim, which at O'Hare can be substantial depending on concourse
• Waiting for checked bags, which is a function of ground crew load and has nothing to do with your flight's punctuality
• For non-precleared international arrivals at Terminal 5, customs and immigration on top of all of the above

Stack those against a taxi-in that was already longer than the tracker implied, and the distance between Landed on a screen and a person on a curb becomes the largest single source of uncertainty in the whole trip.

Why keying on the wrong signal fails in both directions

A driver dispatched on the scheduled arrival time arrives too early, burns the free waiting window sitting in a lot, and is still there when the passenger emerges late. A driver dispatched on Landed arrives too early in a different way, gets moved along by enforcement, and is circling when the text comes.

Both failures look identical to the passenger. They are standing outside with luggage, and the car is somewhere else.

The compounding case is the one worth flagging. If a flight also arrives ahead of schedule, which happens more often than most travelers expect because airlines build cushion into published block times, then the scheduled-time error and the early-arrival error point in the same direction and add together. We wrote about that separately in why on-time statistics have a blind spot for early arrivals.

What tracking has to do to actually work

Useful arrival tracking is not one number. It is a chain, and each link narrows the estimate:

1. Watch the departure, not the arrival. Tracking begins when the flight leaves its origin. That is the point at which a genuine arrival estimate becomes possible, hours before anything lands.
2. Take Wheels-On as a start signal, not a finish. Touchdown is when the clock on the ground portion starts running.
3. Add the terminal. The gap between Gate-In and curb differs by terminal and by concourse. A Terminal 5 arrival and a Terminal 2 arrival are different problems.
4. Add bag status. Carry-on only removes fifteen to twenty-five minutes of uncertainty in one stroke.
5. Stage, then commit. Hold nearby, move to the curb on a signal from the passenger, not from a screen.

This is why we ask for a flight number rather than an arrival time when you book. An arrival time is a guess you have made. A flight number lets us watch the actual chain, and the difference between those two inputs is most of the value of a pre-booked car. The mechanics are detailed on our arrivals and flight tracking page.

What you can do as a traveler

• Give a flight number to whoever is meeting you. Not a time. This is the single highest-value thing on the list, whether that person is a chauffeur or your brother-in-law.
• Say whether you are checking a bag. It changes the estimate more than almost anything else.
• Send one text at Gate-In. The moment you stand up is a better signal than any tracker, because it is the first data point that includes you rather than the aircraft.
• Know your terminal, not just your airline. Airlines move between terminals, and a stale assumption sends your ride to the wrong building. Our terminal pickup guide covers where each meeting point actually is.
• If somebody is waiting inside, use a greeter. For international arrivals or first-time visitors, meet and greet removes the coordination problem entirely by putting a person at the door instead of a car at a curb.

The takeaway

Landed is a fact about an aircraft. Arrived is a fact about a schedule. Neither is a fact about you. The number that matters to the person holding your bags has no timestamp, no dataset, and no push notification, which is precisely why it has to be estimated from the ones that do.

Anyone can read a tracker. Knowing which of the four numbers to act on is the part that gets a car to the curb at the right minute.