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

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}

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}

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}

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}

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}

^{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}