Safe Airspace – Conflict Zone and Risk Database

View Map

Updates Alerts

19 Jun

Risk summary updated: Latest developments, current airspace restrictions, operational risks.

04 Jun

Risk summary updated: Drone attacks across Russia are ramping up - including areas around Moscow, with some reaching as far as Siberia.

28 Feb

Country summary updated to reflect flight bans issued by several countries due to risk from military conflict.

17 Feb

Country summary updated: Added info on spillover risks from the conflict in Ukraine including Russian drone and missile strikes.

28 Feb

Country summary updated to reflect airspace warnings issued by several countries due to risk from military conflict in Ukraine.

28 Apr

Updated summary for Albania.

Pakistan carried out airstrikes against targets in eastern Afghanistan overnight on June 28-29. They appear to have followed a militant attack in Karachi the day before. This is the latest flare-up of violence between the two countries despite earlier attempts at a ceasefire. No new airspace warnings have been issued - flights continue to operate over central Afghan airspace or via the P500/G500 corridor. However we suggest treating the shared border region as higher risk at this time due to unannounced military activity.

An Airbus A321 reported a drone strike while on approach to Runway 13L on June 29. The collision occurred at around 3000 ft, with impact just above the cockpit. No damage was found afterwards, but the FAA is investigating. This follows a similar incident at KEWR/Newark on June 26 when a Boeing 737 narrowly missed a drone at 2000 ft while landing. Recreational drones are normally limited to 400 ft AGL unless operating under special approvals - these reports suggest that some are being operated well above that limit close to major airports.

The GPS interference reported near the Kamchatka Peninsula on June 21 is affecting aircraft on the North Pacific routes between Asia and North America. An FAA analysis suggests an unknown jammer has affected more than 100 civil aircraft since then. Most crews reported GPS jamming, while at least four described spoofing. The interference spans the Magadan West and Anchorage Oceanic FIRs, centred near NUZAN off the southern tip of the peninsula. Anchorage ARTCC (ZAN) issued Notam A2219/26 warning about it on June 24, but there is still no equivalent warning from the Russian side.

Another member report of GPS interference in the OMAE/Emirates FIR. Aircraft type was a Global 6000. The event began on descent into OMDW/Al Maktoum near UMEKO (20nm north of Muscat). GPS was deselected beforehand. During descent, several amber and cyan CAS messages appeared. This was followed by a full loss of GPS signal along with synthetic vision, ADS-B out, TAWS and terrain map. ATC were advised. After landing the signal returned, but one receiver couldn’t be recovered. They later departed with it in-op. This adds to a growing number of reports of GPS interference in UAE airspace.

A GPS interference warning was issued by the PAZA/Anchorage Oceanic FIR near NUZAN at approx 2100z on June 21. An OPSGROUP member subsequently reported significant interference while westbound on the R220 airway at FL450 between NUZAN and NIPPI in a G650. GPS was completely lost, along with ADS-B and synthetic vision. When the signal returned, it appeared to be spoofed displaying erroneous altitude and time. The event lasted from 2134-2222z. ATC were advised, and other aircraft in the area reported similar issues. The source remains unclear - no related Notams were published by adjacent Russian airspace.

The US and Iran have agreed to keep the ceasefire in place through at least mid-August. So that reduces concerns about a sudden return to missile attacks and airspace closures, but for ops in the region not much has changed yet. Some Middle East carriers are overflying Iraq and Syria again, but most traffic is still going south via Egypt-Saudi or north via the Caucasus-Afghan. Kuwait is still closed to overflights, and routing restrictions remain in place across Bahrain, Qatar and the UAE. There have also been no significant downgrades to any of the airspace warnings updated in recent weeks, another sign that not much has changed yet.

Missile strikes between Iran and Israel resumed overnight on June 7 for the first time since the April ceasefire. Israel struck Beirut, Iran responded with missile attacks on Israel, and Israel then carried out retaliatory strikes inside Iran. Despite reports of widespread airspace closures, the actual impact today looks fairly limited so far. Iraq's ORBB/Baghdad FIR is the main new closure, while much of the same restrictions remain in place elsewhere. One noticeable change is that several Middle East airlines which had recently started overflying Syria again now appear to be avoiding it, routing south via Egypt and Saudi Arabia instead. So despite the overnight escalation, the overall routing picture hasn't changed much for now.

Iran overnight launched ballistic missiles at northern Israel for the first time since the April ceasefire, in response to Israeli strikes on Beirut earlier in the day. Israel is also reported to have conducted retaliatory strikes on Iran overnight, although details remain limited. Following the attacks, airspace closures spread quickly across the region, with Iran, Iraq, Jordan and Qatar all temporarily closing airspace, while Syria closed its southern airspace and suspended operations at Damascus. As of 2300Z, most of the affected airspace has reopened, with operations returning to normal across southwestern Saudi Arabia, Doha, the UAE and Bahrain. At this stage, the closures appear to have been precautionary measures while authorities assessed the scope of the attacks.

There was a new wave of drone strikes on infrastructure at the airport on May 23 - reportedly the fourth time the field has come under fire recently. Rebel forces are likely responsible - the same group involved in ongoing fighting around North Kivu and FZNA/Goma near the Rwanda border. The US Embassy has previously warned that the security situation in and around the airport remains unpredictable. While Kisangani is not in the main conflict zone, it is a reminder of the broader instability in DRC. Several states maintain airspace warnings for the eastern portion of the Kinshasa FIR due to potential anti-aircraft fire.

On May 15, suspected drones entered the airspace over southern Finland, triggering a military response and shutting EFHK/Helsinki for around three hours. Several flights diverted. The drones appear to have been linked to a large Ukrainian strike on Russian infrastructure near St Petersburg. Ukraine says the incursion was unintentional and caused by GPS interference. Finland and the Baltic States continue to warn about spill-over risks in the region, particularly over the Baltic Sea where military activity remains high.

The security situation has continued to deteriorate since militant groups launched coordinated attacks across the country on April 25. Risk to aviation remains high - especially in the north where fighting between insurgent and government forces continues. The UK has issued a new airspace warning advising operators not to enter the portions of the DRRR/Niamey and GOOO/Dakar FIRs over Mali at levels below 25,000 ft AGL due to the risk from anti-aircraft fire and military activity. France has already issued similar advice. See safeairspace.net for more info.

The security situation has escalated sharply. On April 25, multiple armed groups carried out coordinated attacks nationwide against state and military targets, with gunfire and explosions reported near GABS/Bamako. Sporadic fighting is ongoing. France has issued a new airspace warning advising French operators not to operate to/from GABS, or use it as an alternate. Several other states maintain active airspace warnings due to risk of anti-aircraft fire and terrorist activity. See safeairspace.net for more info.

Spoofing in Eastern Europe / Black Sea is now producing extreme position errors, with aircraft appearing thousands of miles from their actual position (including false positions over South America). Data from GPSwise shows repeated events, not a one-off glitch. This is a step change from previous spoofing, which typically displaced aircraft locally rather than globally. No real change to what you’ll see onboard, but the scale of the position error can now be much bigger. The wider cause is ongoing electronic warfare in the region, and this may be linked to newer spoofing systems such as Ukraine’s Lima EW. If you’re operating in this airspace, expect unreliable GNSS and be ready to revert to conventional nav if required.

The central Middle East corridor remains largely shut. Iran and Kuwait remain closed. Qatar, UAE and Bahrain are open but tightly controlled - overflights restricted, corridors in use, and prior approval required. Iraq is technically open but not usable in practice due to the Kuwait closure. Most operators continue to reroute north via the Caucasus or south via Egypt-Saudi-Oman, and most international carriers are not returning to Gulf hubs. A temporary US-Iran ceasefire on April 8 has not restored normal ops, and talks to stabilise it collapsed April 12-13. Risk remains high, with threats around the Strait of Hormuz and ongoing strikes across the region. Expect short-notice changes and continued disruption.

Missile and drone launches from Yemen toward Israel have been ongoing since March 28, with further activity this week. This pushes spillover risk into the Red Sea corridor, a key reroute via Saudi and Egypt. Expect increased air defence activity, possible ESCAT measures (airspace restrictions and traffic prioritisation), and GNSS interference. Aircraft routing along the southern edge of the OERK/Jeddah FIR, near the Yemen border, face the highest exposure. Several airspace warnings remain in effect - see safeairspace.net.

A major space launch is planned for Cape Canaveral on Apr 1, with a primary window 2224-0109Z (later on back-up days through Apr 8). Expect large hazard areas and short-notice ATC restrictions. The main impact is off Florida’s east coast (KZMA), where airspace closures may affect coastal routes and some NAT entry/exit points. Additional debris response areas extend into LPPO/Santa Maria and TTZP/Piarco - if triggered, expect holding or reroutes for eastbound NAT traffic and Caribbean flows, and possible delays for westbound traffic entering TTZP.

Balloon and kite hazards are particularly bad at this time of year due to Lent. We’ve had a new member report from a recent departure off Rwy 10L. During the takeoff roll (around 120kts), a large balloon landed on the runway ahead of the aircraft (B787). The takeoff continued over the object which consisted of a thick rope and reflective material. ATC were advised but have limited ability to control or track the issue. Consider the risk of engine ingestion or airframe damage elevated at this time.

EASA and Eurocontrol have published a joint action plan (attached) to tackle GPS interference across Europe. Short term, it’s about managing the problem including better monitoring, clearer Notams, standard procedures and more use of back-up nav (VOR/DME/ILS etc). Long term, the focus is on building resilience with upgraded aircraft systems and alternative nav. There’s no immediate operational change but expect a more coordinated and consistent response in areas where interference is occurring.

Just one significant update in the past 24 hours. The UAE briefly closed its entire airspace on Mar 17 as a precaution during new missile and drone threats. The shutdown lasted about two hours before reopening, but caused fresh disruption to already limited ops into OMDB/Dubai and OMDW/Al Maktoum. This comes just one day after a drone strike near OMDB hit fuel storage, caused a large fire, and forced a temporary suspension of ops with at least 65 diversions. It shows how quickly the situation can change - even FIRs that are technically open can shut with little or no warning.

Several developments over the past few days. A drone strike near OMDB/Dubai on Mar 16 caused a fire at fuel storage and briefly suspended operations with some diversions. Drones also damaged OKKK/Kuwait airport radar on Mar 14, and rockets struck near ORBI/Baghdad airport on Mar 15. In Israel, the earlier BizAv ban at LLBG/Tel Aviv appears to have eased - operators can again apply for PPR, though slots remain extremely limited. Saudi Arabia has also issued new Notams introducing contingency routings and altitude restrictions in the OEJD/Jeddah FIR, with some routes unavailable due to military activity. Main Europe-Asia bypass routings remain north via the Caucasus or south via Egypt-Saudi-Oman.

A few operational updates today as the Middle East conflict continues. OKKK/Kuwait was hit by several drones on March 12 causing damage at the airport, though no casualties were reported. In Oman, drones struck a port near OOSA/Salalah, causing a large fire and heavy smoke near the airport. There have been no incidents reported at OOMS/Muscat, which remains open and handling rerouted and evac flights while much of the region’s airspace is closed. Meanwhile Azerbaijan is directing overflying traffic in the UBBA/Baku FIR to specific boundary crossings, useful for east-west flights routing through the Caucasus to avoid Middle East airspace closures.

A few operational updates today as the Middle East conflict continues. Israel has advised that no BizAv flights will be approved at LLBG from March 11 until further notice, with only ambulance and state flights permitted. Some Opsgroup members say their LLBG permit requests have already been rejected or withdrawn. Across the Gulf, missile and drone attacks continued overnight, with Saudi Arabia, Kuwait and Qatar reporting interceptions and air defence alerts in the UAE briefly causing arrivals to hold at OMDB/Dubai. Member reports today suggest the western routing via Saudi-Egypt is working fine, with normal ops reported at OERK/Riyadh, but with GPS issues near Riyadh and higher insurance premiums for the trip.

Update: overnight March 9-10 another wave of missile and drone launches from Iran targeted several Gulf states. Saudi Arabia, Kuwait, the UAE and Qatar all reported interceptions. In the UAE, a missile alert briefly caused arrival holding at OMDB/Dubai but no airport strikes or new airspace closures have been reported. One OPSGROUP member who recently operated into OMDW/Al Maktoum reported generally smooth ops, with GPS jamming beginning near Riyadh and a short departure delay due to military activity. The overall routing picture remains unchanged - the central Gulf corridor remains closed, with traffic routing north via the Caucasus-Afghanistan or south via Egypt-Saudi-Oman.

Update: the status of Gulf airspace remains largely unchanged. Over the weekend multiple drone and missile interceptions have continued across the region. OMDB/Dubai briefly closed on Mar 7 after a drone strike near Terminal 3, reopening later the same day. OTHH/Doha has begun a very limited reopening with some approved flights now operating. UAE airports remain operational via the OMAE corridor routing system, but capacity is tight. OOMS/Muscat issued a “scheduled flights only” Notam, though local handlers report BizAv ops continuing normally. The central Gulf corridor remains closed, with traffic routing north via the Caucasus-Afghan or south via Egypt-Saudi-Oman.

Small developments overnight, but the airspace picture remains largely unchanged. Airlines have started operating more limited flights from UAE airports using the restricted corridor system. Oman has issued a Notam confirming the routes to be used through the OOMM/Muscat FIR for traffic to and from UAE airports. Missile and drone activity continued across the Gulf overnight, including interceptions near Doha and in the UAE, with no confirmed impacts on civil airports. Ops at LLBG/Tel Aviv were briefly disrupted when an El Al repatriation flight had to go around during missile sirens. Otherwise the central block of Middle East airspace remains closed with the same routing options as yesterday. If you've operated in the region this week, please get in touch if you have any info to share.

Iranian drones crossed the Iran-Azerbaijan border early on March 5 and one struck the terminal building at UBBN/Nakhchivan airport. Damage appears limited to the terminal area with no confirmed runway impact. A Notam has since closed the UBBA/Baku FIR south sector today, which covers the airspace around UBBN. This is the first time the current Iran conflict has spilled into the Caucasus, close to the Armenia-Azerbaijan overflight corridor used by traffic avoiding the Middle East airspace closures. No impact reported to UBBB/Baku airport or the main overflight flows so far.

Middle East airspace restrictions remain largely unchanged since yesterday’s update. A small number of repatriation flights have now resumed from UAE airports under the restricted corridor routing via Saudi/Oman airspace, though most airlines continue to extend cancellations. There have also been additional missile and drone strikes reported across the region, including in Qatar, Kuwait, Oman and Saudi Arabia. The central corridor between Israel and Iran remains shut - OIIX/Tehran, ORBB/Baghdad, OTDF/Doha, OBBB/Bahrain, OKAC/Kuwait and OSTT/Damascus FIRs are still closed by Notam, and LLLL/Tel Aviv remains PPR only. Europe-Asia traffic continues to reroute either north via the Caucasus-Afghanistan or south via Egypt-Saudi-Oman. If you've operated in the region this week, please get in touch and share your experience.

Middle East airspace remains heavily restricted as of March 3. The central corridor is still shut. OIIX/Tehran, ORBB/Baghdad, OTDF/Doha, OBBB/Bahrain, OKAC/Kuwait and OSTT/Damascus FIRs are closed by Notam, and there is no through routing across the Gulf. LLLL/Tel Aviv remains PPR only. The OMAE/Emirates FIR is partially open but only via strict waypoint corridors, with ESCAT areas active, flow control in force and GNSS interference reported. UAE airports are technically accessible under these restrictions, but commercial schedules remain heavily disrupted and many airlines are extending cancellations or operating relief flights instead of normal services. Doha, Bahrain and Kuwait airports remain unavailable due to FIR closures. Europe-Asia traffic continues to route south via Egypt-Saudi-Oman or north via the Caucasus-Afghanistan, with both corridors seeing increased demand.

The UK has issued an airspace warning for the OAKX/Kabul FIR which is unrelated to the current Iranian crisis. Following renewed border clashes with Pakistan late last week, it appears to reinforce long-standing advice to consider the risks of heightened military activity before entering. While Afghanistan is a popular Iran-avoidance option right now (including the G500/P500 corridor), it’s important to note that these routes are not guaranteed to be risk-free. There’s no evidence that airlines are actively avoiding Afghan airspace, but treat the shared border region with Pakistan as higher risk at the current time.

Middle East airspace remains heavily restricted as of 2 March 1330z. The central corridor is still shut. OIIX/Tehran, ORBB/Baghdad, OTDF/Doha, OBBB/Bahrain, OKAC/Kuwait and OSTT/Damascus FIRs are closed. LLLL/Tel Aviv is closed except limited PPR. There is no through routing across the Gulf. The OMAE/UAE FIR remains partially open under new Notam issued today. The Notam permits arrivals and departures for Dubai, Abu Dhabi and other UAE airports via tightly defined waypoint corridors. But official airport updates still describe operations as suspended or heavily disrupted, so this is controlled access rather than a full reopening. Airports in Doha, Bahrain and Kuwait remain unavailable while their FIRs are closed. Europe-Asia traffic continues south via Egypt-Saudi-Oman or north via the Caucasus-Afghanistan. Both corridors are busy. Check our article for more info.

Update (2000z Mar 1). US and Israeli operations continue against targets in Iran. Retaliatory missile and drone activity has been reported across the Gulf, including Iraq, Kuwait, Bahrain, Qatar and the UAE. Israel has also been targeted. Missiles were reportedly fired toward Cyprus, with no confirmed impacts there. Airspace closures remain broad. At time of writing, the following FIRs are closed: OIIX/Tehran, ORBB/Baghdad, OBBB/Bahrain, OTDF/Doha, OKAC/Kuwait and LLLL/Tel Aviv. OMAE/Emirates FIR remains technically open but with very limited civil traffic. EASA advises operators not to overfly these FIRs at any level, and includes OJAC/Amman, OLBB/Beirut, OOMM/Muscat and OEJD/Jeddah in its risk advisory (attached). Current routings show two main corridors in use: south via Saudi Arabia, the Red Sea and Egypt, or north via Georgia, Azerbaijan and Turkmenistan.

Following the reported death of its leader, Iran has launched a fresh wave of missiles and drone strikes across the region. One reportedly hit Terminal 3 at OMDB/Dubai. Further strikes have been reported at OMAA/Abu Dhabi, high-rise buildings in Bahrain, and Tel Aviv. There have also been additional targets in Qatar and Syria. The risk of further escalation remains likely. Airspace closures are widespread. LLLL/Tel Aviv, OKAC/Kuwait, OTDF/Doha, OBBB/Bahrain, OIIX/Tehran and ORBB/Baghdad FIRs are closed. The southern part of OSTT/Damascus FIR is also closed. This effectively blocks the central Middle East corridor. Traffic is diverting south via Saudi Arabia towards Oman, or north via Armenia, Azerbaijan, Georgia. There is heavy traffic through Afghanistan also. Expect significant reroutes and congestion in Saudi and Caucasus airspace. There is also potential flow control for aircraft using the L750 and P644 in Afghanistan. OMAE/UAE FIR and OJAC/Amman FIR remain open, but in practice no civilian aircraft are obeserved operating in them. All commercial flights into and out of the UAE, Qatar and Bahrain have been cancelled. There is no timeline for the resumption of services. The UK FCDO and US Dept. Of State are advising citizens in the UAE, Qatar, Bahrain and Kuwait to shelter in place. If you have aircraft positioned in the Middle East, notify your insurers immediately, as many policies carry war-risk exclusions. Crew on layover should follow hotel security instructions and keep movements to an absolute minimum. If you’re operating in the region and have more info to share, please join the conversation in Slack.

Update - US and Israeli strikes on Iran began early Feb 28, with reported impacts near military facilities. The situation is fluid and there is a credible risk of further action and retaliation. Airspace closures remain significant. OIIX/Tehran FIR is closed, with warnings the conflict area may extend over the Persian Gulf and Oman Sea. ORBB/Baghdad, OBBB/Bahrain and OTDF/Doha FIRs are closed. LLLL/Tel Aviv FIR is closed except for limited PPR civil movements. Saudi Arabia and Oman remain open, but expect congestion as traffic diverts south via Saudi into UAE and Oman, or north via Armenia, Azerbaijan and Georgia. Notably, the bulk of Europe–South East Asia traffic appears largely unaffected using the Georgia–Turkmenistan–Afghanistan routing. There are also reports that an Iranian ballistic missile wave destroyed the US AN/TPY-2 radar at Al Udeid, Qatar. This was a key early-warning radar for Gulf missile defence systems. US confirmation of damage is still pending.

US and Israeli strikes on Iran began early Feb 28, with multiple reports of impacts near military facilities. The situation remains fluid and there is a credible risk of further action and retaliation. Airspace closures are widespread. OIIX/Tehran FIR is closed, with a warning that the conflict area may extend over the Persian Gulf and Oman Sea. The ORBB/Baghdad, OBBB/Bahrain, and OTDF/Doha FIRs are all closed. LLLL/Tel Aviv FIR is closed to all flights except limited PPR civil arrivals and departures. This effectively blocks the central Middle East corridor. Traffic is diverting south via Saudi Arabia towards UAE and Oman, or north via Armenia, Azerbaijan and Georgia. Expect significant reroutes and congestion in Saudi and Caucasus airspace. Check Notams carefully - timings are short and subject to rapid extension. If you’re operating in the region and have more info to share, please join the conversation in Slack.

Fighting between Pakistan and Afghanistan is escalating, with further cross border strikes reported and increased military activity along the shared border. There is no indication civil aircraft are being targeted, and there is currently no evidence of airlines adjusting routings to avoid Afghanistan - flights continue to operate over central Afghan airspace or via the P500/G500 corridor. That route sits further from the main reported strike areas, but it is not guaranteed risk free. No new state airspace warnings have been issued. Afghanistan remains uncontrolled airspace - the OAKX/Kabul FIR is Class G with no ATC service. Review routing and cruise levels carefully and check safeairspace.net for current state guidance.

Level 1 Level 2 Level 3

Open country information in new window