'Hit very hard': Trump ties FlyDubai attacker to Iran
Donald Trump says the Omani co-pilot who tried to bring down a Dubai–Tel Aviv flight may be linked to Iran — and promises Tehran will be hit ‘very hard’ if so. The investigators, and even Netanyahu, are not so sure.
Published 2 October 2026 · 18:00 GMT

Key facts
- Trump said the Omani co-pilot could have links to Iran — “based on what I’m hearing” — and warned Tehran would be hit “very hard” if a link is confirmed. He offered no evidence. Fox News, 1 October 2026
- Flight FZ1073, Dubai–Tel Aviv, 30 September: the co-pilot stabbed Captain Smit Machchhar, the jet shed 14,000 feet in under 30 seconds, and landed at Tabuk at 9:45am. All 182 aboard survived; 166 of the 174 passengers were Israeli. CGTN / Economic Times, 1–2 October 2026
- Machchhar was airlifted from Tabuk to Abu Dhabi for further treatment. India’s embassy says he is “in good health and recovering well”; the ambassador visited him in hospital and met his family. Economic Times (ANI), 2 October 2026
- A colleague told Israel’s Channel 16 the co-pilot, ~8 months at FlyDubai, was a “religious extremist” who “refused to shake hands with women” — a colleague’s claim, not established fact or motive. Hindustan Times / kokthum.com, 1–2 October 2026
- Two Israeli security officials told Reuters that no Iranian connection has been found so far; Netanyahu himself says it is “too early” to link Tehran. The UAE is probing a possible terror link under its own jurisdiction. Shafaq News citing Reuters / CGTN, 2 October 2026
On Thursday the president pointed a finger at Tehran over the FlyDubai cockpit attack — ‘based on what I’m hearing.’ The investigators, the Israelis and the airline all say the same thing: it is too early to know anything. In a seven-month war, that gap is the whole story.
The question was shouted at the edge of a helicopter. On Thursday, as Donald Trump prepared to board Marine One, a Fox News reporter asked whether he had been briefed on a possible Iranian connection to the FlyDubai co-pilot who had tried to bring down a passenger jet. The president did not hesitate, and he did not produce evidence. “We’re working on it right now,” he said. Then, pressed: “I would say the answer, based on what I’m hearing, is yes, but we’re working on it right now.” Asked whether Iran’s Islamic Revolutionary Guard Corps could have placed the man in the cockpit, or radicalised him by some other route, Trump replied: “Could have been, yeah.” And asked what the United States would do if Tehran were found to be behind it, he answered: “Oh, they’ll be hit very hard, don’t worry.” A beat later: “You ask them. They know what happened. They’ll be hit very hard.” Earlier, after speaking with Netanyahu, Trump had offered a different theory of the man: “It seems as though the co-pilot was perhaps a terrorist or perhaps a whack-job.” Notice the machinery of the sentence. Not “intelligence indicates.” Not “a briefing concluded.” Just: what he is hearing. In the same 24 hours, the people actually holding the investigation said something far less useful for a headline. Netanyahu, the most invested man in the region, told Fox News it was “too early” to determine whether Iran was involved — a caution he repeated on the wider question of motive. Two Israeli security officials went further, telling Reuters that Israel had so far found no Iranian connection. FlyDubai itself, which has suspended its flights to and from Israel while its own inquiry runs, has warned against “premature speculation” and says the underlying reasons for the event remain unknown. So the ledger stands like this: a president says yes; his own ally’s security services say not yet; the airline says unknown; and the man at the centre of it all sits in Emirati custody saying nothing in public.
What happened inside that cockpit, on the other hand, is no longer much in doubt, and it is astonishing. On Wednesday 30 September, FlyDubai flight FZ1073 — a Boeing 737 MAX 8 from Dubai to Tel Aviv, carrying 174 passengers, 166 of them Israeli according to media reports cited by CGTN, and eight crew — became the scene of an attempted murder at altitude. An Israeli official told the Associated Press that a fight broke out between the two pilots and that one of them was armed with an axe. The co-pilot, an Omani national, stabbed Captain Smit Machchhar, an Indian veteran with nearly 9,750 flying hours, and fought for control of the aircraft. Flight-tracking data shows the jet shedding nearly 14,000 feet in under thirty seconds. The transponder spoke the language of emergencies twice over: 7700, the general emergency code, then 7500 — unlawful interference. Bleeding, Machchhar did the thing that saved everyone. He opened the cockpit door. Passengers poured onto the flight deck and grappled with the attacker. Dr Shota Musaev, a dentist among the passengers, told the Israeli journalist Ilana Dayan that he tied the co-pilot’s hands with headphones and then turned to treating the pilot; Machchhar’s words to him, with a wife and two children waiting at home, were: “I don’t want to die, I have children.” Another passenger, Asaf Rajuan, described the chaos in a statement shared by Israel’s presidency: “We felt helpless, suspended in midair, and I didn’t know who to turn to. But it was all instinct to survive.” Two off-duty FlyDubai pilots happened to be aboard — four pilots in total, a precaution the airline takes on this route against regional airspace disruptions that can force longer flight times — and they took the controls. Passengers later described a descent so violent it tore the rudder. The jet touched down at Tabuk in northwestern Saudi Arabia at 9:45 in the morning. Everyone — all 182 souls — survived. The captain went to a Tabuk hospital, reported stable. The passengers reached Tel Aviv that evening on a replacement aircraft at 5:40pm; the rest of the crew flew back to Dubai. And on the morning of 1 October, after being cleared by Saudi medical staff, both pilots were taken to Abu Dhabi under the escort of UAE security officials. The captain would go on to hospital care; the co-pilot, to questioning.
A Claim Landing Mid-War
A claim like Trump’s does not land on a calm sea. It lands in the middle of a seven-month war between the United States and Iran — a war in which the same president, days earlier, rejected Tehran’s latest proposal for ending it, and in which Iranian officials said on Wednesday they had received Washington’s official response to that proposal, contents undisclosed. On Thursday, in a Time magazine interview, Trump said he would not accept Iranian proposals he “wouldn’t have approved a year ago” — and left the door open to resuming bombing after the 3 November US election. An American official told the Associated Press that roughly 9,000 troops aboard a group of ships have been dispatched to the Middle East, with as many as three aircraft carriers potentially in the region by late October. Meanwhile mediators, unnamed officials say, are still working both sides toward a deal that would end the fighting and reopen the Strait of Hormuz. Read Trump’s “very hard” warning against that backdrop and its function becomes clear: the FlyDubai allegation is not merely a crime story any more. It is a potential predicate. If an Iranian link hardens into evidence, the White House has already announced the punishment; if it evaporates, a president has still publicly accused a country at the edge of escalation of an attempted mass-casualty terror attack on the basis of what he was hearing. Both outcomes rearrange the war’s information terrain. And this is not the only accusation in the air: on the same Thursday, the British prime minister claimed “strong indications” of Iranian involvement in an alleged plot against a UK airbase, and Iran summoned the British ambassador in Tehran. A pattern is forming in which the allegation itself is the weapon — fired before the investigation can catch up, useful whether or not it ever lands.
A president said “yes” before the investigators could. In a seven-month war, that is the whole story.
How we got here
Strip the politics away and what remains is a man in a cockpit, and a long list of unanswered questions about him. The co-pilot is Omani — holding only Omani citizenship, according to The Jerusalem Post — and had joined FlyDubai about eight months ago. Israeli media have not published his name; Omani authorities have not commented at all. What has surfaced is a portrait painted by a colleague. Speaking anonymously to Israel’s Channel 16, a fellow FlyDubai pilot described the attacker as a “religious extremist” who “prayed excessively throughout the day and refused to shake hands with women,” displaying behaviour his colleague considered out of step with his surroundings at the airline. The same colleague reportedly told Channel 16’s foreign editor Yosef Yisrael that the airline had “betrayed Israel”: “There is no other way to put it, we hired the services of a terrorist and nearly caused the deaths of 180 people.” These are one colleague’s claims, not established facts — and the reports themselves note they do not establish that the man’s religious observance was itself evidence of a motive. There is more, all of it in the same unconfirmed register. An iNews24 correspondent, citing an Emirati source, reported that “Free Palestine” pamphlets and other anti-Israel literature were found among the co-pilot’s belongings, and that the pilot had expressed hostility toward Israel and support for the Palestinians. One Indian outlet reported, in turn, that the co-pilot had talked of killing Jews. Netanyahu, who has the ear of the investigators, told Fox News the attacker had undergone “Islamist radical indoctrination” — and added that once passengers restrained him, the man repeatedly shouted “kill me, kill me” at the crew, which the prime minister read as suicidal intent. Then, in the same interview, Netanyahu refused to close the case: “I don’t make final conclusions yet. But that’s the indications we have now.” Israel’s foreign ministry spokesperson, Michal Maayan, confirmed that investigators are examining ideological motives, possible accomplices, and prior planning or direction — but said the inquiry is “still in the initial stages.” Even Israel’s envoy to the UAE, Yossi Shelley, has urged caution: too early for conclusions. Against that caution stands the political language. Israel’s defence minister, Israel Katz, called the episode “an attempted jihadist terror attack.” The foreign ministry went further, framing it as “an attempted terrorist attack against Israelis, the United Arab Emirates, and the Abraham Accords” — and foreign minister Gideon Saar said he had spoken with his Emirati counterpart Abdullah bin Zayed Al Nahyan and agreed to “collaborate against extremist elements seeking to harm security and undermine stability.” There is also the uncomfortable administrative question of how an Omani national came to be flying an Israel-bound service at all. Oman has no diplomatic ties with Israel, and Omani nationals need a visa to enter the country; Israel’s transportation ministry has told The Jerusalem Post that FlyDubai pilots should be citizens of nations with diplomatic ties to Israel — yet the bilateral aviation agreement between the UAE and Israel does not require it. Netanyahu said the co-pilot had exploited a “loophole.” The UAE, meanwhile, has moved to own the investigation. Its attorney general ordered a probe, and the state news agency announced the judicial authorities are seeking to establish “whether the incident was linked to any terrorist activity or purpose, or involved prior planning or direction” — asserting jurisdiction on the grounds that the aircraft is UAE-registered, flies under the Emirati flag, and that UAE law covers crimes aboard even outside its territory. The attacker is also being investigated in Saudi Arabia, where the plane landed, though Riyadh has issued no statements. Abu Dhabi, not Tabuk, is now where the co-pilot’s answers will be sought.
And then there is the other man in the cockpit — the one whose conduct on 30 September turned a likely mass-casualty event into a story of 182 survivors. Captain Smit Machchhar, 39, never intended to be a pilot at all. The Mumbai Ghatkopar boy from a textile-trading family studied textile engineering to join the family business, then enrolled in a management course at Mumbai’s Welingkar Institute — and there, at an aviation seminar, at the age of nineteen, “the aviation bug really found me.” His mother was frightened; his father, he recalled, was more comfortable with the leap. He trained at Mainland Air in Dunedin, New Zealand — his first trip outside India — took his Boeing 737 rating at the Flight Safety Training Centre in Manesar, and joined SpiceJet in 2011, spending eleven years there and rising to line training captain, the pilots’ pilot, responsible for mentoring younger crews. He moved to FlyDubai as a direct-entry captain in June 2022. His professional profile lists nearly 9,750 flying hours on the 737-800 and the MAX 8 and 9, and his LinkedIn bio reads: “Airline Captain, Lifelong Learner, Father, Helping Others Fly Higher.” His brother is also a FlyDubai pilot. He and his wife Sonal have two children, Ziva, nine, and Krishay, two. A year-old podcast interview, recorded long before Wednesday, now reads like a preview of the crisis: “Delay is not my problem,” he said of his operating philosophy. “As long as you’re walking out of the aircraft is what I want.” And: “When I get out of the cockpit or the aircraft, I don’t want the other guy to know that I’m a pilot… When you wear the uniform, then no nonsense and just do your job, finish the job.” He finished the job on Wednesday — bleeding, with a co-pilot trying to kill him, he got the door open. Since then the machinery of two states has wrapped around him: airlifted from Tabuk to Abu Dhabi for further treatment, where India’s embassy says he is “in good health and recovering well”; the ambassador visited him in hospital and met his family, pledging every possible support. Prime Minister Narendra Modi called him “a HERO” and spoke with the captain’s father, mother and wife. Netanyahu called him “a true hero.” The chief minister of Gujarat, his home state, announced the Visisht Gujarat Garima Award. It is worth pausing on what all this adulation can do: it turns a man who did his job into a symbol, and symbols get spent. The captain’s recovery, mercifully, is reportedly going well. Whether his name is allowed to remain a pilot’s — rather than a flag’s — is the next question.
The 5D read
Geopolitics. The cockpit attack is a fact; its meaning is being manufactured in real time. In the information terrain of a seven-month war, the first actor to fix a motive owns the story, and the White House has just tried to fix it on Tehran before the Emiratis have finished asking questions. Watch what is really being asserted: not evidence, but jurisdiction over the narrative. The UAE’s careful statement — jurisdiction, law, “prior planning or direction” — is a sovereign act by a small state that hosts an American president’s theory about its own airline while Saudi Arabia, Israel and now Washington all circle the evidence. Macroeconomics. Every escalation now runs through oil and the Strait of Hormuz, which mediators are reportedly trying to pry open even as carriers steam toward it. FlyDubai’s suspension of its Israel services is a small commercial casualty with an outsized signal: the Dubai–Tel Aviv corridor was the Abraham Accords made flesh, a six-year experiment in turning diplomacy into departure boards. Every cancelled rotation is the Accords’ economics taking the hit the diplomacy was supposed to absorb. Demographics. One cockpit, three worlds: an Indian captain, an Omani co-pilot, 166 Israeli passengers. Gulf aviation is built on expatriate labour — the region’s carriers could not fly a day without it — which makes crew vetting a demographic and diplomatic problem at once. The coming argument over who may fly where, and under which passport, will be fought in the language of security but decided by the labour map. History. The industry’s deepest fear has always been the trusted insider — the threat no scanner, no reinforced door, no passenger blacklist can reach, because the weapon is a uniform. Post-2001 cockpit doors were engineered to keep intruders out; they also keep everyone else out, which is exactly what a rogue pilot wants. The procedural answer — two people in the cockpit at all times, reinforced after the last European catastrophe — only works if it is followed, and on a routine regional hop, routine is the enemy. Structure. The loophole Netanyahu named is structural, not personal: security architecture assumes the state that certifies the crew and the state that receives the flight share a definition of trust. The UAE–Israel aviation agreement does not encode one. Until it does, every Gulf carrier flying to Tel Aviv is operating on political goodwill dressed up as a security regime — and goodwill, as Wednesday showed, does not open locked doors.
What to watch
The investigation is the hinge on which everything now swings. In Abu Dhabi, the co-pilot will be questioned under Emirati jurisdiction, and the three questions Israel’s foreign ministry laid out — ideological motive, accomplices, prior planning or direction — are the ones that decide whether this was a disturbed individual, an organised plot, or the Iranian-directed operation the American president is already describing. Netanyahu has said Israel will follow the inquiry and may participate in it; what investigators say next will be measured against what Trump has already said. Second: watch whether the White House produces anything firmer than “what I’m hearing.” The two Israeli security officials who told Reuters no Iranian connection has been found so far are the only people on the record with access to actual evidence, and they point the other way. Third: the man himself. The co-pilot’s legal fate — charges, custody, a trial under Emirati law — will be watched across the Gulf as a test of whether the UAE can run a politically radioactive prosecution while two larger powers narrate it over its head. Fourth: the route. FlyDubai’s suspension of Israel services cannot last forever without becoming a verdict on the Abraham Accords themselves; its resumption, and under what new vetting rules, will tell you how much Wednesday really changed. Fifth: the carriers. Three American carrier groups in the region by late October is a deployment looking for a mission, and “hit very hard” is a promise looking for a trigger. The FlyDubai claim could be that trigger — or, if the investigators find nothing, it could become one more allegation that did its work and dissolved. Either way, Captain Machchhar — recovering, by all accounts, in an Abu Dhabi hospital — has already done the only thing in this whole affair that is beyond dispute: he opened a door.
From the Western vantage, the FlyDubai affair is first a security failure and only second a geopolitical one. An airline put a man of eight months’ standing, reportedly flagged by colleagues for behaviour they found extreme, into the right-hand seat of a flight to Tel Aviv — a route every intelligence service on earth would classify as sensitive. That a president then reaches for Iran on “what I’m hearing” is treated in this reading not as strength but as the familiar pathology: attribution racing ahead of evidence, the way it did in the run-ups to older wars. The proper response, Western editorialists will insist, is the investigation — motive, accomplices, planning, direction — before the cruise missiles.
At the same time, the Western lens carries genuine solidarity with the victims’ side of the story. A plane full of Israelis nearly fell out of the sky; Israel’s defence minister calls it an attempted jihadist attack, and the restraint of Netanyahu — “too early” — is read here as statesmanship, not weakness. FlyDubai’s suspension of Israel flights, the Abraham Accords framing, the Saar–Abdullah call: all of it reads as a civilised world closing ranks around a shared security architecture. The uncomfortable question this lens tends to underplay is whether Washington’s own “very hard” rhetoric is part of the threat to that architecture, or its defence.
The Eastern reading starts from a different file entirely: the seven-month American war on Iran. Trump rejected Tehran’s proposal days ago, told Time he will not accept terms he “wouldn’t have approved a year ago,” and is moving carriers into position while openly discussing resumed bombing after the November election. In this light, the FlyDubai allegation looks less like intelligence than like stagecraft — a pretext being assembled in public, “what I’m hearing” as a substitute for a dossier. Beijing and Moscow have watched this film before, this lens argues, and they note the tell: the accusation arrives before the evidence, the punishment is announced before the verdict.
None of which, in the Eastern account, proves Iran’s innocence — it proves the poverty of the process. The honest version of this lens takes Tehran’s position at face value only insofar as it mirrors its own complaint: that Muslim-majority publics are being primed to see a “religious extremist” as proof of a state-directed plot, collapsing the distance between one troubled Omani pilot and a government of ninety million people. If the investigation finds a real chain of command, say the Eastern commentators, publish it; if it does not, the “very hard” threat will stand exposed as what it currently is — coercion wearing the uniform of counter-terrorism.
The Global South lens reads this story through the people who actually flew the plane. Captain Smit Machchhar is a national hero in India tonight — praised by Modi, decorated by Gujarat, his family visited by an ambassador — and New Delhi’s interest is concrete: millions of its citizens crew the Gulf’s aircraft, hospitals and construction sites, and an Indian captain bleeding in a cockpit is a domestic story before it is a geopolitical one. The South’s question is practical, not ideological: who protects the workers who keep other people’s airlines flying, and what does consular muscle look like when the cockpit becomes a crime scene?
From the Gulf itself, the lens is sovereignty. The UAE has asserted, carefully and publicly, that this is its investigation — its aircraft, its flag, its law — even as Washington narrates it and Jerusalem watches it. That is a small state refusing to become scenery in someone else’s war. And the South notices what the North skips: that the co-pilot is Omani, that Oman has said nothing, that an entire region’s aviation economy — its crews, its routes, its fragile normalisation with Israel — now hangs on what a few interrogators in Abu Dhabi can establish. Evidence, not rhetoric, is the South’s demand — because the South is where the next war’s first casualties always live.
The consensus
- What we agree on
- What we agree on: on 30 September 2026, the co-pilot of FlyDubai flight FZ1073 from Dubai to Tel Aviv stabbed Captain Smit Machchhar in the cockpit, the aircraft plunged nearly 14,000 feet in under thirty seconds, and all 182 people aboard survived after an emergency landing at Tabuk.
- What we don't agree on
- What we don’t agree on: whether the attack was terrorism, an organised plot, or the act of a disturbed individual — Israel’s defence minister says jihadist terror, Netanyahu and the airline say it is too early, and Trump has named Iran without evidence.
- What we know
- What we know: the co-pilot is an Omani national who joined FlyDubai about eight months ago; Captain Machchhar opened the cockpit door while injured, enabling passengers and crew to subdue the attacker; both pilots are now in Abu Dhabi, one for treatment, one for questioning.
- What we don't know yet
- What we don’t know yet: the motive, whether anyone directed, assisted or radicalised the co-pilot, whether any link to Iran or the IRGC exists, and why a man described by a colleague as a “religious extremist” was cleared to fly an Israel-bound service.
- What we expect
- What we expect: the Emirati-led investigation in Abu Dhabi to be the arbiter of the facts; FlyDubai’s Israel suspension to hold until it concludes; and Washington’s “hit very hard” warning to hover over — or harden into — the seven-month war’s next phase.
Sources
- Fox News, 1 October 2026
- CGTN / Economic Times, 1–2 October 2026
- Economic Times (ANI), 2 October 2026
- Hindustan Times / kokthum.com, 1–2 October 2026
- Shafaq News citing Reuters / CGTN, 2 October 2026