← the contents·corridors · the air lane
War Atlas · corridors · the air lane
The vanishing tracks
The tracks were a surveillance artefact, not a wind artefact.
Positions updated roughly every 840 seconds, so aircraft were slotted into lanes. T2BRIEF-2026-09-08C
Space-based ADS-B cut that to 7–8 s and separation fell from ~40 nm to 14 nm. The lanes stopped being necessary. T3BRIEF-2026-09-08C
The wind explanation is true of where the lanes were put and false of why they existed. It is the right answer to a different question.
“THE TRACKS WERE A SURVEILLANCE ARTEFACT, NOT A WIND ARTEFACT”route_corridor.note (R-NAT)
“Space-based ADS-B cut position updates to 7-8 seconds”route_corridor.why (R-NAT-RANDOM)
“separation went from about 40 nautical miles to 14”route_corridor.why (R-NAT-RANDOM)
the three figures in the second sentence are T3, one tier below the T2 of the first: they belong to route_corridor.why (R-NAT-RANDOM), and route_corridor.note (R-NAT) states no separation at all
Why a lane was needed at all
Separation is a function of how old the controller’s picture is. At a fourteen-minute refresh an aircraft is a smear rather than a point, and the smear has to be given a lane of its own. Shrink the refresh and the smear becomes a point; the lane becomes surplus.
The second bar is about six pixels wide on the same linear scale. That is the point, not a defect — roughly 112× shorter, and between 105× and 120× across the stated range. T3BRIEF-2026-09-08C
T2BRIEF-2026-09-08C “840 seconds”route_corridor.note (R-NAT)
T3BRIEF-2026-09-08C “Space-based ADS-B cut position updates to 7-8 seconds”route_corridor.why (R-NAT-RANDOM)
26 nm removed from between each pair of aircraft — a factor of 2.86. T3BRIEF-2026-09-08C
T3BRIEF-2026-09-08C “separation went from about 40 nautical miles to 14”route_corridor.why (R-NAT-RANDOM)
both bars, before and after, are read from that one sentence — the track-era spacing is not stated by route_corridor.note (R-NAT) at all
One witness. Both operands of both ratios carry source_ref BRIEF-2026-09-08C. That is one witness, not two, and the ratio inherits no independence from being a ratio. Both separation figures come from ONE SENTENCE of one row, so the separation ratio is a sentence divided by itself. The post-ADS-B interval is the midpoint of a stated 7–8 second range, so the interval ratio is a midpoint and lands inside the range printed beside it.
54 years, then 7
“Up to a dozen” is a ceiling the record states, not a count anyone took on a given day. Twelve lanes drawn is an illustration of that ceiling and is labelled as one.
NO PER-YEAR LANE COUNT IS RECORDED ANYWHERE IN THIS TABLE. The thinning after 2019 is drawn as an explicit absence band, not as a measured decline, because a measured decline is not something this record contains.
the lanes and the spanT2BRIEF-2026-09-08C “Up to a dozen tracks each way”
the 5 dated rules on it2019, 2021, 2022 T3BRIEF-2026-09-08C2025, 2026 T3 · unverifiedBRIEF-2026-09-08C
the event rules are T3 and the lanes beneath them are T2: they are different rows, and the marks are labelled with their own tier on the diagram rather than inheriting the lanes’
The dissolution
8 dated events, every one of them read out of two text columns. The last 4 are marked unverified under a rule fixed before they were counted: an item dated 2025 or later carries the badge.
- 1965
The Organised Track System opens
Up to a dozen tracks each way, laid on the strongest tailwinds eastbound, repositioned twice daily.
T2BRIEF-2026-09-08C
“Up to a dozen tracks each way”
route_corridor.era_from + why (R-NAT)
- 2019
Space-based ADS-B
Position updates fall from roughly 840 seconds to 7–8. Separation falls from about 40 nautical miles to 14.
T3BRIEF-2026-09-08C
“Space-based ADS-B cut position updates to 7-8 seconds”
route_corridor.era_from + why (R-NAT-RANDOM)
- 9 March 2021
The first OTS Nil day
The first day in the system's history with no westbound tracks at all. Roughly twenty more followed.
T3BRIEF-2026-09-08C
“9 March 2021 was the first day in the system's history with NO westbound tracks”
route_corridor.note (R-NAT-RANDOM)
- 1 March 2022
FL330 and below leave the track system
The lower levels stop using the OTS entirely. route_corridor closes the OTS record at 2022.
T3BRIEF-2026-09-08C
“From 1 March 2022 FL330 and below left the OTS entirely”
route_corridor.note (R-NAT-RANDOM) + era_to (R-NAT)
below this line: 4 of 8 items, 2025 and later — the weakest in the record
“the 2025 and 2026 items are the weakest” — the row’s own note. The badge marks these because the record says they are the frailest, not because everything above them is solid.
- 1 July 2025
ADS-B mandatory across the Reykjavik FIR
Surveillance becomes the floor rather than the improvement.
T3 · unverifiedBRIEF-2026-09-08C
“ADS-B mandatory across the Reykjavik FIR since 1 July 2025”
route_corridor.note (R-NAT-RANDOM)
- 2025
Blue Spruce routes removed from NAT Doc 007
The contingency routes for aircraft without full equipage leave the document.
T3 · unverifiedBRIEF-2026-09-08C
“Blue Spruce routes removed from NAT Doc 007”
route_corridor.note (R-NAT-RANDOM)
- 2025
GNSS spoofing procedures issued
NAT Ops Bulletin 01/2025. The position source that removed the lanes acquires a declared failure mode.
T3 · unverifiedBRIEF-2026-09-08C
“GNSS spoofing procedures in NAT Ops Bulletin 01/2025”
route_corridor.note (R-NAT-RANDOM)
- January 2026
Half-degree coordinate trial
Finer position reporting than the track era ever needed.
T3 · unverifiedBRIEF-2026-09-08C
“a January 2026 half-degree coordinate trial”
route_corridor.note (R-NAT-RANDOM)
What the badge does not mean. The whole R-NAT-RANDOM row is brief-sourced and unchecked. The UNVERIFIED badge marks the WEAKEST items, not the only weak ones — nothing on this page has been read against a primary document.
Why nothing above is drawn as a line between two places
The corridor’s endpoints are recorded as Shanwick and Gander — two names in a text column. No coordinate store in this atlas holds either, so there is no segment to draw, rightly or wrongly. That is a fact about the record and it is reported rather than patched.
It would still be the wrong drawing if the coordinates arrived. 1 of the 2 rows below states it outright, in its own note. The other is a route of that shape and makes no such claim — an instance of the rule, which is a weaker thing than a statement of it, and the cards say which is which.
an instance of the shape — this row makes no straight-line claim of its own
Run the roaring forties east, then turn north.
note is null on this row — there is no straight-line claim here to quote
T2BRIEF-2026-09-08C
states the rule
Sailing away from the destination to reach the westerlies is shorter in time than sailing toward it.
Looks like a detour on a map and is not one. Any map of this atlas that draws routes as straight lines will make every entry here look wrong.
T2BRIEF-2026-09-08C
The receipt
- rows behind this page
- 15 across route_corridor and chokepoint · T2×6, T3×9
- independent attestations
- 1 — BRIEF-2026-09-08C
- verified rows
- 0
- recompute
python db/export_routes.py- anchors checked
- 16 distinct quote(s) confirmed present in route_corridor text, over 19 assertions — 3 figure(s) share a sentence already asserted for another figure, and a shared sentence is one quote, not two
- generated
- 2026-09-08 · war-atlas db/export_routes.py
positive control PASS — 19 assertions over 16 distinct anchor strings, every one literally present in route_corridor text
negative control PASS — "1987" is absent from route_corridor.note (R-NAT-RANDOM), so the matcher returns false when it should
Neither table carries a verification column. Every one of the 15 rows traces to BRIEF-2026-09-08C and to nothing else, so the T2 and T3 tiers here are SELF-DECLARED BY ONE BRIEF. Two figures from one source are one witness, and finding a second document that repeats this brief would not change that. Single-source dependence is a permanent property of these rows, not a field waiting to be revised upward.
The chokepoint rows in this payload are deliberately not rendered on this page. Their volumes double-count the same voyage at three gates and their criticality is not a function of their volume; both refusals need a view built around them rather than eight numbers borrowed into a page about aviation surveillance.
the ceiling of 12 lanes, the 8 dated events and every figure above are read from route_corridor by python db/export_routes.py — war-atlas db/export_routes.py, generated 2026-09-08