News Made Clear · Loading…
The UN chief has expressed concern about the flight incident and condemned acts that endanger passengers or civil aviation.
Updated news: UAE prosecutor says Flydubai co-pilot used axe in cockpit attack
The original report remains below. New verified developments are added with their own timestamp.
A flydubai flight from Dubai to Israel landed in Saudi Arabia after a cockpit fight on Wednesday. An unnamed Israeli official told Haaretz that authorities were treating the incident as terrorism, according to an ANP report published by Nieuws.nl. [1] [2]
Flight FZ1073, bound for Ben Gurion Airport, landed safely in Tabuk. Flydubai said all passengers were safe and accounted for. A regional official told AP that a fight had broken out in the cockpit, apparently involving the pilots, and that crew members had been questioned. [2]
A passenger told The Jerusalem Post that one pilot had stabbed the other. The paper also reported that Tabuk airport said both pilots were wounded and taken to hospital. [4]
Accounts of what prompted the fight differ. Reuters reported that Prime Minister Benjamin Netanyahu’s office said the incident did not appear to have been caused by a hijacking. AP quoted an unnamed Israeli official saying it might have been an attempt to attack Israelis and that the investigation was continuing. [5] [2]
Netanyahu’s office said the situation was under control and Israel was working to bring the passengers home. Flydubai planned to send another aircraft to take them to Tel Aviv. [2] [4]
Israel’s national security minister, Itamar Ben-Gvir, has alleged that a “terrorist” planned to crash the flydubai aircraft diverted to Saudi Arabia and kill the 180 Israelis he said were on board. He made the claim on X but did not explain how he had reached his conclusion about a terrorist motive, Nieuws.nl/ANP reported. [10]
Reuters reported that two Israeli officials described an attempted terrorist attack as Israel’s current assessment. A regional official told the Associated Press that the cause of the fight between the pilots was not immediately clear. [14] [2]
Ben-Gvir’s figure of 180 Israelis on board differs from Israeli media accounts cited by Reuters, which put the number at around 150. Flydubai said all passengers were safe after the aircraft landed at Tabuk. [10] [14] [13]
Israeli Defence Minister Israel Katz said the incident aboard flydubai flight FZ1073, travelling from Dubai to Tel Aviv, was an attempted jihadist attack. The aircraft diverted to Tabuk in Saudi Arabia after an altercation in the cockpit and landed safely. [15] [17]
Katz said preliminary information indicated that the person he called the attacker intended to crash the aircraft with everyone aboard. He credited several Israeli passengers with entering the cockpit, subduing the person and returning control to another team of pilots on board. [16]
Flydubai said on-duty crew travelling on the flight secured the aircraft and that all passengers and crew were safe and accounted for. It said the reasons and motives behind the incident remained unknown and were subject to a formal investigation. [17]
Prime Minister Benjamin Netanyahu’s office said Israel was tightening security for commercial aviation after an incident on a flydubai flight bound for Tel Aviv, ANP/Reuters reported. [20] The airline said an altercation occurred on the flight deck of flight FZ1073 before it diverted to Tabuk, Saudi Arabia, where it landed safely. [22]
In remarks reproduced by Israeli outlet Srugim, Netanyahu said he had instructed the security establishment to prepare for further potential threats. [21] It remains unclear what the aviation measures will involve or when they will take effect.
A passenger from the diverted flydubai flight told Israeli Prime Minister Benjamin Netanyahu at Ben Gurion Airport that he helped pin down an alleged cockpit attacker and pulled the aircraft’s controls backwards as it nosedived, the BBC reports. [25]
Separately, The Times of Israel reported that a passenger it identified as Yaniv told Channel 12 he had realised nobody was at the two cockpit control levers as the plane began to descend. He said watching the television programme Air Disasters had taught him that pulling the levers would make an aircraft climb. [26]
Flydubai said crew travelling on the flight secured the aircraft before it landed safely in Tabuk, Saudi Arabia. The airline said the reasons for the incident and the motive remained under formal investigation. [22]
A BBC News newspaper review, citing Metro, says two off-duty pilots took control of the Israel-bound flydubai aircraft after an altercation in the cockpit and landed it safely. Metro described one of them as British. [31]
The Independent reports that passenger Almog Itali described two relief pilots who were aboard to operate a later flight. He said they stabilised the aircraft and landed it in Saudi Arabia, and described one as British. [34]
Flydubai says crew travelling on flight FZ1073 secured the aircraft, diverted it to Tabuk and landed safely. The airline describes those crew members as on-duty, in contrast to Metro’s account of off-duty pilots. [32]
Flydubai has also announced a temporary suspension of flights to and from Israel while the investigation continues. It says the reasons for the cockpit incident remain unknown. [32]
Passenger Almog Itali compared the sudden descent of flydubai flight FZ1073 to a “rollercoaster”, the BBC reported. Speaking to AFP, he said it felt like severe turbulence, although he believed there was none. He told the Associated Press that the strongest sensations lasted “20 or 30 seconds”. [37] [40] [2]
The BBC puts the altitude loss at 17,000ft (5,200m) in less than two minutes. CNN’s analysis describes a fall of 17,400ft in just over two minutes. Flightradar24 describes a sharp descent interrupted by a climb before a further descent. [37] [41] [38]
Flight FZ1073 was diverted from its Dubai-to-Tel Aviv route and landed safely in Tabuk, Saudi Arabia, on 30 September. Flydubai says the reasons for the flight-deck altercation remain under investigation. [32]
In a statement on 30 September, India’s embassy in Saudi Arabia identified Smit Machchhar as the injured Indian pilot aboard a flydubai flight diverted to Tabuk. BBC News identified him as the aircraft’s captain. [43] [42]
The flight was travelling from Dubai to Tel Aviv when an altercation took place in the cockpit. Flydubai said crew travelling on the aircraft landed it safely at Tabuk airport. [32]
The embassy said Machchhar was receiving medical attention in a Tabuk hospital and was reported to be in a stable condition. It said a full update on his health was still awaited. [43]
India’s embassy in Riyadh said on 30 September that Capt Smit Machchhar was receiving medical attention in a hospital in Tabuk, Saudi Arabia, and had been reported stable. It said a fuller update on his health was awaited. The Times of Israel reported the embassy’s statement. [43]
Machchhar was wounded during an incident aboard flydubai flight FZ1073 from Dubai to Tel Aviv. The airline says an altercation occurred in the cockpit before crew travelling on the aircraft diverted it to Tabuk and landed safely. It says the cause and motive remain under investigation. [32] [46]
The BBC reports that Machchhar grew up in Mumbai, joined the aviation college Mainland Air in New Zealand in 2008, became a SpiceJet pilot in 2011 and joined flydubai in 2022. [46]
Mainland Air chief executive Philip Kean told the BBC that Machchhar had trained for forced landings, though not for an incident of this kind. SpiceJet said he had worked for the airline for more than 10 years. [46] [51]
Flight FZ1073 was travelling from Dubai to Tel Aviv on 30 September when an altercation broke out in the flight deck. Flydubai said crew travelling on the aircraft secured it and landed safely at Tabuk in Saudi Arabia. It said all passengers and crew were safe and accounted for. [32]
Shota Musayev, a passenger described by the Associated Press as a dentist who treated the captain, told the agency that one pilot was stabbing another when passengers intervened. Another passenger told Israeli broadcaster N12 that she heard screams and saw blood when the cockpit was opened; she said passengers understood that a pilot had been stabbed. [56] [53]
The Indian Embassy in Saudi Arabia said Captain Smit Machchhar was in hospital and reportedly stable, according to the Associated Press. UAE authorities have begun investigating the incident, including whether it had a terrorist purpose. Flydubai said the motive remained unknown. [56] [32]
Flydubai says it will review the suspension as more information becomes available. It has not given a date for flights to and from Israel to resume. [32]
Adam Polovincik told BBC Newshour that he hugged his six-year-old son and three-year-old daughter tightly as their flydubai flight descended suddenly on 30 September. He said he tried to keep his face and voice calm for them. [58]
Polovincik recalled that, after about 10 to 15 minutes, a passenger in the cockpit told those on board that the situation was under control and other staff were flying the aircraft. [58]
Flydubai says an altercation occurred in the cockpit of flight FZ1073. The aircraft was diverted from its Dubai–Tel Aviv route and landed safely in Tabuk, Saudi Arabia. [32]
Tickets offered online for two planned El Al flights from Dubai to Israel sold out in about five minutes, Israeli news site Ynet reported. The one-way Lite tickets were priced at $249. The sales come after flydubai suspended flights to and from Israel following Wednesday’s cockpit emergency. [66] [32]
Arkia has also opened sales for flights from Friday 2 October, including Saturday services, with fares starting at $279. Israir is preparing two Friday flights from Dubai to Tel Aviv, with one-way tickets priced at $299. The planned flights require final security approval. [66] [65]
Ynet reported that passengers on the El Al and Arkia flights would be allowed a bag but not a wheeled cabin case, with suitcases sent separately by cargo flight. Israel’s transport ministry has also requested additional Etihad flights from Abu Dhabi to Tel Aviv. [66] [65]
In a statement issued by his spokesperson on 30 September, UN Secretary-General António Guterres expressed deep concern about an incident involving a Tel Aviv-bound FlyDubai flight. He said he was relieved that tragedy had been averted and condemned any act that puts civilian lives or civil aviation safety at risk. [68]
Guterres thanked the authorities involved for keeping passengers safe and conducting an investigation. His spokesperson said the UN would continue to monitor developments. [68]
The terrorism assessment was reported by ANP via Haaretz and attributed to an unnamed Israeli official. [1]
Nieuws.nl/ANP reported Ben-Gvir’s X statement, and ynet reproduced his allegation in Hebrew. [1] [2]
Katz’s remarks were reported by Nieuws.nl/ANP–AFP and Srugim; City 1016 carried flydubai’s statement. [1] [2] [3]
The security announcement was reported by ANP/Reuters via Nieuws.nl; Srugim reproduced Netanyahu’s remarks.
The BBC reports the airport account in its video description; The Times of Israel relays Yaniv’s remarks to Channel 12. [1] [2]
The pilot account was reported by Metro and summarised by BBC News; The Independent separately reported passenger Almog Itali’s account. Flydubai gave its account in a company update.
The BBC, AFP and AP accounts feature the same passenger; published descriptions of the altitude loss use different intervals. [1] [5] [6] [7]
The Times of Israel reproduced the Indian embassy’s 30 September statement about Machchhar’s condition. [3]
The embassy’s health statement is dated 30 September; the career details were reported by the BBC.
Flydubai provided the flight and suspension updates; the passenger accounts were reported by AP and N12.
BBC News published Polovincik’s account of the flight after speaking to him for Newshour. [1]
Ynet reported the ticket sales, fares and baggage arrangements. The planned return flights require final security approval.
Source: a UN spokesperson’s statement published by United Nations Press on 30 September 2026. [1]
Source date as found: 2026-09-30
Source date as found: 2026-09-30
Source date as found: 2026-09-30
Source date as found: 2026-09-30
Source date as found: 2026-09-30
Source date as found: 2026-09-30
Source date as found: 2026-09-30
Source date as found: 2026-09-30 (retrieved)
Source date as found: 2026-09-30 (retrieved; publication date not stated)
Source date as found: 2026-09-30, 14:05 as displayed
Source date as found: 2026-09-30
Source date as found: 2026-09-30, 12:48 as displayed
Source date as found: 2026-09-30; updated 16:27 as displayed
Source date as found: 2026-09-30
Source date as found: 2026-09-30; displayed time 15:58
Source date as found: 2026-09-30 according to supplied publication metadata; displayed time 16:42
Source date as found: 2026-09-30 17:36; timezone not stated on the page
Source date as found: 2026-09-30; updated 10:00 EDT
Source date as found: 2026-09-30 14:11; timezone not stated on the page
Source date as found: 30 September 2026; displayed publication time 17:38
Source date as found: Captured on 30 September 2026; page displays 16:27
Source date as found: 30 September 2026; displayed publication time 17:36
Source date as found: 30 September 2026; displayed publication and update time 02:16 PM
Source date as found: 30 September 2026; displayed publication time 11:31 AM, timezone unspecified
Source date as found: Captured 2026-09-30T18:53:26.443Z; the page displays relative publication times
Source date as found: Liveblog dated 30 September 2026; captured 2026-09-30T19:12:06.052Z
Source date as found: Updated 2:33 PM EDT, September 30, 2026
Source date as found: 30 September 2026, 17:34 as displayed; time zone not stated
Source date as found: 30 September 2026, 18:58 as displayed; time zone not stated
Source date as found: Captured 2026-09-30T19:12:06.926Z
Source date as found: 2026-10-01
Source date as found: Verklaringen over 2026-09-30; opgehaald op 2026-10-01
Source date as found: 2026-09-30
Source date as found: Opgehaald op 2026-10-01; publicatietijd niet zichtbaar in de aangeleverde tekst
Source date as found: 2026-09-30
Source date as found: Opgehaald op 2026-10-01; tekst over het incident van 2026-09-30
Source date as found: Vastgelegd op 1 oktober 2026, 04:43 UTC; de pagina toont een relatieve publicatietijd
Source date as found: Gepubliceerd en bijgewerkt op 30 september 2026; vastgelegd op 1 oktober 2026, 05:07 UTC
Source date as found: 30 september 2026, 18:18 UTC; vastgelegd op 1 oktober 2026, 05:07 UTC
Source date as found: Gepubliceerd op 30 september 2026; bijgewerkt op 1 oktober 2026; vastgelegd om 05:07 UTC
Source date as found: Gepubliceerd op 30 september 2026; vastgelegd op 1 oktober 2026, 05:07 UTC
Source date as found: 2026-09-30; opgehaald op 2026-10-01
Source date as found: 2026-09-30 (ingesloten ambassadepost); opgehaald op 2026-10-01
Source date as found: 2026-09-30
Source date as found: 2026-10-01 (opgehaald; publicatiedatum niet zichtbaar in de aangeleverde tekst)
Source date as found: 2026-10-01 feed date; captured 2026-10-01
Source date as found: 2026-10-01; updated 14:49 IST
Source date as found: Interview after arrival on 2026-09-30; publication time not shown in supplied text
Source date as found: 2026-10-01; updated 05:57 EDT
Source date as found: Updated 2026-10-01 at 06:30 IST
Source date as found: 2026-10-01 reproduced SpiceJet post; captured 2026-10-01
Source date as found: 2026-09-30
Source date as found: 2026-09-30; weergegeven publicatie 03:28, update 09:22; tijdzone niet vermeld
Source date as found: Publicatietijd niet zichtbaar; opgehaald 2026-10-01
Source date as found: 2026-09-30; weergegeven publicatie 16:30, update 17:08; tijdzone niet vermeld
Source date as found: 2026-10-01; bijgewerkt 07:56 EDT
Source date as found: 2026-09-30, 11:06; weergegeven tijd zonder tijdzone
Source date as found: 2026-10-01
Source date as found: 2026-10-01
Source date as found: 2026-10-01
Source date as found: 2026-09-30
Source date as found: Opgehaald 2026-10-01; ingebed Fox-bericht gedateerd 2026-10-01
Source date as found: Captured 2026-10-01T17:07:06.808Z
Source date as found: 2026-10-01; captured 2026-10-01T17:07:09.377Z
Source date as found: Captured 2026-10-01T17:07:06.909Z; publication time not shown in supplied text
Source date as found: Captured 2026-10-01T17:07:07.050Z
Source date as found: 2026-10-01; captured 2026-10-01T17:08:03.392Z
Source date as found: 2026-09-30
This source finding must be read within the stated scope and source context. Flight identification, diversion and safe landing 30 September 2026 The airline statement is reproduced by news outlets rather than supplied as a directly published airline release. The flight-history entry corroborates the diversion, not its cause. The statement about passenger safety does not establish that crew members were uninjured.
This source finding must be read within the stated scope and source context. Reported Israeli terrorism assessment Reporting on 30 September 2026 These sources support the existence of reported assessments, not proof of terrorist intent. The original Haaretz report and a formal classification decision are absent. The officials are unnamed, and separate publications do not establish that their information came from independent underlying sources.
This source finding must be read within the stated scope and source context. Suspected attempted hijacking and unresolved motive Assessments reported on 30 September 2026 The official's assertion is reportable as an attributed allegation, not as an established finding. The supplied record contains no completed investigative report, cockpit recording or testimony from the pilots resolving intent.
This source finding must be read within the stated scope and source context. Reports discounting hijacking 30 September 2026; the Times of Israel entry describes the landing as having occurred moments earlier The supplied Times of Israel body has no publication timestamp. The sources do not establish whether the differing descriptions reflect changing assessments, different meanings of hijacking or different information. Neither the non-hijacking assessment nor the attempted-hijacking allegation conclusively resolves intent.
This source finding must be read within the stated scope and source context. Cockpit confrontation, alleged stabbing and passenger intervention Incident and subsequent interviews on 30 September 2026 The regional official and passenger are unnamed. Their accounts support attributed reporting of a confrontation and alleged stabbing but do not independently reconstruct the sequence, establish responsibility for the descent or determine who inflicted each injury.
This source finding must be read within the stated scope and source context. Reported injuries and descriptions of video 30 September 2026 The airport statement is available only through The Jerusalem Post's account. The supplied material contains a publisher's description of video, not independently authenticated footage or a medical assessment. It does not establish injury severity or the full circumstances in which the injuries occurred.
This source finding must be read within the stated scope and source context. Reported emergency-code sequence and its meaning Flight on 30 September 2026; FAA guidance retrieved that day The supplied flight-history page does not expose the code time series. The sequence remains attributable to the news reporting. The FAA guidance explains the signal; it is not evidence about what happened aboard this aircraft. Transmission of the code alone does not establish a completed hijacking or motive.
This source finding must be read within the stated scope and source context. Reported rapid descent and differing measurements During the flight on 30 September 2026 The retrieved Flightradar24 page contains no altitude time series with which to resolve these differences. The accounts may describe different intervals. None of the measurements establishes intent or identifies who controlled the aircraft during the descent.
This source finding must be read within the stated scope and source context. Israeli operational response and passenger travel arrangements 30 September 2026, during the incident and after landing The warplane deployment is attributed to an anonymous official in AP's report; the quoted military statement confirms an assessment, not that deployment. The passenger arrangements are reported plans, not confirmation of a completed onward journey.
This source finding must be read within the stated scope and source context. Ben-Gvir's statement concerning the flydubai incident Reported on 30 September 2026 The supplied reporting supports the attribution, not proof of the alleged intent, motive or passenger count. The original X post was not supplied. The reproduced quotation does not itself identify the flight number.
This source finding must be read within the stated scope and source context. A named passenger's account of intervention in the cockpit Interview published on 30 September 2026 at 12:48, as displayed by Calcalist This is a named participant's account obtained in a direct interview. It does not establish which parts of the initial attack he personally witnessed or independently establish a terrorist motive. Nationality claims in the quotation are not verified by an authoritative identification.
This source finding must be read within the stated scope and source context. Flight identification, safe landing and reported injuries 30 September 2026, following the landing at Tabuk The institutional statements are available through news reports rather than their original publication channels. The passenger-safety statement does not imply that the crew were uninjured. The airline statement reproduced by Khaleej Times does not establish the nature or motive of the incident.
This source finding must be read within the stated scope and source context. Provisional official assessments of intent and cause Assessments reported on 30 September 2026 The officials were anonymous and the reports provide no underlying investigative records. The regional official's uncertainty is not a finding that terrorism was ruled out; the Israeli officials' assessment does not independently prove terrorism or exclude a medical explanation.
This source finding must be read within the stated scope and source context. Competing reported numbers of Israelis aboard Flight FZ1073 on 30 September 2026 Neither figure is supported here by an official manifest. The discrepancy does not invalidate the accurate attribution of Ben-Gvir's figure, and the Reuters report is not an independently verified passenger count.
This source finding must be read within the stated scope and source context. Earlier characterization by the Israeli prime minister's office Around the landing on 30 September 2026, before the later assessment reported by Reuters This was an earlier assessment, not a final conclusion. Saying the event was not believed to be a hijacking does not exclude deliberate violence or a terrorist motive.
This source finding must be read within the stated scope and source context. Katz's public characterization of the flight incident Reported on 30 September 2026 The attribution is supported across the retrieved reports. They may reproduce the same ministerial statement and do not constitute independent confirmation of jihadist intent. Katz's original official publication is not included.
This source finding must be read within the stated scope and source context. The preliminary information and intervention described by Katz Statement reported on 30 September 2026 These are Katz's assertions, not independently established findings about intent or the sequence of events. The reproduced statement does not identify the underlying information or present evidence establishing a jihadist motive.
This source finding must be read within the stated scope and source context. Flight diversion and the airline's account of the immediate outcome Incident and airline update reported on 30 September 2026; article timestamp 17:36 The airline's statement is reproduced by ARN News Staff on City 1016 rather than retrieved from an airline-owned channel. 'Safe and accounted for' does not establish that nobody was injured. The reference to crew securing the aircraft does not exclude passenger involvement or independently resolve the division of roles.
This source finding must be read within the stated scope and source context. The airline's stated uncertainty about cause and motive Airline statement reported on 30 September 2026 This is material evidence of the airline's stated uncertainty, not proof that Katz's allegation is false. The statement neither establishes an alternative cause nor rules out deliberate or terrorist action.
This source finding must be read within the stated scope and source context. Other preliminary assessments reported by Walla Walla report dated 30 September 2026, with a displayed publication time of 14:11 The assessments rely on anonymous sources, and the underlying inquiry is not supplied. They establish that tentative explanations were being reported, not that suicide, a psychological condition or terrorist intent was proven. A suicidal intention would not by itself exclude an ideological motive.
This source finding must be read within the stated scope and source context. Reported Israeli commercial-aviation security response 30 September 2026; Nieuws.nl displays publication time 17:38. The supplied page supports an accurately attributed announcement. It does not include the original office notice, specify measures or coverage, give an effective date, or independently establish implementation.
This source finding must be read within the stated scope and source context. Netanyahu's reported preparatory instruction Statement reproduced on the Srugim page captured on 30 September 2026; displayed time 16:27. The original video is not supplied. The reproduced statement supports the attribution of a preparatory instruction, but identifies neither a concrete additional threat nor specific new aviation-security controls.
This source finding must be read within the stated scope and source context. Cockpit incident, flight route and safe diversion Flight and reported statements of 30 September 2026. Flydubai's account is reported by Dubai Eye/ARN, and the airport operator's account by Saudi Gazette. These statements do not settle the complete cockpit sequence, every participant's role, or the intent behind the incident.
This source finding must be read within the stated scope and source context. Pilot injuries and investigation status Airport operator's statement reported on 30 September 2026. The supplied report does not specify injury severity or determine criminal responsibility. The original operator statement is not separately included.
This source finding must be read within the stated scope and source context. Attributed arrest and questioning Public account reported on 30 September 2026, as preserved in the supplied version. The page supports attribution of the arrest claim to Netanyahu, not direct Saudi confirmation. Missing public confirmation does not establish that the arrest or questioning did not occur.
This source finding must be read within the stated scope and source context. Evidential status of the deliberate-crash and jihadist-motive claims Statements and early-stage investigation reported on 30 September 2026. No completed investigative finding establishing deliberate crash intent or jihadist motivation is included. Flydubai's stated uncertainty does not rule out deliberate action or terrorism; it prevents treating the official allegations as established investigative conclusions.
This source finding must be read within the stated scope and source context. AP's review of injury footage AP reporting in the supplied version updated on 30 September 2026 at 11:12 AM EDT. The footage itself is not supplied for direct examination. AP's description does not identify the two men in that passage, show the complete confrontation, or establish deliberate crash intent, additional threats or implementation of aviation-security measures.
This source finding must be read within the stated scope and source context. Flydubai's reported operational response Flydubai update reported on 30 September 2026; Dubai Eye displays 17:36. This is the airline's account of its own network at that time, not a finding about every carrier or subsequent disruption. Dispatch of replacement aircraft does not establish completion of passenger repatriation or implementation of Israeli security measures.
This source finding must be read within the stated scope and source context. Airport conversation and reported speaker identification 30 September 2026 The BBC description does not name its speaker; the name and meeting date come from The Times of Israel's caption. No image, full recording or transcript was independently examined. The published caption supports the reported meeting, not the passenger's actions during the flight.
This source finding must be read within the stated scope and source context. The passenger's reported account of the controls and his television reference Statements reported on 30 September 2026 These texts support the reported statements, not an independently measured causal effect. The BBC provides a description rather than a full transcript, and The Times of Israel relays a Channel 12 interview. The supplied Channel 12 summary does not establish the detailed action-and-handover sequence claimed through the unavailable S5 page.
This source finding must be read within the stated scope and source context. Other witness and airline accounts of intervention and recovery Accounts published on 30 September 2026 The retrieved texts describe collective intervention but do not independently identify Yaniv's specific control input or isolate its effect. Dubai Eye relays the airline's statement and Walla relays the Kan 11 interview; the original statement and broadcast were not reviewed. The airline report uses 'on-duty', while Shahar's account uses 'off-duty'; the exact staffing status is not resolved by these pages.
This source finding must be read within the stated scope and source context. Published altitude-loss figures and their verification boundaries Flight FZ1073 on 30 September 2026 These are published descriptions with different stated time windows, potentially covering different intervals rather than contradictory measurements. The AP page does not identify its altitude-data source. Walla's account of Flightradar24's warning is relayed reporting, not a directly retrieved Flightradar24 announcement. No supplied altitude/time series reconciles the figures or connects them to the passenger's action.
This source finding must be read within the stated scope and source context. Reported investigative status and allegations of deliberate intent 30 September 2026; airline statement reported at 17:36 as displayed The airline statement establishes its attributed public position at that time, not the underlying motive. It neither proves nor rules out deliberate intent. No original investigative report or later flydubai revision was supplied.
This source finding must be read within the stated scope and source context. How participants obtained cockpit access Reporting published on 30 September 2026 These are reports of statements by the same political official, not two independent cockpit reconstructions. Their wording may describe compatible parts of the intervention; it does not establish a demonstrated conflict or a forced breach of a locked door.
This source finding must be read within the stated scope and source context. Direct flight-history confirmation of the diversion 30 September 2026 The supplied text contains a flight-history table, not a readable series of time-stamped altitude points. No data export or playback was reviewed. This record does not independently validate the descent figures or the effect of any cockpit control input.
This source finding must be read within the stated scope and source context. Reported recovery and landing by additional pilots 30 September 2026 incident; BBC roundup published 1 October 2026 The supplied evidence is the BBC's summary, not Metro's original report. Metro's sourcing for the number, duty status and nationality is not available for assessment. This accurately supported attribution does not independently establish those underlying details.
This source finding must be read within the stated scope and source context. Passenger testimony about two relief pilots and a British nationality Account of the 30 September 2026 flight; supplied page captured 1 October 2026 The BBC clip itself was not supplied for direct assessment. The Independent's reproduced testimony supports the attributed account; it is not an independently verified crew identification. The primary airline statement does not identify a number or nationality.
This source finding must be read within the stated scope and source context. The airline's operational account and differing duty-status terminology 30 September 2026 flight; airline statements captured 1 October 2026 This is the carrier's direct operational description. Its on-duty wording differs from BBC/Metro's off-duty wording, but the supplied statements do not explain the scope of those labels. The airline account neither confirms the specific two-off-duty-pilots description nor disproves the presence of relief pilots travelling for another flight.
This source finding must be read within the stated scope and source context. Alleged cockpit assault and evidence of injuries Reporting dated 30 September 2026 Reuters' reported verification concerns aftermath footage, not footage of the assault itself. The off-camera identification is distinct from verification of culpability. The original airport statement was not supplied. Flydubai's own statement describes an altercation without identifying an assailant or weapon.
This source finding must be read within the stated scope and source context. Attributed crash-intent assessment and proposed Israeli-city target 30 September 2026 statements and reporting; 1 October 2026 BBC roundup Katz's statement is a supported attribution of a preliminary official assessment, not independent proof of intent or a completed investigative finding. No supplied investigative evidence identifies an Israeli city as the intended target. The original Telegraph report and its anonymous sources were not assessed. Flydubai's stated uncertainty does not itself refute the assessments.
This source finding must be read within the stated scope and source context. Unsettled nationality reports concerning the recovery crew Aviacionline account of the 30 September 2026 incident, captured 1 October 2026 The nationality accounts are derivative reporting. The original Israel Hayom report and the linked BBC material were not supplied. Aviacionline's statement about absent official confirmation is bounded to its own time of writing; the supplied airline statement names no recovery-crew nationalities.
This source finding must be read within the stated scope and source context. Announced temporary suspension of Israel services Post-incident announcement concerning the period after 30 September 2026; captured 1 October 2026 The announcement provides no effective time, fixed end date or cancelled-flight total. It establishes the announced decision, not its complete implementation, the incident's motive or the recovery crew's identities.
This source finding must be read within the stated scope and source context. Relationship between passenger control input and the crew's landing 30 September 2026 accounts The inference establishes compatibility, not a verified cockpit timeline. Hayun's quoted account does not identify him as the person who performed the landing, while flydubai attributes the landing collectively to travelling crew without naming the individual pilot.
This source finding must be read within the stated scope and source context. Flight identification and diversion; background to the passenger account 30 September 2026 These are background facts about the same incident, not evidence of a separate event. A safe landing does not establish that everyone was uninjured or explain what happened in the cockpit.
This source finding must be read within the stated scope and source context. Passenger description of the descent Incident on 30 September 2026; BBC page captured on 1 October 2026 at 04:43 UTC The supplied BBC page contains accompanying text, not a readable full interview transcript. The reports concern the same named passenger, not additional independent eyewitnesses. AFP explicitly identifies a video call from Saudi Arabia; AP does not specify the interview circumstances for its quotation. His 20-or-30-second estimate concerns the sensations he described, not a measured duration of the entire altitude loss.
This source finding must be read within the stated scope and source context. Published flight-tracking account of the altitude changes 30 September 2026; initial altitude disturbance beginning at 05:21 UTC These are the tracking providers' published descriptions of their records. The linked granular CSV and raw flight-log samples were not supplied or recalculated here. AirNav's reported descent rate is not an established average over the entire altitude loss. Flightradar24 describes reversals in altitude, not one continuous descent through the full 05:21–05:33 interval.
This source finding must be read within the stated scope and source context. Differing precise altitude-loss and duration descriptions Descent on 30 September 2026; reporting captured on 1 October 2026 The reports use different altitude endpoints and may describe different portions of the irregular trajectory. Without raw samples and common interval definitions, this is an unresolved measurement discrepancy, not proof that one publisher's calculation is wrong. AFP and AP cite Flightradar24; they are not additional independent aircraft measurements. CNN's calculation is an editorial data analysis, not an investigator's finding.
This source finding must be read within the stated scope and source context. Descriptions of the alleged attacker and victim roles Reporting about the 30 September 2026 incident, captured on 1 October 2026 The published wording differs, including within the AP page. The generic word 'pilot' is not necessarily an explicit reference to the captain, so a definite BBC role reversal is not established. The witness allegations are supported as reported statements; no supplied investigative finding definitively assigns the assault roles or criminal responsibility.
This source finding must be read within the stated scope and source context. Investigation status, sequence and allegations of intent Statements and reporting about 30 September 2026, available in the 1 October 2026 captures Netanyahu's and Katz's characterizations remain attributed claims, not established investigator findings. AP's account of the GCAA is indirect because the listed direct statement S5 is absent. This review verifies AP's description of its footage review, not the original footage itself. No cockpit-recorder analysis, evidentiary police report or completed investigation was supplied. Those absences do not disprove the witness allegations.
This source finding must be read within the stated scope and source context. Passenger intervention and additional crew control Incident on 30 September 2026; accounts captured on 1 October 2026 BBC does not explicitly identify Itali as the source of its two-pilot detail. AP reports the control-input statement to Netanyahu and supplies no duration for Hayoun's intervention. AFP's 'took over control' quotation does not specify particular flight-control inputs. Travelling on the aircraft does not establish off-duty status. No crew roster or definitive control-and-landing sequence was supplied.
This source finding must be read within the stated scope and source context. Identity and reported medical condition of the injured captain Embassy statement dated 30 September 2026; supplied pages captured on 1 October 2026 The supplied S3 page reproduces the embassy statement and includes an embedded post, but the standalone original X page was not supplied. This supports an accurately attributed condition report on 30 September, not a new medical assessment on 1 October.
This source finding must be read within the stated scope and source context. Reported crew and passenger injuries Injury reports concerning the incident and passenger return on 30 September 2026 The original airport statement and emergency-service medical records were not supplied. The airport account does not identify who caused either pilot's injuries. The embassy's report about one named patient is not an exclusive count of injured people.
This source finding must be read within the stated scope and source context. Netanyahu's assault, crash-intent, weapon and custody allegations Netanyahu's statements and interviews concerning the 30 September 2026 incident The original interviews and a Saudi police or custody record were not supplied. The reporting supports attribution of these statements to Netanyahu; it does not independently establish custody, the weapon or deliberate crash intent. The absence of a supplied police record does not refute his arrest statement.
This source finding must be read within the stated scope and source context. Flydubai's direct account of the incident and recovery of control Flight FZ1073 incident on 30 September 2026 The airline statement does not identify an attacker or describe a weapon. No crew roster or cockpit recording was supplied, and the statement does not reconstruct who operated the controls at each stage. The BBC's additional count is a reported detail, not a demonstrated error or independently verified crew breakdown.
This source finding must be read within the stated scope and source context. Completed onward travel and passenger arrival in Israel Passenger departure from Tabuk and arrival in Israel on 30 September 2026 The quoted departure time in S7 has no explicit time-zone label. The precise arrival time comes from BBC; AP's dated photo captions corroborate arrival but not that clock time. The operator's statement concerns passengers, not the return of every crew member.
This source finding must be read within the stated scope and source context. Announced suspension of flydubai's Israel services Announcement concerning the 30 September 2026 incident, present in the supplied 1 October capture The statement establishes the announced suspension but does not provide a count of cancelled flights, a fixed end date or execution figures. Whether this announcement is already covered in either existing article cannot be checked.
This source finding must be read within the stated scope and source context. Meaning and attribution of the figure of 174 people Netanyahu's statement concerning the 30 September 2026 incident No authoritative manifest or passenger-and-crew breakdown was supplied. That limits treating the figure as an audited onboard total; it does not prevent accurate reporting of Netanyahu's attributed figure.
This source finding must be read within the stated scope and source context. Katz's terrorist characterisation and stated evidential basis Statement concerning the 30 September 2026 incident; S8 captured on 1 October 2026 The original ministerial statement and the evidence underlying the initial information were not supplied. S8 has no visible publication timestamp in the supplied text. Its quotations support attribution to Katz without establishing the underlying terrorist motive.
This source finding must be read within the stated scope and source context. Eyewitness evidence separately presented from the prime minister's account Passenger accounts of the 30 September 2026 incident The underlying interview recordings were not supplied. AP and BBC accounts involving Hayoun concern the same witness, not two independent eyewitnesses. The accounts do not settle the precise door-opening sequence, assault mechanism or motive.
This source finding must be read within the stated scope and source context. Investigation status and unresolved criminal intent Investigation status described in statements about the 30 September 2026 incident, supplied on 1 October The Saudi safety-investigation account is available through Khaleej Times, not an original investigative document. No completed report, Saudi police statement, cockpit-recorder evidence or suspect response was supplied. The airline's early-stage uncertainty is not a denial that an assault occurred or a refutation of the attributed political statements.
This source finding must be read within the stated scope and source context. Reported flight-tracking measurements and their evidential boundary Flight FZ1073 on 30 September 2026, approximately two and a half hours after departure The underlying tracking record and flight-recorder data were not supplied. The publications refer to the same tracking provider rather than independently collected telemetry. Their descriptions support attributed reporting of a sharp descent, not a verified reconstruction of its cause.
This source finding must be read within the stated scope and source context. Flight incident and safe diversion Flight of 30 September 2026; statements available by 1 October 2026 The airline statement does not identify the participants or establish a weapon, cause or intent. Its description of occupants as safe and accounted for does not mean that nobody was injured.
This source finding must be read within the stated scope and source context. Identity, hospital location and dated condition reports Embassy statement dated 30 September 2026; Hindustan Times report updated 1 October 2026 The embassy statement is reproduced by a news publication rather than supplied as a separately retrieved X page. Its condition report is dated 30 September, not a new 1 October clinical assessment. Hindustan Times gives neither the medical sources' identities nor the assessment time.
This source finding must be read within the stated scope and source context. Direct witness reporting of injuries and emergency treatment Injuries and emergency treatment on 30 September 2026; Hayun interview published 1 October 2026 These are witness and treatment accounts, not clinical records. The quoted observations concern the injured pilot after the attack and do not establish that either witness saw the stabbing itself.
This source finding must be read within the stated scope and source context. Training and employment history Historical training and employment from 2008 onward, as reported by 1 October 2026 SpiceJet's statement confirms employment duration, not exact joining or departure dates. The BBC's biographical paragraph does not explicitly attribute its career dates to LinkedIn. Hindustan Times' more precise dates are profile attributions; the original profile and institutional records are not supplied.
This source finding must be read within the stated scope and source context. Cockpit access and attribution of the door opening Flight of 30 September 2026; accounts published or available on 1 October 2026 Hayun's account was translated during the interview by his daughter Noa. His stated observation begins with an already-unlocked door. AP's summary does not detail Musayev's view of the actual unlocking moment. No cockpit recording or account from Machchhar is supplied.
This source finding must be read within the stated scope and source context. Reported stabbing, alleged crash intent and unknown motive Netanyahu's account after the 30 September incident; airline statements and 1 October 2026 witness interview The cautious statements do not disprove Netanyahu's allegation. They limit the available finding to an attributed allegation rather than an established investigative conclusion. No investigating-authority findings or cockpit-recorder evidence are supplied.
This source finding must be read within the stated scope and source context. Announced suspension of Flydubai's Israel services Announcement following the 30 September 2026 incident, available by 1 October 2026 The page gives no fixed restart date or quantified number of affected flights or travellers. Its earlier statement that other scheduled operations were unaffected precedes the third statement announcing the Israel-service suspension.
This source finding must be read within the stated scope and source context. Touchdown time versus final tracking message Flight of 30 September 2026; supplied reporting and tracking summary available on 1 October 2026 The airport operator's original statement is not supplied. The 09:45 local-time/06:45 GMT landing remains a source-attributed airport time; Al Jazeera is not an independent second confirmation.
This source finding must be read within the stated scope and source context. Occupant count and Netanyahu's rescue assessment Flight of 30 September 2026; statements reported in publications available on 1 October 2026 No supplied manifest separates passengers from crew. The sources do not establish 174 passengers. Netanyahu's accurately attributed lives-saved assessment is supported as his statement, not as a verified calculation of individual rescue causation.
This source finding must be read within the stated scope and source context. Profile-derived flight-hour figures and their coverage Cumulative career figures reported in documents available on 1 October 2026; underlying measurement periods unspecified All three accounts invoke the same LinkedIn profile rather than independent flight-hour records. The original profile and logs are not supplied, so the exact employer coverage and cumulative end date cannot be resolved. This does not invalidate the accurately attributed published figures.
This source finding must be read within the stated scope and source context. Passenger intervention and relieving crew Flight of 30 September 2026; Hayun interview published 1 October 2026 and airline statements available that day Hayun's account is a translated participant interview, not a verified record of control inputs. The airline's on-duty description and the witness report's off-duty label cannot be reconciled to a confirmed crew roster from the supplied material.
This source finding must be read within the stated scope and source context. Confirmed flight-deck incident and diversion of FZ1073 30 September 2026; airline statements captured on 1 October 2026. The airline's statements do not identify an attacker or weapon. Its wording 'safe and accounted for' does not establish that everyone was uninjured.
This source finding must be read within the stated scope and source context. Traceable early passenger account and source dependence Account concerning the flight of 30 September 2026; pages captured on 1 October 2026. N12, The Times of Israel and ANP form a reporting chain for this account, not three independent eyewitness confirmations. The captures do not establish when the quoted passage was first added.
This source finding must be read within the stated scope and source context. Separate named AP witness account of a stabbing in progress Flight of 30 September 2026; AP report updated at 07:56 EDT on 1 October 2026. This is AP's description of Musayev's statement, not a supplied full interview transcript or independently inspected footage of the stabbing. It supports a separately attributed witness allegation, not a completed official reconstruction or determination of motive.
This source finding must be read within the stated scope and source context. Participant account of intervention and the airline's crew attribution N12 interview published and visibly updated on 30 September 2026; airline statement captured on 1 October 2026. Rajuan's account is a participant's statement. Flydubai does not identify who restrained the suspect or who controlled the aircraft at each stage; its statement does not corroborate the passengers' detailed allocation of roles.
This source finding must be read within the stated scope and source context. Tracking service's published flight and transponder sequence Flight of 30 September 2026; all stated flight times are UTC. Analysis published on 30 September and updated on 1 October 2026. The linked granular CSV is not supplied, so no separate raw-data calculation was performed. The finding rests on the tracking service's own published analysis. The codes do not identify who entered them or independently establish what happened in the cockpit.
This source finding must be read within the stated scope and source context. Attributed medical-status reports concerning the captain Medical-status reports available in the supplied captures of 1 October 2026; AP describes the embassy update as occurring overnight. Both outlets attribute the medical status to the embassy; they are not two separate clinical assessments. The primary embassy statement, GCAA page and medical records are not supplied. These reports do not independently establish how the injuries were inflicted.
This source finding must be read within the stated scope and source context. Investigation status and unestablished motive Investigation status reported by AP on 1 October 2026; flydubai statements captured on that date. The UAE announcement is available here through AP, not through the missing UAE1 primary text. The regional official is anonymous. No completed investigation or statement from the accused pilot is included.
This source finding must be read within the stated scope and source context. Announced suspension of flydubai services to and from Israel Third statement present in the page captured on 1 October 2026, following the incident of 30 September 2026. This establishes the airline's announcement, not implementation for individual flights. Statement-level publication timestamps, cancellation records and a fixed resumption date are not supplied.
This source finding must be read within the stated scope and source context. Passenger's account of protecting his children Flight of 30 September 2026; BBC written account published 1 October 2026. BBC's written report supports this attributed personal account. The Newshour recording is not supplied, and the report does not establish that Polovincik personally witnessed the assault inside the cockpit. Novelty relative to the unavailable target article is undetermined.
This source finding must be read within the stated scope and source context. Recalled reassurance from the cockpit Recollection of the 30 September 2026 incident, reported by BBC on 1 October 2026. The interval is his approximate recollection of receiving reassurance, not a measured cockpit timeline. It does not establish the exact moment control was regained or identify the speaker.
This source finding must be read within the stated scope and source context. Reported altitude changes and the limits of interval verification 30 September 2026 flight; Flightradar24 analysis updated 1 October 2026. The linked granular CSV is not supplied, so no point-by-point calculation verifies BBC's particular drop-and-duration figure. The reports use different endpoints and durations. These altitude descriptions do not by themselves establish aircraft pitch, structural loads, the cause of damage or a pilot's intent.
This source finding must be read within the stated scope and source context. Airline-confirmed incident, diversion and landing 30 September 2026 flight; airline statements retrieved 1 October 2026. The airline statement does not specify a weapon, identify the attacker or provide a detailed control-recovery sequence. Its statement that everyone was safe and accounted for is not evidence that nobody was injured.
This source finding must be read within the stated scope and source context. Eyewitness support for the reported stabbing and passenger intervention Witness reports concerning 30 September 2026, available by 1 October 2026. AP provides directly attributed eyewitness reporting. NOS relays another outlet's account; the underlying Channel 12 interview and the unidentified speaker's relationship to other witness accounts are not supplied. These reports do not establish motive or a complete cockpit chronology.
This source finding must be read within the stated scope and source context. Investigation status and unresolved motive Investigation status reported on 1 October 2026; airline's earlier statement available in the same source snapshot. The UAE announcement is supported here through AP's attributed reporting, not through the absent WAM/UAE1 document. No completed investigative report is supplied. An investigative possibility is not an established motive or diagnosis.
This source finding must be read within the stated scope and source context. Netanyahu's radicalisation allegation and qualified assessment of Iranian links Fox & Friends interview and written reports dated 1 October 2026. The sources establish Netanyahu's allegation and qualified assessment, not the underlying radicalisation or Iranian involvement. The refusal to explain his basis is not a disproof. FOX1 supplies programme metadata but contains a player error and no transcript; detailed wording is supported by the retrieved written quotations.
This source finding must be read within the stated scope and source context. Reported arrest and possible transfer destinations Reports available on 1 October 2026; the retrieved TOI text does not establish the exact time of the Hannity interview. No Saudi custody order or transfer authorisation is supplied. An expected transfer to the UAE and a reported Israeli request describe different possible destinations, not an agreed or completed transfer. TOI1 concerns an interview with Sean Hannity, distinct from the Fox & Friends appearance quoted in FOX2.
This source finding must be read within the stated scope and source context. Reported condition of the injured captain Medical status reported on 1 October 2026. These are attributable status reports. The original embassy statement and clinical records are not supplied.
This source finding must be read within the stated scope and source context. Subsequent operational announcement in the airline source Airline statements concerning the 30 September incident, retrieved 1 October 2026. Individual statement timestamps, the exact suspension start time and a resumption date are not shown. The announced suspension concerns flights to and from Israel, not the airline's entire network.
This source finding must be read within the stated scope and source context. Netanyahu's indoctrination allegation and stated basis 1 October 2026 Fox's own published extracts support the attribution and stated basis, not proof of indoctrination. The underlying personal information is not disclosed in these extracts. The supplied video page shows a playback error and contains no full transcript.
This source finding must be read within the stated scope and source context. Crash intent, mental state and possible external involvement 1 October 2026 The reported cry and inference of suicidality remain Netanyahu's account and interpretation, not a clinical finding. The extracts do not establish crash intent or Iranian involvement. His expected timetable is a forecast, not a verified investigative outcome.
This source finding must be read within the stated scope and source context. Additional reporting underlying the radicalization allegation Reporting on 1 October 2026; the anonymous official referred to recent years The official's information was not shown to be independent of Netanyahu's. The original Channel 16 report and full colleague testimony were not supplied. Axios uses recent months in its account of Netanyahu and recent years in the official's quotation; these do not establish a verified chronology. Religious observance and refusal to comment neither prove nor disprove indoctrination.
This source finding must be read within the stated scope and source context. Open investigations into motive and possible planning Investigation reporting available on 1 October 2026 concerning the 30 September incident; Statement 2's issue time is not supplied The original UAE statements were not supplied, so their content is retained through AP and Axios reporting. The regional official was anonymous. These are accounts of open inquiries, not findings of terrorism or mental illness, and not a refutation of Netanyahu's allegations.
This source finding must be read within the stated scope and source context. Reported Israeli investigation and participation 1 October 2026; inquiries into the 30 September incident Reports of Israeli participation do not independently corroborate the BBC Arabic-specific passenger interviews or preliminary crash-intent conclusion. No underlying interview records or Israeli investigative report were supplied.
This source finding must be read within the stated scope and source context. UAE jurisdiction position Reported on 1 October 2026 This is the UAE authorities' reported position, not an adjudication of exclusive jurisdiction or a decision about the eventual place of prosecution. The original foreign-ministry or WAM statement was not supplied.
This source finding must be read within the stated scope and source context. Flydubai suspension and proposed passenger-return arrangements Statements available on 1 October 2026; proposed return-flight start on 2 October 2026 The statements establish the announcement and preparations, not completed flights. Flydubai's Statement 3 gives no fixed resumption date. The ministry's original statement was not supplied. The basic Friday return-flight plan already appears in the captured BBC source.
This source finding must be read within the stated scope and source context. Request for additional Etihad services Request on the night of 30 September 2026; reported on 1 October 2026 The supplied reporting supports a request, not Etihad's acceptance or additional operated capacity. No Etihad statement or expanded timetable was supplied. The request already appears in the captured BBC source.
This source finding must be read within the stated scope and source context. Reported ticket-sale openings and announced fares Reported on 1 October 2026; intended start on Friday 2 October 2026 These are Ynet's reports of sales and airline announcements; direct booking records and airline statements were not supplied. Sold-out website tickets do not establish total aircraft capacity. No departure is confirmed. These sale and fare details are absent from the supplied BBC snapshot, but novelty relative to the internal article remains unverified.
This source finding must be read within the stated scope and source context. Reported baggage restrictions and differing descriptions Reports available on 1 October 2026 concerning proposed return flights from 2 October Ynet does not specify the permitted bag's dimensions. Generic carry-on wording does not by itself prove a contradiction, and the supplied record does not establish the chronology of any policy changes. Final carrier conditions, particularly Israir's allowance, remain unverified.
This source finding must be read within the stated scope and source context. Reported custody, questioning and possible transfer Reported status on 1 October 2026 No direct Saudi custody document, approved transfer decision or completed-handover record was supplied. A reported Israeli request and Netanyahu's UAE-transfer expectation do not establish an agreed destination or a jurisdiction ruling.
This source finding must be read within the stated scope and source context. Incident background and observable violence Incident on 30 September 2026; statements and reporting captured on 1 October The airline statement and eyewitness account support the incident and successful diversion, not indoctrination, a medical diagnosis or a final determination of intent. Safe and accounted for does not mean uninjured.
This source finding must be read within the stated scope and source context. Publication and attribution of the statement 30 September 2026 The publication date is not established as the date of the flight incident.
This source finding must be read within the stated scope and source context. Guterres’s reaction to the flight incident Statement issued 30 September 2026; incident date unspecified The release provides no account of what happened; its description of the outcome is attributed to the statement.
This source finding must be read within the stated scope and source context. Guterres’s condemnation Statement issued 30 September 2026 The wording does not identify a particular act or person responsible for the flight incident.
This source finding must be read within the stated scope and source context. Authorities and investigation Statement issued 30 September 2026 The release does not name the authorities or describe the investigation; passenger safety is reported as part of Guterres’s statement, not independently verified here.
Smit Machchhar says he opened the cockpit door while injured and under attack, enabling others to help as the aircraft descended.
Captain Smit Machchhar told Indian Prime Minister Narendra Modi in a video call that he was injured on the cockpit floor and still being attacked by his co-pilot when he noticed the aircraft descending. He said he made a final effort to open the door from inside, after which others entered and helped. [1]
The account adds detail to the emergency aboard flydubai flight FZ1073 from Dubai to Tel Aviv on 30 September. Saudi authorities say preliminary investigations indicate that the co-pilot attacked Machchhar, injuring both men. The flight, with 182 people aboard, landed safely in Tabuk. Flydubai credits on-duty crew travelling on the aircraft with securing it, diverting it and landing it. [4] [5]
Machchhar said he was fighting for his own life but did not want others to die, and acknowledged the help of those who entered the cockpit. Flydubai says the reasons behind the incident remain under investigation. [1] [4]
BBC News reports Machchhar’s account to Modi; flydubai describes the travelling crew’s role in the safe landing.
Source date as found: 2026-10-02 (captured at 08:16:04.713 UTC; extracted body displays only a relative publication time)
Source date as found: 2026-10-02 (capture date; article describes Friday's account)
Source date as found: 2026-10-02 (displayed page timestamp: 12:34:48 PM; time zone unstated)
Source date as found: Captured 2026-10-02; individual statements are undated in the supplied text
Source date as found: Captured 2026-10-02; statement describes events on 30 September and 1 October 2026
Source date as found: 2026-10-01 (published 16:14; updated 20:10; time zone unstated)
This source finding must be read within the stated scope and source context. Reported video call and the captain's account of his injuries Account reported on 2 October 2026, recalling the incident of 30 September 2026. The quotations were checked against the supplied published text, not the recording. The dated reporting supports the account's reporting date but does not independently authenticate the recording or establish an exact call time.
This source finding must be read within the stated scope and source context. Continuing assault and opening the cockpit door Recollection of the 30 September 2026 incident, reported on 2 October 2026. The explicit continuing-assault detail and first-person door-opening quotation are supported by BBC. AP1 reproduces different first-person remarks; its door-opening sentence is attributed to witnesses and Israeli authorities. The precise relationship between the end of the assault and the door opening remains unverified.
This source finding must be read within the stated scope and source context. Flight identity, incident date, safe landing and number aboard Flight and emergency landing on 30 September 2026. The airline statement is directly retrieved; the Saudi official statement is available through Sabq rather than a ministry-hosted page. No passenger manifest was supplied. The 182 total is the number aboard, not an established number of deaths prevented. A safe landing does not mean that everyone was uninjured.
This source finding must be read within the stated scope and source context. Preliminary official finding about the assault Incident of 30 September 2026; statement describing developments through 1 October 2026. This is a preliminary investigative statement, not a final technical reconstruction or an adjudicated criminal finding. The retrieved record does not establish a proven intention to crash the aircraft.
This source finding must be read within the stated scope and source context. Shared intervention and the limits of the causal reconstruction Incident of 30 September 2026, as described in sources available by 2 October 2026. No timestamped cockpit record, flight-data analysis or completed causal report was supplied. AP1's witness and authority summary is not a separately inspected eyewitness interview. The evidence supports a plausible contribution by the door opening, but not that this action alone arrested the descent or that a crash was otherwise inevitable.
This source finding must be read within the stated scope and source context. The captain's stated purpose and Modi's praise Video-call account reported on 2 October 2026. These passages establish what BBC reports the speakers said. Missing flight data does not invalidate an accurately attributed statement about the captain's belief or purpose, but the praise is not a substitute for technical evidence about the outcome without intervention.
This source finding must be read within the stated scope and source context. Investigative status and possible motives Attorney-General's inquiry reported on 1 October 2026; airline statements available by 2 October 2026. The Attorney-General's wording is supported here through Khaleej Times, not a retrieved original order or the listed WAM page. No final investigative finding establishing motive, crash intent, terrorism or state involvement is included.
This source finding must be read within the stated scope and source context. Transfer to Abu Dhabi and the dated recovery update Transfer and embassy update on 1 October 2026; hospital account reported on 2 October 2026. The embassy's health assessment is a dated diplomatic statement reported by a news outlet, not an independently obtained medical prognosis. The original embassy health post was not separately supplied. The transfer statement does not by itself establish the co-pilot's subsequent custody status.
This source finding must be read within the stated scope and source context. Announced operational consequence Announcement present in the source captured on 2 October 2026; individual statement dates and implementation time are not displayed. The source supplies no duration or cancelled-flight count. Earlier-numbered Statement 2 said other scheduled operations were unaffected; that wording does not establish the absence of the Israel-specific suspension subsequently announced in Statement 3. Its novelty relative to the target article cannot be checked without that article.
A UAE prosecutor says the co-pilot tried to seize control of a Tel Aviv-bound flight that later landed safely in Saudi Arabia. Investigators are still examining the motive.
The UAE prosecutor general says the co-pilot on Flydubai flight FZ1073 attacked the captain with a crash axe and tried to take control of the aircraft during its 30 September flight to Tel Aviv. Reuters reports that he described it as an attempted terrorist attack. Investigators are still examining the motive and any possible connections to others. [7] [1]
An axe had been mentioned before the UAE account: CNN reported Israeli Prime Minister Benjamin Netanyahu’s description of an axe attack on 1 October. A passenger told CNN through a translator that the attacker had a knife. It remains unclear how the two descriptions fit together. [4] [7]
Flightradar24 recorded a steep descent followed by sharp changes in altitude, along with general-emergency and unlawful-interference transponder codes. Flydubai says pilots travelling on the flight secured the aircraft and landed it in Tabuk, Saudi Arabia, while cabin crew and passengers also assisted. [3] [2]
The Associated Press reports, citing two unnamed sources, that the co-pilot had previously been barred from flying in Oman over concerns about extremist views. Investigators are examining whether he acted alone or had links to extremist groups. [8]
Reuters and the BBC report the UAE prosecutor’s account of the axe and attempted takeover; the investigation into motive and possible connections continues. [7] [1]
Source date as found: Captured 2026-10-03T07:56:05Z
Source date as found: Statements concerning 2026-09-30; captured 2026-10-03
Source date as found: Published 2026-09-30; updated 2026-10-03
Source date as found: Aired 2026-10-01, 08:00–08:30 ET
Source date as found: Page entries dated 2026-10-01; captured 2026-10-03
Source date as found: 2026-10-01, 21:08; timezone not specified
Source date as found: 2026-10-03
Source date as found: Updated 2026-10-03, 04:17 AM EDT
This source finding must be read within the stated scope and source context. Reported UAE prosecutorial assessment of the FZ1073 cockpit attack Statement reported on 3 October 2026; incident on 30 September 2026 The original WAM document listed as GOV1 is absent from the supplied documents. These passages verify Reuters' attribution, not independent forensic confirmation of the weapon or takeover attempt. No charge sheet or judicial finding is supplied.
This source finding must be read within the stated scope and source context. Chronology of the axe account and comparison with the supplied BBC article 1–3 October 2026 CNN was reporting Netanyahu's account, not independently identifying the weapon. Only the supplied current BBC capture can be compared; no earlier BBC version or separate previously published article is provided for a before-and-after comparison.
This source finding must be read within the stated scope and source context. Publicly reported investigative status Public reporting available on 3 October 2026 The original UAE statement is not supplied. An ongoing inquiry does not invalidate the prosecutor's assessment, but these reports do not supply a finalized account of a specific ideology, directing party or intended crash outcome.
This source finding must be read within the stated scope and source context. Earlier Saudi assault account and the translated passenger description of a knife Saudi statement and CNN broadcast on 1 October 2026; comparison with reporting on 3 October 2026 The Saudi text is a republication, not a supplied original SPA page. CNN labels its transcript as a rush transcript. The passenger's precise vantage point and observation time are not established, and the documents do not determine whether one or more objects were used. His description does not by itself disprove the axe account.
This source finding must be read within the stated scope and source context. Flight trajectory, emergency signals and reported descent measurements Flight on 30 September 2026, including the trajectory from 05:21 to 05:33 UTC; source accounts captured on 3 October 2026 The linked granular CSV is not supplied, so Reuters' calculation was not independently reproduced. The BBC passage does not define the same measurement interval, preventing a like-for-like comparison. Flight movement and transmitted codes do not identify who made each control input or establish intent; the unlawful-interference signal is not an adjudication of terrorism.
This source finding must be read within the stated scope and source context. Airline account of intervention, diversion and landing Incident on 30 September 2026; airline statements captured on 3 October 2026 The statements do not provide a complete second-by-second reconstruction of cockpit entry, restraint or control inputs. Passenger assistance cannot be equated with operating the aircraft during landing on this evidence.
This source finding must be read within the stated scope and source context. Nationality and reporting about previous extremism concerns Netanyahu's Fox remarks on 1 October 2026; AP report updated on 3 October 2026 Fox's supplied account contains no publicly checkable supporting security records. AP's previous-employment account is relevant additional reporting, but no personnel or regulatory document is supplied. The independence of all information chains is not established, and reported prior concerns do not establish the motive for this attack.
This source finding must be read within the stated scope and source context. Attributed crash-intent assessment and unresolved external connections Netanyahu's remarks on 1 October 2026; AP investigative reporting on 3 October 2026 The supplied documents contain no direct recording of the reported words, interrogation record or final technical reconstruction establishing a deliberate crash plan or external direction. The ongoing inquiry does not exclude either possibility.
This source finding must be read within the stated scope and source context. Conflicting passenger-and-crew totals Saudi statement published on 1 October 2026; flydubai Statement 4 captured on 3 October 2026 Statement 4 has no publication date in the supplied page. No passenger manifest or record reconciling counting categories is supplied. GOV2 is the SPA-bylined republication, not a retrieved original SPA page.
This source finding must be read within the stated scope and source context. Announced suspension of Israel operations Suspension reported by 1 October 2026; airline page captured on 3 October 2026 The supplied statements give no resumption date or verified number of canceled flights. Their announcement does not independently measure the operational extent of the suspension.
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…