Route analysis
Analyse a flight, phase by phase.
Load one recorded flight — by flight number, by route, or as a CSV track export — and get its phases and timings, routing and efficiency, light conditions and a 30-day route benchmark. Every figure is labelled observed or analysed.
- CSV files are read in your browser, and uploaded only if you save them
- The PDF report is built in your browser too
- For information only — not for flight planning or operations
Load a flight
Drop a flight track CSV here, or choose one
Parsed in your browser — the file is uploaded only if you save it to your account. Up to 10 MB and 100,000 rows. Columns: Timestamp, UTC, Callsign, Position, Altitude, Speed, Direction.
Works with the CSV track export from Flightradar24, available to its subscribers.
What the analysis covers
One flight, read end to end
Phases and timings
Nine phases from taxi-out to taxi-in, nine event anchors, and every duration from block time to the takeoff and landing rolls — summing exactly to block.
Profile and route
Vertical profile with phase bands and a speed panel, and a map coloured by phase with the great circle, holds, step climbs and playback.
Operational efficiency
A 0–100 score and A–E grade from five findings — track miles, taxi-out, holding, step climbs, descent level-offs — in minutes and miles.
Light and local time
Day, twilight and night along the track, sunrise and sunset crossings, which side of the cabin had the sun, and local clocks at both ends.
30-day route benchmark
Block, airborne, taxi and route extension against other sectors on the city pair, with operators, aircraft types and runway use. Runs only on request.
PDF report and flight card
A full A4 report or a four-page summary, built in your browser: the route on a map, the timeline, where the time went, efficiency and the benchmark. Plus a square flight card to share.
Built to show its own uncertainty
Observed, analysed, and how sure it is
Positions, altitudes and groundspeeds are observed. Phases, durations, findings and the benchmark are analysed — estimates, not an airline’s records — and they are labelled that way everywhere. A confidence score and plain-language notes say what the data can and cannot support: a four-minute gap on approach reads as “approach timings are approximate”, not as a precise figure.
- Validate. Rows outside physical bounds are dropped, the track is sorted on its epoch timestamps, and reported speeds are checked against the movement between positions.
- Detect. Phases and events come from altitude above the measured ground elevation, speed and movement — the same rules for every flight, published on the Assumptions tab.
- Qualify. Gaps, interpolation and corrected samples lower the confidence score and appear as notes beside the figures they affect.
See a complete analysis first
The sample is a synthetic London–New York track built to exercise every analysis: step climbs, a hold, a coverage gap and a sunset.