Airspace & Aviation Chaos

Friday morning, February 28 (06:00–10:00 UTC) — the first hours after strikes began at ~06:10 UTC. The earliest airspace signals came exclusively from Russian Telegram. Readovka, with its massive audience, reported at 07:01 UTC that Khamenei had been moved to safety as explosions hit Tehran — the airspace story was initially embedded within the kinetic narrative, not yet a standalone thread. By 07:52, Readovka was relaying Israeli media claims that strikes would continue for four days, implicitly signaling prolonged airspace disruption. The 09:27 report of explosions over Abu Dhabi — Iranian missiles targeting the US base — marked the moment airspace chaos expanded beyond Iran into the Gulf.

At this stage, no aviation authority had issued formal statements. The airspace story existed only as inference from combat reports. Russian channels were the first movers not because of aviation expertise, but because their milblog networks were tracking missile trajectories that crossed civilian flight paths.

Friday late morning, February 28 (10:00–12:00 UTC) — roughly four hours after the first strikes. The thread crystallized as a distinct story when OSINT channels began treating aviation disruption as its own beat. IntelSlava posted the European Aviation Safety Agency advisory at 10:53 UTC, and by 11:20 was tracking the global cascade: 'The absolute chaos in aviation in the Middle East has spread to the global air transport network.' At 11:44, Emirates Airlines' suspension of all Dubai flights became the thread's first named-carrier shutdown.

Al Jazeera English entered at 11:52 with a comprehensive headline — 'Airspace closed, airlines halt flights as US, Israel attack, Iran responds' — marking the moment the aviation story crossed from Telegram into mainstream web journalism. Tehran Times appeared in this window too, though with an off-topic Venezuela article flagged by keyword matching, illustrating the noise in early data collection. The ecosystem was still sorting signal from noise, but the OSINT channels had established the aviation thread as an independent story with its own rhythm.

Friday midday to afternoon, February 28 (12:00–16:00 UTC) — six to ten hours into the strikes. Turkish sources entered the thread through Anadolu Agency's report on Saudi Airlines cancellations and Muscat airport closure at 12:23 UTC. More significantly, Soloviev's channel posted Turkey's presidential statement at 13:33: Ankara would not permit its territory or airspace to be used for attacks. This was a sovereignty declaration disguised as an aviation update.

Readovka reported Dubai airports suspended operations at 12:56 UTC, and CIG Telegram began challenging unverified claims — noting at 14:19 that 'despite multiple reports of airstrikes or American or Israeli jets flying inside Iranian airspace, none have been backed up by any credible evidence.' By 15:05, CIG was carrying Saudi Arabia's condemnation of Iranian attacks on its airbases alongside its claim of not allowing US aircraft to use Saudi airspace. The airspace thread was becoming a litmus test for neutrality claims — who was closing airspace to protect civilians, and who was closing it to signal non-participation?

Friday evening through Saturday early morning, February 28 16:00 UTC – March 1 06:00 UTC — the first night of the war. BBC Persian entered at 17:12 UTC with Iran's Civil Aviation Organization announcing complete closure of Iranian airspace 'until further notice.' This was the first official Iranian confirmation, arriving eleven hours after strikes began. Russian channels dominated volume with 22 of 33 items, tracking everything from Rosaviatsia's count of cancelled Russian flights (29 domestic, 31 foreign at 16:32 UTC) to IntelSlava's footage of Dubai residents watching Iranian missiles overhead at 16:37.

The thread's geographic scope expanded dramatically. Rybar reported fires near Erbil, Iraq at 18:20 UTC. Anadolu carried the striking detail that over 100,000 Israelis were stranded abroad at 22:34 UTC — a number that humanized the crisis beyond the Gulf. Middle East Spectator noted at 00:17 UTC on March 1 that Jordan had conspicuously never closed its airspace, a strategic silence that spoke volumes about Amman's positioning. The overnight hours revealed airspace as a map of allegiances.

Saturday morning to afternoon, March 1 (06:00–16:00 UTC) — day two. The amplification surge began with IntelSlava reporting at 06:55 UTC that Iran's airspace would remain closed until March 3 — the first timeline estimate, signaling this was not a brief disruption but a multi-day crisis. TRT World produced the first global-scope aviation article at 07:38: 'Air travel disruption spreads across continents,' framing the story beyond the Middle East.

Rybar's detailed analysis of overnight Iranian strikes on UAE targets at 07:48 UTC explained why Dubai remained closed, while CIG Telegram posted updated NOTAM expiration times at 10:25, becoming a de facto aviation information service. Rozhin's most-viewed post of the window (43,300 views at 12:20 UTC) mapped the obstacle chain between Iran and Israel — ships, bases, air defenses — effectively visualizing the airspace as a layered battlespace. Arab outlets contributed four items focused on Gulf state responses, while Malaysian media (Malay Mail) carried the thread to Southeast Asian audiences, reflecting the disruption's impact on the Dubai-Singapore travel corridor.

Saturday evening to Sunday early morning, March 1 16:00 UTC – March 2 02:00 UTC — the thread's second night. Chinese sources entered via Xinhua at 17:36 UTC, though the first flagged item was a stray match (Afghanistan-Pakistan airstrikes). The real Chinese entry came through web articles tracking Gulf aviation status with characteristic factual restraint. TASS reported at 17:00 UTC that at least 800 Russian citizens were stranded in Doha awaiting Qatar's airspace reopening — Moscow was now actively tracking its citizens as a diplomatic pressure point.

The thread expanded into new dimensions. Qatar's Interior Ministry banned all civilian drone use nationwide at 20:50 UTC. Maria Zakharova, Russia's Foreign Ministry spokesperson, posted at 21:45 about foreign airlines adjusting schedules due to Middle Eastern airspace closures — elevating the story from aviation chaos to diplomatic concern. CIG Telegram captured a remarkable real-time intercept at 23:51: Cyprus air traffic control warning aircraft that 'there are a lot of missiles between Cyprus and Iran' — the airspace thread momentarily fusing with the kinetic war in the most literal possible way.

Sunday early morning, March 2 (02:00–04:00 UTC) — a brief overnight spike driven almost entirely by non-core sources. Malay Mail produced multiple articles reflecting Southeast Asian anxiety about the crisis's global reach. A Uzbek-language Telegram channel (@kun_uz) announced the formal suspension of all Umrah pilgrimage flights to Saudi Arabia at 02:30 UTC — the aviation disruption now touching religious obligations, a dimension absent from Western or Russian coverage.

IntelSlava posted Pentagon strike footage at 03:54 UTC, the kinetic reality underlying every cancelled flight. This was a thin window informationally, but the geographic spread of sources — Malaysia, Uzbekistan, Switzerland — revealed how the airspace story had become genuinely global by hour 44 of the conflict.

Sunday morning March 2 through Tuesday midday March 3 (04:00 UTC Mar 2 – 14:00 UTC Mar 3) — the long middle of the crisis. Israeli sources entered this window, though the thread's Israeli dimension was less about aviation reporting and more about the stranded-citizen crisis. The most significant ecosystem development was the emergence of a Russian consular narrative: Soloviev reported at 06:37 that Dubai authorities ordered hotels to extend tourist stays, and TASS quantified Russian tour operator losses at $1.5 million per day at 07:05.

Central Asian sources emerged strongly. Asia-Plus (Tajikistan) reported Somon Air suspending Dushanbe-Dubai flights at 16:56, then Tajik embassies issuing safety advisories at 21:49. CIG Telegram tracked France deploying air defense to Cyprus at 11:13 on March 3 — the airspace thread now overlapping with NATO's defensive posture. By this point the aviation story had fragmented into regional sub-narratives: Gulf hub disruption, stranded-traveler diplomacy, and the militarization of airspace in countries not party to the conflict.

Tuesday afternoon through Wednesday morning, March 3 14:00 UTC – March 4 08:00 UTC — the crisis entered its fourth day with no resolution in sight. Times of Oman reported nearly 8,000 transit passengers stranded in Qatar alone at 14:08 UTC. Xinhua flashed at 15:19 that Israeli airspace would 'gradually open Wednesday night' — a signal that even Israel recognized prolonged closure was unsustainable, though the qualifier 'gradually' hedged against renewed missile attacks.

The thread took a dramatic turn when Soloviev reported at 18:29 that British F-35Bs had shot down a drone over Jordanian airspace — the first NATO combat engagement tied directly to the airspace thread. UAE's Foreign Ministry stated through TASS at 20:55 that it had not permitted its territory or airspace for attacks on Iran, a claim that sat uncomfortably alongside the ongoing closure of Emirates flights. Nigeria's Punch newspaper carried the stranded-traveler story at 20:42, and by 07:24 on March 4, Singapore's Channel News Asia reported Emirates and Etihad resuming limited UAE-Singapore service — the first tentative reopening signal.

Wednesday morning, March 4 (08:00–10:00 UTC) — day five opened with the airspace crisis intensifying rather than resolving. Al Jazeera confirmed Qatar Airways flights remained suspended at 08:18 UTC. Russia's MID posted at 08:25 that Thailand had imposed entry restrictions due to the Middle Eastern situation — the disruption now affecting tourism flows far beyond the Gulf. Kashmir Observer ran a comprehensive piece at 08:39 on global shipping and air cargo supply chain disruption, framing the story through a South Asian economic lens.

TASS reported Emirates suspending all Dubai flights until 22:59 Moscow time on March 4, and critically, that Iraqi airspace would remain fully closed for at least three more days at 09:17. Kuwait Times carried news of Kuwaiti armed forces intercepting missiles and drones — the airspace was not merely closed but actively contested.

Wednesday mid-morning, March 4 (10:00–12:00 UTC) — a compressed two-hour window that marked the thread's most dramatic escalation. Anadolu reported Kuwait 'dealing with a wave of missiles and drones' at 10:09 UTC. Then the bombshell: Rozhin reported at 11:47 that Turkey had shot down a ballistic missile in its airspace — no casualties, no damage, but an extraordinary breach. Xinhua flashed the Turkish military's confirmation at 11:57, and the story migrated instantly across ecosystems.

This was the moment the airspace thread intersected with the war's geographic expansion. A missile entering Turkish airspace — NATO airspace — transformed the aviation safety story into a potential Article 5 trigger. Al Masirah (Houthi media) offered a different angle at 10:54: a second Emirati aircraft was urgently transporting stranded Israeli soldiers back to Israel, framing UAE aviation as Israeli military logistics. CIG Telegram geolocated a US THAAD deployment at Jordan's Muwaffaq Al-Salti Air Base at 11:01, the air defense architecture literally reshaping which corridors remained flyable.

Wednesday noon March 4 through Thursday morning March 5 (12:00 UTC Mar 4 – 08:00 UTC Mar 5) — the thread's peak activity window, with 43 items across the broadest ecosystem spread yet. The Turkey missile incident dominated the first hours: Rozhin reported at 12:32 that Turkey's foreign minister called his Iranian counterpart demanding no more missiles through Turkish airspace. TRT World carried NATO's confirmation of shooting down the Iranian ballistic missile at 12:59. Readovka published footage of the intercept at 13:05.

Then the framing war escalated. Rozhin noted at 13:17 that Hegseth claimed the US and Israel would 'fully control Iranian airspace within a week' — transforming the thread from civilian disruption to declared military objective. CIG Telegram carried Hegseth's elaboration at 16:16: the war could last 'up to 8 weeks.' By early March 5, Channel News Asia reported the first Singapore repatriation flight landing — families reunited after days of uncertainty. The human-interest angle provided counterpoint to the militarization narrative. Israeli sources appeared tracking air superiority claims and stranded-soldier logistics, while Chinese outlets (5 items) maintained steady factual relay of each development.

Thursday March 5, 08:00 UTC through Friday March 6, 10:00 UTC — the sixth and seventh days brought the Azerbaijan escalation and continued global displacement. The thread's most significant new dimension emerged at 09:44 UTC on March 5: Azerbaijan's MFA condemned Iranian drone impacts in Nakhchivan, with two people injured. By 14:54, IntelSlava reported Azerbaijan closing its airspace near Iran for 12 hours. Rozhin editorialized at 14:55: 'Iranian comrades should be wary, I wouldn't be surprised by attempts to drag Azerbaijan into the conflict.'

The dva_majors channel framed it more sharply at 14:35: 'Regional countries are being set against Iran' — with Aliyev calling the drone impacts a 'terrorist act.' The airspace thread was now documenting the conflict's centrifugal spread into the Caucasus. Meanwhile, the humanitarian story continued: Singapore arranged evacuation flights to Oman (CNA, 07:29 Mar 6), and Readovka's most viral post of the window (66,300 views) compared UAE flight paths to Moscow taxi routes — 'planes over the UAE have started to look like Moscow taxis, zigzagging across the map the same way.'

Friday, March 6 (10:00–22:00 UTC) — one week since the strikes began, and the airspace thread remained unresolved. Zakharova posted at 10:50 that nearly 21,000 passengers had been transported from UAE and Oman on 105 flights since the start of the week — Russia's consular operation now a quantified achievement narrative. TASS reported at 12:56 that Poland was closing its eastern airspace for three months, extending the thread's footprint deep into Europe.

The thread's endgame framing crystallized in the evening. Middle East Spectator posted at 18:54 and 18:55 (duplicated, suggesting urgency) that the White House claimed to be 'well on track to control Iranian airspace.' Quds News reported Aqaba airport in Jordan receiving planes designated to transport stranded Israelis at 20:06 — Jordan's open-airspace policy now serving Israeli evacuation needs, a quiet operational detail with significant political implications. A Flydubai air corridor to Ben-Gurion was announced via Israeli broadcaster Kan at 11:17, marking the first commercial link back to Israel. After seven days, the airspace thread had not reached closure but rather a new equilibrium: permanent disruption managed through ad hoc corridors, evacuation flights, and military-controlled zones.