Indian ambassador visits injured flydubai captain in hospital
Ambassador Deepak Mittal says Captain Smit Machchhar is stable and recovering well after meeting him and his family in the UAE.
Updated news: Flydubai flight lands in Tel Aviv after apparent diversion
The original report remains below. New verified developments are added with their own timestamp.
Flydubai flight FZ1073, travelling from Dubai to Tel Aviv on Wednesday, diverted to Tabuk in Saudi Arabia and landed safely. Flight-tracking data records the diversion, and Flydubai confirmed that the aircraft had experienced an in-flight incident. [1] [4]
Israeli officials told local media that the pilots had fought, the BBC reported. AP cited an unnamed regional official who said a fight had broken out in the cockpit and apparently involved the pilots; the official said its cause was unclear. Ynet reported that Flydubai had confirmed a fight between the pilots, although the airline statement it published described an in-flight incident without specifying what happened. [3] [4] [5]
The BBC reported that the aircraft transmitted a general emergency signal, switched minutes later to a code associated with hijacking or unlawful interference, then returned to the general emergency signal. The Israeli prime minister’s office said it did not believe the incident was a hijacking. [2] [3]
Flydubai said all passengers were safe after the landing, in a statement quoted by Ynet. Ynet also reported that the airline planned to send another aircraft to collect them and continue to Israel. [5]
Update
Tabuk airport said the captain and first officer were injured and taken to hospital after flight FZ1073 landed there. The airport did not say how they were hurt. [7] [9] The flight had been travelling from Dubai to Tel Aviv. Flydubai said the aircraft landed safely and all passengers were safe and accounted for. [10]
Tabuk airport also said it was working with flydubai to arrange a replacement aircraft so passengers could continue their journey. [9]
Update
Passengers from a flydubai flight diverted to Tabuk in Saudi Arabia have left on another aircraft bound for Tel Aviv, a passenger told AFP in a report carried by Nieuws.nl. Calcalist also reported, citing ynet, that a replacement flydubai flight had taken off from Tabuk for Israel. [12] [13]
The original flight was travelling from Dubai to Tel Aviv. Flydubai said it had sent two replacement aircraft to Tabuk for passengers and crew. [14]
Calcalist earlier reported that some passengers had refused to board. In a later update citing ynet, it said all Israeli passengers had boarded a flydubai aircraft. It remains unclear whether everyone from the original flight continued the journey. [13] [12]
Update
Israeli Prime Minister Benjamin Netanyahu met passengers from the diverted flydubai flight at Ben Gurion Airport on Wednesday evening, after they returned from Saudi Arabia on a replacement aircraft. He listened to their accounts, ANP reported. [16] [17]
Passenger Yaniv told Netanyahu that he and another man had entered the cockpit and that he had pulled a man away from the controls. Yaniv said the man had been trying to disable the aircraft. Flydubai has said the reasons and motives behind the incident remain unknown pending an investigation. [17] [18]
ANP also reported that soldiers were present in the airport departure hall and that the replacement aircraft arrived with air-force accompaniment. [16]
Update
Yaniv Hayun said he put a man in a chokehold and pulled him from the cockpit during the flydubai flight that diverted to Saudi Arabia on 30 September. Hayun gave his account to Israeli Prime Minister Benjamin Netanyahu after the passengers reached Israel. [22] [23]
Another passenger, Zvika Meness, said he and two others helped overpower the man. Meness told Israeli broadcaster N12 that they used the aircraft’s multimedia headphones to tie him up. BBC News reported that Meness also told broadcaster Kan they used the man’s own zip ties. [24] [22]
Hayun said he returned to the cockpit and pulled on the controls before a pilot who had been travelling in the passenger cabin took over. Flydubai said on-duty crew travelling on the flight secured the aircraft and landed it safely in Tabuk. [22] [25]
The wounded captain, Smit Machchhar, was in a stable condition in hospital, the Indian embassy in Saudi Arabia said, as reported by BBC News. Flydubai said the motive remained unknown and suspended flights to and from Israel while the investigation continues. [22] [25]
Update
Speaking to Sean Hannity on Fox News on 30 September, Israeli Prime Minister Benjamin Netanyahu said it was too early to say whether Iran was involved in the violence aboard a flydubai flight from Dubai to Israel. He said he expected investigators to establish soon whether the attacker had accomplices or Iranian backing. [28] [30]
Netanyahu said Israel would follow the investigation and might take part. In a separate CNN interview that day, he said the UAE president had agreed to Israeli participation in questioning. AP later reported, citing a regional official, that Saudi authorities were working with Israel and other countries to determine a motive. The official did not specify the extent of Israel’s involvement. [30] [31] [32]
Israeli security officials told News 13 on 30 September that they had no clear indication of Iranian direction. Flydubai said the motives behind the cockpit incident remained unknown. [33] [25]
Update
ANP reported on 1 October, citing the UAE state news agency, that the UAE prosecutor-general had ordered an investigation into the incident aboard flydubai flight FZ1073. The inquiry will examine the circumstances and motive, including whether the reported attack on a pilot was planned or linked to terrorist activity. [35]
Flydubai says an altercation occurred in the cockpit of the Dubai-to-Tel Aviv flight on 30 September. Crew travelling aboard secured the aircraft and diverted it to Tabuk in Saudi Arabia, where it landed safely. The airline said all passengers and crew were safe and accounted for. [25] The UAE government says investigators have begun examining the motive and any possible terrorist purpose, the Associated Press reported. [32]
Israel’s defence minister, Israel Katz, has called the incident an attempted jihadist terrorist attack. Flydubai says the motive remains unknown. [37] [25]
Update
A replacement flydubai aircraft flew from Tabuk in Saudi Arabia to Ben Gurion Airport near Tel Aviv on 30 September, bringing passengers from the Dubai–Tel Aviv flight diverted earlier that day. Flight records list the replacement aircraft as having landed, and Associated Press photo captions describe passengers arriving at the airport. [1] [40]
Israel’s Magen David Adom ambulance service said it examined the returning passengers and took a 51-year-old man with upper-body trauma to hospital in good condition. [17]
Flydubai said the original flight diverted after an altercation in the cockpit. It has suspended flights to and from Israel while the incident is investigated. [25]
Update
Flydubai has suspended flights to and from Israel while the investigation into the 30 September incident aboard flight FZ1073 continues. The airline says the suspension was arranged in coordination with relevant authorities and will be reviewed as more information becomes available. [25]
The Dubai–Tel Aviv flight diverted to Tabuk, Saudi Arabia, after what flydubai described as an altercation in the cockpit. On 1 October, flight-status service Aviability listed that day’s FZ1073 service as cancelled. [25] [45]
Emirates has also suspended its flydubai codeshare services to and from Tel Aviv until further notice. Under its travel notice, passengers whose final destination is Tel Aviv will not be accepted for travel at their point of origin; Emirates says it will support those already en route. [42]
Flydubai says it is working to support affected passengers and provide alternative arrangements where possible. It has not announced a date for services to resume. [25]
Update
Indian Prime Minister Narendra Modi called Captain Smit Machchhar a “hero” in a tribute published on 1 October. He praised the pilot’s courage despite his serious injuries and credited him with helping to save hundreds of lives. [48]
Machchhar was captain of a flydubai flight from Dubai to Israel on 30 September. After an altercation in the flight deck, crew diverted the aircraft and landed safely in Tabuk, Saudi Arabia, the airline said. [25]
Modi said India was proud of Machchhar and wished him a speedy recovery. Flydubai said the motive for the altercation remained under investigation. [48] [25]
Update
Saudi Arabia’s Interior Ministry says preliminary investigations, conducted with an Emirati security team, indicate that the co-pilot of flydubai flight FZ1073 assaulted the captain, leaving both men injured. The Dubai-to-Tel Aviv flight diverted to Tabuk on 30 September after an altercation in the cockpit. [51] [25]
The ministry said both pilots left Saudi Arabia for Abu Dhabi on Thursday morning after their health improved and doctors cleared them to travel. They were accompanied by the Emirati security team. Separately, passenger Shota Musayev told the Associated Press that one pilot was stabbing another when passengers intervened. [51] [32]
The UAE attorney-general has appointed specialist prosecutors to investigate the incident. The UAE says the inquiry will examine motives, including any possible terrorist intent and whether there was prior planning or direction. [52]
Update
India’s ambassador to the UAE, Deepak Mittal, has met injured flydubai captain Smit Machchhar and his family. India’s foreign ministry says the ambassador visited the captain in hospital. Mittal told Akashvani News that Machchhar was in a stable condition and recovering well. [54] [55]
Mittal said the captain was speaking openly, smiling and laughing when they met. The Indian embassy described him as being in good health, the Khaleej Times reported. [54] [57]
Machchhar was injured during a cockpit altercation on 30 September aboard a flight from Dubai to Tel Aviv. The aircraft diverted to Tabuk in Saudi Arabia and landed safely, flydubai said. [54] [25]
Mittal said Machchhar was receiving good medical care and that the Indian embassy remained in contact with UAE authorities. [54]
Sources and review for this contribution
The account of a cockpit fight comes from officials cited by BBC News and AP; Flydubai’s statement quoted by Ynet describes an in-flight incident. [3] [4] [5]
Details of the pilots’ hospital treatment come from Tabuk airport’s account as reported by Reuters and Al Roya. [4] [5]
The departure account was carried by AFP via Nieuws.nl; the boarding updates appeared in Calcalist’s ynet reporting.
ANP reported the airport reception; The Times of Israel carried Yaniv’s account of the meeting. [1] [2]
BBC News and Walla report Hayun’s account to Netanyahu; N12 reports Meness’s account of helping restrain the man.
Netanyahu’s Hannity remarks are cited through reports by Nieuws.nl and The Times of Israel; CNN carried his separate interview.
ANP’s account of the UAE state news agency is the source for the prosecutor-general’s order and the inquiry’s stated remit. [1]
AP’s arrival photo captions identify returning passengers but do not give a passenger total. [4]
Flydubai’s incident update covers its suspension [1]; Emirates’ travel notice concerns its flydubai codeshares [2].
Modi’s tribute was published by the Indian prime minister’s office on 1 October 2026. [1]
Saudi Interior Ministry statement carried by SPA via FANA; UAE Foreign Ministry statement and Associated Press passenger account.
Akashvani News reported Mittal’s remarks and India’s foreign ministry account; Khaleej Times reported the embassy’s assessment.
- Flight history for flydubai flight FZ1073 · Flightradar24
Source date as found: Geraadpleegd op 2026-09-30
- Distress and Urgency Procedures · Federal Aviation Administration
Source date as found: Geraadpleegd op 2026-09-30
- Israel-bound flight diverted after fight between pilots · BBC News
Source date as found: 2026-09-30
- A commercial plane traveling from Dubai to Israel is diverted to Saudi Arabia after a distress call · Associated Press
Source date as found: Geraadpleegd op 2026-09-30; publicatietijd niet uitgelezen
- מטוס מדובאי צלל באוויר, דיווח על חשש לחטיפה ונחת בסעודיה - אחרי עימות אלים בין הטייסים · Ynet
Source date as found: Geraadpleegd op 2026-09-30
- Vliegveld Tabuk: twee piloten van flydubai-toestel in ziekenhuis · Nieuws.nl / ANP/RTR/AFP
Source date as found: 2026-09-30; captured at 11:25 UTC
- Israel says pilot tried to hijack flydubai flight to Tel Aviv that diverted, landed in Saudi Arabia · The Jerusalem Post
Source date as found: 2026-09-30; captured at 11:48 UTC
- Israeli officials say diverted flydubai incident may be attempted ‘terror attack’ · Reuters / Internazionale
Source date as found: 2026-09-30; captured at 11:48 UTC
- السعودية تكشف تفاصيل هبوط طائرة فلاي دبي اضطراريا · Al Roya
Source date as found: 2026-09-30; published at 14:48 Muscat time
- Flydubai flight diverts to Saudi Arabia amid reports of pilot fight · AeroTime
Source date as found: 2026-09-30; captured at 11:48 UTC
- Flight history for flydubai flight FZ1081 · Flightradar24
Source date as found: 2026-09-30; captured at 11:48 UTC
- Passagiers uitgeweken flydubai-toestel vertrokken naar Tel Aviv · Nieuws.nl / ANP–AFP
Source date as found: 2026-09-30, 16:10 displayed
- טיסת החילוץ של פליי דובאי המריאה מסעודיה לישראל · Calcalist / ynet
Source date as found: 2026-09-30; relevant updates displayed at 15:43, 17:09 and 17:31
- Flydubai issues update on flight FZ1073 diverted to Tabuk · City 1016 / ARN News Staff
Source date as found: 2026-09-30, 17:36 displayed
- מירי רגב: לבטל את טיסות פליי דובאי עד תום החקירה - להחזיר קווי החברות הישראליות · Walla
Source date as found: 2026-09-30, 14:11 displayed
- Netanyahu ontvangt passagiers flydubai-vlucht op Ben Gurion · Nieuws.nl / ANP
Source date as found: 2026-09-30; displayed time 19:26, time zone unspecified
- Passengers saved from flydubai copilot's alleged attempt to hijack and crash their plane arrive back in Israel · The Times of Israel
Source date as found: 2026-09-30; liveblog captured at 2026-09-30T17:54:06.207Z
- Flydubai issues update on flight FZ1073 diverted to Tabuk · Dubai Eye 103.8 / ARN
Source date as found: 2026-09-30; displayed time 17:36, time zone unspecified
- Flydubai flight incident: All passengers departed Saudi Arabia, airport management says · Khaleej Times
Source date as found: 2026-09-30; published 7:27 PM, updated 9:51 PM, time zone unspecified
- CNN News Central: Flight to Tel Aviv Diverts to Saudi Arabia After Violent Incident · CNN
Source date as found: 2026-09-30; broadcast 08:00–08:30 ET; rush transcript
- بيان من مطار تبوك حول حادثة طائرة فلاي دبي · Al-Sharq
Source date as found: 2026-09-30; displayed time 1:39 PM, time zone unspecified
- Flydubai passenger describes putting attacker in chokehold after cockpit stabbing · BBC News
Source date as found: 2026-10-01T09:23:06.439Z (opgehaald; pagina vermeldt ‘12 hours ago’)
- "ידעתי למשוך את ההגה, ראיתי 'תעופה בחקירה'": הישראלי שהשתלט על המטוס משחזר · Walla
Source date as found: 2026-09-30 19:44 (zoals weergegeven; tijdzone niet vermeld)
- צביקה השתלט על הטייס: "קשרנו אותו עם אוזניות, הבנות שלי צעקו 'אנחנו לא רוצות למות'" · N12 / תוכנית חיסכון
Source date as found: 2026-09-30 12:26 (zoals weergegeven; tijdzone niet vermeld)
- Updates on FZ 1073 DXB-TLV on 30 September 2026 · flydubai
Source date as found: 2026-10-01T09:23:04.492Z (opgehaald; verklaringen betreffen 2026-09-30)
- The Brief with Jim Sciutto · CNN
Source date as found: 2026-09-30 18:00 ET (uitzending; voorlopig transcript)
- Saudi Arabia launches investigation into Flydubai flight’s emergency landing in Tabuk · Anadolu Ajansı
Source date as found: 2026-09-30 (publicatie en update)
- Netanyahu: te vroeg voor conclusies rol Iran bij flydubai-vlucht · Nieuws.nl, ANP/RTR
Source date as found: 1 oktober 2026, 04.32 uur volgens de pagina; opgehaald om 09.41 UTC
- Netanyahu praises passenger, pilot who acted with ‘incredible heroism’ to stop rogue co-pilot · Fox News, Hannity
Source date as found: 30 september 2026 volgens de zichtbare clipdatum; sitemaplink verwijst naar 1 oktober
- Netanyahu: 'Too early to say' if Iran involved in flydubai attack, Israel 'possibly' joining investigation · The Times of Israel
Source date as found: Opgehaald op 1 oktober 2026; publicatietijd van de liveblogbijdrage ontbreekt in de aangeleverde tekst
- The Brief with Jim Sciutto · CNN International
Source date as found: Uitgezonden op 30 september 2026 om 18.00 uur ET
- Attacker’s motive remains unknown after FlyDubai flight to Israel escapes disaster · Associated Press
Source date as found: 1 oktober 2026, bijgewerkt om 05.37 uur EDT
- גורמי ביטחון: אין אינדיקציות להכוונה איראנית, החקירה נמשכת · Nieuws 13, Israël
Source date as found: 30 september, 20.01 uur volgens de pagina; geen tijdzone vermeld; opgehaald op 1 oktober 2026
- Netanyahu: te vroeg voor conclusie dat Iran bij aanval in vliegtuig betrokken was · NOS
Source date as found: 1 oktober 2026, 08.09 uur volgens de paginadatum en ophaalcontext
- Openbaar aanklager VAE opent onderzoek naar flydubai-incident · Nieuws.nl / ANP
Source date as found: 2026-10-01, 10:21 (page display)
- FlyDubai passengers recount terrifying ordeal as pilot allegedly attempted to hijack and crash flight to Israel · CBS News
Source date as found: Coverage concerning 2026-09-30; captured 2026-10-01; publication timestamp not visible
- Katz says flydubai incident was 'jihadist terrorist attack attempt thwarted by brave Israelis' · The Times of Israel
Source date as found: Captured 2026-10-01; publication timestamp not visible
- FlyDubai flight spirals into chaos. What we know and what remains a mystery · Axios
Source date as found: 2026-09-30 (URL date and reporting context); captured 2026-10-01
- Vervangend flydubai-toestel aangekomen in Tel Aviv na incident · Nieuws.nl / ANP
Source date as found: 2026-09-30, 18:18 as displayed; captured 2026-10-01
- Photos of passengers returning to Tel Aviv after attack aboard FlyDubai flight · Associated Press
Source date as found: Photo captions dated 2026-09-30; captured 2026-10-01
- ESCORTED HOME: IDF Fighter Jets Accompany Flydubai Rescue Flight Carrying Israelis To Ben Gurion Airport · The Yeshiva World
Source date as found: 2026-09-30; captured 2026-10-01
- Travel updates — Update on Emirates’ codeshare flights with flydubai to Tel Aviv · Emirates
Source date as found: 2026-09-30 19:19 Dubai (GMT+4); capture: 2026-10-01T10:10:05.363Z
- Flydubai vliegt gedurende onderzoek niet van en naar Israël · Nieuws.nl / ANP/Reuters
Source date as found: 2026-09-30 22:31 as displayed; capture: 2026-10-01T10:10:08.271Z
- Flying from UAE today? Israel flights suspended; check Emirates, Etihad, flydubai, Air Arabia cancellations and delays · Gulf News
Source date as found: Main article: 2026-10-01 09:46; embedded suspension report: 2026-09-30 23:59; timezones not stated; capture: 2026-10-01T10:10:05.688Z
- FZ 1073 flydubai from Dubai to Tel Aviv on 1 October 2026 · Aviability
Source date as found: 2026-10-01 flight status; last updated 05:49 UTC; capture: 2026-10-01T10:10:04.667Z
- Israel suspends Flydubai flights for 6 days after suspected terror attack · Ynet
Source date as found: 2026-09-30 15:47, displayed as Yesterday in the 2026-10-01 capture; timezone not stated
- Regev orders flydubai flights to Israel halted over hijacking pilot's Omani background, sources say · The Jerusalem Post
Source date as found: 2026-09-30 14:32; updated 18:18; timezone not stated; capture: 2026-10-01T10:10:04.297Z
- PM lauds Captain Smit Machchhar for immense courage and valour in saving lives · Kantoor van de premier van India
Source date as found: 1 October 2026
- Modi prijst Indiase piloot na mesaanval in flydubai-toestel · Nieuws.nl / ANP-AFP
Source date as found: 1 October 2026, 08:56 as displayed; timezone not specified on the page
- An Indian airline captain is hailed as a hero after a cockpit attack on a FlyDubai flight · Associated Press
Source date as found: Updated 1 October 2026, 5:57 AM EDT
- عام / بيان توضيحي من مصدر مسؤول بوزارة الداخلية بشأن الهبوط الاضطراري لطائرة شركة (فلاي دبي) في مطار الأمير سلطان بن عبدالعزيز الدولي بمنطقة تبوك · Saudi Press Agency (SPA), republished by FANA
Source date as found: 2026-10-01; dispatch displays 21:03
- UAE Following Incident Involving flydubai Flight to Tel Aviv · UAE Ministry of Foreign Affairs
Source date as found: 2026-10-01
- Eerste onderzoek bevestigt dat piloot flydubai collega aanviel · Nieuws.nl / ANP / AFP
Source date as found: 2026-10-01; page displays 21:11
- Captain Smit Machchhar in UAE; recovering well, says Indian Ambassador in Abu Dhabi · Akashvani News
Source date as found: 2026-10-01
- MEA Closely Monitoring Health Condition of Captain Smit Machchhar · Akashvani News
Source date as found: 2026-10-01
- Indiase piloot uit flydubai-drama in goede gezondheid · Nieuws.nl / ANP / AFP
Source date as found: 2026-10-01
- Flydubai pilot Smit Machchhar recovering in UAE hospital, Indian ambassador confirms · Khaleej Times
Source date as found: 2026-10-01
Flydubai flight FZ1073 from Dubai to Tel Aviv diverted to Tabuk, Saudi Arabia, on 30 September 2026. Flightradar24 records the diversion. Flydubai confirmed an in-flight incident and a safe landing in Tabuk, according to AP.
This source finding must be read within the stated scope and source context. Flight identity, route and diversion 30 September 2026 The flight-history entry establishes the recorded diversion, not its cause. The airline confirmation is available through AP rather than a directly retrieved airline release.
Ynet reported that the aircraft transmitted code 7700 followed by code 7500. The BBC, citing Flightradar24, reported a general emergency signal, a switch minutes later to a hijacking signal, and a subsequent return to the general emergency signal.
This source finding must be read within the stated scope and source context. Reported emergency-code sequence During the flight on 30 September 2026 The retrieved Flightradar24 history table does not display the transmitted codes or their timestamps. The sequence is supported as news reporting attributed to flight-tracking information, not as an independently reconstructed transmission record.
FAA guidance identifies 7700 as an emergency code and 7500 as the code associated with hijacking or unlawful interference. The guidance also provides for controllers to verify a 7500 transmission and for pilots to clarify if no unlawful interference is occurring.
This source finding must be read within the stated scope and source context. Meaning and evidential limits of emergency codes FAA guidance retrieved on 30 September 2026 These are procedural definitions, not findings about FZ1073. A reported code transmission alone does not establish that a hijacking occurred or explain who selected the code.
The BBC attributed the account of a physical fight between the pilots to Israeli officials speaking to local media. AP separately reported that an unnamed regional official briefed on the incident described a fight in the cockpit that apparently involved pilots; that official said the cause of the fight was unclear.
This source finding must be read within the stated scope and source context. Evidence for the alleged cockpit altercation Reporting retrieved on 30 September 2026 These sources establish that officials gave those accounts, not a conclusive reconstruction of the cockpit incident. The officials' information sources are undisclosed, so the reports cannot be treated as demonstrably independent confirmation of the underlying allegation or its causal connection to the diversion.
Ynet reported that Flydubai confirmed a fight between the pilots and opened an investigation. However, the formal airline statement reproduced in that same article describes an in-flight incident without naming its cause. AP likewise reports airline confirmation of an incident and safe landing, rather than confirmation of a fight.
This source finding must be read within the stated scope and source context. Scope of the reported airline confirmation Statements and reporting retrieved on 30 September 2026 The narrower formal statement does not disprove Ynet's report of a separate confirmation. It does distinguish Ynet's attribution from what the reproduced airline statement itself establishes.
AP reported, citing a second unnamed official, that Israel scrambled warplanes because it feared a hijacking involving dozens of Israeli citizens. Ynet reproduced an Israeli military spokesperson's statement that the chief of staff held a situation assessment with the air force commander and other senior officers.
This source finding must be read within the stated scope and source context. Reported Israeli military response 30 September 2026 The military statement quoted by Ynet confirms an assessment, not fighter deployment. No original operational record or separately retrieved military release is available in the supplied material.
According to the BBC, the Israeli prime minister's office did not believe the incident was a hijacking. Ynet quoted the office saying Prime Minister Benjamin Netanyahu had held consultations and followed developments, that the situation was under control, and that efforts were underway to return the Israeli passengers safely to Israel.
This source finding must be read within the stated scope and source context. Prime minister's office assessment and consultations 30 September 2026, following the initial alarm This is the office's reported assessment, not a final investigative determination. It counters an assertion that a hijacking was established but does not rule out an onboard altercation.
The retrieved reports give unreconciled counts with different denominators: the BBC reports approximately 150 people aboard, while Ynet reports 174 passengers, including 27 children.
This source finding must be read within the stated scope and source context. Passenger and occupant totals Reporting retrieved on 30 September 2026 No passenger manifest or airline-confirmed total is supplied. The BBC's approximate occupant count and Ynet's passenger count do not establish a definitive passenger or crew total.
In a spokesperson statement quoted by Ynet, Flydubai said all passengers were safe and being monitored after the landing. Ynet also reported that the airline's chief executive said an aircraft would be sent from Dubai to Saudi Arabia to collect the passengers and continue to Israel.
This source finding must be read within the stated scope and source context. Passenger safety and planned onward transport After the landing on 30 September 2026 The passenger-safety statement is not a comprehensive injury assessment and does not establish the condition of every crew member. The replacement aircraft is an announced arrangement; its departure, arrival and completion of the onward journey are not established.
The reports do not establish a consistent chronology. The BBC places the initial emergency signal two hours into the flight, while Ynet places code 7700 after about 1.5 hours. AP describes an emergency alert shortly after takeoff but later places the incident about 2.5 hours after takeoff.
This source finding must be read within the stated scope and source context. Unresolved elapsed-time chronology During the flight on 30 September 2026 The reports do not always identify the same event when giving elapsed times. The retrieved original flight-history table lacks the detailed signal and incident timestamps needed to reconcile these accounts.
Tabuk airport said both pilots were injured and taken to hospital for medical treatment after the aircraft landed. Al Roya, Reuters and The Jerusalem Post report this airport account. It supports an accurately attributed hospitalisation update, without establishing how either pilot was injured.
This source finding must be read within the stated scope and source context. Hospital treatment following the diversion of FZ1073 30 September 2026, after landing in Tabuk The original airport release is not supplied. These reports share the airport as their source and do not constitute separate clinical confirmations. Diagnoses, duration of treatment and subsequent condition are not established.
Nieuws.nl places the possible-hijacking signal after the emergency landing. This conflicts with Reuters' account and the Flightradar24 timeline embedded in AeroTime. That timeline lists code 7700 at 05:31 UTC, code 7500 at 05:38 UTC, and receipt of code 7700 by satellite at 06:28 UTC. Reuters explicitly places the renewed general-emergency signal before landing. Code 7500 indicates unlawful interference; its transmission does not by itself establish that a hijacking occurred.
This source finding must be read within the stated scope and source context. Emergency-code sequence and the contrary chronology in Nieuws.nl 30 September 2026; code times in UTC, before landing The original X post and raw transponder log are not supplied. AeroTime reproduces the relevant code entries, but its embedded post is truncated after the 06:58 last-signal entry. It does not establish an exact touchdown time or identify who selected the codes.
Al Roya, citing Saudi media reporting the airport's account, says Tabuk air traffic control received a distress call requesting permission for an emergency landing at 08:44 local time. The airport reportedly gave 09:45 local time as the safe landing time. The request to air traffic control is a distinct event from the transponder-code changes.
This source finding must be read within the stated scope and source context. Airport-reported distress call and landing times 30 September 2026; local time in Tabuk These are reported airport times, not independently checked radio or touchdown-log entries. The original airport publication is absent. No UTC conversion or exact comparison with the code-change times is retained.
The Jerusalem Post reports an unnamed passenger's allegation that one pilot stabbed another and tried to force him out of the cockpit. Reuters attributes to two Israeli officials the belief that the co-pilot stabbed the captain. These are attributable allegations, not established investigative findings. The airport's reported statement gives no cause for the pilots' wounds, and an official quoted by The Jerusalem Post said the alleged hijacker's precise objective remained unclear.
This source finding must be read within the stated scope and source context. Evidence for the alleged stabbing and limits on responsibility and intent Accounts published on 30 September 2026 The passenger is unnamed and Reuters' officials spoke anonymously. No public investigative findings or medical account supplied here establish responsibility for either injury or a specific motive. The injuries alone do not resolve those allegations.
Nieuws.nl reports, citing Flightradar24, that a second Dubai–Tel Aviv flydubai aircraft returned to Dubai, without identifying the flight or explaining the return. The supplied FZ1081 record instead lists the 30 September Dubai–Tel Aviv service as 'Landed 2:36 PM', not the estimated-arrival status described in the research. This record does not confirm the reported return. Because Nieuws.nl does not identify the second flight as FZ1081, it also does not disprove a return by another flight. No connection to FZ1073 is established.
This source finding must be read within the stated scope and source context. Reported return of an unidentified second flight 30 September 2026; tracking snapshot captured at 11:48 UTC The FZ1081 status is limited to the captured record. Its landing time is retained as displayed, without a timezone conversion. The identity and flight record of the aircraft meant by Nieuws.nl remain unresolved.
According to Al Roya, Tabuk airport announced coordination with flydubai to arrange a replacement aircraft so passengers could continue to their destination. This describes an arrangement in progress, not a completed replacement flight.
This source finding must be read within the stated scope and source context. Arrangements for onward passenger transport 30 September 2026, following the diversion The supplied sources do not establish that a replacement aircraft arrived, departed with these passengers or completed their onward journey.
FZ1073 was operating from Dubai to Ben Gurion Airport on 30 September and diverted to Tabuk in Saudi Arabia. Flightradar24's flight-history page records the diversion to TUU. Flydubai confirmed an incident en route and a safe landing; its statement to AeroTime said all passengers were safe and accounted for. That passenger-safety statement does not assert that both pilots were uninjured.
This source finding must be read within the stated scope and source context. Flight identity, diversion and the airline's passenger-safety statement 30 September 2026 The airline did not specify the cause of the incident in the supplied statement. The tracking page supports the diversion, not the cockpit allegations. Whether these facts already appeared in either NMC article cannot be checked from the supplied material.
Reuters reports that two anonymous Israeli officials described Israel's then-current assessment as an attempted terrorist attack rather than a mental-health-related incident. Around the time of landing, however, Doron Spielman, spokesperson for the Israeli prime minister's office, had told Reuters the incident was not believed to be a hijacking. Reuters also recorded conflicting media reports alleging a suicide attempt. These accounts show differing and evolving assessments, not a settled determination of motive.
This source finding must be read within the stated scope and source context. Attribution and evolution of the Israeli terrorism assessment 30 September 2026; the statement around landing and subsequent assessments reported that day The terrorism classification is attributed to anonymous officials, not presented as an investigative conclusion. Their rejection of a mental-health explanation is not clinical evidence. Reuters reported no immediate follow-up response from Spielman, so an explicit withdrawal or correction of his earlier statement is not established. The suicide account is media reporting, not evidence of a formally established investigative hypothesis.
Passengers from the diverted flydubai aircraft departed for Tel Aviv on another aircraft, according to a passenger account conveyed by ANP/AFP and published by Nieuws.nl. Separately, a Calcalist update credited to ynet reporter Iris Lifshitz-Kliger reported that a replacement flydubai flight had taken off from Tabuk for Israel.
This source finding must be read within the stated scope and source context. Onward departure from Saudi Arabia 30 September 2026; Calcalist/ynet departure update timestamped 17:31 The two reporting chains support an attributed departure report. Their underlying sources are not demonstrably independent. The 17:31 timestamp is the publication time of the update, not a recorded takeoff time. The supplied pages contain no replacement-flight number or airline or airport confirmation of its actual departure or arrival.
Calcalist reported at 15:43 that some passengers were refusing to board and wanted to return with an Israeli airline. At 17:09, an update credited to ynet reporter Itamar Eichner said all Israelis had boarded the flydubai aircraft at Tabuk. Nieuws.nl's report left open whether every occupant of the original aircraft had continued the journey.
This source finding must be read within the stated scope and source context. Reported boarding and earlier refusals 30 September 2026; Calcalist updates timestamped 15:43 and 17:09 The later boarding report concerns Israelis and supplies no numerical tally. It does not establish the outcome for any non-Israeli passengers. The earlier refusal report is not evidence that Israeli passengers remained behind after departure; the boarding and departure reports are separate updates within the same Calcalist/ynet reporting chain.
ARN's report on City 1016 identifies the diverted service as FZ1073, travelling from Dubai to Tel Aviv's Ben Gurion Airport. In its account of the airline's statement, flydubai said it had sent two replacement aircraft to Tabuk to relieve passengers and crew.
This source finding must be read within the stated scope and source context. Flight identification and replacement-aircraft deployment 30 September 2026; City 1016 report timestamped 17:36 The statement is available through ARN's reporting, not an airline-owned page in the supplied material. Sending two aircraft does not establish that two passenger flights subsequently departed, or their occupancy.
Israeli Defence Minister Israel Katz described the incident as an attempted jihadist attack in a statement reproduced by Calcalist, saying preliminary information indicated an intention to crash the aircraft with everyone aboard. AP separately attributed to Prime Minister Benjamin Netanyahu the claim that a pilot stabbed another pilot and apparently tried to crash the aircraft.
This source finding must be read within the stated scope and source context. Named Israeli officials' deliberate-crash allegations 30 September 2026; Katz statement in Calcalist's 16:40 update and Netanyahu remarks in AP's updated report These sources establish the officials' stated allegations, not intent or motive. The supplied pages do not provide the underlying investigative evidence or establish which official first originated the deliberate-crash allegation.
Flydubai's account, reported by ARN, acknowledged an altercation on the flight deck and credited on-duty flydubai crew travelling on the flight with securing the aircraft, which then landed safely in Tabuk. The airline said the reasons and motives were unknown and remained subject to a formal investigation.
This source finding must be read within the stated scope and source context. Airline account of the cockpit incident and investigation Airline statement reported on 30 September 2026 This is material uncertainty concerning the deliberate-crash allegation, not a finding that the allegation is false. The airline's account is not an independent investigation and does not rule out assistance by passengers.
Walla cited an unnamed senior military official as tentatively suggesting, on the basis of a preliminary inquiry, that the pilot had attempted suicide by crashing the aircraft. It also cited an unnamed source familiar with the preliminary inquiry as saying the reason for the violence between the two crew members could not be determined with certainty.
This source finding must be read within the stated scope and source context. Alternative preliminary assessment reported by Walla 30 September 2026; Walla report timestamped 14:11 The sources' identities, direct knowledge and underlying evidence are unavailable. Their assessments do not establish a suicide attempt or a psychiatric condition, and do not conclusively disprove a jihadist motive.
Nieuws.nl includes a figure of 180 Israelis aboard the original diverted aircraft in its account of the Israeli allegation. That figure is not a count of passengers on the replacement flight.
This source finding must be read within the stated scope and source context. Passenger-number claim 30 September 2026 The basis of this precise count is not stated. The supplied airline statement provides neither a passenger total nor a nationality breakdown, and the other supplied pages do not corroborate the figure of 180.
AP reported that Netanyahu, citing a passenger he had spoken to, said a passenger and a crew member broke into the cockpit as the aircraft began to dive, after which other crew members took over flying. Calcalist also reported that passenger Tzvika Mans confirmed his involvement in subduing the alleged attacker in an interview with the outlet.
This source finding must be read within the stated scope and source context. Evidence for passenger and crew intervention 30 September 2026; Calcalist interview account in its 12:58 update Netanyahu's account is relayed testimony rather than his own observation. Calcalist supplies a named participant account, but the available interview excerpt does not reconstruct the entire intervention. These accounts support reports of passenger assistance without independently establishing that an intentional crash was prevented.
AP said its review of circulating video showed two men with bloody wounds on the aircraft floor, people apparently providing emergency treatment and others guarding the cockpit. AP also reported that a Tabuk airport statement carried by Saudi state-run Alekhbariya television said the captain and first officer were injured and taken to hospital. Flydubai separately said all passengers and crew were safe and accounted for.
This source finding must be read within the stated scope and source context. Reported injuries and limits of the available visual evidence Reports available on 30 September 2026 The video review is AP's, not a direct review undertaken here. The described footage does not establish the participants' identities, the sequence of cockpit actions or motive. The airline's phrase 'safe and accounted for' does not establish that everyone was uninjured.
Israeli Prime Minister Benjamin Netanyahu met passengers from the diverted flydubai flight at Ben Gurion Airport on Wednesday evening, 30 September 2026, and listened to their accounts. ANP reported the gathering, while The Times of Israel published a meeting report and a photograph caption placing Netanyahu with passenger Yaniv at Ben Gurion on that date.
This source finding must be read within the stated scope and source context. Netanyahu's meeting with returning passengers Evening of 30 September 2026 S2 credits the photograph to Kobi Gideon/GPO and embeds a post from the Prime Minister of Israel account. No precise meeting time is shown. The reception material corroborates the meeting, not the earlier cockpit allegations.
The replacement flydubai flight carrying passengers from Saudi Arabia landed at Ben Gurion on 30 September. The Times of Israel reported the landing using flight-tracking data; AP reported the evening arrival and published captioned arrival photographs credited to Ariel Schalit. Separately, Cluster2 Airports said all passengers had departed Tabuk on a replacement aircraft that took off at 5:40pm, according to its statement reproduced by Khaleej Times.
This source finding must be read within the stated scope and source context. Replacement flight's departure and arrival 30 September 2026; evening arrival, with departure reported as 5:40pm The supplied documents do not establish the exact landing minute. S2's relative publication-time labels are not landing times. S5 does not explicitly identify the departure time zone. The raw tracking record and a separately retrieved Cluster2 release are not included.
In The Times of Israel's 30 September meeting report, an Israeli passenger identified as Yaniv told Netanyahu that he and another man entered the cockpit and that he pulled the suspected assailant away from the controls and outside. Asked what the man had been doing, Yaniv said he was trying to destroy the controls to disable the aircraft.
This source finding must be read within the stated scope and source context. Passenger Yaniv's account during the meeting Meeting at Ben Gurion on 30 September 2026, recounting the earlier flight The supplied report supports the attribution of this eyewitness account. It does not independently establish the suspect's intention or the complete cockpit sequence. Yaniv's characterization of the man's purpose remains part of his testimony.
AP reproduced Netanyahu's statement that one pilot stabbed the other and 'apparently' tried to crash the aircraft with its occupants. In CNN's 30 September News Central broadcast, Jerusalem correspondent Jeremy Diamond said two Israeli officials and another Israeli source told him and colleague Tal Shalev that the incident was being investigated as an attempted terrorist attack at that stage.
This source finding must be read within the stated scope and source context. Named crash-intent allegation and reported terrorism investigation Statements and reporting on 30 September 2026; CNN segment aired 08:00–08:30 ET Netanyahu's wording was tentative about crash intent. CNN's sources were unnamed and described an investigation, not a completed determination. These passages establish the attributed statements, not a final finding of deliberate crash intent or terrorist motivation.
ANP reported that soldiers stood in the airport departure hall and that the replacement aircraft was brought in with air-force accompaniment. AP's separate report that Israel scrambled warplanes concerned the original flight's emergency and concerns about a possible hijacking; it does not corroborate an escort of the later replacement flight.
This source finding must be read within the stated scope and source context. Reported military reception of the replacement flight 30 September 2026; evening reception versus the earlier original-flight emergency The military reception details are supported as ANP reporting. No independent confirmation of the later accompaniment or soldiers' presence appears in the supplied record. The earlier scrambling of warplanes cannot be transferred to the replacement flight.
According to AP, Netanyahu said Saudi Arabia had arrested a pilot. AP added that Saudi Arabia had no immediate comment and that authorities had not immediately shared the pilot's identity.
This source finding must be read within the stated scope and source context. Netanyahu's reported Saudi arrest statement Reported on 30 September 2026 The attribution to Netanyahu is supported. The supplied Saudi airport statements address injuries and investigation, not detention. They neither confirm nor disprove an arrest, and hospitalization does not rule out custody. No passage attributes a questioning claim to Netanyahu.
ANP attributed a jihadist-motive allegation generically to 'Israel' without identifying the speaker and said the allegations were not independently confirmed. Flydubai's spokesperson said the underlying reasons and motives were unknown at that early stage and subject to formal investigation. The Tabuk airport statement reproduced by Al-Sharq said competent authorities were continuing the necessary investigations. The supplied record contains no completed finding establishing a jihadist motive or deliberate plan to crash the aircraft, and no finding excluding those possibilities.
This source finding must be read within the stated scope and source context. Status of jihadist-motive and deliberate-crash allegations Investigative status reported in the captured pages of 30 September 2026 The airline and airport statements are media reproductions rather than separately retrieved official releases. ANP does not identify the source of its specific jihadist characterization. An ongoing investigation and a statement of unknown motive are neither proof nor rebuttal of the allegations.
Flydubai confirmed a flight-deck altercation on Dubai–Ben Gurion flight FZ1073, with on-duty crew securing the aircraft before its safe diversion and landing at Tabuk. The airport reported that both the captain and first officer were injured and transferred to hospital. AP said footage it reviewed showed two bloodied and wounded men on the aircraft floor. Citing Flightradar24, AP reported a descent from 33,000 to 17,000 feet, approximately 10,000 to 5,100 metres, in about one minute.
This source finding must be read within the stated scope and source context. Original-flight emergency, injuries and reported physical evidence Original-flight emergency on the morning of 30 September 2026 and the subsequent landing in Tabuk AP's footage review and tracking analysis were not independently repeated here; the supplied pages do not include the raw tracking dataset, a complete cockpit recording or medical records. These reported observations do not by themselves establish who controlled the aircraft at each moment or whether the descent was intended to cause a crash. A safe landing does not mean nobody was injured.
Passenger Yaniv Hayun told Israeli Prime Minister Benjamin Netanyahu on 30 September that he grabbed the alleged attacker in the cockpit, put him in a chokehold and pulled him outside. BBC and Walla report the same conversation. This establishes a reportable, attributed account of Hayun's actions, not an independently reconstructed struggle.
This source finding must be read within the stated scope and source context. Passenger account of removing the alleged attacker Incident and conversation on 30 September 2026 The original social-media recording is not supplied for direct audio or translation verification. BBC and Walla's accounts of the same conversation are not independent eyewitness corroboration. Novelty relative to the existing article cannot be established.
Hayun described the wounded pilot's position near the cockpit door as an obstacle to opening it. His airport statement reported by AP says the door apparently was not locked and that they managed to open it. Walla presents the injured pilot's opening of the door before collapsing as Hayun's assessment, whereas BBC states it without that qualification. These pages do not settle who unlocked or first opened the door.
This source finding must be read within the stated scope and source context. Cockpit access and uncertainty over who opened the door Accounts concerning the 30 September 2026 incident The airport statement and meeting account come from the same passenger. They do not independently establish the unlocking sequence, and no official cockpit reconstruction is supplied.
Hayun said he returned to the cockpit after the man was restrained and pulled on the controls. BBC reports his account that the aircraft then began to level out and that one of two on-duty pilots previously seated in the passenger cabin told him he was taking control. Flydubai separately credits on-duty crew travelling on the flight with securing, diverting and safely landing the aircraft.
This source finding must be read within the stated scope and source context. Reported control inputs and takeover by travelling crew Flight on 30 September 2026 Hayun's account supports his stated actions and chronology, not proof that his input caused recovery. No recorder or flight-data analysis links individual inputs to particular people. Flydubai does not identify the travelling crew or establish who held control at every stage.
In an interview reported by N12's Savings Programme, passenger Zvika Meness said he and two others helped subdue the pilot and that they tied the copilot using the aircraft's multimedia headphones. BBC additionally reports that Meness told Israeli public broadcaster Kan that the man was tied with his own zip ties as well as multimedia headphones.
This source finding must be read within the stated scope and source context. Meness's account of restraint and the materials used Interview accounts reported on 30 September 2026 N12's written interview report is supplied, but its video has not been directly assessed. The complete Kan recording is absent. The zip-tie statement is supported as BBC's attribution to Meness's Kan interview, not as independently verified ownership or evidence of planning.
On CNN's The Brief with Jim Sciutto on 30 September, Israeli Prime Minister Benjamin Netanyahu said the attacking pilot was being interrogated in Saudi Arabia. AP also attributes a reported arrest there to Netanyahu's CNN interview.
This source finding must be read within the stated scope and source context. Attributed custody information CNN interview on 30 September 2026; reporting retrieved on 1 October 2026 CNN supplies a provisional rush transcript. Its quoted passage records questioning, while the arrest is reported by AP in its account of the interview. Neither is an independent Saudi custody record. No Saudi police or judicial statement confirming charges or procedural status is supplied.
Hayun described the man at the instruments as trying to damage them to disable the aircraft; that is his interpretation of the conduct he reported seeing. BBC attributes the description 'attempted jihadist terror attack' to Israeli Defence Minister Israel Katz. Flydubai stated that the underlying reasons and motives were unknown and subject to formal investigation. Netanyahu told CNN he could not say whether Iran was involved before the interrogation concluded.
This source finding must be read within the stated scope and source context. Interpretations of intent and unresolved motive Statements concerning the 30 September 2026 incident, available in documents retrieved on 1 October 2026 Witness interpretations and political characterisations do not establish a crash plan, terrorist motive or organisational involvement. No completed official finding on those issues is included in the supplied pages.
Flydubai confirmed a flight-deck altercation on flight FZ 1073 from Dubai International to Ben Gurion International on 30 September. It said travelling on-duty crew secured the aircraft and landed safely at Tabuk, with all passengers and crew accounted for. Its Statement 3 announces suspension of flights to and from Israel while the investigation continues.
This source finding must be read within the stated scope and source context. Airline-confirmed flight details and operational response Incident on 30 September 2026; airline statements available on 1 October 2026 These are airline confirmations and announcements, not a detailed reconstruction of the alleged stabbing or control sequence. No suspension end date is stated. The airline's wording that people were safe and accounted for does not establish that nobody was injured.
AP reports that eyewitness Shota Musayev told it one pilot was already stabbing another when passengers intervened. BBC and AP identify the wounded captain as Smit Machchhar, an Indian national, and report that the Indian embassy in Saudi Arabia said he was hospitalised in stable condition. AP also reports that Israeli emergency services treated three passengers with minor injuries.
This source finding must be read within the stated scope and source context. Additional eyewitness reporting and reported injuries Reports concerning the 30 September 2026 incident and passenger return Musayev provides an additional named eyewitness account, not a criminal determination. The original embassy statement and clinical records are absent; BBC and AP's references to the same embassy statement are not independent medical assessments. The reported condition is not a subsequent medical update.
BBC reports a loss of 17,000 ft (5,200 m) in less than two minutes. AP, citing Flightradar24, reports descent from 33,000 to 17,000 ft, approximately 10,000 to 5,100 m, in about one minute. The calculated difference between AP's rounded endpoints is 16,000 ft; that calculation is not a separate measurement. Both accounts describe a steep descent, but they do not supply an identical loss and interval.
This source finding must be read within the stated scope and source context. Differing published measurements of the descent Flight on 30 September 2026; reports retrieved on 1 October 2026 No original flight-track dataset or official flight-data analysis is supplied. The numerical difference cannot be resolved from these pages, which also do not establish what caused the descent or recovery.
Hayun described pulling the man out as taking a matter of seconds. Meness estimated that subduing the pilot took between twenty minutes and half an hour. These may concern different phases: Hayun's quoted wording concerns extraction, while Meness describes subduing the pilot. The statements do not establish matching start and end points or a demonstrated contradiction.
This source finding must be read within the stated scope and source context. Witness estimates of extraction and restraint duration Witness accounts reported on 30 September 2026 Both are usable as attributed witness estimates. Their relationship cannot be resolved from the supplied statements, and neither estimate establishes the duration of the aircraft's descent.
Anadolu's 30 September report attributes the launch of an aviation safety investigation into the emergency landing at Tabuk to Saudi Arabia's National Transport Safety Center. AP reports that the UAE's civil aviation authority said it was investigating a security incident. These are reported investigative announcements, not conclusions about guilt, motive or aviation causation.
This source finding must be read within the stated scope and source context. Reported Saudi and UAE investigations Investigation announcements reported on 30 September 2026 The original NTSC and UAE authority statements are not supplied. S7 has no accompanying source text. The available support is the agencies' reported announcements through Anadolu and AP, not direct review of official findings.
Israeli Prime Minister Benjamin Netanyahu said in his 30 September 2026 interview with Sean Hannity on Fox News that it was too early to say whether Iran was involved in the flydubai incident. Nieuws.nl (ANP/RTR) and The Times of Israel report this answer. He also forecast quick answers about whether the assailant had accomplices or Iran was behind the incident; that was his expectation, not an investigative finding.
This source finding must be read within the stated scope and source context. Netanyahu's assessment of possible Iranian involvement Hannity clip visibly dated 30 September 2026; remarks reported by Nieuws.nl on 1 October. The Fox page contains a player error and no transcript of the answer. The wording is supported by the supplied reports, not direct playback. Reports referring to the same interview corroborate the attributed statement, not an Iranian link. The visible clip date differs from the 1 October date in the sitemap link.
In the Hannity interview, Netanyahu said he thought the suspect would be taken to the UAE and that Israel would follow and possibly participate in the investigation. In CNN International's The Brief with Jim Sciutto, broadcast on 30 September at 18:00 ET, the Israeli prime minister said the suspect was being questioned in Saudi Arabia, assumed a UAE transfer would happen soon, and said UAE President Sheikh Mohamed bin Zayed had agreed Israel would join the interrogation. The reported formulations differ in certainty.
This source finding must be read within the stated scope and source context. Expected transfer and possible Israeli participation CNN broadcast: 30 September 2026, 18:00 ET. Hannity clip: 30 September 2026; no interview time is supplied. Both accounts concern statements by Netanyahu. An asserted agreement, investigative cooperation and actual participation in questioning are distinct. No supplied primary Saudi or UAE statement confirms interrogation access or a completed transfer. CNN labels its text a rush transcript. The wording difference alone does not establish a policy reversal.
AP reported on 1 October that the UAE government said its investigation team had begun work on the motive and whether the incident was linked to a terrorist purpose. This supports an attributed report of a government announcement, rather than direct verification of the missing WAM announcement.
This source finding must be read within the stated scope and source context. Reported start of a UAE investigation AP report updated on 1 October 2026 at 05:37 EDT; the announcement's exact time is not established by the supplied text. No retrieved text for S5 is supplied. The attorney-general's formation order, the claimed 11:17 announcement time, named cooperating agencies and the broader remit concerning prior planning or direction cannot be checked. AP's account does not establish a terrorist motive or confirmed Israeli participation.
According to NOS, Israeli Defense Minister Katz characterized the incident on 30 September as a jihadist terrorist attempt and alleged an intention to crash the aircraft with all passengers aboard, citing preliminary information. The Times of Israel reported that Netanyahu told Hannity he did not know the copilot's exact background but believed he hated Israelis. Flydubai's early statement said the reasons and motives were unknown. An anonymous regional official briefed on the investigation told AP that possibilities ranging from terrorism to mental disorders were being examined and nothing was ruled out.
This source finding must be read within the stated scope and source context. Official allegations about crash intent and motive, alongside open investigative possibilities Israeli assessments reported for 30 September 2026; airline statement retrieved on 1 October; AP report updated on 1 October. The sources support the attributed official assessments and an open investigation, not a completed finding on intent, motive or state responsibility. The airline's caution does not refute intentional crashing. AP's official is anonymous; the possibilities mentioned are investigative lines, not diagnoses or equally established explanations.
A regional official briefed on the investigation told AP that the suspect, described as an Omani citizen, was under arrest and that Saudi authorities were working with Israel, the UAE, the United States and Oman to determine a motive. The official did not describe the extent of Israeli involvement. A second anonymous regional official said Israeli intelligence and security officials were investigating the copilot in Saudi Arabia.
This source finding must be read within the stated scope and source context. AP's reporting on arrest and international investigative cooperation AP report updated on 1 October 2026 at 05:37 EDT. These are accounts from two anonymous officials within one AP report, not two independently retrieved publications or named Saudi confirmations. Their identities and access cannot be checked. Investigative involvement does not necessarily establish attendance at an interrogation, a transfer or formal charges.
News 13 reported that Israeli security officials said on the evening of 30 September they had no clear indications of Iranian direction. The report described a lone assailant trying to crash the aircraft as the leading investigative theory and said Saudi authorities were not sharing many details with Israel. Separately, NOS relayed Kan's reporting, based on security sources, that there were no indications of a state or terrorist organization behind the incident.
This source finding must be read within the stated scope and source context. Time-specific security assessments concerning Iranian direction and accomplices News 13 assessment reported on the evening of 30 September 2026. Kan's assessment appears in the NOS page retrieved on 1 October; its original time is not supplied. The original Kan report is absent, making NOS an intermediary for that account. The identity and independence of the anonymous security sources cannot be established. A leading theory is not a conclusion, and a lack of clear indications at that stage does not exclude later evidence of Iranian involvement or accomplices.
Flydubai's own statements confirm an altercation in the flight deck of FZ 1073 from Dubai to Ben Gurion on 30 September. The airline said its crew secured the aircraft, diverted it and landed safely at Tabuk, with all passengers and crew accounted for. It also announced a suspension of flights to and from Israel while the investigation continued.
This source finding must be read within the stated scope and source context. Airline-confirmed incident and announced operational response Incident on 30 September 2026; statements retrieved on 1 October at 09:23 UTC. The statements are not individually timestamped, and no resumption date is given. 'Safe and accounted for' is not a medical finding or a denial of injuries. The airline statements do not identify the assailant, establish a motive or confirm foreign direction.
AP reported testimony from passenger Shota Musayev that one pilot was already stabbing another when passengers intervened. Its article identifies Musayev as a dentist who treated the captain and describes his video as showing the copilot kneeling with his hands tied behind his back. This provides reporting about observed violence and subsequent restraint beyond Netanyahu's account.
This source finding must be read within the stated scope and source context. AP's original eyewitness reporting about cockpit violence and restraint Incident on 30 September 2026; AP account updated on 1 October. The supplied evidence is AP's testimony and video description, not direct review of the full recording. The account supports attribution of the observed attack and restraint; it does not establish an ultimate crash objective, jihadist motivation, accomplices or Iranian direction.
AP, citing Flightradar24, reported a descent from 33,000 to 17,000 feet—approximately 10,000 to 5,100 metres—in about a minute. NOS described a dive of almost 5,000 metres lasting thirty seconds. Both describe a severe descent, but the supplied reports differ materially on its duration.
This source finding must be read within the stated scope and source context. Reported magnitude and unresolved duration of the aircraft's descent Descent during the 30 September 2026 flight; reports retrieved on 1 October. No original Flightradar24 record or flight-recorder data are included. The supplied sources do not resolve the timing difference or establish whether the durations cover the same portion of the descent. These reported measurements do not alone establish deliberate crash intent.
ANP reported on 1 October 2026 that the UAE Attorney-General had ordered an investigation into the incident on flydubai flight FZ1073 to Tel Aviv, citing the UAE state news agency. AP separately reported that the UAE government said its investigation team had begun work on the motive and possible terrorist purpose.
This source finding must be read within the stated scope and source context. Reported prosecutorial order and investigative stage Order reported on 1 October 2026; flight incident on 30 September 2026 The original prosecution/WAM notice is not supplied. ANP and AP support the attributed announcement and reported investigative stage, not independent observation of the team's work. The order's issue time and the team's formal designation remain unverified.
ANP's account describes an inquiry into the circumstances and motives, including whether the reported pilot attack had been planned and whether it had links to terrorist activities. These are matters to investigate, not reported determinations of premeditation or terrorism.
This source finding must be read within the stated scope and source context. Reported remit of the UAE investigation Investigative remit reported on 1 October 2026 The original notice's wording cannot be checked. The supplied account supports planning and terrorist links as investigative questions, but does not support the additional claim that direction by others was explicitly included.
According to ANP's account of the UAE state-news-agency notice, the authorities claim investigative jurisdiction because the aircraft is registered in the UAE and flies under its flag. The same account says UAE law applies despite the incident occurring outside the country. AP also reports the government's assertion that UAE law applies to crimes committed on board.
This source finding must be read within the stated scope and source context. The UAE's stated jurisdictional justification Legal position reported on 1 October 2026 This establishes the reported UAE position, not an independent legal determination. No statute, court ruling or Saudi acceptance was reviewed, and the material does not establish exclusive jurisdiction or any entitlement to transfer or extradition.
Flydubai's spokesperson statements confirm a cockpit altercation on FZ1073 from Dubai International to Ben Gurion International Airport on 30 September. The airline says on-duty flydubai crew travelling on the flight secured the aircraft, diverted it and landed safely at Tabuk. It says all passengers and crew were safe and accounted for.
This source finding must be read within the stated scope and source context. The airline's account of the flight incident and landing Flight on 30 September 2026; statements retrieved on 1 October 2026 This is the directly involved airline's account. 'Safe and accounted for' does not establish that nobody was injured. The account does not identify an assailant or weapon and does not contradict the reported stabbing.
ANP reports that one pilot attacked the other with a knife. AP reports that named eyewitness Shota Musayev told it a pilot was already stabbing another pilot when passengers intervened. This provides direct witness corroboration for the reported stabbing. CBS interviewee Ron Levi described bloodied people but was not close enough to see the cockpit event. These accounts support in-flight violence, not a conclusion about motive.
This source finding must be read within the stated scope and source context. Corroboration and boundaries of the stabbing allegation Accounts of the 30 September 2026 incident, available on 1 October 2026 The AP evidence is reporter-mediated eyewitness testimony. The knife description is explicit in ANP's account; the quoted AP eyewitness passage does not specify the weapon's identity or provenance. No forensic record is supplied. CBS's Levi account concerns the aftermath rather than direct observation of the attack.
Israel's Defence Minister Israel Katz characterized the incident as an attempted jihadist terrorist attack in a statement quoted by The Times of Israel. He said initial information indicated an intention to crash the aircraft with all its passengers. This is Katz's stated assessment, not a reported result of the UAE investigation.
This source finding must be read within the stated scope and source context. Israel Katz's terrorist characterization Statement concerning the 30 September 2026 incident; page captured on 1 October 2026 The quoted statement substantiates the reported characterization, not the underlying terrorist intent. The initial information is not disclosed in the supplied text, and the liveblog's precise publication timestamp is not visible.
Flydubai says the underlying reasons and motives were unknown at the early stage described in its statement and remained subject to formal investigation. AP quotes an anonymous regional official briefed on the investigation as saying scenarios ranging from terrorism to mental disorders were being examined and nothing was ruled out. Neither account supplies a determination of motive.
This source finding must be read within the stated scope and source context. Unresolved motive and alternative investigative possibilities Airline statements about the 30 September 2026 incident and AP reporting updated on 1 October 2026 Flydubai is an involved source and AP's official is unnamed. The official's description of investigative possibilities is not a medical diagnosis or a proven alternative explanation, and does not conclusively rebut Katz's allegation.
Flydubai announced that its flights to and from Israel would be suspended while the investigation continued. It said it was working to support affected passengers and provide alternative arrangements where possible. Axios reports receiving the airline's suspension statement on Wednesday, 30 September 2026, before ANP's 1 October publication of the prosecutorial-order report.
This source finding must be read within the stated scope and source context. Announced suspension of flights to and from Israel Suspension announcement reported on 30 September 2026; duration unspecified No resumption date or number of affected flights or passengers is supplied. The evidence establishes the sequence of reported announcements, not the precise issue time of the prosecutorial order or a causal relationship between the order and suspension.
Passengers from the flydubai aircraft diverted to Saudi Arabia reached Ben Gurion International Airport near Tel Aviv on a different flydubai aircraft on 30 September 2026. AP's dated captions identify the incoming replacement aircraft and record passengers arriving. The Times of Israel also reports that the replacement flight landed.
This source finding must be read within the stated scope and source context. Replacement-flight arrival 30 September 2026 AP's captions are retrieved reporting; the underlying photographs were not visually examined here. The Times of Israel's landing item relies on flight-tracking data. No manifest establishes that every occupant of the original flight travelled on this one replacement aircraft.
Flightradar24's FZ1073 history lists A6-FKR on a Tabuk (TUU)–Tel Aviv (TLV) flight dated 30 September 2026, with the displayed status 'Landed 6:35 PM'. A separate same-day entry lists A6-FKF on the Dubai (DXB)–Tel Aviv route, diverted to TUU. Both records appear under FZ1073; the aircraft registrations distinguish them.
This source finding must be read within the stated scope and source context. Flight number, aircraft registrations and displayed arrival time Flight records for 30 September 2026, captured on 1 October 2026 The captured interface contains 'TIMEUTC' and an option to display local airport time, but does not reliably establish the active setting. It supports the displayed 6:35 PM, not the research's purported 'Landed 15:35' quotation or an unqualified conversion to 15:35 UTC or 18:35 Israel time.
Magen David Adom, as reported by The Times of Israel, said its teams were on standby at Ben Gurion for arriving passengers. The service subsequently said it had examined all the returning passengers and was taking one 51-year-old man to hospital in good condition with upper-body trauma.
This source finding must be read within the stated scope and source context. Medical reception and reported hospital transfer 30 September 2026, at and after the replacement flight's arrival This is an attributed ambulance-service assessment, not a reviewed medical record or a total injury count for all original passengers and crew. Standby arrangements alone do not establish injury.
ANP tentatively reports an Israeli fighter escort for the replacement flight. The Yeshiva World asserts that IDF fighters are seen escorting it. The Times of Israel's report that fighters were scrambled concerns the original emergency flight and does not corroborate an escort of the replacement aircraft.
This source finding must be read within the stated scope and source context. Reported fighter escort 30 September 2026 No directly retrieved air-force statement or assessed, authenticated escort imagery is supplied. S7 contains an image link, but its image and provenance were not assessed here. The escort reports are neither established as independent nor disproved.
ANP says BBC images showed Israeli soldiers waiting to receive passengers in a reception hall, with ambulances outside the airport. Its wording is 'ontvangsthal', not a departure hall. AP's dated captions separately place returning passengers at the arrivals gate.
This source finding must be read within the stated scope and source context. ANP's description of BBC footage and the reception location ANP arrival report and AP captions concerning 30 September 2026 The original BBC page or footage is not supplied. AP's captions locate the passengers in its own reporting; they do not establish the contents, date or provenance of the BBC footage or independently confirm soldiers waiting there.
In Statement 2, a flydubai spokesperson describes an altercation in the flight deck of FZ1073 from Dubai to Ben Gurion on 30 September. The airline says on-duty flydubai crew travelling aboard secured the aircraft and landed safely at Tabuk, that passengers and crew were safe and accounted for, and that two replacement aircraft had been deployed. It says the underlying reasons and motives were unknown and under formal investigation.
This source finding must be read within the stated scope and source context. Flydubai's account of the original incident and replacement arrangements Statement concerning the 30 September 2026 incident, available in the 1 October capture This establishes the airline's published account, not a completed investigation. 'Safe and accounted for' does not establish absence of injury. The limited statement neither confirms deliberate-crash intent nor rules it out.
In a video statement reported by The Times of Israel on 30 September, Prime Minister Benjamin Netanyahu alleged that one pilot stabbed the other and that 'all indications' showed an attempt to crash the aircraft with its passengers. He referred to a passenger account of a dive and attempts to damage aircraft systems, and said Saudi authorities were questioning the suspect. ANP's account additionally attributes an arrest to Netanyahu.
This source finding must be read within the stated scope and source context. Netanyahu's deliberate-crash allegation and reported Saudi questioning 30 September 2026, Netanyahu's public response to the original incident The arrest wording comes from ANP. The retrieved account of Netanyahu's video explicitly mentions questioning but not arrest. No Saudi custody or investigator record is supplied. Netanyahu's assessment remains an attributed allegation, not proof of intent or criminal guilt.
The retrieved reporting contains evidence of injury and alleged stabbing beyond government statements. Passenger and dentist Dr. Shota Musayev told The Times of Israel at Ben Gurion that he saw the pilot bleeding heavily in the cockpit and treated him. In a Channel 12 interview reproduced by The Times of Israel, passenger Tzvika Manes said the copilot was stabbing the pilot as the pilot fell out of the cockpit. The liveblog also attributes injuries and hospitalization of both captain and first officer to Tabuk's airport.
This source finding must be read within the stated scope and source context. Witness accounts of injury and alleged stabbing; reported airport statement Accounts concerning the original incident on 30 September 2026, including interviews after arrival Musayev's arrival interview is original reporting. Manes's Channel 12 account and the airport statement are available here through the liveblog; the underlying recording and original airport release were not retrieved. Injury evidence does not by itself establish an assailant's purpose.
The passenger accounts are consistent with serious interference with flight control, providing support for the deliberate-crash allegation without conclusively establishing intent. Yaniv Hayun told Netanyahu that the alleged attacker was trying to destroy the controls to disable the aircraft. Assaf Rajuan told Channel 12 that passengers and crew overcame the copilot and two off-duty pilots stabilized the plane. Flydubai's different description of on-duty crew travelling aboard leaves their precise assignments unresolved; its statement that motives were unknown is not a denial of the allegation.
This source finding must be read within the stated scope and source context. Bounded assessment of control interference, crew takeover and intent Original flight and subsequent passenger accounts on 30 September 2026 The inference is limited to the reported accounts of interference and recovery. A witness's interpretation of another person's intention is not a completed investigative finding. No directly reviewed technical investigation or Saudi investigator conclusion resolves intent or motive. The crew-duty descriptions may concern different assignments and are not necessarily contradictory.
Statement 3 on the captured flydubai page announces a temporary suspension of flights to and from Israel while the investigation continues. This changes the earlier operational assurance in Statement 2 that the incident had no impact on other scheduled operations, at least for Israel services.
This source finding must be read within the stated scope and source context. Later operational update versus the earlier no-impact assurance Subsequent statements about the 30 September incident, as captured on 1 October 2026 The airline page does not supply exact publication times for individual statements. The suspension cannot therefore be backdated to the original arrival report's publication time. No suspension end date or resumption confirmation is supplied.
Flydubai announced that flights both to and from Israel would be suspended while the investigation into the 30 September FZ1073 incident continued. Its spokesperson said the measure was taken in coordination with relevant authorities and would be reviewed as more information became available. This establishes an airline announcement, rather than merely an Israeli request to stop flights.
This source finding must be read within the stated scope and source context. Flydubai’s own suspension announcement and stated duration Following the 30 September 2026 incident; Statement 3 was available in the supplied 1 October 2026, 10:03 UTC capture. The statement does not identify an exact effective time, a fixed restart date or a regulator’s separate legal decision. The page retains Statement 2’s earlier assurance about other scheduled operations; that assurance does not establish continued Israel service after Statement 3.
Aviability listed FZ1073 from Dubai to Tel Aviv on 1 October as cancelled, with a status update at 05:49 UTC. Gulf News reported seven listed flydubai Tel Aviv-service cancellations in Dubai International Airport information for that Thursday. Each listed service pairs a flydubai operating number with an Emirates codeshare number; these are seven entries, not fourteen separate flights.
This source finding must be read within the stated scope and source context. Recorded practical effects on 1 October 1 October 2026; Aviability updated at 05:49 UTC; Gulf News displayed an update time of 09:46, without an explicit timezone. These are status snapshots and attributed airport information, not a complete count of affected operations or passengers. The underlying DXB feed was not directly retrieved, and the two services’ data provenance does not establish independent operational corroboration. GULF1 is assessed only from its supplied passages.
Emirates’ own travel notice states that its flydubai codeshare operations to and from Tel Aviv are suspended with immediate effect until further notice. It says passengers whose final destination is Tel Aviv will not be accepted for travel at their point of origin, while customers already en route will be accommodated and supported in completing their journeys.
This source finding must be read within the stated scope and source context. Emirates codeshare operations and passenger acceptance Emirates notice last updated on 30 September 2026 at 19:19 Dubai time, GMT+4; captured on 1 October. The notice concerns Emirates’ codeshares with flydubai, not a verified suspension of every Emirates-operated service or every airline’s Israel flights. Support for customers already travelling is a stated commitment, not evidence of how many journeys have been completed.
Flydubai apologised to affected passengers and said it was working to provide support and alternative arrangements where possible.
This source finding must be read within the stated scope and source context. Flydubai’s arrangements for affected passengers Statement 3 following the 30 September 2026 incident; captured on 1 October. The statement does not quantify completed arrangements or promise a specific replacement flight, exception to the suspension or guaranteed completion date.
The Jerusalem Post, citing an unnamed Transport Ministry source, reported that Transportation Minister Miri Regev requested that the Shin Bet halt flydubai flights entering and exiting Israel. Ynet reported an Israeli six-day suspension of flydubai flights to Ben Gurion Airport, with a possible extension. That reported government period is distinct from flydubai’s own formulation that its suspension would last while the investigation continued.
This source finding must be read within the stated scope and source context. Reported Israeli restriction and responsibility for the decision Israeli reports dated 30 September 2026, compared with flydubai’s statement available in the 1 October capture. The Post’s body describes a request, despite the stronger wording in its headline. A request does not prove that Shin Bet issued a prohibition. No official decision text establishes the six-day period, its precise start, legal basis or responsibility for individual cancellations. The reported restriction and the airline’s announcement need not conflict.
According to flydubai, an altercation occurred in the cockpit of FZ1073 while it was operating from Dubai International to Ben Gurion on 30 September. The airline said on-duty flydubai crew travelling on the flight secured the aircraft, diverted it and landed safely at Tabuk Airport. It said all passengers and crew were safe and accounted for, and two replacement aircraft had been deployed to Tabuk. In that statement, it described the underlying reasons and motives as unknown and subject to a formal investigation.
This source finding must be read within the stated scope and source context. Flydubai’s account of the incident, diversion and immediate response Incident on 30 September 2026; Statements 1 and 2 retained in the supplied 1 October capture. This is the participating airline’s account, not an independent reconstruction. Its description neither confirms nor expressly denies a knife attack or terrorist intent. The statement that everyone was safe does not establish that nobody was injured.
The ANP/Reuters report published by Nieuws.nl attributes to ‘Israel’ the allegation that a terrorist hijacking was narrowly averted when one pilot attacked his colleague with a knife and was overpowered. It does not name the authority or speaker. Ynet attributes to unnamed Israeli officials a suspicion that an Omani co-pilot attempted a terrorist attack and intended to crash the aircraft; its account says another pilot, assisted by Israeli passengers, thwarted the attempt. These are reported allegations and suspicions, not established investigative findings.
This source finding must be read within the stated scope and source context. Attribution and evidential status of the Israeli allegations Reports published on 30 September 2026; supplied captures dated 1 October. No primary statement, witness record or forensic evidence supporting the knife allegation or terrorist intent is supplied. The minister’s flight-halt request does not identify her as the source of the knife allegation. Flydubai’s crew-security account and Ynet’s passenger-assistance account could coexist; neither is independently reconstructed here.
Gulf News’s embedded suspension report attributes to the UAE General Civil Aviation Authority an account of a security incident brought under control, an emergency landing at Tabuk and injuries to some crew members who were taken to hospital in Saudi Arabia. It also reports that GCAA teams were examining operational and security aspects. This is material counterevidence to an injury-free interpretation of flydubai’s statement that everyone was safe and accounted for.
This source finding must be read within the stated scope and source context. Reported crew injuries and aviation-authority investigation Incident on 30 September 2026; embedded Gulf News suspension report updated that day at 23:59 and captured on 1 October. The GCAA release and hospital records are not directly supplied. No injury count or severity is established. Being safe after the incident can coexist with having sustained injuries, so these statements are not necessarily contradictory.
The secondary accounts disagree on the signal sequence. Ynet says the aircraft transmitted code 7700 and later code 7500. Gulf News, citing Flightradar24 data, says code 7500 preceded a switch to 7700. The supplied evidence does not resolve that chronology.
This source finding must be read within the stated scope and source context. Conflicting secondary accounts of emergency transponder signals Signals reported during the 30 September 2026 incident; secondary reports captured on 1 October. No original tracking data is supplied. A reported unlawful-interference or possible-hijacking signal is not, by itself, evidence identifying an assailant, weapon or terrorist motive.
The Indian prime minister's office published a page dated 1 October 2026 reproducing an X post by Prime Minister Narendra Modi calling Captain Smit Machchhar a hero. Modi praised his courage and determination to protect others despite serious injury, expressed India's pride and prayed for his recovery. The official reproduction uses the surname Machchhar; Nieuws.nl uses Machchar.
This source finding must be read within the stated scope and source context. Documented publication, wording and identification in Modi's tribute 1 October 2026 The official reproduction verifies the tribute's wording and attribution. It supplies a publication date, not the original X-post timestamp. The spelling comparison concerns the two publications.
In the official tribute, Modi credited Machchhar's bravery with helping save hundreds of lives and averting a great tragedy. AP's report updated on 1 October also attributes to the Indian prime minister the stronger comparison that the captain's actions prevented another 9/11-like attack.
This source finding must be read within the stated scope and source context. Modi's assessment of the captain's contribution Statements published or reported on 1 October 2026, concerning the 30 September flight The life-saving estimate is verified as Modi's statement, not as an independently established count. The 9/11 comparison appears in AP1 but not in GOV1's reproduced tribute; its original publication is absent. Neither quotation independently establishes terrorist intent.
Flydubai confirmed an altercation in the flight deck of FZ 1073, operating from Dubai International Airport to Ben Gurion International Airport on 30 September 2026. It said on-duty crew travelling on the flight secured the aircraft, diverted it and landed safely at Tabuk Airport in Saudi Arabia. The airline reported that all passengers and crew were safe and accounted for.
This source finding must be read within the stated scope and source context. Airline-confirmed route, confrontation, diversion and landing Flight of 30 September 2026; statements captured on 1 October 2026 The airline statement establishes its account of the operational incident, not the weapon, assailant's intent or complete cockpit sequence. Its phrase 'safe and accounted for' does not establish that nobody was injured. TOI1 describes additional pilots in the cabin as off-duty; the supplied material does not resolve the formal duty terminology.
AP reported that the copilot stabbed the captain and identified Machchhar as the seriously injured captain. Its reporting includes eyewitness Shota Musayev's account of one pilot stabbing another when passengers intervened. AP also reported passenger descriptions of the wounded captain opening the cockpit door before they restrained the attacker during a sharp descent. The Times of Israel separately interviewed Musayev about entering the cockpit and finding the pilot bleeding heavily.
This source finding must be read within the stated scope and source context. Original eyewitness reporting supporting the stabbing allegation and passenger intervention Attack on 30 September 2026; eyewitness reporting on 30 September–1 October 2026 This is independently gathered eyewitness reporting beyond political praise. AP and TOI interviewed the same identified witness, so those interviews are not two independent witnesses. The accounts do not establish motive, every participant's contribution or a completed legal determination.
The Times of Israel relayed the Tabuk airport operator's statement that both the captain and copilot had injuries and were taken to hospital. AP1 reported that the Indian Embassy in Riyadh said late Wednesday that Machchhar was hospitalized and in stable condition. AP2 subsequently described the copilot's condition as unclear.
This source finding must be read within the stated scope and source context. Reported injuries and medical condition of the two operating pilots Medical updates following the 30 September 2026 landing, reported through 1 October 2026 These updates are attributed to the airport operator and Indian embassy through the retrieved reporting, not to supplied hospital records. Reported stability is compatible with serious injury and does not establish recovery. Earlier hospitalization does not resolve the copilot's later condition.
In a statement reported in The Times of Israel's 30 September liveblog, Israeli Defense Minister Israel Katz called the incident a jihadist terrorist attack attempt. He attributed the alleged intention to crash the aircraft to initial information in his possession. AP2 records Israeli Prime Minister Benjamin Netanyahu telling Fox News that it was too early to say, in response to a question about Iranian involvement.
This source finding must be read within the stated scope and source context. Katz's terrorism characterization and Netanyahu's response about Iranian involvement Statements reported on 30 September–1 October 2026; exact Fox News interview time not supplied Katz's characterization and Netanyahu's answer address different questions: the nature of the alleged attack and possible Iranian involvement. They do not establish a direct disagreement about whether the assault occurred. The original Katz statement and Fox interview are not supplied; their wording is verified through TOI1 and AP2.
Flydubai stated that the underlying reasons and motives were unknown and subject to a formal investigation. AP2 quoted an anonymous regional official briefed on the investigation saying scenarios ranging from terrorism to mental disorders were being examined and nothing was ruled out. AP also reported that the UAE government was investigating whether the incident had a terrorist purpose. JP1 reported, through unnamed sources, a preliminary Israeli-agency assessment that the suspect acted alone rather than under orders from Iran or another terrorist group.
This source finding must be read within the stated scope and source context. Reported investigation, unresolved motive and preliminary external-direction assessment Investigation and preliminary assessments reported on 30 September–1 October 2026 The regional official and JP1's sources are unnamed. AP2's account of the UAE inquiry is indirect; the cited WAM/UAE1 text and direct Saudi investigative records are absent. Investigation scenarios are not diagnoses, and the reported lone-actor assessment is not a final finding. These uncertainties do not negate the eyewitness evidence of an assault.
AP1 describes the original flight as carrying 174 people. Nieuws.nl and JP1 describe 174 passengers, with JP1 explicitly attaching that figure to FZ1073. TOI1 reports 174 passengers, including 166 Israelis, specifically on the rescue flight. JP1 attributes the figure of 166 Israelis to Israeli media, while its opening inconsistently describes all 174 returning passengers as Israeli.
This source finding must be read within the stated scope and source context. Reported totals, passenger-versus-occupant denominator and nationality figures Original and replacement flights of 30 September 2026; reporting through 1 October 2026 The figures are verified as reported figures, not rejected merely because a manifest is absent. AP's word 'people' does not explicitly define whether crew are included. The rescue flight and original flight are different populations, and the supplied sourcing does not establish two independent nationality counts. No manifest or nationality list resolves the breakdown. The differing formulations do not themselves prove that Nieuws.nl's passenger total is wrong.
In its third statement, flydubai announced a temporary suspension of flights to and from Israel while the investigation continued. It said the suspension would be reviewed as more information became available. The announcement was also reported in The Times of Israel's liveblog dated 30 September.
This source finding must be read within the stated scope and source context. Separate airline operational response to the incident Announcement reported in the 30 September 2026 liveblog; official page captured on 1 October 2026 The official page does not provide a statement-specific timestamp or suspension end date. This is an airline announcement, not proof of every subsequent cancellation or an outcome of Modi's tribute. Statement 2's earlier assertion of no impact on other scheduled operations precedes the suspension announcement in Statement 3.
An unnamed official source at Saudi Arabia's Interior Ministry said on 1 October 2026 that preliminary investigations by Saudi authorities, with an Emirati security team participating, indicated that the copilot assaulted the captain of flydubai flight FZ1073, resulting in injuries to both pilots.
This source finding must be read within the stated scope and source context. Saudi preliminary assault finding Statement dated 1 October 2026, with displayed dispatch time 21:03; incident on 30 September 2026. The supplied page is a FANA republication credited to SPA, not a retrieved SPA-hosted page. It supports the attributed preliminary finding, not a final investigative or judicial determination. The statement does not disclose the evidence underlying that finding.
AP published an account from passenger Shota Musayev, identified as a doctor and eyewitness, who said one pilot was already stabbing another when passengers intervened. This supplies a witness account separate from the Saudi official statement.
This source finding must be read within the stated scope and source context. Separately obtained eyewitness testimony AP reporting updated on 1 October 2026 about the flight of 30 September 2026. This is testimonial corroboration of an attack, not a forensic reconstruction. The cited witness passage does not itself identify the pilots' command roles, the particular object used or an intention to crash.
The Saudi Interior Ministry source said both pilots left Saudi Arabia for Abu Dhabi on the morning of 1 October, accompanied by the Emirati security team, after their health improved and the medical team allowed them to travel. AP separately reported that the Indian government said Captain Smit Machchhar was recovering in Abu Dhabi. AP also reported that an unnamed regional official briefed on the investigation said the suspect was under arrest, and attributed a handover to the UAE to Saudi Arabia.
This source finding must be read within the stated scope and source context. Departure, medical clearance and reported subsequent status Morning of 1 October 2026 for the reported departure; AP status reporting updated on 1 October 2026. The Saudi statement records departure, not arrival or formal custody arrangements. AP's recovery-location report concerns the captain alone; the underlying Indian government statement is not supplied directly. The arrest account relies on an anonymous official, and the handover account is also Saudi-attributed. Neither specifies the copilot's exact current location, custody conditions or charges.
Nieuws.nl's ANP/AFP report attributes the assertion of an intended crash to Israel. AP reports, citing Flightradar24, a descent from 33,000 to 17,000 feet—approximately 10,000 to 5,100 metres—in about a minute. The UAE Foreign Ministry says its investigation includes examining motives, possible terrorist activity or intent, and prior planning or direction; it announces no conclusion on those questions.
This source finding must be read within the stated scope and source context. Crash-intent assertion and unresolved motive Statements and reporting dated 1 October 2026 concerning the flight of 30 September 2026. The original Israeli statement and original Flightradar24 record are not among the supplied retrieved pages. The supplied Saudi and UAE statements do not establish crash intent or motive. The reported assault and descent provide relevant context but do not, by themselves, prove intention. An unresolved investigation is neither confirmation nor refutation of Israel's assertion.
In its 1 October report, AP said Israeli Prime Minister Benjamin Netanyahu alleged that the attacker had undergone Islamist indoctrination without providing details. The report identifies Fox News channel's “Fox and Friends” as the interview medium and says Netanyahu did not know who had helped radicalize the copilot. His office declined to comment when AP asked how he knew indoctrination had occurred.
This source finding must be read within the stated scope and source context. Attributed indoctrination allegation AP report updated on 1 October 2026; the original interview timestamp is not separately supplied. The verified content is AP's attribution of Netanyahu's allegation and his office's response, not proof of indoctrination. The original Fox interview and supporting material are not supplied directly. Refusal to comment does not disprove the allegation.
The UAE Foreign Ministry said Attorney-General Counsellor Dr. Hamad Al Shamsi had ordered a team of specialised Public Prosecution members to investigate the circumstances and causes of the incident. The ministry asserted that UAE judicial authorities have jurisdiction because the aircraft is registered in the UAE and bears its flag, and that UAE law applies to crimes aboard it even outside UAE territory.
This source finding must be read within the stated scope and source context. UAE investigative action and stated jurisdiction UAE statement dated 1 October 2026. These are an announced investigative action and the ministry's stated legal position. The statement supplies no charging decision, court ruling or detention document.
In Statement 2 on its update page, flydubai described a cockpit altercation on the 30 September flight from Dubai to Ben Gurion Airport. It said on-duty flydubai crew travelling aboard secured the aircraft, diverted it and landed safely at Tabuk. At that early stage, the airline said the reasons and motives were unknown and subject to a formal investigation.
This source finding must be read within the stated scope and source context. Airline account of the cockpit incident and intervention Statement 2 concerns the incident of 30 September 2026; the page was captured on 1 October 2026. Individual statement publication times are not displayed. The supplied airline statements do not contain an investigative determination identifying the assailant. The airline's broader description of an altercation and its early statement of unknown motives do not contradict the Saudi preliminary assault finding.
India's ambassador to the UAE, Deepak Mittal, confirmed to Akashvani News that he had met Captain Smit Machchhar and his family in the UAE. India's Ministry of External Affairs said the ambassador visited the captain in hospital. Khaleej Times reported on 1 October 2026 that the Indian embassy described Machchhar as being in good health and recovering well.
This source finding must be read within the stated scope and source context. Consular visit and the embassy's recovery assessment Reported on 1 October 2026; the precise date and time of the captain's hospital visit are not specified. The original embassy post is not supplied. The retrieved interview report and ministry account support the visit, while the embassy's recovery wording is available through news reporting. These are official assessments, not a treating clinician's findings.
In Akashvani News's account of its own interview, Mittal said Machchhar was in stable condition and recovering well. He described the captain as speaking openly, smiling and laughing, and said he was receiving good medical care.
This source finding must be read within the stated scope and source context. The ambassador's directly reported observations Interview report published on 1 October 2026. These observations and assessments are attributable to Mittal. The report provides no clinical prognosis or finding that Machchhar is fit to resume flying.
According to India's Ministry of External Affairs, as reported by Akashvani News, Machchhar received initial hospital treatment in Tabuk, Saudi Arabia, before being transferred to Abu Dhabi for continued medical attention and recovery.
This source finding must be read within the stated scope and source context. Machchhar's treatment location and transfer Transfer reported as completed in the ministry statement published on 1 October 2026. The ministry statement is reproduced by the broadcaster. It does not name the hospital or describe the treatment. It concerns Machchhar's transfer and does not establish that both pilots were transferred.
The ANP/AFP report says Machchhar was attacked with a knife by his copilot and attributes the allegation of an intended terrorist attack to Israeli authorities. flydubai's Statement 2 described the reasons and motives as unknown and subject to formal investigation. Khaleej Times reported that the UAE attorney-general's investigation would examine possible terrorist activity or purpose and prior planning or direction. Terrorist intent is therefore an attributed allegation and an investigative question in the supplied evidence, not a confirmed finding. The airline and prosecution descriptions do not themselves disprove the allegation.
This source finding must be read within the stated scope and source context. Reported knife attack and unresolved terrorist intent Incident on 30 September 2026; news reporting published and airline statements retrieved on 1 October 2026. The original Israeli allegation and its supporting evidence are not supplied. Neither the Saudi investigative record nor the WAM statement is available here. The prosecutor's wording is supported only through Khaleej Times; the detailed knife-attack account has not been checked against an original investigative record.
flydubai's Statement 2 described an altercation in the flight deck of flight FZ 1073 on 30 September 2026, travelling from Dubai International to Ben Gurion International Airport. It said on-duty flydubai crew travelling on the flight secured the aircraft, diverted it and landed safely at Tabuk Airport.
This source finding must be read within the stated scope and source context. The airline's account of the cockpit incident and landing Incident on 30 September 2026; Statement 2 retrieved on 1 October 2026. This is the airline's account, not a final investigative reconstruction. It does not identify a weapon or assailant. Its statement that passengers and crew were safe and accounted for does not establish that nobody was injured.
Netanyahu says flydubai co-pilot was Omani and radicalised
Netanyahu says the co-pilot who attacked a colleague had undergone Islamist indoctrination. Investigators are still examining the motive.
Israeli Prime Minister Benjamin Netanyahu told Fox & Friends that the flydubai co-pilot who attacked the captain was an Omani national and had undergone Islamist radical indoctrination. He said the assessment of indoctrination appeared to come from information gathered about the co-pilot’s personal history. [2]
An Omani official told CBS News that the co-pilot held Omani citizenship, although Oman has not publicly confirmed it. [6] The attack happened on Wednesday aboard a flight from Dubai to Tel Aviv. Flydubai said crew travelling on the aircraft secured it and landed safely in Saudi Arabia. [4]
Flydubai says the reasons for the attack remain unknown and subject to a formal investigation. UAE authorities are examining whether it had a terrorist purpose. The airline has announced that it will suspend flights to and from Israel while the investigation continues. [4] [5]
Sources and review for this contribution
Source context: Fox News reported Netanyahu’s interview; Flydubai and AP reported on the investigation.
- Benjamin Netanyahu reveals details of foiled flydubai hijacking attempt · Fox News
Source date as found: 1 October 2026
- Pilot on Tel Aviv-bound FlyDubai 'prevented another 9/11,' Netanyahu says | Live Updates · Fox News
Source date as found: 1 October 2026
- Netanyahu: aanvaller flydubai-vlucht is Omaanse islamist · Nieuws.nl / ANP
Source date as found: 1 October 2026
- Updates on FZ 1073 DXB-TLV on 30 September 2026 · Flydubai
Source date as found: Statements about 30 September 2026; copy retrieved on 1 October 2026
- Trump says Iran will be hit ‘very hard’ if it is behind copilot who tried to crash flight to Israel · Associated Press
Source date as found: Updated 1 October 2026, 7:26 PM EDT
- What we're learning about the FlyDubai co-pilot who allegedly stabbed the captain and tried to crash the plane · CBS News
Source date as found: Copy retrieved on 1 October 2026
- Saudi Interior ministry: Flydubai co-pilot assaulted captain; both transferred to Abu Dhabi · Saudi Gazette
Source date as found: 1 October 2026
- Co-piloot was geradicaliseerd, zegt Netanyahu, veel vragen nog open · NOS
Source date as found: Copy retrieved on 1 October 2026; page displays relative publication dates
- Netanyahu: Omani co-pilot went through Islamic radicalization · Axios
Source date as found: 1 October 2026
On 1 October 2026, Israeli Prime Minister Benjamin Netanyahu told Fox & Friends that the co-pilot who attacked the captain was an Omani national and had undergone “Islamist radical indoctrination.” He qualified the latter assessment as appearing to emerge from unspecified personal information. The Nieuws.nl/ANP report also attributes the radicalization assertion to Netanyahu. The retrieved material establishes that he made the statement, not that the asserted radicalization has been proved.
This source finding must be read within the stated scope and source context. Netanyahu's statement about the co-pilot Interview and reporting dated 1 October 2026, concerning the flight incident of 30 September 2026 FOX1 is an interview landing page with a playback connection error and no transcript. The statements were checked against Fox's written coverage in FOX2, not against a watched recording. The supplied pages do not establish when either assertion was first made publicly.
AP reports that Netanyahu's office declined to explain how he knew the co-pilot had undergone indoctrination. Axios quotes an unnamed Israeli intelligence official making a similar radicalization assertion while acknowledging uncertainty about whether the suspect acted alone or was sent by someone. This is additional attributed support from an Israeli official, but the retrieved material does not disclose its evidentiary basis or establish that it is independent of Netanyahu's information.
This source finding must be read within the stated scope and source context. Publicly available basis for the radicalization assertion Reporting available on 1 October 2026 No underlying document, interrogation record or independently inspectable investigative finding supporting radicalization is supplied. That absence does not establish that either official's assertion is false. The origin of Netanyahu's personal information remains unspecified.
AP reports that the UAE government said an investigation team had begun examining the attack and whether it was linked to a terrorist purpose. Flydubai's second statement says the underlying reasons and motives were unknown and subject to a formal investigation. These accounts leave the motive unresolved in the retrieved record; they are a material qualification of an established-motive interpretation, not a rebuttal of Netanyahu's assertion.
This source finding must be read within the stated scope and source context. Investigative status of the motive and possible terrorist purpose Statements available in the copies retrieved on 1 October 2026 about the 30 September incident The listed UAE1/WAM source text is not included in the supplied documents and was not examined. The UAE government's statement is retained only through AP's attributed reporting. Flydubai's page does not provide individual publication timestamps for its sequential statements.
CBS reports that an unnamed Omani official confirmed the co-pilot was born in Oman and currently held Omani citizenship. AP separately attributes Omani citizenship to an unnamed regional official briefed on the investigation. The nationality assertion therefore has attributed support beyond Netanyahu's statement. CBS says the Omani government had not publicly confirmed it, and AP says the co-pilot had not been publicly identified.
This source finding must be read within the stated scope and source context. Additional reporting about Omani nationality Reporting available in the copies retrieved on 1 October 2026 Neither official is named for readers, and no public identity document is supplied. The reports do not establish the independence of the officials' underlying information. Nationality supplies no evidence of an ideological or terrorist motive.
A regional official briefed on the investigation told AP that scenarios ranging from terrorism to mental disorders were being examined and that nothing had been ruled out. NOS also describes unanswered questions about the co-pilot's history. Axios relays an Israeli Channel 16 report that a colleague considered him more religiously observant than most co-workers. That anecdote is distinct from evidence of radical indoctrination or a terrorist purpose.
This source finding must be read within the stated scope and source context. Alternative investigative possibilities and the religious-observance anecdote Reporting about the investigation available on 1 October 2026 The AP official was unnamed and described investigative possibilities, not a diagnosis or established motive. Neither the original Channel 16 report nor an interview with the colleague is supplied. Greater religious observance alone does not establish violent ideology or intent.
Preliminary Saudi findings, reproduced by Saudi Gazette, say the co-pilot assaulted the captain and both were injured. AP reports that eyewitness Shota Musayev said one pilot was stabbing another when passengers intervened. Flydubai confirms that flight FZ1073 was operating from Dubai to Tel Aviv on 30 September and that travelling on-duty crew secured the aircraft and landed it safely in Tabuk. Saudi Gazette's account gives 174 passengers and eight crew members: 182 people in total.
This source finding must be read within the stated scope and source context. The attack, safe landing and number aboard flight FZ1073 Incident on 30 September 2026; preliminary findings reported on 1 October 2026 The Saudi findings were read through Saudi Gazette, not a retrieved ministry or Saudi Press Agency original. They are preliminary findings about an assault, not a final legal determination of terrorism. A safe landing and everyone being accounted for do not mean nobody was injured. No passenger manifest is supplied.
Fox quotes Netanyahu explicitly cautioning that it was too early to say whether the co-pilot had connections with Iran or anyone else. Axios reports that Israeli officials said they had no indications of Iranian involvement but had not ruled it out. Netanyahu's radicalization assertion is therefore not an assertion of established Iranian involvement, and the retrieved material does not establish organized or foreign direction.
This source finding must be read within the stated scope and source context. Unresolved external connections Statements and reporting of 1 October 2026 These cautions are not completed investigative findings and do not exclude involvement by any actor. The retrieved material supplies no independently inspectable evidence proving or disproving external coordination.
In its third statement, Flydubai announced that flights to and from Israel would be suspended while the investigation continued. It stated that the temporary suspension would allow authorities to establish the facts surrounding the incident. This documents an announced operational response, not confirmation of an ideological motive.
This source finding must be read within the stated scope and source context. Operational response announced by Flydubai Statement concerning the 30 September 2026 incident, available in the copy retrieved on 1 October 2026 The statement has no individual timestamp in the retrieved text and specifies neither a resumption date nor the number of affected flights. Actual implementation was not independently checked against flight operations.
Flydubai flight lands in Tel Aviv after apparent diversion
A flydubai flight shown as diverted back to Dubai landed in Tel Aviv. The airline attributed the tracking display to radar disturbances.
Flydubai flight FZ1081 landed in Tel Aviv on Wednesday after appearing on Flightradar24 as diverted back to Dubai. PassportNews reported the earlier display; Flightradar24’s flight history records the aircraft as having landed in Tel Aviv. [1] [2]
Nieuws.nl, carrying an ANP/Reuters report, said a separate flydubai aircraft had turned towards Dubai before heading again for Tel Aviv. It said the reason for the reported turn was unclear. The report did not give a flight number. [3]
PassportNews identified the flight shown as diverted as FZ1081. It reported that flydubai attributed the display to radar disturbances and said the flight would continue to Israel as normal. [2]
Sources and review for this contribution
Flightradar24 records FZ1081’s arrival; PassportNews reports the airline’s explanation for the earlier diversion display. [1] [2]
- Flight history for flydubai flight FZ1081 · Flightradar24
Source date as found: 2026-09-30
- בשל שיבושים: טיסה נוספת מדובאי לתל אביב הוצגה כ"חוזרת לדובאי" - אך תמשיך לישראל · PassportNews
Source date as found: 2026-09-30
- Tweede flydubai-toestel dat omkeerde, nu weer richting Tel Aviv · Nieuws.nl / ANP-RTR
Source date as found: 2026-09-30
Flightradar24's flight history records flydubai flight FZ1081, operated by aircraft A6-FKB, as having landed in Tel Aviv after departing Dubai on 30 September 2026. The listed flight time is three hours.
This source finding must be read within the stated scope and source context. FZ1081 identity and recorded arrival 30 September 2026; flight-history page captured at 12:43 UTC The table records the flight's endpoints and arrival status, not its complete route. Its row displays departure at 12:36 PM and landing at 2:36 PM. The exported page contains both a TIMEUTC label and a local-airport-time setting, without unambiguously exposing the table's active setting; no UTC conversion is retained.
PassportNews identified FZ1081 as the flight shown on Flightradar24 as 'Diverted to DXB'. It reported, following a check with flydubai, that radar disturbances had caused the flight to appear diverted and that it would continue normally to Israel.
This source finding must be read within the stated scope and source context. Reported diversion display and airline explanation 30 September 2026; PassportNews displays publication at 13:14 and an update at 13:24, without an explicit time zone The explanation is attributed to the airline through PassportNews's reporting. It is not a directly published airline statement or an independently established technical diagnosis. The supplied Flightradar24 history does not preserve the earlier diversion display.
Nieuws.nl's ANP/RTR report said a flydubai aircraft had turned back towards Dubai early that afternoon but was again heading towards Tel Aviv, citing Flightradar24. It said the reason for the reported turnback was unclear and distinguished this aircraft from the other flydubai aircraft involved in the reported incident.
This source finding must be read within the stated scope and source context. Nieuws.nl's account of the reported turnback 30 September 2026; Nieuws.nl displays publication at 14:13 Nieuws.nl supplies no flight number or aircraft registration. FZ1081 is identified in PassportNews's account of the apparent Dubai diversion, rather than explicitly in Nieuws.nl. The retrieved flight-history table does not independently establish the physical manoeuvre described by Nieuws.nl.
PassportNews's reported display-error explanation provides an alternative to interpreting the tracking status as an actual turnback. Flightradar24 records Tel Aviv, not Dubai, as FZ1081's final destination for the flight. That arrival record does not, by itself, disprove a brief turn towards Dubai en route.
This source finding must be read within the stated scope and source context. Material counterevidence to treating the diversion display as proof of a physical turnback 30 September 2026; evidence available in the supplied captures The sources support the recorded arrival and an attributed explanation for the display, but do not resolve the aircraft's complete trajectory. The landing record is not evidence that no course reversal occurred.
About this discussion and AI questions
Private test discussion. Comments are readers’ views and are not yet automatically fact-checked. Editing is available for 60 seconds after posting.
Sign in with a confirmed reader account and choose a username to read comments and participate.
Sorting applies to top-level comments; replies remain oldest first. New comments and likes can change the order. Refresh for the current ranking.
Loading comments…