NOTAM Comprehension Failure: A Systematic Review
Analysis of incident reports where NOTAMs were issued but pilots reported unawareness. The problem is often cognitive load and information presentation, not data availability.
Investigations into runway incursions, temporary flight restrictions, and obstacle conflicts frequently note that a NOTAM existed but the pilot 'was unaware.' That framing implies a simple information gap. A closer read of ASRS and NTSB supplemental material suggests a different failure mode: the NOTAM was available, but buried in volume, encoded in abbreviations, or not mapped to the specific phase of flight where it mattered.
Cognitive load is the central constraint. Preflight briefings already combine weather, performance, fuel, and human factors. When NOTAM lists arrive as long, unsorted text blocks, pilots satisfice — they scan for keywords near departure and destination and deprioritize en-route items. Items with operational impact during cruise or approach may never enter working memory.
Presentation quality varies sharply across providers. Some sources group NOTAMs by airport; others sort by issuance time. Plain-language summaries help, but only when they preserve the operational trigger (closed runway end, displaced threshold, crane height) without stripping the geographic reference pilots need to correlate with charts.
Better workflows separate 'must know before taxi' from 'review along route.' FlightReady's NOTAM integration emphasizes route-relevant hazards and flags when the NOTAM corpus is partial or proxied, so pilots can calibrate confidence. The goal is not to replace official briefings — it is to reduce the chance that a critical restriction never surfaces in the decision set.
Put it to work