Flight Delay Tracker

A flight delay is a moving comparison between the schedule passengers were sold and the latest timing known for the aircraft. The schedule gives the baseline, but the useful delay reading changes as the trip moves from planned departure, to estimated departure, to actual takeoff, to arrival and gate completion. A flight can push back late and recover time in the air, or leave close to schedule and lose time because of holding, arrival congestion, runway changes, or gate availability.

The first question is identity, not minutes. A flight number may refer to a daily service, a marketing-carrier code-share, an operating-carrier record, or a nearby variant returned by a flight data provider. Overnight trips add another trap: the correct search date is usually the scheduled local departure date, even when the aircraft arrives after midnight at the destination.

Delay information becomes easier to trust when the record, route, and phase all agree. The same number can appear on rows with different carrier labels, and a provider may update estimates several times during a disruption. A pickup driver cares mostly about arrival timing, while a passenger at the airport may care about departure gate timing, missed connections, and whether the carrier has classified the flight as cancelled, diverted, active, or landed.

Departure delay and arrival delay answer different planning problems. Departure delay matters for airport timing, crew handoffs, and missed outbound slots. Arrival delay matters for connections, pickups, hotel shuttles, curfews, and baggage pickup. A small departure slip can disappear in flight, while a modest en-route hold can turn an on-time departure into a late arrival.

Status words also need restraint. Airport and airline systems can revise estimates during a disruption, and early delay estimates are often less stable than later updates. A timing readout helps decide what to check next, but high-stakes travel changes still belong with the operating carrier, airport notices, and the passenger-rights rules that apply to the itinerary.

How to Use This Tool:

Use sample mode for a no-key walkthrough, or turn it off when you are ready to query a selected flight data provider.

1. Enter one Flight number, such as DL105 or SA101, then set Flight date to the scheduled local departure date.
2. Choose Data source. AeroDataBox (RapidAPI) expects a RapidAPI key, while AviationStack expects its own API key.
3. Keep Use sample data on when you only need the demo flight. Turn it off for live data, then enter the key for the selected source.
4. Open Advanced when the first result needs adjustment. Include codeshares, Include cancelled, Result limit, Match strategy, Request timeout, and Proxy prefix change how many rows can be returned and how strict the lookup should be.
5. Click Fetch status. If the result says no matching flights were found, check the departure date, provider choice, sample setting, and exact-versus-relaxed matching before changing the flight number.
6. Read Flight status first to confirm the selected row. Then compare Delay Timeline and Delay Minutes Chart for departure-versus-arrival movement.
7. Use Flight Matches whenever multiple rows appear. Select the route and carrier row that matches the itinerary before copying, downloading, or exporting the result.

Interpreting Results:

Confirm the identity fields before reading the delay. Flight, Route, Flight date, and Source should match the trip you mean to check. A precise delay attached to the wrong code-share, route, or departure date is worse than an empty lookup.

Positive delay values mean the latest actual or estimated time is later than scheduled. Negative values mean the latest time is earlier than scheduled. Dep delay and Arr delay can disagree because taxi time, airborne routing, holding, and gate availability affect different parts of the trip.

• On time means no disruption wording was found and the derived delay did not cross the warning thresholds.
• Delayed begins when the larger departure or arrival delay reaches 15 min, or when an active scheduled flight is more than 5 min late.
• Diverted / Severe delay appears for diversion wording or a delay of at least 60 min, unless the provider has already classified the flight as landed.
• Landed means the status text indicates arrival, but terminal, gate, baggage, or final timestamps may still update.
• Cancelled should be verified with the carrier before travel changes, especially when cancelled rows were hidden and then re-enabled.

Do not treat a delay category as passenger-rights advice. Refunds, amenities, rebooking, or compensation depend on carrier policy, route, jurisdiction, cause, and the size of the schedule change, not only on the timing fields shown here.

Technical Details:

Flight status records usually combine identifiers, route fields, departure timing, arrival timing, aircraft details, and a provider status word. The useful comparison depends on bringing those fields into the same shape: one selected flight, one route, one departure section, one arrival section, and delay minutes for each phase.

Delay minutes are derived from timestamp pairs. The scheduled timestamp is the baseline. The actual timestamp is preferred when the phase has happened; otherwise the estimated timestamp is used as the current forecast. When a provider does not supply enough timing data for a phase, a zero-minute display should be read cautiously because missing timestamps can look the same as no derived delay.

Formula Core:

The delay equation is applied separately to departure and arrival after each available timestamp is parsed.

For a scheduled departure at 10:00 and an actual departure at 10:18, Dep delay is +18 min. If the actual departure is not available yet but the estimate is 10:12, the same formula displays +12 min. The sign is preserved, so an actual arrival at 14:55 for a 15:00 schedule displays -5 min.

Status Rule Core:

Lookup and Match Boundaries:

The chart uses the same departure and arrival delay rows as the timeline. Values at or above 15 min are treated as material delays, and values at or above 60 min are treated as severe unless earlier status wording, such as landed or cancelled, has already decided the category.

Accuracy and Privacy Notes:

Flight status data is provider-assisted when sample mode is off. The selected flight number, departure date, provider choice, and the credential needed by that provider are used for the live lookup.

• Sample mode uses synthetic flight data and avoids a live provider request.
• Provider keys and the optional proxy setting are kept for the current browser session and are not placed into share links.
• Live lookups are sent to the selected provider or to the configured proxy when one is supplied. That path can see the flight number, date, credential, and provider request.
• A configured proxy can see the forwarded lookup, so use one only when you trust that path.
• Provider feeds may lag the airline, airport, or operating carrier during active disruptions.
• Copied, downloaded, or exported results can contain route, aircraft, timing, and provider details. Treat them as travel or operational records.

Worked Examples:

Checking a sample arrival pickup

Enter SA101, leave Use sample data on, and fetch the default provider sample. The result shows a Route like JFK → LHR, Dep delay near +10 min, and Arr delay near +18 min. For pickup planning, the arrival side matters more than the departure slip because the arrival estimate is the time the driver will feel.

Reading a threshold crossing

If a selected row shows Dep delay of +14 min and Arr delay of +16 min, the larger delay crosses the 15 min rule and the category becomes Delayed. If the arrival estimate later improves to +8 min and the provider status wording has no disruption signal, the same row can move back toward On time.

Sorting out code-share noise

A live search can return several rows with similar carrier names and the same city pair. Open Flight Matches, compare Flight, Status, Departure, Arrival, and Delays, then select the row that matches the itinerary. If hiding code-shares removes the passenger-facing flight number, turn Include codeshares back on and verify the carrier name before exporting.

Recovering from a failed lookup

If the result panel reports an API-key error, provider response error, timeout, or no matches, switch Use sample data on to confirm the page can render a result. Then check Data source, the key field, Request timeout, Proxy prefix, and Flight date. A valid flight number on the wrong departure date can still return an empty match list.

FAQ:

Glossary:

Scheduled time

The planned departure or arrival time used as the baseline for delay minutes.

Estimated time

The provider's latest forecast before an actual event time is available.

Actual time

The recorded departure or arrival event time after that phase has happened.

Code-share

A flight sold under one carrier's code while another carrier may operate the aircraft.

Departure date

The local scheduled date used to identify the right daily instance of a repeated flight number.

Provider

The selected flight data source used for live status, route, timing, and match details.

References:

• Gate Departure Time reporting guidance, Bureau of Transportation Statistics.
• Understanding the Reporting of Causes of Flight Delays and Cancellations, Bureau of Transportation Statistics.
• Fly Rights, U.S. Department of Transportation.
• Refunds, U.S. Department of Transportation.
• Aviationstack API Documentation, APILayer.
• AeroDataBox API Official Documentation and Playground, AeroDataBox.