Emirates, Etihad, flydubai Flights Cancelled Across UAE October 8

Another morning of cancellations across UAE hubs

For UAE travellers, Thursday October 8 opened the way the past several mornings have: with a fresh scatter of delays and cancellations across Dubai International Airport and Abu Dhabi's Zayed International Airport, hitting services operated by Emirates, Etihad, flydubai and Air Arabia as regional security concerns continued to bear down on selected routes12. The pattern has become grimly familiar — UAE airports remain open, the big carriers keep flying most of their networks, but a persistent band of Gulf routes keeps getting scrubbed day after day9.

The concrete damage at Dubai International was concentrated on Saudi and Russian routes. The cancellation list in the latest updates included flydubai's FZ969 to Moscow Vnukovo, FZ815 and FZ811 to Abha, FZ817 to Yanbu, Emirates' EK855 to Kuwait, and Saudia's SV563 to Riyadh, while flynas flight XY202 from Dubai to Riyadh was listed as delayed112. At Sharjah, Air Arabia cancelled its G9068 and G9124 services to Kuwait along with G9107 to Bahrain, saw G9101 to Bahrain arrive late, and pulled its Abu Dhabi–Kuwait flight 3L020 entirely; its Bahrain-bound G9103 and G9105 were still listed as scheduled to operate117.

Abu Dhabi's disruption was milder in degree but similar in character. Etihad's EY653 to Kuwait and its EY575 and EY577 services to Dammam all arrived late, with several other morning flights recording only minor delays1. Etihad's own flight-status page shows the day's problems weren't all geopolitical: EY300 from Abu Dhabi to Islamabad was delayed on October 8 due to a technical issue, pushing the return EY301 late as well18. That distinction matters, and the daily trackers are careful to make it — not every late departure traces back to the conflict; some are crew, technical or weather issues that would have happened anyway1.

The FZ1073 shadow over Dubai–Tel Aviv

The single heaviest structural disruption remains the total shutdown of flydubai's Tel Aviv services following the September 30 cockpit attack on flight FZ1073, and Emirates has suspended its codeshare operations with flydubai to and from Tel Aviv until further notice113. That suspension has no announced end date, and passengers holding Tel Aviv bookings are being told to check their status before travelling1.

The incident itself is now the subject of an official investigation that has taken a darker turn than early reporting suggested. The UAE Attorney-General has said the co-pilot attempted to carry out a terrorist act, attacking Captain Smit Machchhar with the cockpit's emergency crash axe and attempting to take control of the aircraft2823. The Boeing 737 broadcast a general emergency code and then the hijack code 7500 before landing at Tabuk in Saudi Arabia roughly 85 minutes after leaving cruise altitude, with the badly injured captain opening the cockpit door from inside so passengers and two off-duty pilots travelling in the cabin could intervene and restrain the attacker3024. Reporting on the passenger count diverges — some outlets cite 182 people on board, flydubai's chief executive has referred to 172 passengers and crew, and another account puts the figure around 174 — but all agree everyone aboard was eventually flown onward safely292630.

Coverage also diverges on interpretation. One account framed the co-pilot's motive as an open question of possible suicide rather than terrorism, quoting experts sceptical that self-destruction alone explains the attack21. The Guardian's reporting and the Attorney-General's framing both acknowledge the motive remains under investigation, but the official line — an attempted terrorist act involving an axe — is now the version of record, and reporting suggests the suspect told investigators he intended to fly the aircraft normally into Israeli airspace after the attack2328. Israeli Prime Minister Benjamin Netanyahu ordered heightened security on all carriers flying to Israel in response.

A regional system under slow squeeze

Zoom out and the UAE's morning list is one node in a much wider gridlock. Aviation tracking logged on October 8 recorded 1,185 flight delays and 83 cancellations across twelve major Middle Eastern airports, with Riyadh's King Khalid International worst hit at 263 delays and 18 cancellations, Dubai second at 221 delays and 19 cancellations concentrated on Emirates and flydubai, Abu Dhabi logging 139 delays driven almost entirely by Etihad, and Air Arabia accounting for 92 of Sharjah's 98 delays16. A separate tally covering October 5–6 counted 75 cancellations and more than 1,200 delayed flights across Saudi Arabia, the UAE, Bahrain, Kuwait, Egypt, Jordan and Israel15.

Some outlets have pushed far more alarmist framings — one blog-style report claimed the Middle East aviation system was "paralysed" with 600,000-plus passengers stranded on October 5 — but that hyperbole sits uneasily beside the measured airport-by-airport updates showing UAE carriers operating the bulk of their international networks with no nationwide suspension36. The credible reading is attrition, not paralysis: the system is functioning at reduced resilience, with recurring daily cuts to Kuwait, Saudi and Bahrain routes and cascading pressure on connections rather than a single-day collapse.

The Saudi dimension deserves particular attention because several of the UAE's cancelled routes point at it. flydubai's Abha services remain cancelled with disruption at the southern airport described as ongoing, and tracking showed roughly half of daily schedules wiped out at some Saudi domestic outstations, with Najran logging a 50 per cent origin cancellation rate and Yanbu a 50 per cent destination cancellation rate6. Riyadh itself was reported fully operational on October 8, with Emirates, Etihad, flydubai and Air Arabia all flying there, though Saudi-bound passengers were advised to treat journeys as high-risk and consider rerouting via Jeddah615. Philippine Airlines cancelled its October 8 Manila–Riyadh flight PR654 and the October 10 return PR655, citing the evolving security situation19.

Airport security, wait times and what passengers are told

The passenger-facing guidance has hardened into a routine with its own logic. Travellers are told to check their flight immediately before leaving home, to arrive at least three hours before departure — four hours for flydubai customers departing Dubai — to complete online check-in where available, and to pad their journey for road traffic, check-in, security and immigration1. That four-hour flydubai buffer, notably higher than the general three-hour advice, reflects both the airline's thinning schedule resilience and the heavier screening environment that followed the FZ1073 incident1.

For now, the empirical queue data does not show meltdown at the checkpoints. Third-party tracking of Dubai International puts average passport-control waits around seven minutes with a peak around eleven, and security checkpoint waits around twenty-two minutes — uncomfortable, but not crisis-level31. The real advice, echoed across every airline update, is schedule volatility: bookings confirmed the night before can still be cancelled at short notice, so the check-before-you-leave habit has effectively become the region's new boarding procedure1.

A two-tier recovery is taking shape

The most important signal in Thursday's coverage is that the disruption now has a visible end shape, even if the timeline is uneven. On one tier, European carriers are preparing to bring Dubai back: Lufthansa Group expects a gradual resumption of Dubai services from around October 25, and Lufthansa, SWISS, Eurowings and Austrian Airlines are planning restorations or increases to Dubai in late October and into November17. Dubai Airports' chief executive Paul Griffiths has pointed to a concrete commercial reason foreign carriers have been slow to return: they have struggled to secure insurance allowing them to operate back into the region.

On the other tier, the suspensions run long and deep. Air France has held its Dubai and Riyadh flights down through October 24; KLM has suspended Riyadh and Dammam to the same date; Singapore Airlines has extended its Singapore–Dubai cancellations to December 1; British Airways' Heathrow–Dubai flights are paused until November 4; Cathay Pacific's Dubai and Riyadh passenger cancellations stretch to January 31, 2027; and Eurowings' Abu Dhabi services are suspended through October 24 with no resumption date announced1. El Al, Arkia and Israir are expected to resume Dubai flights around November22. Iranian carriers face a separate squeeze, with the UAE suspending all Iranian airline flights to and from the country and Iranian operators confronting sanctions-driven restrictions across Iraq, Oman, Georgia and Azerbaijan13.

Government advisories frame the demand side of this two-tier picture. The UK has dropped its broad warning against all but essential travel to the UAE but still flags possible flight cancellations and airspace disruption; the US keeps the UAE at Level 3, Reconsider Travel, citing terrorism, armed conflict and commercial flight disruption; Australia has eased from Do Not Travel to Reconsider; and Europe's EASA conflict-zone bulletin has been extended to November 16, 2026, covering UAE, Bahrain, Qatar, Oman, Kuwait and Saudi Arabian airspace1.

The bottom line

Reading across the coverage, the honest verdict on October 8 is that UAE aviation is running a managed decline-and-rebuild rather than weathering an emergency. The morning's cancellations — concentrated in Kuwait, Saudi Arabia and Bahrain, anchored by the unresolved FZ1073 investigation and the Tel Aviv suspension — are chronic, not acute. The airlines' advice to build in hours of buffer and re-check every booking reflects a system whose schedules can change faster than its passengers can reach the terminal. Until the GCAA investigation closes, the Gulf route cuts stop repeating daily, and insurers regain confidence in the region, travellers should plan on the assumption that Thursday's list of cancelled flights is not an anomaly but a preview of Friday's.2316