Skip to content
Skip to main content
OnArrival

Flight truth, pushed in seconds.

A standalone status layer: subscribe to any flight, including bookings made anywhere else. Schedule changes, delays, gates, belts, diversions and cancellations arrive as one normalised event stream, pushed within seconds with a confidence score attached.

Illustration: a traveller sits calmly in an airport seating area checking a phone while one dot on the minimal departures board above has turned warm apricot
flights tracked live, every day
100k+
median, source change to webhook
<5s
carriers — the same graph Flights books
517+
Inventory

Every source disagrees. We referee.

The airline, the airport and the aircraft each tell a different story about the same flight. We listen to all three and hand you one answer with a confidence score.

AIRLINE

Airline systems

Schedules, operational messages and departure control data across the same 517+ carriers the Flights graph books, from NDC majors to operator-direct LCCs.

517+ carriers
AIRPORT

Airport & ground

Airport operational databases for gates, terminals, stands and baggage belts: the ground truth the airline feed often learns last.

Gate + belt level
AIR

Airborne positions

ADS-B and radar-derived positions confirm what actually happened: real off-block, real wheels-up, and diversions caught mid-flight.

Live positional feed
MODEL

The confidence model

When sources conflict, each field resolves to a winning value with a score and full attribution. You choose the threshold at which your app speaks up.

Per-field confidence
How it works

Subscribe once. We push.

Subscribe with a carrier, flight number and date; one call returns the current state and registers your webhook. From then on we push: schedule change, delay, gate, terminal, baggage belt, diversion, cancellation, each as a typed event with old value, new value and confidence attached, within seconds of any source changing. The flight does not need to be booked through OnArrival.

Read the reference 
POST /v1/flight-status/subscriptions
{ "carrier": "6E", "flight": "1407",
  "date": "2026-09-04",
  "webhook": "https://api.you.com/flight-events" }

// pushed 4s after the gate moved
{ "event": "gate_change",
  "old": "B12", "new": "C04",
  "confidence": 0.98,
  "source": "airport_aodb" }
In depth

From polling to push.

Rate-limited polling loops, source reconciliation and alerting pipelines are plumbing, not product. All of it is on our side of the API.

01

One event schema, every source

Airline systems, airport operational databases and airborne positional data emit wildly different messages. They arrive at your webhook as one typed event: what changed, old value, new value, when, and how sure we are.

Normalise
02

The confidence model

Sources disagree constantly: the airline says on time, the airport says the stand is empty, the transponder says the aircraft never left the origin. Each field carries the winning value with a confidence score and full source attribution, so you decide when to notify.

Resolve
03

Gate, terminal, baggage belt

The changes that actually ruin a travel day rarely reach the airline app in time. Gate and terminal moves and belt assignments push as first-class events, down to the last belt change after landing.

Ground
04

Diversions, detected in the air

Positional data catches a diversion while the aircraft is still flying, often before any official feed admits it. The event carries the new destination and a revised arrival estimate.

Airborne
05

Historical on-time performance

5 years of punctuality per route, carrier and flight number: delay distributions, cancellation rates, seasonal patterns. Set expectations at booking time, or price risk with it the way our Travel Fintech underwriting does.

History
06

Standalone by design

Flight Status is an independent service. Subscribe to any scheduled flight by number and date, including bookings made on other platforms or none at all. No OnArrival booking is required, ever.

Standalone
Capabilities

The Flight Status surface

Track
  • Per-flight subscriptions
  • Schedule changes
  • Delay + revised estimates
  • Gate / terminal / belt
  • Diversions + cancellations
Push
  • Webhooks within seconds
  • Signed payloads
  • Retries with backoff
  • Event replay
  • Digest + batch mode
Data
  • Per-field confidence scores
  • Source attribution
  • 5-year on-time history
  • UTC + local timestamps
  • Actual off-block to on-block times
Integrate
  • REST + webhook API
  • Bulk subscribe
  • Current-state endpoint
  • Sandbox with replayed disruption days
  • No booking required
The point

Polling an airline every five minutes is undifferentiated heavy lifting. Subscribe once and the change finds you, whether the trip was booked on your platform, ours, or nowhere near either.

— an independent service, no booking required
Flights tracked daily100k+
Source change to webhook<5s
Carriers covered517+
Who it's for

Where Flight Status earns its keep.

OTA & TMC

Travel sellers

Tell travellers before the airline does. Delay, gate and cancellation events feed notifications, duty of care and proactive rebooking, with confidence scores deciding when to speak.

"Our app beat the departures board to the gate change."
Fintech & super-apps

Cards & apps

You see the ticket purchase on the card. Subscribe to the flight behind it and your app becomes the travel companion, without selling a single ticket.

"We status-track flights our users bought anywhere."
Insurer

Parametric products

Delay and cancellation events with confidence and timestamps are the trigger feed for parametric payouts, the same feed our own Travel Fintech products settle on.

"The payout lands while the traveller is still at the gate."
Questions

Before you integrate Flight Status.

Something we haven’t covered? Talk to the team. A real engineer answers, never a bot.

Illustration: an airport operations officer calmly places one warm apricot token on a board of uniform blue on-time markers while a traveller nearby checks a phone
Do I need to book flights through OnArrival to use Flight Status?

No. Flight Status is a standalone service. Subscribe to any scheduled commercial flight by carrier, number and date, whether it was booked on your platform, through OnArrival, or anywhere else. Bookings made through our Flights API can auto-subscribe if you want them to.

Airlines, airports and trackers disagree. Whose number do I show?

Ours, with a score. Every field resolves to a winning value through the confidence model, with the raw sources and their timestamps attached. Set a threshold and only notify travellers above it; below it, hold back or show a range.

How fast do events actually arrive?

Median under 5 seconds from a change appearing in any source to your webhook receiving the typed event. Delivery is signed, retried with backoff, and replayable if your endpoint was down.

Which events are covered?

Schedule changes, delay and revised-estimate updates, gate, terminal and baggage-belt changes, diversions and cancellations, plus actual off-block, take-off, landing and on-block times. Each event carries the old value, the new value, confidence and source attribution.

Can I poll instead of using webhooks?

Yes. Every subscribed flight exposes a current-state endpoint that answers from our store, not from a live upstream call, so reads are fast and never rate-limited by an airline. Most integrations still poll only as a reconciliation sweep; push is the point.

How far back does the historical on-time data go?

5 years of punctuality per route, carrier and flight number: delay distributions, cancellation rates and seasonal patterns. Use it to set expectations at booking time or to price risk, the way our Travel Fintech underwriting does.

Pairs well with

One product is rarely enough. Compose them.

Related reading

All field notes →
Technical · 11 min

Your dashboard stops at checkout

Search latency gets measured because it emits a span. The six weeks between a confirmation and a boarding gate emit nothing, which is why the only post-booking monitor most travel products run is the support inbox.

Manan VaghasiyaOperations · 10 min

Post-booking is the trust product

Checkout wins one transaction. What you do during a schedule change, a cancellation and a refund decides whether there is a second one.

Ankit SawantTechnical · 9 min

The NDC capability matrix

The certification levels people still quote were retired in 2022. What a flight product needs instead is a matrix: the dimensions on which one carrier's NDC connection differs from another's, because those differences decide what your checkout and your support team can do.

Aditi Acharya
Start building
Wire Flight Status into your stack with a sandbox key.