Help / Uitleg
ACTIVEConfirmed operational for the briefing window.PERMANENT PROHIBITEDPermanent prohibited baseline airspace.SCHEDULED ACTIVEActive according to an applicable published schedule.HIGH / TEMPORARY NOTAMTask-relevant temporary activity; high relevance alone is not proof of restricted airspace.ACTIVATION UNCERTAINA NOTAM may activate an area, but the match or timing is not conclusive.POSSIBLE MATCHPossible relation between FAA NOTAM and baseline airspace; inspect both.BY NOTAM — NO ACTIVATION FOUNDOnly an official NOTAM-only rule plus a complete, current FAA dataset can establish INACTIVE. Otherwise no match remains UNKNOWN.FLEXIBLE BASELINEP/R/D, TRA/TSA or comparable OpenAIP context whose current status is not established here.CONTROLLED BASELINECTR/TMA/ATZ/RMZ/TMZ context, shown only when selected.
How the layers differ
Baseline airspace comes from OpenAIP and the curated authoritative Netherlands AIP SUP layer. NOTAM information comes from the FAA NMS environment named in the live source indicator (production for normal publication; staging only for explicit testing). Task relevance means the time, altitude and corridor filters include the item. Activation status is a separate operational interpretation and is never inferred inactive merely because no NOTAM match was found.
Geographic coverage
Tasks may be created inside EHAA, EBBU, EDGG, EDWW, EDMM, LFFF, LFEE, LFBB, LFMM and LFRR. New points outside these FIR boundaries are blocked; a corridor crossing beyond them is marked PARTIAL. OpenAIP baseline coverage includes the Netherlands, Belgium, Luxembourg, Germany and metropolitan France. The daily FAA INTERNATIONAL classification load is filtered locally for EHAA, EBBU, EDGG, EDWW, EDMM, LFFF, LFEE, LFBB, LFMM and LFRR. Coverage is COMPLETE only when every FIR required by the task corridor has current, validated FAA and OpenAIP data.
Data sources
FAA NMS, OpenAIP and NL AIP SUP status loading…