Flight Replay and Evidence-Based Debrief

Recorded network evidence

Replay is available for flights operated after recording was enabled and only when network samples exist. It displays the phase-coloured actual route, planned route, heading-rotated aircraft marker, playback controls, altitude/speed profile, timeline, recorded weather, assigned/actual stands and aircraft identity with a link to Aircraft Chronicle.

ATC and Traffic Encounters

ATC History lists position-and-time-overlapping services; it does not claim that the pilot tuned or contacted a frequency. A Traffic Encounter requires both aircraft airborne and normally two consecutive observations within 10 NM horizontally and 2,000 ft vertically. A single new-format observation is retained only inside 3 NM and 1,000 ft. Sessions show callsign, pilot VID where available, closest time, duration, phase and an observational class. They are not separation-violation findings.

Connection Flight evidence

Connection Replay contains the frozen multi-aircraft passenger manifest. Allocated inbound aircraft are also recorded through their final 20 NM and can appear on the map with callsign and heading alongside the SKYLINK outbound replay. Public language describes operational evidence without exposing internal collection or airport-data implementation details.

Evidence-Based Debrief

The debrief exposes its evidence: sample coverage, recorded/planned distance, low-altitude groundspeed observations, possible descent-to-climb go-around patterns and assigned-stand verification. No samples means “Insufficient evidence”. Groundspeed is not IAS, and unavailable flap, gear, engine, touchdown-rate or control-input telemetry is never presented as fact.

Sharing

The flight owner may create or revoke a canonical public /shared/replay/<token>/ URL. Legacy shared addresses redirect permanently to the canonical route. Public Replay initializes the same map and playback data, while share control remains with the flight owner.