Operational impact · Financial exposure

BreachCalc

Loading sector assumptions…

INCIDENT LAB / 001 · AVIATION

When flight plans stop flowing.

NATS · United Kingdom · 28 August 2023

Interactive case study

A documented technical disruption. Explore how a shared processing failure becomes an operational backlog. This is a browser-local training model, with illustrative traffic and compressed time—not live air traffic.

PLANNING NETWORK · SCHEMATICT+0.0 h
Illustrative flight planning networkIncoming flight plans flow through primary and backup processing to the operations queue. Amber paths indicate suspended automatic processing. Moving symbols represent data, not real aircraft. Flight plansIllustrative arrivalsPrimaryAvailableBackupAvailableOperations queue0 plans waiting

● Flight-plan data ● Automatic processing suspended

CHAPTER 01 / 05

The documented incident

Preparing Bruce Mellow narration…

New demand100 plans/h
Processing capacity100 plans/h
Waiting backlog0 plans
Processed to date0 plans
Model assumptions, evidence & full transcript

Historical evidence: NATS describes a duplicate-waypoint processing exception, fail-safe behavior in primary and backup systems, and maintained safety. The CAA estimates over 700,000 affected passengers and issued 34 recommendations. This exercise does not attribute the event to a cyberattack.

Training assumptions: Constant demand of 100 plans/hour; one hour at normal capacity, three hours of reduced fallback capacity, then four hours at 150 plans/hour. These are invented scenario values, not the NATS incident timeline or measured capacity. No cancellations or abandonment are modeled. Per interval: processed = min(backlog + arrivals, capacity × hours); remaining backlog = previous backlog + arrivals − processed. Values are rounded for display. The calculator below remains a separate model.

Loading calculator…

Saved scenarios

Saving, sharing and PDF export require an active license. Public calculations remain available offline.