Przejdź do treści
Teraz

Prawo · Cockpit attackRozwijający się temat · relacja 2 z 3

Flydubai captain recovering as assault inquiry moves to UAE; Iran link unproven

Captain Smit Machchhar is recovering in Abu Dhabi as Saudi Arabia’s preliminary inquiry identifies a co-pilot assault. The transfer to the UAE advances the case—not proof of motive, crash intent or an Iranian connection.

Napisano 7 min czytania · 185 źródeł

HeyDex

Dostępne po angielsku

Co się zmieniło od naszej ostatniej relacji

44 godziny później

Wtedy

What forced Flydubai’s safe diversion? Crash-attempt allegations remain unproven

Co uznaliśmy za wciąż otwarte

  1. The cockpit sequence, pilots’ medical condition, complete injury count, any arrests and passengers’ onward journey remain unresolved.

    Wciąż otwarte

    Both pilots were injured, the captain is recovering in Abu Dhabi, the detained suspect was transferred to the UAE, and passengers reached Israel. The complete injury inventory and exact cockpit sequence remain unresolved.⁠148⁠129⁠3⁠59⁠20

  2. A directly attributable airline or investigating-authority update explaining the incident and its consequences.

    Wyjaśnione

Teraz

Captain Smit Machchhar is recovering in Abu Dhabi as Saudi Arabia’s preliminary inquiry identifies a co-pilot assault. The transfer to the UAE advances the case—not proof of motive, crash intent or an Iranian connection.

Wyjaśnione od tego czasu

  1. A directly attributable airline or investigating-authority update explaining the incident and its consequences.

    The Saudi Interior Ministry’s October 1 preliminary finding identifies an assault by the co-pilot on the captain and reports both pilots’ return to the UAE. UAE prosecutors have begun an investigation, not announced a final motive or intent finding.⁠148⁠124⁠159

Captain Smit Machchhar is alive, stable and recovering in an Abu Dhabi hospital after the emergency that brought his Dubai-to-Tel Aviv flight down safely in Saudi Arabia. The Indian captain initially received treatment in Tabuk for reported head and hand wounds and underwent surgery. By October 2, 2026, an envoy’s account described him as “smiling, laughing, chatting.” That recovery is the clearest human consequence of a flight whose survival depended on help reaching the cockpit.⁠16⁠129

The investigation has also moved forward. Saudi Arabia’s Interior Ministry said on October 1 that its preliminary inquiry found the co-pilot assaulted the captain during Flydubai flight FZ1073, leaving both injured. Both pilots subsequently returned to the United Arab Emirates with an Emirati security team; the Associated Press reported that the suspect was transferred late Thursday, October 1. Assault is now a preliminary investigative finding. Motive is not.⁠148⁠124⁠3

When HeyDay News reported this emergency on September 30, we established that the aircraft had diverted safely to Tabuk and that passengers were described as safe and accounted for. Stabbing and deliberate-crash allegations remained unproven. The new finding identifies who assaulted whom, but it is neither a court judgment nor a final determination that the attacker intended to destroy the aircraft.

On October 1, UAE Attorney-General Hamad Saif Al Shamsi ordered specialised public prosecutors to investigate with the General Civil Aviation Authority and other relevant bodies. The inquiry covers circumstances, motive, possible terrorism, prior planning and outside direction. No specified criminal counts or public suspect name are established in the available reporting. Israeli authorities are seeking questioning after the transfer, but no completed interview or scheduled date is established.⁠156⁠181⁠178⁠150

The door that let help in

Passenger accounts describe the badly injured captain opening or unlocking the cockpit door, allowing others to enter. Passengers and crew reportedly restrained the attacker, pulled him out and tied him with headphone cables. Two pilots travelling off duty reportedly helped regain control and land the aircraft. The precise division of responsibility—who first restrained the attacker, moved the controls and performed the landing—still lacks a final reconstruction.⁠168⁠20⁠1

I grabbed the attacker, put him in a chokehold and pulled him out.

Yaniv Hayun 161

Hayun, whose surname also appears as Hayoun, said he then returned to the cockpit and pulled back the controls before another pilot took over. His testimony describes an extraordinary intervention; it is not an independently verified measurement of the aircraft’s response. A passenger dentist, variously named Shota Musayv or Shota Musayev, reportedly treated the bleeding captain. His precise treatment method is undocumented.⁠161⁠2⁠162

The dentist also recalled the restrained suspect asking to be killed. That recollection may matter to investigators, but it does not establish a clinical diagnosis or motive. Passenger Miriam Okayion described shaking, blood aboard and fear that the aircraft would crash. The accounts convey terror without settling the cockpit sequence.⁠2⁠9

Some reporting reversed the pilots’ roles. NBC News on October 1 attributed to Netanyahu an account of a pilot stabbing the co-pilot; the BBC that day called Machchhar the injured co-pilot. ABC News on October 2 described the co-pilot stabbing the captain. The Saudi preliminary finding resolves the central distinction: Machchhar was the injured captain, and the co-pilot was the alleged attacker. The earlier role descriptions are superseded, not competing current findings.⁠19⁠17⁠2⁠148

A steep descent, not settled intent

FZ1073 was flying from Dubai International Airport to Ben Gurion on September 30 when it diverted to Prince Sultan bin Abdulaziz International Airport in Tabuk. Flightradar24 places the incident above Saudi Arabia; other route accounts describe the Saudi–Jordanian transition and a turn back from Jordanian airspace. The Israeli destination does not establish that the assault happened over Israel, and individual cockpit actions cannot yet be assigned exact positions.⁠73⁠106⁠16

The aircraft descended rapidly, but published measurements differ. NBC News’s October 1 account gave 33,000 to 17,000 feet in about a minute. BBC Verify’s October 1 analysis gave 34,000 to about 16,600 feet over roughly 90–100 seconds. Channel 4 News, also on October 1, described 14,000 feet lost in about 30 seconds. These may cover different segments or inconsistent readings; matching timestamped samples are unavailable. They cannot be averaged into one definitive flight profile, and altitude loss alone cannot prove intent to crash.⁠1⁠7⁠11

Flightradar24 records the transponder sequence 7700 → 7500 → 7700: general emergency, unlawful interference, then general emergency again. Exact switch times and who selected the codes remain unknown. Israel scrambled fighter aircraft as a precaution, but no particular interception or escort is established. An unlawful-interference alert explains the alarm; it does not identify motive.⁠106⁠46

An Aviation Safety Network entry identifies the aircraft as a Boeing 737 MAX 8, registration A6-FKF, and classifies its damage as substantial. That identification lacks independent confirmation through a complete airline aircraft statement. Reports and photographs describe tail or rudder damage, but no available technical inspection establishes its extent, timing or cause. A safe landing does not mean an undamaged aircraft.⁠135⁠138

The reported departure and landing clocks are likewise not fully reconciled against an event-specific record. Nor is the onboard total: ABC News on October 2 reported 174 passengers and eight crew, implying 182 people by arithmetic. Channel 4’s October 1 account said all 180 aboard survived. NBC’s earlier “nearly 200” was an approximation, not an authoritative manifest. The specific breakdown is more useful, but remains unconfirmed as a final total.⁠2⁠6⁠1

No death is reported. NBC reported three passengers with minor injuries, while other accounts described no passenger harm or no serious injuries. “No serious injuries” can coexist with minor injuries; “no injuries” cannot serve as a complete medical finding here. Both operating pilots were injured, and the suspect has no comparable final recovery update.⁠6⁠20⁠148

The consequences extend beyond this flight

Passengers subsequently reached Israel on a rescue or replacement flight. Their reported September 30 arrival at Ben Gurion was around 18:40 local, although that exact time is not independently confirmed. Their completed onward journey answers one of the practical questions left open in our first report.⁠59⁠31

Flydubai suspended Dubai–Tel Aviv service pending investigation, with no verified fixed end date or confirmed resumption. Repatriation flights for 1,800 travellers stranded in Dubai were approved to begin October 2. That figure is not FZ1073’s passenger count. El Al, Israir and Arkia were named as planning rescue flights; approval and plans do not establish actual departures or arrivals.⁠154⁠153⁠17

Israel is examining whether assigning an Omani pilot breached an aviation agreement described as permitting pilots from countries with diplomatic relations with Israel to land there. Oman has no formal diplomatic relations with Israel. No breach finding is established. Nationality is relevant to that reported eligibility rule, not evidence of the individual’s motive. Questions about the weapon, screening and cockpit-door controls also remain unanswered.⁠16⁠9⁠18

Israeli officials have advanced a terrorism interpretation. Defense Minister Israel Katz called it an attempted jihadist terror attack; Netanyahu cited indications of Islamist indoctrination and said a deliberate crash attempt was “very likely,” while acknowledging that final conclusions had not been reached. An official’s claim about antisemitic social-media statements came without supporting posts. These assessments are not independently established findings.⁠31⁠17⁠2

Netanyahu said it was too early to determine Iranian involvement. Trump nevertheless answered a question about a possible Iran link with “Based on what I'm hearing, yes,” and warned Iran would be “hit very hard” if responsible. He also said the inquiry continued. No investigating-authority finding established through October 2 supports an Iran connection.⁠17⁠2⁠5⁠183

Sources for this developing report

⁠1⁠2⁠3⁠4⁠5⁠6⁠7⁠8⁠9⁠10⁠11⁠12⁠13⁠14⁠15⁠16⁠17⁠18⁠19⁠20⁠21⁠22⁠23⁠24⁠25

⁠26⁠27⁠28⁠29⁠30⁠31⁠32⁠33⁠34⁠35⁠36⁠37⁠38⁠39⁠40⁠41⁠42⁠43⁠44⁠45⁠46⁠47⁠48⁠49⁠50

⁠51⁠52⁠53⁠54⁠55⁠56⁠57⁠58⁠59⁠60⁠61⁠62⁠63⁠64⁠65⁠66⁠67⁠68⁠69⁠70⁠71⁠72⁠73⁠74⁠75

⁠76⁠77⁠78⁠79⁠80⁠81⁠82⁠83⁠84⁠85⁠86⁠87⁠88⁠89⁠90⁠91⁠92⁠93⁠94⁠95⁠96⁠97⁠98⁠99⁠100

⁠101⁠102⁠103⁠104⁠105⁠106⁠107⁠108⁠109⁠110⁠111⁠112⁠113⁠114⁠115⁠116⁠117⁠118⁠119⁠120⁠121⁠122⁠123⁠124⁠125

⁠126⁠127⁠128⁠129⁠130⁠131⁠132⁠133⁠134⁠135⁠136⁠137⁠138⁠139⁠140⁠141⁠142⁠143⁠144⁠145⁠146⁠147⁠148⁠149⁠150

⁠151⁠152⁠153⁠154⁠155⁠156⁠157⁠158⁠159⁠160⁠161⁠162⁠163⁠164⁠165⁠166⁠167⁠168⁠169⁠170⁠171⁠172⁠173⁠174⁠175

⁠176⁠177⁠178⁠179⁠180⁠181⁠182⁠183⁠184⁠185

Oś czasu

Dzień 3 · 3 relacje

Oś czasu historii

  2. Podało jako pierwsze

  3. Podało jako pierwsze

  4. Nasze materiały · Aktualizacja 1

    What forced Flydubai’s safe diversion? Crash-attempt allegations remain unproven

  5. Nasze materiały · Aktualizacja 2Jesteś tutaj

    Flydubai captain recovering as assault inquiry moves to UAE; Iran link unproven

  6. Nasze materiały · Aktualizacja 3Nowsza

    Flydubai co-pilot allegedly targeted Ben Gurion terminal. How did he clear checks?
Wersja z emisji
  1. On September 30 we reported FZ1073 landed safely, with its cause unresolved. Now investigators identify a cockpit assault. Both injured pilots have been moved to the United Arab Emirates, and the flight suspension leaves 1,800 other travellers awaiting repatriation. What does the assault finding establish—and what remains unproven about a crash attempt or an Iran connection?
  2. Assault is now a preliminary investigative finding, not merely an allegation surrounding an unexplained diversion. The co-pilot assaulted the captain during the flight, and both were injured. That finding is not a court judgment. It does not establish a formally filed criminal charge, a terrorist motive, or a final determination that the attacker deliberately tried to destroy the aircraft.
  3. The suspect was sent from Saudi Arabia to the UAE late Thursday, October 1. Both pilots returned with an Emirati security team. Earlier descriptions of questioning in Saudi Arabia or an expected transfer are now outdated. Security-accompanied transfer does not establish a particular extradition procedure, remand order or charging decision.
  4. UAE Attorney-General Hamad Saif Al Shamsi ordered specialised public prosecutors to investigate on October 1, coordinating with the civil aviation authority and other relevant bodies. The inquiry covers the circumstances, motive, possible terrorist activity, prior planning and outside direction. Saudi and Emirati officials participated in the initial investigation. Israeli officials are also investigating or seeking involvement, including questioning after the transfer; no completed Israeli interview or scheduled questioning date is established.
  5. Smit Machchhar was the injured captain—not the attacking co-pilot. Some early accounts reversed those roles, and inconsistent spellings made the same Indian captain appear under several names. The newer preliminary finding resolves that central distinction, but not every action either man took inside the cockpit. The suspect’s public name and specified criminal charges remain unestablished.
  6. Machchhar is now reported stable and recovering in an Abu Dhabi hospital. He initially received treatment in Tabuk for reported head and hand wounds and underwent surgery. Severe early descriptions were followed by updates that he was stable, out of danger and recovering well. India’s ambassador to the UAE, Deepak Mittal, visited him. An earlier destination account placed him in Dubai; whether that described an intermediate movement or an error remains unresolved. Abu Dhabi is the current location account. The injured suspect has no comparable final recovery update.
  7. The badly injured captain reportedly unlocked or opened the cockpit door, allowing help to enter. Passengers and crew restrained the attacker and pulled him out. The reported restraint included headphone cables. Two pilots travelling off duty, also described as reserve pilots, reportedly helped regain control, stabilise the aircraft and land it.
  8. A passenger, Yaniv Hayun, reportedly used a chokehold to remove the attacker, then returned to the cockpit and pulled back the controls before another pilot took over. That remains a recollection, not an independently verified reconstruction of the aircraft’s movements. Who first restrained the attacker, who first moved the controls, and which pilots handled the subsequent flight and landing remain unsettled.
  9. A dentist travelling as a passenger reportedly treated the captain’s heavy bleeding from his head and hands. His name appears as Shota Musayv, Shota Musayev and Musaev Shota; an authoritative spelling and the precise treatment method are not established. The restrained suspect reportedly asked to be killed. That recollection does not establish a clinical diagnosis, a settled suicidal state or a motive.
  10. Passenger Miriam Okayion, also rendered Aion, experienced shaking, a rapid descent and blood aboard, and feared the aircraft would crash. Another account describes her reassuring fellow passengers. One count identifies four Israeli passengers entering the cockpit. A promised special award for five Israeli passengers recognises assistance more broadly; it does not establish that five entered the cockpit or operated the controls. The award’s name, presentation date and complete recipient list remain unestablished. Narendra Modi and Benjamin Netanyahu praised the captain’s actions, and Netanyahu also praised the assisting passengers.
  11. The aircraft lost thousands of feet rapidly, but its exact descent profile remains unsettled. One account describes 33,000 to 17,000 feet in about a minute: a 16,000-foot difference. Another describes 34,000 to about 16,600 feet in roughly 90 to 100 seconds: about 17,400 feet. A shorter interval is described as 14,000 feet in about 30 seconds. These are different endpoints and intervals, not interchangeable measurements.
  12. Other estimates include more than 14,000 feet in 29 seconds, specifically 14,125 feet in one account, and 14,300 or 15,075 feet in 37 seconds. Longer estimates include roughly 17,000 feet in under two minutes, 16,000 feet in two minutes, and 4,000 metres in about a minute. Another pairs an initial altitude near 34,000 feet with about 15,600 feet later. Broader descriptions range from about 13,000 to 20,000 feet.
  13. One account contains a factor-of-ten discrepancy: more than 1,400 feet in seconds, then around 14,000 feet later. Another describes a drop, a brief climb and a second descent; a separate estimate puts stabilisation at about five minutes. Matching timestamped altitude samples and altitude definitions are unavailable. The figures must not be averaged, added together or turned into a definitive flight profile. The descent alone does not prove an intent to crash.
  14. The aircraft transmitted an unlawful-interference alert between two general-emergency codes: 7700, then 7500, then 7700 again. The first change is placed about seven minutes after the initial alert. Exact switch times and who selected each code remain unknown. The codes are not a recording of everything said over the radio, and they do not establish motive. Israel scrambled fighter aircraft as a precaution; a particular interception, escort or aircraft type is not established.
  15. FZ1073 landed safely at Prince Sultan bin Abdulaziz International Airport in Tabuk, northern Saudi Arabia. It had been flying from Dubai International Airport to Ben Gurion on September 30. The more specific aircraft identification is a Boeing 737 MAX 8, registration A6-FKF, manufacturer serial number 61013 and construction number 8422. That identification has not been independently confirmed through a complete airline aircraft statement.
  16. The reported departure was 7:05 a.m. Dubai time, or 03:05 UTC; a conflicting account gives 6:05 a.m. local. Reported landing was 9:45 a.m. Saudi time, or 06:45 UTC. These clocks have not been independently reconciled. The emergency is placed roughly two to two-and-a-half hours into the flight. An approximate 05:25 UTC event time is not a departure time and cannot settle the entire chronology.
  17. The Israeli destination does not mean the assault happened over Israel. Tracking descriptions place the incident above Saudi Arabia, south-southeast of Tabarjal. Other route accounts describe the Saudi–Jordanian transition, entry into Jordanian airspace and a turn back toward Tabuk. A claim placing the stabbing as the aircraft entered Israeli airspace conflicts with that route description and remains unestablished. Without timestamped positions for individual cockpit actions, their precise locations cannot be assigned.
  18. A safe landing does not mean an undamaged aircraft. Photographs and reports describe tail or rudder damage, including an allegation that part of the rudder was missing. The damage classification is substantial, but no supplied technical inspection establishes its extent, timing or cause. Neither the images nor the classification justify a claim about how close the structure came to failure.
  19. The most explicit breakdown is 174 passengers and eight crew, implying 182 people by arithmetic—not an independently verified manifest. Another total is 180; an earlier approximation is nearly 200. Other counts use 174 as everyone aboard, or describe more than 170, more than 150, 160 to 180, and even 127. They cannot all be treated as the same count.
  20. No death is reported. Passengers were described as safe and accounted for, but the complete injury inventory remains open. Three passengers reportedly had minor injuries. That can coexist with no serious injuries; it cannot be reconciled with an unqualified claim of no injuries. Both operating pilots were injured. Descriptions of more than 20 or about 30 children, four Americans and at least one U.S. citizen likewise lack a complete roster to reconcile them.
  21. The passengers subsequently reached Israel on a rescue or replacement flight. Their reported Ben Gurion arrival was around 18:40 local, or 15:40 UTC, on September 30, but the exact clock time and flight details are not independently established. Flydubai reportedly sent two aircraft to retrieve them. An eight-hour wait is described in one account, not established as every passenger’s individual waiting time.
  22. The suspension now affects 1,800 travellers stranded in Dubai—not 1,800 people from FZ1073. Repatriation flights were approved to begin Friday, October 2. El Al, Israir and Arkia planned rescue flights, and Israel’s Transportation Ministry asked Etihad to increase Abu Dhabi–Tel Aviv service. Approval and plans do not confirm particular departures or arrivals. Flydubai’s suspension has been described as temporary, lasting several days or a week; no verified fixed end date or confirmed resumption is established.
  23. The co-pilot’s reported Omani citizenship raises an eligibility question, not proof of motive. Israel is examining whether assigning him breached an aviation agreement described as permitting pilots from countries with diplomatic relations with Israel to land there. Oman has no formal diplomatic relations with Israel. The Israeli Civil Aviation Authority was asked to examine compliance, and increased pilot checks were announced. Neither a breach finding nor completed implementation of those checks is established. “Ammani” in some accounts should not create a different nationality. His employment history also remains unsettled, including an account placing his Flydubai service at less than a year.
  24. The weapon remains unidentified forensically. A knife, penknife and possible axe have been discussed, but none is an established identification. How a weapon came aboard, what cockpit access and door controls allowed, and whether hiring or screening missed a demonstrable warning remain unanswered. Suggestions about repeated checks, door overrides or a deliberately induced dive are analysis, not findings of a specific security failure.
  25. Terrorism, radicalisation, sabotage and an intended crash remain assessments under examination. Claims of Islamist indoctrination and social-media discussion of killing Jews lack independently established supporting evidence. Mental illness, a politically motivated attack and other possibilities remain under investigation. An initial suggestion that the suspect acted alone is not a final conclusion. An early assessment against hijacking has been overtaken by a broader investigation of assault and possible unlawful takeover—not by a final terrorism verdict.
  26. The incident is already a political issue before an expected late-October Israeli election. Supporters of Netanyahu frame it as vindicating security warnings; opponents accuse the government of exploiting it and cite earlier security failures. Polling descriptions place his bloc slightly higher but still short of a majority in the 120-seat Knesset, without enough numerical detail to isolate an incident-specific change. No demonstrated electoral effect is established, and no specific intelligence warning of an event like this has been identified in his public account.
  27. A conditional threat to hit Iran “very hard” now hangs over an investigation that has not established an Iranian connection. The suggestion of involvement remains unsubstantiated; no supporting details establish a link. A separate preliminary assessment places Iranian involvement and outside connections in the too-early-to-determine category. Preparations to send another 9,000 U.S. troops to the Middle East add a military backdrop, not evidence about this assault.
  28. The answer to the central question is therefore narrower than the retaliation rhetoric: investigators have preliminarily identified an assault by the co-pilot, both injured pilots have moved to the UAE, the captain is recovering, and the passengers completed their onward journey. The exact cockpit sequence, final intent and motive remain unresolved. No investigating-authority finding established through October 2 connects Iran to the attack.

Źródła86

Spośród cytowanych źródeł CBC News opublikował jako pierwszy, 2 dni przed emisją tej relacji. Potem opublikowało 70 kolejnych mediów.
  1. CBC News
  2. CNN
  3. RTÉ News
  4. The Hill
  5. The Telegraph
  6. The Arabian Stories News
  7. The Sydney Morning Herald
  8. The National
  9. +63 kolejne media
  10. HeyDay News

15 mediów bez daty:AnadoluIsrael National Newstimesofisrael.comalarabiya.netndtv.comahram.org.eg

Rozwijający się temat · relacja 2 z 3

Wszystkie źródła według medium

185 źródeł z 86 redakcji· Najczęściej cytowane najpierw

Ostatnio na antenie