Each link below produces an OpenAir file
(.txt) compatible with FlySkyHy,
XCTrack, XCSoar, and other XC apps.
Coordinates are written as DMS with cardinal direction; classes are
Q (Danger, fire), R (Restricted, NOTAM), and
W (Wave Window, landing guidance).
Situational awareness only — not for sole navigation. Wildfire and NOTAM data are pulled live from BC Wildfire Service / CWFIS / NAV CANADA / FAA TFR (tfr.faa.gov); landing guidance polygons are community-maintained. FlySkyHy keeps only one custom OpenAir file at a time — importing one file replaces any previously imported custom airspace.
Fetches NAV CANADA NOTAM polygons, wildfire 5 NM advisory no-fly polygons (same shapes as the website's red advisory rings — buffered hull or 5 NM disk per fire), and all enabled landing-guidance overlays — one OpenAir file with the same semantics as each section below.
NAV CANADA polygon NOTAMs (CFPS-derived) plus FAA
TFR polygons (USA) — wildfire / mil exercise /
skydiving / glider / UAV / CYR / training / general (Canada), and
regulatory TFR shapes (USA). Canada altitudes use F) /
G) where present; USA TFR exports use
GND .. UNLIM unless detail text is added later. Altitudes
(AH / AL) come from each NOTAM's
F) / G) lines; falls back to
GND .. UNLIM.
For every active fire (BC Wildfire Service for BC; CWFIS for the rest
of Canada): a 5 NM outward buffer of the published
perimeter, or a 5 NM geodesic disk for incidents with
no published outline. These are the
same red advisory rings shown on the website map. Class
Q (Danger) with GND .. UNLIM — fires with
status OUT are dropped.
Every enabled community landing-guidance overlay (from
CONFIG.noLandingOverlays), emitted as
AC W (Wave Window) so apps render them as informational
and don't alarm on entry. Use your XC app's per-class styling to make
them outline / shaded. Colours on the map: red = no landing, yellow =
restricted, green = OK to land.
How alarms behave — XCTrack / XCSoar / FlySkyHy will
alarm on Q and R by default, and treat
W as informational. Final behaviour depends on each
pilot's per-class settings on the device.
Not included in All categories above — external sources and reference links only.
The map’s Airspace overlay uses bundled Canada and US exports. For OpenAIR files to load into XCTrack, XCSoar, FlySkyHy, or other apps, the Worldwide Soaring Turnpoint Exchange — Airspace for North America is a good place to start: CanAirspace (NAV CANADA Designated Airspace Handbook) and US files (see SoaringData for the latest NASR export).