NOTAMs are spatial by nature
Read any European NOTAM and you'll notice something strange: most of them describe places. A polygon over here. A radius around there. A corridor between two coordinates. A runway, a navaid, a danger area, a corner of a TMA. Spatial language, all the way down.
And yet, for decades, pilot briefing has been delivered as a list of text — page after page of Item E narratives that the pilot is expected to mentally project onto a chart. The result is predictable: pilots either skim and miss something, or pore over the text and burn 20 minutes of pre-flight time on geometry.
NOTAMs describe areas. A map shows them. It's a small reframe, but it's the whole product.
Every extra step a pilot has to take to translate text into spatial awareness is another chance to miss something.
The translation tax
Every time a pilot reads 510930N 0045200E and decides whether it matters, they pay a tax. Not in money — in cognitive load. The conversion from coordinates to mental map is real work, and the work compounds across a 60-page PIB.
The cost isn't comprehension. Pilots can decode coordinates. The cost is what doesn't happen because of the translation work — the conditions that don't get cross-checked, the alternates that don't get briefed, the time-window mismatch that doesn't get caught because the eye glazed over the B) and C) lines on page 14.
Move the geometry onto the chart, and the tax disappears. The pilot still reads the underlying text — but only for the four or five notices that actually intersect their flight, not for the four hundred that exist somewhere in the region.
What changes when you can see it
When NOTAMs land on the map, the briefing workflow inverts. Instead of reading a list and projecting it onto geography, you scan geography and read only the items that touch your flight. That sounds like a small UX choice. It changes everything downstream:
- Route conflicts become obvious. A red wedge clipping your planned track is a more reliable signal than a coordinate string buried in Item E.
- Time windows get checked. When the polygon is on the map, the popup naturally surfaces B) and C) — and pilots actually look at them.
- Inactive zones stop competing for attention. Combined with DYNAM, only what's active during your flight window stands out.
- Brief time drops from 20 minutes to under 2. Not because anything is hidden — because nothing irrelevant is shown.
The map and the text, together
On NOTAMbriefing.com, the polygon and the underlying NOTAM live next to each other. Tap any shape and the full Item E, the Q-line, and the validity window come up. The polygon is faithful to the text; when the text carries nuance — vertical bands, exception clauses, reporting requirements, frequency callouts — that nuance is one tap away for the few NOTAMs that actually clip your flight.
That's the workflow change in a sentence: you read the text for what's on the map and in your way, not for the four hundred notices that exist somewhere in the region. Less translation, more attention on what matters.
FAQ
Common pilot questions
How much text do I actually still read?
Only the handful of NOTAMs whose polygon or point intersects your route. The map filters the four hundred regional notices down to the four that touch the flight — those are the ones worth full text, validity window and Q-line review. The rest stay on the chart for orientation but don't compete for attention.
What about NOTAMs that aren't spatial?
Frequency changes, runway closures, administrative notices and other non-area NOTAMs are shown as point markers at the relevant airfield. The map distinguishes graphical (area) and point (event) NOTAMs visually.