Air Corridor Cascade Simulator

Model how runway construction accidents, fiber cuts, and ground stops cascade across busy Northeast air corridors (JFK, LGA, EWR, PHL, BOS) into holding stacks, ground delays, and airborne diversions.

AIRSPACE SECTOR: ZNY NORTHEAST CORRIDOR STACK CONGESTION: CRITICAL SIM TIME: T+02:45
Timeline Scrub: 02h 45m
Delayed Flights 142 74% of scheduled bank
Average Delay 88 min Peak stack: 135 min
Diverted Flights 18 Diverting to BWI, SWF, BDL
Canceled Flights 24 Crew duty time-outs
Pax Delay Impact 26,480 h Est. Cost: $2.1M
Airborne Holding Stack Origin Ground Stop Hold (EDCT) Recovered Capacity Inflow Fuel Divert Ceiling
Simulation running. Showing tactical delay ripple through 18 feeder airports.

Tactical Flight Operations: Anatomy of an Airspace Cascade

1. Physical Mishap to Capacity Collapse

When a backhoe cuts ground radar cabling or an unpaved construction trench buckles a critical taxiway, an airport's acceptance rate (AAR) immediately plummets by 40% to 80%. Multi-runway configurations collapse into single-runway operations with increased separation intervals.

2. Airborne Holding to Fuel Starvation

Inbound flights already aloft enter published racetrack holding patterns (e.g., LENDY, CAMRN, ROBER). As stack wait times exceed 35–45 minutes, pilots hit minimum diversion fuel (Bingo Fuel), declaring "minimum fuel" or diverting to regional relievers like SWF, BWI, or BDL.

3. Ground Delay Programs (GDP)

The FAA Air Traffic Control System Command Center (ATCSCC) implements GDPs to hold departures at their origin gates rather than burning fuel in the air. This delays outbound banks from Atlanta (ATL), Chicago (ORD), and Charlotte (CLT), causing cascading crew duty-hour timeouts nationwide.

How the synthetic air-corridor queue model works

Read the explanation

This page runs a synthetic eight hour queue model, not a live air traffic feed. Its stored JFK baseline is sixty operations per hour. A sixty five percent capacity reduction leaves thirty five percent of that baseline: twenty one per hour, or three point five per ten minute bucket. The engine permits fractional counts internally and rounds many display totals. After the outage, the authored capacity rule recovers linearly over one point five hours. During the outage, the ground delay input becomes a held fraction: buffer divided by one hundred twenty, capped at point eight five. In the first default bucket, eleven synthetic arrivals are scheduled. At zero buffer, all eleven enter the airborne queue. At seventy five, six point eight seven five are held and four point one two five are released. At one hundred fifty, the cap holds nine point three five and releases one point six five. This fraction rule is an assumption, not a per-flight seventy five minute timer. Another authored rule cancels flights whenever the ground queue exceeds thirty five, subtracting rounded eight percent of that queue. A synthetic queue of forty therefore cancels three and leaves thirty seven. Despite a comment mentioning three hour delays, that branch checks queue size, not each flight’s waiting time. Inspect the capacity, buffer and fuel assumptions, scrub the timeline, compare the synthetic manifest, and export the CSV. These outputs describe the page model rather than an operational dispatch plan.

Enjoy this tool? Build your own with Super