SORTIE STARTERv1.122.0

Back to mission builder · Sources · Historical Library · JSON register

Historical map coverage

13 maps · 26 supported map/era pairs · reviewed 3 October 2026.

A research register, not a claim that every historical corridor has been found. Routing networks, tactical axes and reference overlays serve different purposes. A route's presence does not certify its accuracy for your scenario date.
Read the map symbolsDashed reconstructed lane; diamond gate; circular zone; hatched exclusion boundary; dash-dot deconfliction; dotted training shape; threat-axis arrow

Download vector specimen

26 map/era pairs

Caucasus · Cold War (1965-1985)

Tactical axes; no routing network
0 route segments · 2 threat axes · 0 overlay features

No complete historical or dated-validity certification.

Black Sea reconnaissance reference — date not established

CIA’s declassified U-2 history describes a 1958 Black Sea flight that did not violate Soviet airspace.

Still missing: Exact dated waypoints are not verified; 1958 precedes this product’s Cold War band and cannot authenticate the authored tactical axes.

Source 1

Official indexed text reviewed; no boundary coordinates extracted

Next evidence needed: Exact dated waypoints are not verified; 1958 precedes this product’s Cold War band and cannot authenticate the authored tactical axes.

Audit the 2 drawn elements
  • Black Sea Coastal Push · training design
    bearing from friendly centroid · REF ? · operational validity ? to ?
    No authenticated individual source; training design.
  • Kutaisi–Krasnodar Corridor · training design
    bearing from friendly centroid · REF ? · operational validity ? to ?
    No authenticated individual source; training design.

Caucasus · Modern (2000s+)

Tactical axes; no routing network
0 route segments · 2 threat axes · 0 overlay features

No complete historical or dated-validity certification.

NATO intercept reports — 2014-10-29

NATO reports a Russian formation over the Norwegian Sea, two bombers continuing southwest along the Norwegian coast, and a separate Black Sea formation.

Still missing: No georeferenced track, corridor width or altitude block is published. Black Sea and Arctic events are distinct, not a connected route.

Source 1

primary text reviewed

2008 campaign geography — 2008-08-08

US Army analysis covers Russian campaign operations and air support in Georgia.

Still missing: Roki Tunnel and ground maneuver axes are not authenticated air corridors. The two existing tactical axes remain training design.

Source 1

primary text reviewed

Next evidence needed: No georeferenced track, corridor width or altitude block is published. Black Sea and Arctic events are distinct, not a connected route. Roki Tunnel and ground maneuver axes are not authenticated air corridors. The two existing tactical axes remain training design.

Audit the 2 drawn elements
  • Black Sea Coastal Push · training design
    bearing from friendly centroid · REF ? · operational validity ? to ?
    No authenticated individual source; training design.
  • Kutaisi–Krasnodar Corridor · training design
    bearing from friendly centroid · REF ? · operational validity ? to ?
    No authenticated individual source; training design.

The Channel · World War II (1939-1946)

No drawn corridor or airspace geometry
0 route segments · 0 threat axes · 0 overlay features

No complete historical or dated-validity certification.

Channel Battle air operations — 1940-07-17

RAF Museum describes attacks over the Channel, Dover Straits and south-east coast during 17 July–12 August 1940. These are operating regions, not fixed cleared lanes.

Still missing: Individual sortie tracks, dimensions and clearance boundaries remain unverified. Naval Dunkirk routes X/Y/Z must not be represented as air corridors.

Source 1

primary text reviewed

Next evidence needed: Individual sortie tracks, dimensions and clearance boundaries remain unverified. Naval Dunkirk routes X/Y/Z must not be represented as air corridors.

Audit the 0 drawn elements

    Persian Gulf · Cold War (1965-1985)

    No drawn corridor or airspace geometry
    0 route segments · 0 threat axes · 0 overlay features

    No complete historical or dated-validity certification.

    Kharg Island strike operations — 1984-03-27

    NHHC’s Stark ship history dates Iraqi Super Étendard/Exocet attacks on Kharg to 27 March 1984 and describes another attack on 24 June.

    Still missing: Targets and dates are established, not a flight centerline, width or launch-to-target track. Do not convert shipping lanes to air corridors.

    Source 1

    primary text reviewed

    Next evidence needed: Targets and dates are established, not a flight centerline, width or launch-to-target track. Do not convert shipping lanes to air corridors.

    Audit the 0 drawn elements

      Persian Gulf · Modern (2000s+)

      Tactical axes; no routing network
      0 route segments · 2 threat axes · 0 overlay features

      No complete historical or dated-validity certification.

      Tanker War attack profile — date not established

      NHHC describes Iraqi maritime-strike staging and low-level Gulf approaches in its Tanker War retrospective.

      Still missing: A profile is not a formal corridor; precise tracks and individual sortie dates remain unverified. The article’s Stark date conflicts with the ship history, so it is not used to date a route.

      Source 1

      primary text reviewed

      Next evidence needed: A profile is not a formal corridor; precise tracks and individual sortie dates remain unverified. The article’s Stark date conflicts with the ship history, so it is not used to date a route.

      Audit the 2 drawn elements
      • Strait of Hormuz CAP · training design
        bearing from friendly centroid · REF ? · operational validity ? to ?
        No authenticated individual source; training design.
      • Bandar Abbas Strike Lane · training design
        bearing from friendly centroid · REF ? · operational validity ? to ?
        No authenticated individual source; training design.

      Nevada (NTTR) · Cold War (1965-1985)

      Partial routing network
      14 route segments · 1 threat axes · 1 overlay features

      No complete historical or dated-validity certification.

      R-4808N dated boundary review — 1995-07-20

      FAA’s 1995 realignment supplies the stored fourteen-vertex R-4808N boundary and effective date.

      Still missing: Earlier Nevada boundaries and individual corridor-validity intervals remain unknown. The 1995 shape on Cold War missions is explicitly a later training reference.

      Source 1

      primary text reviewed

      Next evidence needed: Earlier Nevada boundaries and individual corridor-validity intervals remain unknown. The 1995 shape on Cold War missions is explicitly a later training reference.

      Audit the 16 drawn elements
      • FLEX turnout · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p14; NELLISAFBI 11-250 4.6.12
      • DREAM departure · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 4.6 (DREAM: northbound IFR departure for high-performance aircraft; FLEX fixes FYTTR / HAYFORD PEAK / DREAM / MORMON PEAK / MMM)
      • Sally Corridor · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 2.8.1; NTTR Add A Table 2.1; dreamlandresort range flight
      • Alamo Corridor · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NTTR Add A Table 2.1 note 3; vJaBoG66 FLIP ALAMO recovery; 99 ABW 4.14.5.5
      • The west road (US-95) · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 4.6.13.4 (north-west bound: FYTTR then BTY); historical_airspace groom_box
      • North range transit to Tolicha · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NTTR Add A Table 2.1 (R-4807A: 71N/S, 74, 75, 76, TPECR); historical_airspace groom_box
      • FYTTR departure west · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p16; NELLISAFBI 11-250 4.6
      • MORMON MESA departure east · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 4.6 (MORMON MESA departure; FLEX fix MORMON PEAK)
      • STRYK recovery · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p30; 99 ABW 4.14.5.1
      • JAYSN recovery via Beatty · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p29; NELLISAFBI 11-250 4.13
      • MINTT recovery (RWY 03) · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        99 ABW 4.14.5.4; NELLISAFBI 11-250 4.13
      • ARCOE recovery (RWY 21) · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        99 ABW 4.14.5.3; NELLISAFBI 11-250 4.13
      • ALAMO recovery · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p28; 99 ABW 4.14.5.5
      • ACTON recovery (Elgin) · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        99 ABW 4.14.5.2
      • Range 74 Threat Axis · training design
        bearing from friendly centroid · REF ? · operational validity ? to ?
        No authenticated individual source; training design.
      • R-4808N · documented structure
        sourced 1995 polygon · REF 1995-07-20 · operational validity 1995-07-20 to ?
        No authenticated individual source; training design.

      Nevada (NTTR) · Modern (2000s+)

      Partial routing network
      14 route segments · 1 threat axes · 1 overlay features

      No complete historical or dated-validity certification.

      R-4808N dated boundary review — 1995-07-20

      FAA’s 1995 realignment supplies the stored fourteen-vertex R-4808N boundary and effective date.

      Still missing: Earlier Nevada boundaries and individual corridor-validity intervals remain unknown. The 1995 shape on Cold War missions is explicitly a later training reference.

      Source 1

      primary text reviewed

      Next evidence needed: Earlier Nevada boundaries and individual corridor-validity intervals remain unknown. The 1995 shape on Cold War missions is explicitly a later training reference.

      Audit the 16 drawn elements
      • FLEX turnout · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p14; NELLISAFBI 11-250 4.6.12
      • DREAM departure · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 4.6 (DREAM: northbound IFR departure for high-performance aircraft; FLEX fixes FYTTR / HAYFORD PEAK / DREAM / MORMON PEAK / MMM)
      • Sally Corridor · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 2.8.1; NTTR Add A Table 2.1; dreamlandresort range flight
      • Alamo Corridor · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NTTR Add A Table 2.1 note 3; vJaBoG66 FLIP ALAMO recovery; 99 ABW 4.14.5.5
      • The west road (US-95) · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 4.6.13.4 (north-west bound: FYTTR then BTY); historical_airspace groom_box
      • North range transit to Tolicha · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NTTR Add A Table 2.1 (R-4807A: 71N/S, 74, 75, 76, TPECR); historical_airspace groom_box
      • FYTTR departure west · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p16; NELLISAFBI 11-250 4.6
      • MORMON MESA departure east · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        NELLISAFBI 11-250 4.6 (MORMON MESA departure; FLEX fix MORMON PEAK)
      • STRYK recovery · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p30; 99 ABW 4.14.5.1
      • JAYSN recovery via Beatty · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p29; NELLISAFBI 11-250 4.13
      • MINTT recovery (RWY 03) · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        99 ABW 4.14.5.4; NELLISAFBI 11-250 4.13
      • ARCOE recovery (RWY 21) · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        99 ABW 4.14.5.3; NELLISAFBI 11-250 4.13
      • ALAMO recovery · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        vJaBoG66 FLIP p28; 99 ABW 4.14.5.5
      • ACTON recovery (Elgin) · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        99 ABW 4.14.5.2
      • Range 74 Threat Axis · training design
        bearing from friendly centroid · REF ? · operational validity ? to ?
        No authenticated individual source; training design.
      • R-4808N · documented structure
        sourced 1995 polygon · REF 1995-07-20 · operational validity 1995-07-20 to ?
        No authenticated individual source; training design.

      Normandy 2 · World War II (1939-1946)

      Reference overlays; no routing network
      0 route segments · 0 threat axes · 1 overlay features

      No complete historical or dated-validity certification.

      NEPTUNE troop-carrier ingress — 1944-06-06

      USAF Study 97 identifies Portland Bill (FLATBUSH), the published HOBOKEN fix and the revised ALBANY landfall near Portbail (MULESHOE). This is a transport ingress, not a generic fighter corridor.

      Still missing: Portland Bill and Portbail are geographic reconstructions. HOBOKEN is transcribed. No continuous validity, clearance, exact flown tracks or generalized fighter use is established.

      Source 1 · Source 2

      Official study, printed pages 11–12; primary-host fetch 403; mirror text reviewed. Map image unavailable; no coordinates extracted from its image.

      Next evidence needed: Portland Bill and Portbail are geographic reconstructions. HOBOKEN is transcribed. No continuous validity, clearance, exact flown tracks or generalized fighter use is established.

      Audit the 1 drawn elements
      • NEPTUNE / ALBANY INGRESS · documented structure
        published fix and reconstructed terminals · REF 1944-06-06 · operational validity ? to ?
        USAF Study 97 identifies Portland Bill (FLATBUSH), the published HOBOKEN fix and the revised ALBANY landfall near Portbail (MULESHOE). This is a transport ingress, not a generic fighter corridor.

      Syria · Cold War (1965-1985)

      Partial routing network
      26 route segments · 0 threat axes · 0 overlay features

      No complete historical or dated-validity certification.

      Levant route dating review — 2018-02-07

      The 2018 coalition release attests to a Euphrates deconfliction line; existing network citations mix civil publications and reported military profiles.

      Still missing: The four-point river sketch is approximate. No single source verifies all 26 route segments throughout both eras.

      Source 1

      primary text reviewed

      Next evidence needed: The four-point river sketch is approximate. No single source verifies all 26 route segments throughout both eras.

      Audit the 26 drawn elements
      • J14 north - Rosh Pina · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 3.1 (J14); ENR 2.1 (northern sector, PLUTO control)
      • The coast road north · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 3.1 (J15 ATLIT); ENR 5.1 LLR01
      • The Bekaa road · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        Anadolu 2 Nov 2017; Times of Israel / Defense Post 9 Apr 2018 (T-4); Times of Israel 9 Apr 2022; Wikipedia Mole Cricket 19
      • The sea road - west of Tripoli · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        TASS 18 Sep 2018; The War Zone 2018; Al Jazeera 28 Dec 2021, 2 Jul 2022
      • The Golan road - Hermon · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        Al Jazeera 31 Jan 2013; GlobalSecurity MML (1973); Al Jazeera 24 Nov 2020, 17 Sep 2022
      • The Amman road - Al-Tanf · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200); Times of Israel 9 Sep 2019; Washington Institute; Al Jazeera 20 Nov 2024
      • Recovery down the coast · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 2.1 / 3.1 / 5.1
      • Recovery via Rosh Pina · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 3.1 (J14)
      • Recovery down the Amman road · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200)
      • EAST SID 3 - IREFA · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA AD 2.22 and SID EAST 3
      • WEST SID 1 - ANANE · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA SID WEST 1
      • The Levant sea road · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA; Syria eAIP ENR 3 (R785 NIKAS); safeairspace Cyprus
      • The Amman run · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        The Aviationist 5 Feb 2019 (Tornado GR4, 'via downtown Amman Jordan'); AIP Israel ENR 3.1 (MERVA, NAT, MUVIN)
      • STAR ALPHA - the TACAN · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA STAR ALPHA / TAC Rwy 28
      • W74 east - the Northern Watch road · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 3.1 (W74) / ENR 4.4; A&SF Feb 2000; Ricks/WaPo 25 Oct 2000; GAO OSI-98-4
      • The Hatay gate - TUNLA · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 4.4 (TUNLA, HTY); Syria eAIP ENR 3 (L601)
      • The Kilis gate - NISAP · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 4.4 (NISAP); Syria eAIP ENR 3 (M861)
      • The Nusaybin gate - LESRI · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 4.4 (LESRI); Syria eAIP ENR 3 (L572/L573)
      • Recovery to Incirlik · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 2.1 (Adana MTMA); LTAG AD 2
      • Recovery from the east - the ROZ · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        A&SF Feb 2000; AIP Türkiye ENR 3.1 (W74)
      • Amman TMA departure · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC ENR 2.1 (Amman TMA); AMDT 19/2022 (ASLON-NADEK excluded from OJP9)
      • L200 east - Al-Tanf · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200); VOA / Military Times 2017; TWZ 2019
      • L513 north - Busra · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L513); Syria eAIP ENR 3 (L513)
      • A412 - Zelaf · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (A412); Syria eAIP ENR 3
      • Recovery to Azraq · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200)
      • Recovery via Busra · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L513)

      Syria · Modern (2000s+)

      Partial routing network
      26 route segments · 2 threat axes · 1 overlay features

      No complete historical or dated-validity certification.

      Levant route dating review — 2018-02-07

      The 2018 coalition release attests to a Euphrates deconfliction line; existing network citations mix civil publications and reported military profiles.

      Still missing: The four-point river sketch is approximate. No single source verifies all 26 route segments throughout both eras.

      Source 1

      primary text reviewed

      Next evidence needed: The four-point river sketch is approximate. No single source verifies all 26 route segments throughout both eras.

      Audit the 29 drawn elements
      • J14 north - Rosh Pina · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 3.1 (J14); ENR 2.1 (northern sector, PLUTO control)
      • The coast road north · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 3.1 (J15 ATLIT); ENR 5.1 LLR01
      • The Bekaa road · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        Anadolu 2 Nov 2017; Times of Israel / Defense Post 9 Apr 2018 (T-4); Times of Israel 9 Apr 2022; Wikipedia Mole Cricket 19
      • The sea road - west of Tripoli · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        TASS 18 Sep 2018; The War Zone 2018; Al Jazeera 28 Dec 2021, 2 Jul 2022
      • The Golan road - Hermon · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        Al Jazeera 31 Jan 2013; GlobalSecurity MML (1973); Al Jazeera 24 Nov 2020, 17 Sep 2022
      • The Amman road - Al-Tanf · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200); Times of Israel 9 Sep 2019; Washington Institute; Al Jazeera 20 Nov 2024
      • Recovery down the coast · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 2.1 / 3.1 / 5.1
      • Recovery via Rosh Pina · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Israel ENR 3.1 (J14)
      • Recovery down the Amman road · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200)
      • EAST SID 3 - IREFA · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA AD 2.22 and SID EAST 3
      • WEST SID 1 - ANANE · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA SID WEST 1
      • The Levant sea road · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA; Syria eAIP ENR 3 (R785 NIKAS); safeairspace Cyprus
      • The Amman run · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        The Aviationist 5 Feb 2019 (Tornado GR4, 'via downtown Amman Jordan'); AIP Israel ENR 3.1 (MERVA, NAT, MUVIN)
      • STAR ALPHA - the TACAN · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        UK Mil AIP LCRA STAR ALPHA / TAC Rwy 28
      • W74 east - the Northern Watch road · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 3.1 (W74) / ENR 4.4; A&SF Feb 2000; Ricks/WaPo 25 Oct 2000; GAO OSI-98-4
      • The Hatay gate - TUNLA · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 4.4 (TUNLA, HTY); Syria eAIP ENR 3 (L601)
      • The Kilis gate - NISAP · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 4.4 (NISAP); Syria eAIP ENR 3 (M861)
      • The Nusaybin gate - LESRI · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 4.4 (LESRI); Syria eAIP ENR 3 (L572/L573)
      • Recovery to Incirlik · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        AIP Türkiye ENR 2.1 (Adana MTMA); LTAG AD 2
      • Recovery from the east - the ROZ · reported track
        reconstructed path and planning width · REF ? · operational validity ? to ?
        A&SF Feb 2000; AIP Türkiye ENR 3.1 (W74)
      • Amman TMA departure · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC ENR 2.1 (Amman TMA); AMDT 19/2022 (ASLON-NADEK excluded from OJP9)
      • L200 east - Al-Tanf · training design
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200); VOA / Military Times 2017; TWZ 2019
      • L513 north - Busra · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L513); Syria eAIP ENR 3 (L513)
      • A412 - Zelaf · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (A412); Syria eAIP ENR 3
      • Recovery to Azraq · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L200)
      • Recovery via Busra · documented structure
        reconstructed path and planning width · REF ? · operational validity ? to ?
        CARC AMDT 19/2022 (L513)
      • Damascus Approach · training design
        bearing from friendly centroid · REF ? · operational validity ? to ?
        No authenticated individual source; training design.
      • Golan–Bekaa Line · training design
        bearing from friendly centroid · REF ? · operational validity ? to ?
        No authenticated individual source; training design.
      • EUPHRATES — APPROXIMATE 2018 REFERENCE · reported track
        approximate four point sketch · REF 2018-02-07 · operational validity ? to ?
        No authenticated individual source; training design.

      Sinai · Cold War (1965-1985)

      No drawn corridor or airspace geometry
      0 route segments · 0 threat axes · 0 overlay features

      No complete historical or dated-validity certification.

      Sinai disengagement zones — 1974-01-18

      UN documents the January-1974 disengagement and later UNEF buffer arrangements. This is subsequent to the October-1973 war setting.

      Still missing: Annex-map georeferencing and separate 1974/1975 geometry remain unresolved. Neither arrangement may be substituted for 1973 battle lines.

      Source 1 · Source 2

      Official indexed text reviewed; annex PDF fetch 403, geometry not extracted

      Next evidence needed: Annex-map georeferencing and separate 1974/1975 geometry remain unresolved. Neither arrangement may be substituted for 1973 battle lines.

      Audit the 0 drawn elements

        Sinai · Modern (2000s+)

        No drawn corridor or airspace geometry
        0 route segments · 0 threat axes · 0 overlay features

        No complete historical or dated-validity certification.

        MFO flight coordination — 1981

        MFO protocol requires verification-flight coordination and prior notification/clearance for international-boundary crossings; Zone C reconnaissance requires civil air-control notification.

        Still missing: Protocol flight rules do not establish a generic corridor. Treaty-zone polygon coordinates and amendments need separate verification.

        Source 1

        Official protocol indexed text reviewed; original fetch unavailable

        Next evidence needed: Protocol flight rules do not establish a generic corridor. Treaty-zone polygon coordinates and amendments need separate verification.

        Audit the 0 drawn elements

          Marianas · World War II (1939-1946)

          No drawn corridor or airspace geometry
          0 route segments · 0 threat axes · 0 overlay features

          No complete historical or dated-validity certification.

          Marianas–Japan B-29 theater route — 1944-11

          NHHC places the first Marianas-based Japan attack in late November 1944 and Iwo Jima on the 1945 B-29 theater path. It also describes avoidance before capture.

          Still missing: No single straight centerline or common corridor width is authenticated. Late-1944/1945 routes must not be applied to the default June-1944 setting; Iwo and Japan lie outside the playable map.

          Source 1 · Source 2

          primary text reviewed

          Next evidence needed: No single straight centerline or common corridor width is authenticated. Late-1944/1945 routes must not be applied to the default June-1944 setting; Iwo and Japan lie outside the playable map.

          Audit the 0 drawn elements

            Marianas · Cold War (1965-1985)

            No drawn corridor or airspace geometry
            0 route segments · 0 threat axes · 0 overlay features

            No complete historical or dated-validity certification.

            Guam W-517 / R-7201 references — 2025-11-27

            FAA Pacific supplement identifies W-517 (unlimited, by NOTAM) and Farallon de Medinilla R-7201/R-7201A (to FL600, by NOTAM). Warning-area avoidance is not a universal flight prohibition.

            Still missing: Coordinates and era-specific establishment/amendment records are not authenticated here. The 2025 supplement is a later reference, not proof of Cold War or 2011 boundaries.

            Source 1 · Source 2

            Official indexed supplement text reviewed; geometry not extracted

            Next evidence needed: Coordinates and era-specific establishment/amendment records are not authenticated here. The 2025 supplement is a later reference, not proof of Cold War or 2011 boundaries.

            Audit the 0 drawn elements

              Marianas · Modern (2000s+)

              No drawn corridor or airspace geometry
              0 route segments · 0 threat axes · 0 overlay features

              No complete historical or dated-validity certification.

              Guam W-517 / R-7201 references — 2025-11-27

              FAA Pacific supplement identifies W-517 (unlimited, by NOTAM) and Farallon de Medinilla R-7201/R-7201A (to FL600, by NOTAM). Warning-area avoidance is not a universal flight prohibition.

              Still missing: Coordinates and era-specific establishment/amendment records are not authenticated here. The 2025 supplement is a later reference, not proof of Cold War or 2011 boundaries.

              Source 1 · Source 2

              Official indexed supplement text reviewed; geometry not extracted

              Next evidence needed: Coordinates and era-specific establishment/amendment records are not authenticated here. The 2025 supplement is a later reference, not proof of Cold War or 2011 boundaries.

              Audit the 0 drawn elements

                Cold War Germany · Cold War (1965-1985)

                Partial routing network
                53 route segments · 3 threat axes · 4 overlay features

                No complete historical or dated-validity certification.

                Berlin corridor documentary review — 1945-11-30

                US State Department records establish three 20-statute-mile corridors and Berlin control-zone arrangements; later discussions prevent treating the exercise ceiling as universal.

                Still missing: Terminal placements remain approximate; other German route segments retain planning geometry and unknown operational validity.

                Source 1 · Source 2

                primary text reviewed

                Next evidence needed: Terminal placements remain approximate; other German route segments retain planning geometry and unknown operational validity.

                Audit the 60 drawn elements
                • The Eifel road - Nattenheim to the Taunus · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports NTM/BUE/TAU; usarmygermany.com 108th ADA Bde
                • Recovery into the Eifel · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  ace-high-journal.eu CRC in Deutschland
                • The Hunsrück road - Hahn to the Taunus · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports HND/KIR/TAU; en.wikipedia List of Nike missile sites
                • Recovery over the Hunsrück · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports HND
                • The Kirn road - Ramstein to the Taunus · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports RMS/KIR/TAU; usarmygermany.com 94th ADA Group
                • Recovery via Kirn · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports RMS
                • Rhein-Main to the Taunus · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  usarmygermany.com 10th ADA Bde
                • Recovery into Rhein-Main · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports TAU/WIB
                • The Fulda Gap - LLTR to Point Alpha · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  GlobalSecurity ww3-fulda-gap; usarmygermany.com 10th ADA Bde
                • The Werra road - LLTR to Herleshausen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  de.wikipedia Flugabwehrraketengruppe 38; en.wikipedia III Corps (Bundeswehr)
                • The Harz road - Kassel to Helmstedt · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports FTZ/WRB; GlobalSecurity NORTHAG (Goslar-Paderborn)
                • The Hof corridor - Würzburg to Hof · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  usarmygermany.com 69th ADA Bde; GlobalSecurity ww3-hof-corridor
                • The Ruhr road - Cologne to the Porta · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports COL/GMH/HMM; JMSS (Minden Gap); relikte.com CRC call signs
                • Recovery into the Rhineland · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  relikte.com nds_radar
                • The Weser road - Wunstorf to Hehlingen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  dewiki ADIZ (Braunschweig); nl.wikipedia Groepen Geleide Wapens
                • Recovery via the Leine · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  relikte.com nds_radar
                • The Heath road south - Fassberg to Hehlingen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  AIP Germany ENR 5.1 (ED-R 31/32); OurAirports FSB/CEL/HLZ
                • Recovery via Celle · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  relikte.com nds_radar
                • The Heath road north - Fassberg to Uelzen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  relikte.com nds_radar; coldwardecoded I NL Corps
                • Recovery via Fassberg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  OurAirports FSB
                • The Elbe road - Hamburg to Lauenburg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  coldwardecoded I NL Corps; en.wikipedia Inner German border
                • Recovery up the Elbe · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  relikte.com nds_radar
                • The Trave road - Lübeck to Lauenburg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  de.wikipedia Innerdeutsche Grenze (Lübecker Bucht)
                • The A2 - Porta to Helmstedt · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • The Wendland - Uelzen to Dömitz · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  JMSS (I GE Corps); coldwardecoded
                • Hehlingen to Helmstedt · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  relikte.com nds_flarak_hawk
                • Lauenburg to Boizenburg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • The north corridor axis - Boizenburg to Berlin · documented structure
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor; de.wikipedia Flugabwehrraketentruppen (NVA)
                • The center corridor axis - Helmstedt to Berlin · documented structure
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • The south corridor axis - Herleshausen to Berlin · documented structure
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor; nva-flieger.de Grenzsperrstreifen
                • Berlin west - Nauen to Rathenow · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de Luftraum der DDR
                • Recovery via Nauen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  d-d-r.de NVA Luftstreitkräfte
                • Berlin north-west - Neuruppin to Pritzwalk · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  mil-airfields.de Wittstock (routes 023-029)
                • Recovery via Neuruppin · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  mil-airfields.de Wittstock
                • Berlin south-west - Sperenberg to Dessau · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • Recovery via Sperenberg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • Merseburg - the Harz foot to Kelbra · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de; en.wikipedia 16th Air Army
                • Recovery via Kelbra · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Merseburg north - Cochstedt to Gröningen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Recovery via Cochstedt · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Parchim - Neustadt-Glewe to Ludwigslust · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Recovery via Neustadt-Glewe · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Parchim south - Perleberg to Osterburg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Recovery via Perleberg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Ludwigslust to Boizenburg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  relikte.com nds_flarak_hawk
                • Ludwigslust to Dömitz · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Pritzwalk to Boizenburg · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • Rathenow to Helmstedt · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • Osterburg to Helmstedt · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Gröningen to Helmstedt · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Kelbra to Herleshausen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Kelbra to Point Alpha · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  nva-flieger.de
                • Dessau to Herleshausen · training design
                  reconstructed path and planning width · REF ? · operational validity ? to ?
                  FRUS 1945 vol. III doc. 1206 (the corridors, 20 English miles wide); nva-flieger.de Luftraum der DDR; en.wikipedia West Berlin Air Corridor
                • Fulda Gap · training design
                  bearing from friendly centroid · REF ? · operational validity ? to ?
                  No authenticated individual source; training design.
                • Inner-German Border · training design
                  bearing from friendly centroid · REF ? · operational validity ? to ?
                  No authenticated individual source; training design.
                • Ruhr Industrial Strike · training design
                  bearing from friendly centroid · REF ? · operational validity ? to ?
                  No authenticated individual source; training design.
                • NORTH (Hamburg) · documented structure
                  approximate terminals · REF 1945-11-30 · operational validity ? to ?
                  No authenticated individual source; training design.
                • CENTER (Hannover) · documented structure
                  approximate terminals · REF 1945-11-30 · operational validity ? to ?
                  No authenticated individual source; training design.
                • SOUTH (Frankfurt) · documented structure
                  approximate terminals · REF 1945-11-30 · operational validity ? to ?
                  No authenticated individual source; training design.
                • BERLIN CONTROL ZONE · documented structure
                  approximate terminals · REF 1945-11-30 · operational validity ? to ?
                  No authenticated individual source; training design.

                Cold War Germany · Modern (2000s+)

                No drawn corridor or airspace geometry
                0 route segments · 0 threat axes · 0 overlay features

                No complete historical or dated-validity certification.

                Modern NATO air policing — date not established

                NATO describes present air-policing command arrangements including Ramstein and Uedem.

                Still missing: Command organization establishes no modern replacement for the Cold War Berlin corridors or a dated German low-level route network.

                Source 1

                primary text reviewed

                Next evidence needed: Command organization establishes no modern replacement for the Cold War Berlin corridors or a dated German low-level route network.

                Audit the 0 drawn elements

                  Kola · Cold War (1965-1985)

                  No drawn corridor or airspace geometry
                  0 route segments · 0 threat axes · 0 overlay features

                  No complete historical or dated-validity certification.

                  Vardø airspace incursion — 1975-02-14

                  Norwegian Armed Forces recount a Soviet aircraft arriving from the Barents Sea, entering south of Vardø, turning right over Vardø and exiting.

                  Still missing: Reported places and direction establish an event, not surveyed waypoints, a formal corridor or recurring validity.

                  Source 1

                  primary text reviewed

                  Next evidence needed: Reported places and direction establish an event, not surveyed waypoints, a formal corridor or recurring validity.

                  Audit the 0 drawn elements

                    Kola · Modern (2000s+)

                    No drawn corridor or airspace geometry
                    0 route segments · 0 threat axes · 0 overlay features

                    No complete historical or dated-validity certification.

                    NATO intercept reports — 2014-10-29

                    NATO reports a Russian formation over the Norwegian Sea, two bombers continuing southwest along the Norwegian coast, and a separate Black Sea formation.

                    Still missing: No georeferenced track, corridor width or altitude block is published. Black Sea and Arctic events are distinct, not a connected route.

                    Source 1

                    primary text reviewed

                    Next evidence needed: No georeferenced track, corridor width or altitude block is published. Black Sea and Arctic events are distinct, not a connected route.

                    Audit the 0 drawn elements

                      South Atlantic · Cold War (1965-1985)

                      Reference overlays; no routing network
                      0 route segments · 0 threat axes · 1 overlay features

                      No complete historical or dated-validity certification.

                      Falklands Total Exclusion Zone — 1982-04-30

                      UK Parliament publishes a 200-nautical-mile circle centered on 51°40′S, 59°30′W, effective 1100 GMT on 30 April 1982. The announcement addresses ships and aircraft supporting the occupation.

                      Still missing: Termination and later amendments remain unknown. This depicts the announced boundary, not an automatic engagement rule. A Naval War College reprint gives 59°39′W in its TEZ passage despite citing the same MEZ limits; Hansard’s 59°30′W is used.

                      Source 1

                      primary text reviewed

                      Black Buck 1 endpoints — 1982-05-01

                      RAF identifies the Ascension departure on 30 April and Stanley attack on 1 May 1982.

                      Still missing: The source does not authenticate a complete georeferenced flight track or refueling anchors. Ascension is outside this terrain; no invented straight-line corridor is drawn.

                      Source 1

                      primary text reviewed

                      Next evidence needed: Termination and later amendments remain unknown. This depicts the announced boundary, not an automatic engagement rule. A Naval War College reprint gives 59°39′W in its TEZ passage despite citing the same MEZ limits; Hansard’s 59°30′W is used. The source does not authenticate a complete georeferenced flight track or refueling anchors. Ascension is outside this terrain; no invented straight-line corridor is drawn.

                      Audit the 1 drawn elements
                      • 1982 TOTAL EXCLUSION ZONE · documented structure
                        sourced center and radius · REF 1982-04-30 · operational validity ? to ?
                        UK Parliament publishes a 200-nautical-mile circle centered on 51°40′S, 59°30′W, effective 1100 GMT on 30 April 1982. The announcement addresses ships and aircraft supporting the occupation.

                      South Atlantic · Modern (2000s+)

                      No drawn corridor or airspace geometry
                      0 route segments · 0 threat axes · 0 overlay features

                      No complete historical or dated-validity certification.

                      Mount Pleasant QRA — 2023-04-08

                      RAF describes 1435 Flight QRA at Mount Pleasant and Voyager tanker support.

                      Still missing: No recurring QRA flight track, patrol box or tanker anchor coordinates are provided. This later report does not certify the default modern mission date.

                      Source 1

                      Official indexed text reviewed; no boundary coordinates extracted

                      Next evidence needed: No recurring QRA flight track, patrol box or tanker anchor coordinates are provided. This later report does not certify the default modern mission date.

                      Audit the 0 drawn elements

                        Afghanistan · Modern (2000s+)

                        Tactical axes; no routing network
                        0 route segments · 2 threat axes · 2 overlay features

                        No complete historical or dated-validity certification.

                        Six Afghan ATS route designators — 2011-08-01

                        ICAO RASMAG/15 WP09 presented by AFCENT for MoTCA names UL333, B466/G792, L750, N644, A466/G796 and M881. It discusses pre-RVSM procedural control and planned changes.

                        Still missing: The airway names are established; georeferenced fixes, segment validity and later changes remain unavailable. This does not verify the existing illustrative Kabul circle or Helmand box.

                        Source 1

                        Official indexed working-paper text reviewed; original URL 404. No figure geometry extracted.

                        Next evidence needed: The airway names are established; georeferenced fixes, segment validity and later changes remain unavailable. This does not verify the existing illustrative Kabul circle or Helmand box.

                        Audit the 4 drawn elements
                        • Helmand River Corridor · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Hindu Kush Passes · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • KABUL — ILLUSTRATIVE TRAINING CIRCLE · training design
                          illustrative · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • HELMAND — ILLUSTRATIVE TRAINING BOX · training design
                          illustrative · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.

                        Afghanistan · War on Terror (2003-2025)

                        Tactical axes; no routing network
                        0 route segments · 3 threat axes · 2 overlay features

                        No complete historical or dated-validity certification.

                        Six Afghan ATS route designators — 2011-08-01

                        ICAO RASMAG/15 WP09 presented by AFCENT for MoTCA names UL333, B466/G792, L750, N644, A466/G796 and M881. It discusses pre-RVSM procedural control and planned changes.

                        Still missing: The airway names are established; georeferenced fixes, segment validity and later changes remain unavailable. This does not verify the existing illustrative Kabul circle or Helmand box.

                        Source 1

                        Official indexed working-paper text reviewed; original URL 404. No figure geometry extracted.

                        Next evidence needed: The airway names are established; georeferenced fixes, segment validity and later changes remain unavailable. This does not verify the existing illustrative Kabul circle or Helmand box.

                        Audit the 5 drawn elements
                        • Helmand Green Zone · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Khost Bowl · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Kunar Valley · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • KABUL — ILLUSTRATIVE TRAINING CIRCLE · training design
                          illustrative · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • HELMAND — ILLUSTRATIVE TRAINING BOX · training design
                          illustrative · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.

                        Iraq · Cold War (1965-1985)

                        Tactical axes; no routing network
                        0 route segments · 3 threat axes · 0 overlay features

                        No complete historical or dated-validity certification.

                        Kharg Island strike operations — 1984-03-27

                        NHHC’s Stark ship history dates Iraqi Super Étendard/Exocet attacks on Kharg to 27 March 1984 and describes another attack on 24 June.

                        Still missing: Targets and dates are established, not a flight centerline, width or launch-to-target track. Do not convert shipping lanes to air corridors.

                        Source 1

                        primary text reviewed

                        Next evidence needed: Targets and dates are established, not a flight centerline, width or launch-to-target track. Do not convert shipping lanes to air corridors.

                        Audit the 3 drawn elements
                        • Kharg Island Strike Lane · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Jafati Valley · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • H-3 Raid Track · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.

                        Iraq · Modern (2000s+)

                        Tactical axes; no routing network
                        0 route segments · 4 threat axes · 2 overlay features

                        No complete historical or dated-validity certification.

                        Southern Watch boundary changes — 1992-08-26

                        Canada’s DND identifies the announcement south of 32°N in August 1992 and expansion to 33°N in 1996; US Army FY1997 history dates the expansion to September.

                        Still missing: Latitude is sourced. Finite line endpoints are diagram extents, not Iraq’s borders. Exact amendment day and terminal validity require further evidence.

                        Source 1 · Source 2

                        primary text reviewed

                        Tanker War attack profile — date not established

                        NHHC describes Iraqi maritime-strike staging and low-level Gulf approaches in its Tanker War retrospective.

                        Still missing: A profile is not a formal corridor; precise tracks and individual sortie dates remain unverified. The article’s Stark date conflicts with the ship history, so it is not used to date a route.

                        Source 1

                        primary text reviewed

                        Iraqi airspace handover — 2010-09-01

                        USAF reports transfer of the Kirkuk sector at FL150 and above to ICAA on 1 September 2010.

                        Still missing: The article does not publish polygon coordinates. Planned later transfers are not treated as completed events.

                        Source 1

                        Official indexed text reviewed; no boundary coordinates extracted

                        Next evidence needed: Latitude is sourced. Finite line endpoints are diagram extents, not Iraq’s borders. Exact amendment day and terminal validity require further evidence. A profile is not a formal corridor; precise tracks and individual sortie dates remain unverified. The article’s Stark date conflicts with the ship history, so it is not used to date a route. The article does not publish polygon coordinates. Planned later transfers are not treated as completed events.

                        Audit the 6 drawn elements
                        • Northern Watch (36th Parallel) · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Southern Watch (33rd Parallel) · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Karbala Gap · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Western Scud Box · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • 1992 SOUTHERN WATCH — 32°N BOUNDARY SEGMENT · documented structure
                          sourced parallel with diagram endpoints · REF 1992-08-26 · operational validity ? to ?
                          Canada’s DND identifies the announcement south of 32°N in August 1992 and expansion to 33°N in 1996; US Army FY1997 history dates the expansion to September.
                        • SEPT 1996 SOUTHERN WATCH — 33°N BOUNDARY SEGMENT · documented structure
                          sourced parallel with diagram endpoints · REF 1996-09 · operational validity ? to ?
                          Canada’s DND identifies the announcement south of 32°N in August 1992 and expansion to 33°N in 1996; US Army FY1997 history dates the expansion to September.

                        Iraq · War on Terror (2003-2025)

                        Tactical axes; no routing network
                        0 route segments · 3 threat axes · 2 overlay features

                        No complete historical or dated-validity certification.

                        Southern Watch boundary changes — 1992-08-26

                        Canada’s DND identifies the announcement south of 32°N in August 1992 and expansion to 33°N in 1996; US Army FY1997 history dates the expansion to September.

                        Still missing: Latitude is sourced. Finite line endpoints are diagram extents, not Iraq’s borders. Exact amendment day and terminal validity require further evidence.

                        Source 1 · Source 2

                        primary text reviewed

                        Iraqi airspace handover — 2010-09-01

                        USAF reports transfer of the Kirkuk sector at FL150 and above to ICAA on 1 September 2010.

                        Still missing: The article does not publish polygon coordinates. Planned later transfers are not treated as completed events.

                        Source 1

                        Official indexed text reviewed; no boundary coordinates extracted

                        Next evidence needed: Latitude is sourced. Finite line endpoints are diagram extents, not Iraq’s borders. Exact amendment day and terminal validity require further evidence. The article does not publish polygon coordinates. Planned later transfers are not treated as completed events.

                        Audit the 5 drawn elements
                        • Tigris Valley · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Haditha Dam Corridor · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • Kirkuk-Hawija Pocket · training design
                          bearing from friendly centroid · REF ? · operational validity ? to ?
                          No authenticated individual source; training design.
                        • 1992 SOUTHERN WATCH — 32°N BOUNDARY SEGMENT · documented structure
                          sourced parallel with diagram endpoints · REF 1992-08-26 · operational validity ? to ?
                          Canada’s DND identifies the announcement south of 32°N in August 1992 and expansion to 33°N in 1996; US Army FY1997 history dates the expansion to September.
                        • SEPT 1996 SOUTHERN WATCH — 33°N BOUNDARY SEGMENT · documented structure
                          sourced parallel with diagram endpoints · REF 1996-09 · operational validity ? to ?
                          Canada’s DND identifies the announcement south of 32°N in August 1992 and expansion to 33°N in 1996; US Army FY1997 history dates the expansion to September.