Safe Airspace – Conflict Zone and Risk Database

View Map

Updates Alerts

01 Jul

Risk summary updated: The ceasefire between Israel and Iran has held so far. All airspace in the region has largely reopened, but the corridor between Israel and Iran remains high risk if the conflict resumes.

04 Jun

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

20 Sep

Risk summary updated: Ceasefire agreed between Armenia and Azerbaijan, following military conflict in the border zone. Azerbaijan has reopened the border airspace, but most operators are still actively avoiding the region, and routing north via Georgian airspace (UGGG/Tbilisi FIR) instead.

20 Sep

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.

New member report of GPS interference (possible spoofing). The event occurred in the north, after waypoint POGOK enroute to ENTC/Tromso, Norway. One FMS position froze, the other was recovered using IRS and DME. The event lasted approx 45 mins (aircraft type Gulfstream). ATC reported this is normal ops for the region. Expect similar events when operating near the border with Russia. These disruptions are more likely the result of Russian military GPS jamming (often traced to sources such as Kaliningrad and the St Petersburg region) spilling over into adjacent airspace.

EASA has downgraded its airspace warning for Iran. The previous Conflict Zone Information Bulletin (CZIB), which advised operators to avoid Iranian airspace at all flight levels, has been withdrawn. It has been replaced by an information note recommending that operators conduct a thorough risk assessment before entry. This change appears linked to the ceasefire agreement with Israel, announced on June 23. The ceasefire has reduced immediate tensions, but if the conflict resumes, the risk to civil aviation could rise quickly - especially from sudden or uncoordinated military activity. The FAA continues to prohibit US operators from entering the OIIX/Tehran FIR at all levels. See safeairspace.net for more info.

Good news: Cambodia and Thailand have agreed to an immediate and unconditional ceasefire starting midnight local time on Monday July 28 (1700z), following five days of intense fighting along their shared border. Both sides have committed to reopening communication lines and setting up a monitoring mechanism to maintain the truce. While this is a major step toward de-escalation, the situation remains fragile - caution is still advised near the border region. No changes so far to the Phnom Penh FIR danger area (SFC–UNL). VDPF Notam A0092/25 remains active.

A major military escalation began on July 24 along the central Cambodia-Thailand border, approximately 100-150 NM north of VDSA/Siem Reap. Cross-border fighting has involved artillery exchanges and Thai airstrikes using F-16s. Both countries have activated danger areas along much of the border, with restrictions extending up to UNL. The Notams do not reference the conflict directly, but military activity may pose a hazard to civil aviation at all levels. Caution is advised throughout the region. Check our article for more info.

There’s major construction happening at the airport, including runway work and taxiway expansion. Some important changes are covered in the Notams (like the suspension of certain ILS and RNP approaches and some SIDs). But a few pretty critical operational details are missing, like the runway being shortened to 2300 meters, THR 27 being displaced by 900 meters, and the loss of key lighting systems. These aren’t mentioned in any Notams and are only published in SUPs 56/25 and 75/25. Crews relying just on Notams or ATIS won’t get warned about the shorter runway or displaced threshold.

A reminder for crews operating into Germany: the LBA Security Department is still carrying out unannounced security checks on business jets. These are not ramp checks but covert tests to see if crew follow proper access control procedures. An OPSGROUP member has reported that at EDDB/Berlin recently, two individuals boarded shortly after arrival, once passengers had disembarked, and asked to see the insurance certificate. One pilot was inside with the handler while the other was alone onboard - suggesting the timing may have been deliberate. We've had multiple reports of operators being charged over 300 euros for these inspections, with no option to opt out. Crews should question anyone trying to access the aircraft, and ensure one pilot remains onboard until departure. For more info on this issue, check our article.

A new state of emergency is in effect due to an alleged plot to criminally target government officials and public institutions. Authorities are especially concerned about the potential for robberies and kidnappings. There are no curfews in place, but police have the power to arrest and detain without a warrant. TTPP/Piarco airport itself has a recent history of violent crime (see our previous alerts). The US Dept of State continues to advise against travel to Trinidad and Tobago due to these kinds of risks - be wary of crew security at all times.

We’ve had another OPSGROUP member report on a recent incident at LFMN that highlights the risks of the strict APU restrictions there. After towing from the Kilo apron to a Stand, the aircraft experienced electrical issues when connected to the stand’s GPU. Several system warnings appeared, followed by a complete blackout. APU start was initially denied despite cabin overheating. A mobile GPU was then brought in but failed to supply power. By the time APU use was finally approved, key navigation and communication systems had been damaged. The flight departed under MEL and required extensive repairs, resulting in significant cost and disruption. Check Airport Spy for the full report.

EASA have revised their CZIBs for the Middle East, effective July 7. They have completely withdrawn their warnings for Israel and Jordan plus nearby airspace in the HECC/Cairo and OEJD/Jeddah FIRs. For Iran, they continue to recommend against flights at any level. For Iraq and Lebanon, they have reverted back to what they previously advised for these countries prior to the recent conflict; operators should avoid Iraq below FL320, and avoid Lebanon unless operating to/from OLBA/Beirut airport over water.

The Russian CAA has issued a warning about jet fuel contamination. Several incidents have occurred over the past two years involving fuel filter clogs. Samples taken revealed a number of nasties such as microorganisms, sulphur, paint particles and fibers which all indicate improper storage. Russia is one of the world’s suppliers of jet fuel. Several countries import the finished product - especially those in Central Asia (the Stans) along with China, Turkey, Belarus, Armenia, Azerbaijan, Mongolia and Egypt. It is important to use certified fuel suppliers who comply with internationally recognised fuel handling standards. If there is any doubt, ask for paperwork.

Iran has reopened the western portion of its airspace to all flights during daylight hours, from 0500–1800 local time (0130–1430Z). Most major airports, including Tehran’s OIII/Mehrabad and OIIE/Khomeini, have also reopened. The eastern portion of the airspace had already reopened on June 26. While a small number of airlines have resumed overflights, the majority continue to avoid Iranian airspace, choosing instead to route north via the Caspian Sea or south via Saudi/Egypt. Several countries still have active airspace warnings in place, advising operators to avoid the OIIX/Tehran FIR entirely.

At least two rockets landed inside the airport perimeter on June 30. The airport authority previously reported that they landed in both military and civilian areas, but didn’t cause any significant damage. It’s not clear who was responsible. Several countries have long-standing airspace warnings for Iraq, including the US which prohibits US operators from overflying the ORBB/Baghdad FIR below FL320 due to risks posed by military activity, and militant attacks against airports. A thorough risk assessment is essential if planning stops here or at other airports, including ORBI/Baghdad.

Since June 24, there has been no full-scale resumption of fighting between Israel and Iran - the ceasefire appears to be holding. Normal ops are slowly resuming throughout the region as airspace restrictions have eased. Flight tracking shows that major carriers are once again transiting Iraq’s ORBB/Bahdad FIR using eastern airways UM860 and UM688. Iran has reopened the eastern portion of its OIIX/Tehran FIR, and its western part is now available for overflight traffic above FL245 with special permission. Lower risk routings are still available either north via the Caspian Sea, or south via Saudi/Egypt.

The ceasefire between Israel and Iran appears to be holding. Israel has reopened for flights to LLBG/Tel Aviv, but only via specific routings. International flights are now running out of Terminal 3, and operators can submit schedules for approval. No update yet on BizJet access. Risk assessments remain essential before operating to Israel or Tel Aviv - there may be a ceasefire, but the risk is still high. Iran has issued a new Notam keeping its airspace closed, except for certain arrivals and departures with prior approval. All other airspace in the region has now reopened, but the corridor between Israel and Iran remains high risk if the fighting resumes.

Qatar, Bahrain, and Kuwait FIRs have reopened following Iranian missile strikes on a US airbase near Doha last night. The overwater portion of the UAE FIR is also open again. Iraq has announced the reopening of its airspace, closed since June 13. A US-brokered ceasefire between Israel and Iran is now in place but already under strain - Israel accuses Iran of violating it with missile launches (denied by Iran) and has vowed heavy strikes on Tehran. Whether those go ahead remains to be seen. So the current airspace picture is this: Israel and Iran remain closed, and while nearby routes have reopened, airspace between the two remains at risk - from military activity or misidentification. Full updates are in the Special Briefing for the Middle East in your Dashboard. OPSGROUP Members are requested to report any additional information or changes to team@ops.group.

Iran is reporting that it has attacked a US airbase in Qatar. It says "devastating missiles" targeted Al Udeid Air Base (OTBD), which is 18nm west of the main Doha airport (OTHH). Qatar says that their "air defenses successfully thwarted the attack and intercepted the Iranian missiles”. The FIR's of Bahrain and Qatar are closed. The Emirates FIR (UAE) is also now partially closed around specific coordinates (see Notam A1757/25). Full updates are in the Special Briefing for the Middle East in your Dashboard. OPSGROUP Members are requested to report any additional information or changes to team@ops.group.

On June 22, the US launched airstrikes on Iranian nuclear sites, marking a major escalation in the Iran-Israel conflict. While there’ve been no direct threats to civil aviation, Iran has warned US involvement could trigger retaliation against American military assets - possibly via proxy groups. This raises airspace risk over Gulf states like Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, and the UAE. EASA also updated its Conflict Zone Bulletin that day, still advising against flights over Iran, Iraq, Israel, Jordan, and Lebanon. It now highlights spillover risks within 100NM of Israel’s western and southern borders, affecting parts of Egypt’s HECC/Cairo FIR (mainly over Sinai) and the northern OEJD/Jeddah FIR in Saudi Arabia. Airspace closures remain in place over Iran, Iraq, and Israel. The region is still highly unstable, with missile activity, GPS interference, and continued military build-up. Check the full briefing in your members Dashboard, updated as new information becomes available.

Pro-Palestinian activists breached EGVN/Brize Norton RAF base on June 19, entering undetected and spraying red paint into the engines of two Airbus Voyager refuelling aircraft. They also claimed to have caused additional damage with crowbars. The incident raises questions about security at a key UK military transport hub - which also permits private BizAv flights. The last time members of this group carried out a similar airport intrusion was at EINN/Shannon in May 2025, when they breached the runway and vandalised a US military-chartered aircraft.

A member has reported a particularly bad GPS jamming encounter over the Andaman Sea while enroute from Thailand to the UAE (Global 6500). GPS inputs had been disabled for the crossing of Myanmar, but were re-activated clear of the coast. A short while later, the GPS signal was lost and two FMS’s were corrupted. The flight continued using INS only as there were no ground aids within range for position updates. This lasted for approx. 30 minutes before the signal was regained prior to entering Indian airspace.

Iran has issued a new Notam warning that a conflict zone exists over international waters in the Persian Gulf and Gulf of Oman within the OIIX/Tehran FIR. This is especially relevant to traffic currently operating to/from Kuwait, Bahrain, Qatar and the UAE in close proximity to the area. The Tehran FIR remains closed, but spillover risk remains in adjacent FIRs. Jordan has also issued a Notam warning of potential short-notice closures within the OJAC/Amman FIR. Meanwhile, for overflights rerouting south via Egypt, several airways in the northern part of the HECC/Cairo FIR now have new restrictions in place until June 22. Check the full briefing in your members Dashboard, updated as new information becomes available.

GPS interference is now a regular occurrence in the Baltic region, particularly around Kaliningrad, Eastern Finland, the Baltic Sea, and nearby airspace. A recent member report from a flight over Finland noted complete GPS1/2 signal loss, ADS-B failure, unavailable terrain data, and FMS/GPS position monitoring loss. The aircraft reverted to DME/DME navigation and the system kept position accuracy within about 0.3nm. Reported to ATC and it was casually acknowledged as "this has been happening". If you're flying in the area, be prepared for GPS interruptions and rely on conventional nav as needed. To check the latest jamming/spoofing hotspots, check the live maps via the link.

GPS spoofing has been detected throughout the region due to the ongoing conflict between Israel and Iran. New additions include both the Persian Gulf and Gulf of Oman with traffic operating to/from both Doha and Dubai affected. This is typically being presented as a position shift to show the aircraft over or near Bidkhun, Iran. The UAE AIP contains contingency procedures for GPS interference (GEN 1.5.5) which includes advising ATC and requesting a revised clearance using alternate means of navigation.

Iran and Israel have exchanged fire for a fifth consecutive day, with explosions reported over Tehran and Iran launching two waves of missiles toward Israel overnight. Air raid alerts were triggered, though the attacks were less intense than previous nights. Airspace risk remains unchanged - Iran, Israel, and Iraq remain closed, with very limited exceptions. High risk also continues in adjacent airspace, particularly over Jordan, Lebanon, and Syria, where missiles and drones are transiting regularly. See the full briefing in your members Dashboard, updated as new information is available.

Over the weekend, the conflict between Israel and Iran has intensified - both sides have continued to exchange fire with ballistic missiles, drones and widespread activations of air defence systems. There has been no reduction in risk to civil aircraft. The airspace of Iran, Iraq and Israel remains closed with very few exceptions. Lebanon and Jordan have reopened, with the latter requiring 30 mins of extra fuel for inbound aircraft. Beware though that both the FAA and EASA strongly advise against overflights of any of the above countries. Routes to avoid the area are heavily congested (north via the Caspian Sea, or south via Egypt and Saudi). See the full briefing in your members Dashboard, updated as new information is available.

As Israel awaits a potential return offensive from Iran, it's apparent that this situation is very different to earlier Israel-Iran exchanges of fire. Israeli airlines have moved their entire fleet out of the country. Earlier today, El Al completed repatriation of aircraft to European airports including Milan, Rome, Sofia, and Larnaca. The airline has cancelled all flights. Arkia, another Israeli carrier, moved their aircraft to Cyprus this morning. LLBG/Ben Gurion is currently almost empty of aircraft. A number of the remaining airlines to operate to Tel Aviv have suspended flights to Israel until well into the second half of this year. It is clear that the expectation of an attack on Israel by Iran, and associated risk to the airspace of Iran, Iraq, and Jordan, is being treated as very likely.

An analysis from the FAA is available via the Special Briefing in your members Dashboard. The key message is that the US assesses that, "there is likely a critical risk to aircraft operating at any altitude in the airspace between Israel and Iran from offensive weaponry, the subsequent air defense responses, and the resulting debris. Potential retaliatory attacks against Israel and regional U.S. assets will expand the conflict and will likely pose a risk to aircraft operations in other parts of the Middle East and Africa". See full note in the Special Briefing.

A key element in the current Middle East airspace situation is the strong likelihood that this will continue for several weeks - Israel has stated their operation will continue for this length of time. Currently the FIR's for Israel, Syria, Jordan, Iraq, and Iran are all closed, with a few exceptions. Any airspace that lies between Israel and Iran is at risk, either directly from counter-missile activity or indirectly through misidentification. There are two routes to avoid it all - North (Caspian Sea) or South (Egypt-Saudi corridor). Egypt and Saudi Arabia have issued routing Notams to handle the traffic flow. In Europe, traffic using Greek and Cypriot airspace (Athens/Nicosia FIR's) is likely to get a slot outbound, as demand is high. Many sectors are at risk of overload, so keep a close eye on TCAS, have onward frequencies ready, and expect GPS interference - even more than usual. And of course, everything can change at any moment. See full briefing in your members dashboard, updated as new information is available.

At approx 00:11z Israel began carrying out major airstrikes on targets in and around Tehran. All Iranian airspace (the OIIX/Tehran FIR) has been closed until at least 10:00z June 13. In expectation of retaliatory attacks, a state of emergency has been declared in Israel. Israeli airspace (the LLLL/Tel Aviv FIR) has also been closed to all traffic apart from north/westbound departures until 07:00z June 14. Previous escalations have shown that in the likely event of a response from Iran, the airspace of Iraq and Jordan may also close at short notice. The situation is still emerging - operators should use a high degree of caution in the region at this time.

The US Government has ordered all non-essential staff to leave its embassies in Iraq, and is also authorizing the departure of non-essential staff and family members from Bahrain and Kuwait. The move follows reports that Israel may be preparing a strike against Iran, raising concerns of regional escalation. Iran has warned it would retaliate against US bases in the region if attacked. Stalled nuclear negotiations between Iran and the US have further heightened tensions. Operators should remain alert to changes — last year’s Iranian missile strikes prompted the sudden closure of several Middle Eastern FIRs.

An airspace incursion by a Russian military aircraft was reported on June 10 over the Gulf of Finland - the second in as many weeks. The aircraft briefly entered the EFIN/Helsinki FIR east of Helsinki itself before returning to Russian airspace. The Finnish Government is taking this seriously and are actively investigating the bust. Take care near the boundary with the ULLL/Sankt-Peterburg FIR - NATO has previously warned that military aircraft may be operating without transponders or reference to ATC.

Drone attacks across Russia are ramping up, with some reaching as far as Siberia, and that’s increasing the risk for any aircraft still using Russian airspace. Hundreds of drones have been shot down recently, including in areas around Moscow. Russian air defense systems are using surface-to-air missiles capable of reaching all altitudes, so the risk applies at every level. While most operators avoid Russian airspace completely, those still flying there for overflights or trips to Russian cities should be prepared for sudden closures or reroutes. Most of this activity happens at night, but daytime disruptions are now common too.

Both Pakistan and India have extended their reciprocal airspace ban on each other’s aircraft. A fragile ceasefire agreement remains in place but we continue to advise caution - especially over the Kashmir region and along the shared border where air defense activity could resume with little warning if hostilities re-start. France has amended its airspace warning for the region - it now recommends operators not to enter a section of cross-border airspace in Northern Pakistan/India below FL260 (LFFF Notam F0779/25 refers).

The mystery of worldwide dual GPS failures appears to have been solved. Over the weekend Boeing, Honeywell, and Collins collaborated to investigate the cause, and the outcome is that the faults were traced to one GPS satellite (PRN 37). A change in the data format being broadcast from it apparently led to the receiver failures. These were limited to Honeywell MMR's, predominantely on B737 and A320 series aircraft. This change has been corrected, and no further issues are expected. There was no connection to an increase in solar activity, or jamming/spoofing. The three OEM's involved consider the case closed. Thank you to all members who responded with reports and information.

This past week, a slew of Dual/Complete GPS Failures began to be reported by airlines and AOs around the world. Typically, the fault is first annunciated as an “ADS-B RPTG” Fault, followed by GPS 1/2 failure. This is unrelated to spoofing or jamming. Many aircraft have been grounded as a result, mostly for short duration pending a reset. An OPSGROUP All-Call is active, requesting further reports and information from members. See link for full Special Briefing on this topic in your members Dashboard.

Panama and Venezuela have agreed to resume commercial flights between the two countries, ending a suspension that lasted nearly a year following a political dispute. This comes shortly after Venezuela announced on May 21 that it is suspending all flights to and from Colombian airports until further notice - although we are still waiting for a Notam to be issued by the SVZM/Maiquetia FIR. The flight suspension appears to be a response to recent political arrests in the region. There is no indication that overflights (that haven’t landed in Colombia) are affected.

Two recent security incidents at the airport to be aware of: On May 17, some protestors entered the airside area and threw paint on an Omni Air International Boeing 767 parked at Stand 42. This caused a full suspension of operations for around 30 mins, placing three inbound flights in a hold. Fire cover was reduced as airport police and fire crews responded. And on May 1, some protestors were arrested after crashing a van through a security fence in a separate breach. While the airport was previously targeted during protests in Nov 2024, these are the first incidents in some time where demonstrators have physically entered the airside area.

Level 1 Level 2 Level 3

Open country information in new window