Where launches, re-entries and space weather meet aviation
The FlySafe engine already tracks aircraft, closures and interference across 300+ FIRs. The space section turns the same data on the sky above: what a launch, a re-entry or a solar flare measurably does to flying — as counted numbers, published with their method.
Published datasets
Share of long-distance HF links lost on the sunlit side of Earth during 794 M- and X-class flares, by class, band, region and hour after peak, with an absorption estimate in dB. Public JSON endpoint.
In measurement — not yet published
Hours of closed sky per launch versus hours of measured traffic displacement, per spaceport. First finding: at Cape Canaveral a typical TFR window spans ~100 h while measurable displacement lasts ~3 h.
Excess orbital decays after geomagnetic storms, from a 25-year catalogue. Clear only for extreme storms so far; needs orbit history to become an index.
Independent latency and loss measurements of Starlink terminals through 21 Kp ≥ 7 storms. Result so far: no robust degradation — which is itself a publishable finding.
Per quarter and per program: launches, closure hours, displaced traffic, maritime warnings, re-entries. Counted, not estimated.
How this relates to FlySafe airspace risk
One database, one engine. The space datasets are computed from the same aircraft positions, NOTAM/TFR feeds and interference maps that drive the airspace indices, joined with public space data (NOAA GOES, GFZ Kp, launch and satellite catalogues). Where a source's licence does not allow commercial redistribution we publish derived aggregates only and say so on the page.