Feature

Automatic flight-incident detection

Go-arounds, unstable and missed approaches, rejected take-offs, excursions, and more, flagged automatically across the whole archive, each with a citable page and one-click replay.

Detected-incident panel highlighting an unstable approach
Millions
of flights reconstructed
60,000+
airports covered worldwide
365 days
of history, expanding to 4 years
24 / 7
continuous data processing

Airlines get this kind of visibility from FOQA programs behind closed doors. SkyMeter opens it up: go-arounds, unstable approaches, missed approaches, rejected take-offs, long rollouts, runway excursions, stall-like events, overspeeds, diversions, and off-airport landings are flagged automatically from the telemetry, continuously, across millions of flights worldwide.

Every detection gets its own dated, shareable page and a one-click replay, so an event isn't just a label. It's something you can open, watch in full 3D, and cite.

Why it matters

FOQA-style visibility for everyone

The categories of event airlines monitor internally, surfaced automatically from public data for any flight in the archive.

Every event is citable

Each detection has a dated detail page with its own URL. Link it, share it, or reference it directly.

From flag to full replay in one click

Go straight from a detected event into the 3D replay with instruments to see exactly how it unfolded.

What you get

  • Go-around and missed-approach detection
  • Unstable-approach flagging against published-style gates
  • Rejected take-off and long-rollout detection
  • Runway excursion, diversion, and off-airport landing detection
  • Stall-like and overspeed event flags
  • Dated, citable detail page + one-click replay per event

How it works

Each reconstructed flight is run through a suite of detectors that look for the signatures of these events in the trajectory, energy state, and runway geometry.

Every detector is documented on the event-detection methodology page, including what each flag means and its known limitations, and is explicit about what's observed versus inferred. SkyMeter never claims a fault or a certified-recorder truth.

How events are detected

Who it's for

Journalists

Find and cite a specific go-around or diversion with a dated, linkable page and a replay to embed.

Safety researchers

Study patterns of unstable approaches or excursions at an airport or across a fleet.

Enthusiasts

Discover the notable moments hiding in ordinary days of traffic.

Frequently asked questions

Does a detected incident mean someone did something wrong?

No. SkyMeter detects observable events in the flight path, like a go-around, and never attributes fault or cause. A go-around, for example, is a normal, safe procedure.

How accurate is the detection?

Detections are made from reconstructed public telemetry and are explicit about what's observed versus inferred. Each event links to its full replay so you can judge it yourself, and the methodology page documents known limitations.

Can I link to a specific incident?

Yes. Every detected event has its own dated, permanent URL built for sharing and citation.

What events are detected?

Go-arounds, unstable and missed approaches, rejected take-offs, long rollouts, runway excursions, stall-like events, overspeeds, diversions, and off-airport landings.

Explore more capabilities

Ready to see it on a real flight?

Start free with the last 7 days, or unlock the full archive and exports with Pro.