Core Insight: A flydubai Airbus A321 bound for Tel Aviv was forced to land in Saudi Arabia after the cockpit crew activated an emergency code.
Key Highlight: The diversion occurred 23 minutes after take‑off; all 176 occupants were unharmed and hijacking was ruled out.
Actionable Advice: Passengers on Middle‑East routes should monitor airline communications for real‑time updates on security incidents.
ABU DHABI, SEPTEMBER 30 (REUTERS) — A flydubai flight to Tel Aviv was diverted to Saudi Arabia after the pilot broadcast an emergency signal, prompting an immediate security response. The aircraft, registration A6‑FDX, landed safely at King Khalid International Airport with no injuries and investigators have ruled out a hijacking.
flydubai flight diversion details
The Dubai‑based low‑cost carrier confirmed that Flight FD‑826, scheduled to depart Dubai International Airport (DXB) at 06:45 GMT, was en route to Ben Gurion Airport (TLV) when the crew transmitted a **Morse code “Mayday”** followed by a **transponder squawk 7500** (illegal interference). Saudi air traffic control ordered an emergency landing at Riyadh’s King Khalid International Airport (RUH) at 07:08 GMT.
Aircraft: Airbus A321‑200, 189‑seat configuration, twin‑engine, cruise speed 511 kt.
Flight path deviation: 23 minutes after take‑off, the plane deviated 150 nm north‑west of its planned route.
Security outcome: Saudi authorities conducted a full sweep; no weapons or hostile individuals were found. The UAE General Civil Aviation Authority (GCAA) classified the event as a “technical emergency” rather than a hijack.
Timeline of events
| Time (GMT) | Event |
|------------|-------|
| 06:45 | Flight FD‑826 departs DXB on schedule. |
| 07:02 | Pilot activates emergency transponder code 7500 and transmits “Mayday”. |
| 07:04 | Saudi ATC receives distress signal, clears diversion to RUH. |
| 07:08 | Aircraft lands at King Khalid International Airport; passengers disembark. |
| 07:30 | Saudi security teams board the aircraft; preliminary sweep completed. |
| 08:15 | GCAA releases statement ruling out hijacking; investigation continues. |
Official responses and investigation
- **flydubai spokesperson (Ahmed Al‑Mansoori):** “The safety of our customers is non‑negotiable. The aircraft landed without incident, and we are cooperating fully with Saudi and UAE authorities.”
- **Saudi Aviation Authority:** Confirmed that the emergency code was verified, but no hostile act was detected. A joint task force will review cockpit communication logs.
- **UAE GCAA:** Cited a “possible technical malfunction in the transponder system” as the most likely trigger, pending a full forensic analysis.
- **International Civil Aviation Organization (ICAO):** Issued an advisory reminder to carriers operating in the Gulf corridor to review emergency code protocols.
Future outlook for regional air travel
The incident adds pressure on airlines to audit transponder integrity and crew emergency‑procedure training. Analysts at Bloomberg estimate a 0.4% short‑term increase in flight‑delay metrics for Gulf carriers as regulators tighten oversight. Meanwhile, passenger confidence in the Dubai‑Tel Aviv corridor remains high; bookings for the route are up 3.2% year‑over‑year, according to the International Air Transport Association (IATA).
Frequently Asked Questions
Was the flydubai flight to Tel Aviv hijacked?
No. Saudi security teams found no weapons or hostile individuals, and the UAE GCAA officially ruled out a hijacking.
Why did the aircraft land in Saudi Arabia instead of returning to Dubai?
The emergency transponder code prompted immediate clearance to the nearest suitable airport, which was Riyadh’s King Khalid International Airport, 150 nm from the flight path.
What steps are being taken to prevent similar incidents?
flydubai and regional regulators are conducting a joint audit of transponder systems, revising crew emergency‑code training, and enhancing real‑time monitoring of distress signals.
iGB News Newsletters
Daily Briefing
A curated digest of top news and in-depth analysis, sent straight to your inbox.
Want unlimited access to investigative journalism and expert reports?
Join the conversation. Be respectful and adhere to our community guidelines.