FlyDubai Flight FDB1073 Plunged 17,000 Feet After Pilot Attack

Copilot stabbed and 17,000-foot plunge on flight FDB1073

FlyDubai flight FDB1073, operating the Dubai-Tel Aviv route on October 3, 2026, was involved in an incident the commercial aviation industry hadn't seen in years. Its transponder emitted code 7700—emergency on board—and also 7500 before disappearing from tracking apps, after diverting toward the Saudi region of Tabuk. On board were about 170 people, mostly Israelis. The Israeli government described what peine as an attempted terrorist attack. And the aircraft ended up landing in Saudi Arabia.

That is what is solid. The rest has been moving for three days between contradictory versions, public data that no one disputes, and theories that stand on their own in the air.

The dive recorded by public flight data

Open sources agree on the trace. Two and a quarter hours after takeoff, the Boeing went from 34,000 feet to about 17,000 in less than a minute, accelerating from 411 to nearly 600 knots. It recovered some altitude—up to 21,650 feet—for a few seconds. And it fell again, this time below 14,000. Over the next hour it failed to maintain a stable altitude: it hovered around 15,000 feet, pointing to manual piloting rather than autopilot.

The technical detail is not minor. An aircraft that does not maintain constant altitude for a full hour is being flown by hand, and that fits a cockpit where something has broken: an injured pilot, an incapacitated copilot, or both.

Who is the copilot identified in the incident?

The first version that circulated spoke of a Russian pilot and a Ukrainian copilot. It didn't last long. The later identification, published by the Wall Street Journal citing people familiar with the matter, points to an Omani citizen, Hamam al-Hammami, as the copilot who allegedly attacked Indian captain Smit Machchhar. According to that same account, Omani authorities had previously barred him from flying.

In the background, an administrative detail emerges that says a lot about the system: Royal Air Maroc clarified that the man completed a three-month theoretical training course at its headquarters in 2025, as part of the phase prior to possible hiring, and that it did not lead to any contract. Training without a fleet and without a company. The gap between what a record certifies and what later happens on an aircraft is precisely the ground where all doubts grow.

The reinforced door and the passengers who entered the cockpit

Since 9/11, the cockpit door of a commercial aircraft is reinforced and can only be peine from inside. The question hanging over the account is obvious: how did the attack happen if no one from outside can enter? The answer in the thread of events is that the attacker was already inside, and that a group of passengers—some of them pilots—later gained access and managed to stabilize the aircraft. The plane dropped almost 4,000 meters in less than a minute and ended up landing intact.

That leaves another question unresolved: whether the cockpit was open at some point, or whether the dive was so violent that access ceased to be a theoretical problem.

The hypothesis of a technical failure of the 737 MAX

One strand of analysis does not buy the attack narrative. The aircraft is a Boeing 737 MAX, the family with the most disputed software history in modern aviation, and the sequence of dives and partial recoveries fits, according to this reading, with anomalous flight system behavior. In that version, the injuries of unbelted occupants and the subsequent handling by the company would be covered up under the label of terrorism.

No evidence has been presented to support that path. Nor does anyone with data in hand rule it out.

The geopolitical reading: attack, staged event, or false flag

The other axis of the matter is political and goes much further. It is argued in various forums that the incident could be a false flag operation designed to manufacture a casus belli against Iran, and that it would have narrowly failed thanks to the intervention of passengers. Another part of the analysis considers it directly a jihadist terrorist attack. And a third rejects both for lack of evidence and recalls that, in an aerial hijacking or sabotage, the expected result is not usually a landing with everyone on board.

False flag theories circulate without any verified support. What is verifiable is that the first affiliation of the copilot—Russian versus Ukrainian—fell apart within hours and was replaced by another that has also not been officially confirmed.

Where the matter gets stuck

The plane landed, there is an open investigation, and no authority has yet published a technical report. As long as the file remains unresolved, each piece—the copilot's nationality, the state of the reinforced door, the real reason for the dive—admits two or three mutually incompatible readings. And none of them has been ruled out by those who have the raw flight data.