Reduce Airport Pickup No-Shows: Dispatch Drivers by Actual Arrival Time

Dispatching on the scheduled time means idle drivers or waiting passengers. Here's how to trigger airport pickups on the real landing — using flight status and live position.

July 22, 2026 · · 5 min read

Airport pickups are unforgiving. Dispatch a driver on the scheduled arrival and one of two things happens: the flight is late and your driver burns an hour at the curb, or it lands early and your passenger is left waiting. Both cost money and goodwill. The fix is simple in principle — dispatch on the actual arrival — and an API makes it automatic.

Why scheduled time is the wrong trigger

A scheduled time is a guess made months ago. Real arrivals drift by delays, early landings, holding patterns and diversions. Every minute your dispatch is wrong is either idle driver time or passenger waiting time. Tracking the flight closes that gap — and the whole thing runs off a handful of API calls.

Step 1 — watch the flight

Poll the flight's status. You get the live disposition plus gate, terminal and estimated times:

curl "https://api.flightnerve.com/airline/KEY?num=136&name=AA"
→ status: "Delayed"  ·  estimated 14:35  ·  terminal 3  ·  gate 41

Statuses like Scheduled, Delayed, In Air, Diverted and Arrived are first-class — you branch on them directly instead of guessing from timestamps.

Step 2 — get a live ETA while it's airborne

Once the flight is in the air, its live position gives you a minute-level ETA — enough to tell the driver exactly when to leave:

curl "https://api.flightnerve.com/track/KEY?num=136&name=AA"
→ [{ "status":"In Air","latitude":51.1,"longitude":-1.2,
     "groundSpeed":430,"updatedAgo":"1 min ago" }]

Step 3 — fire the dispatch on wheels-down

When the status flips to Arrived, trigger the pickup — send the driver, notify the passenger, start the meet-and-greet clock. That single transition is the event your whole workflow hangs on, and it's the difference between a driver waiting an hour and one arriving just in time.

Handle the messy cases

• Diversions. A Diverted status means the passenger isn't landing where you booked — surface it immediately.
• Gate & terminal changes. These update as the flight progresses; pass the latest to the driver so the meet point is right.
• Early arrivals. Just as common as delays — the live ETA catches them too.

Doing it at fleet scale

Managing a whole airport's worth of pickups? One call lists every aircraft inbound to a hub, with distance and ETA — a live board to sequence your drivers against:

curl "https://api.flightnerve.com/airspace/KEY?inbound=DXB"

The dispatch timing model

Dispatching by the timetable guarantees waste: dispatch too early and the driver idles (or the meter runs); too late and the client stands at the curb. The fix is to dispatch against a live model of when the client actually reaches the pickup point, not when the flight is scheduled to land. That model is: estimated landing (from the live position) + taxi-in + immigration and baggage + the walk to the car. Each term is tunable per airport, and the first, landing time, comes straight from tracking the airborne aircraft.

# when will the client reach the car?
pickup_eta = landing_eta + taxi_in + border_and_bags + walk_to_curb
dispatch_at = pickup_eta - drive_time_to_airport - safety_margin

Handling the hard cases

Most no-shows and long waits come from a handful of scenarios a naive "scheduled time" dispatch cannot see:

• Diversions. The flight lands somewhere else entirely. Watching live status catches it; a timetable never will.
• Go-arounds and holds. The aircraft is over the field but has not landed; a position-based ETA absorbs the extra minutes automatically.
• Early arrivals. Tailwinds can land a long-haul 20-30 minutes early; dispatching on the live estimate means the driver is already there.
• Multi-leg numbers. Pin the exact arriving leg by its destination so you never dispatch for the wrong airport.

Measuring the impact

The wins are easy to quantify. Track two numbers before and after: average driver wait time (idle minutes between arriving on-site and the client appearing) and no-show / re-dispatch rate. Teams that switch from scheduled-time to actual-arrival dispatch typically see both fall sharply, fewer wasted driver-hours and far fewer stranded clients, which is money on both sides of the ledger.

Frequently asked questions

Should I dispatch on the scheduled or the actual arrival time?

Actual. Estimate landing from the live aircraft position and add taxi, border, baggage and walk time, then work backwards to when the driver should leave.

How do I detect a diversion in time to react?

Poll the flight’s status as it approaches; a diverted flight surfaces as a Diverted status with a new destination, which a timetable-based flow would miss entirely.

What if the flight arrives early?

Because you dispatch against the live estimate rather than the schedule, an early arrival simply moves the dispatch time earlier, so the driver is waiting, not the client.

Does an empty position response cost me anything?

No. If the flight is not airborne yet, the live-position response is empty and free, so you can check as often as you like before it departs.

Getting started

FlightNerve puts all of this behind a single API key: flight status, live position, airports, routes and live airspace, in one clean JSON shape. It is free to start, no card required. Create a key, make your first call in a minute, and browse the documentation or the airlines and airports we track on the Airlines and Airports pages.