Former Oman Air Trainee Later Flew for Flydubai

A Pilot Oman Removed Over Extremism Concerns Was Flying an Israel-Bound Flight a Year Later, Nobody Has Yet Explained the Information Gap Between Those Two Facts

Flydubai Flight FZ1073, carrying more than 170 Israelis from Dubai to Tel Aviv, suffered what Israeli Prime Minister Benjamin Netanyahu called "a highly severe security incident" on September 30, 2026, after a cockpit altercation left the captain stabbed and the aircraft briefly entering a steep dive before passengers and crew subdued the co-pilot and diverted safely to Tabuk Airport in Saudi Arabia. CNN, the Wall Street Journal and Al Arabiya have since reported, citing sources familiar with the matter, that the co-pilot, identified as Omani national Hamam Alhamami, had previously been removed from a co-pilot trainee role at Oman Air in 2024 over concerns about his alleged extremist views, before being hired by Flydubai roughly a year ago. Nobody involved has yet explained how that information gap occurred, or whether it was a gap at all.

What Is Actually Confirmed, and What Remains Sourced to Anonymous Officials

The confirmed, on-record facts are narrower than the headlines surrounding this case. Flydubai's own statement describes an "altercation" in the flight deck of Flight FZ1073. Israeli officials told Reuters the co-pilot is an Omani national who was arrested after the aircraft landed in Saudi Arabia, where authorities are questioning him. Netanyahu, citing a passenger account, said passengers and crew broke into the cockpit after the aircraft "entered a tailspin and began to dive" and found the co-pilot "trying to sabotage the plane's systems." Israel's Transport Ministry confirmed a joint investigation involving the defence establishment is underway, and an Israeli official told CNN that Shin Bet, Mossad, the military and the Transportation Ministry were all separately investigating how an Omani pilot came to be part of the crew on a flight to Tel Aviv at all.

The claim that Alhamami was previously barred from flying in Oman over extremist views, and that he spent considerable time in Syria where he was allegedly exposed to radical ideas, is reported consistently across CNN, the Wall Street Journal and Al Arabiya but every one of those reports attributes the claim to anonymous sources, diplomatic contacts or people "familiar with the matter," not to an on-record statement from Oman Air, Flydubai, or either government. CNN's own reporting states plainly that it had "reached out to Oman Air, Royal Air Maroc and the Dubai government's media office for comment" without confirmation at time of publication. Reuters separately reported there was no evidence at that stage linking the incident to Iran. None of this should be read as establishing a confirmed motive, ideology, or chain of causation, it should be read as exactly what it is: a serious, still-unfolding investigation in which significant elements remain sourced to people speaking anonymously, not to any aviation authority's formal public findings.

Why the Actual Scandal Here May Not Be What Oman Knew, It May Be What Nobody Had to Share

The genuinely important aviation policy question this incident raises is structural, not personal. International commercial aviation has no unified, mandatory global database through which an airline removing a pilot trainee over a security or ideological concern is obligated to flag that removal to other carriers, other countries' civil aviation authorities, or any centralised vetting system a future employer would automatically check. Pilot background screening today typically relies on a patchwork of national regulatory requirements, individual airline due-diligence processes, criminal record checks within specific jurisdictions, and voluntary reference exchanges between employers, not a single, internationally shared security flagging system comparable to, say, international terrorism watchlists that immigration authorities can query.

That gap means a scenario like this one is not necessarily evidence of institutional failure by any single party. Oman Air removing a trainee internally, reportedly reassigning him to another role rather than terminating him outright according to one CNN source, may never have triggered any formal external reporting obligation at all, because no such obligation exists in international aviation regulation the way it might in, say, banking's anti-money-laundering frameworks, where suspicious activity reports flow through mandated international channels. If Oman never formally disclosed the concern to any external body, Flydubai's recruitment team would have had no database to check that would have surfaced it, regardless of how thorough their own internal vetting process was.

Why "He Was Given Another Role" Complicates the Story Further

One of CNN's sourced details, that after being removed from pilot training over extremism concerns, Alhamami "was given another role at the airline" rather than dismissed entirely, is genuinely significant and underreported relative to the more dramatic "barred from flying" framing dominating most headlines. If accurate, it suggests Oman Air's own internal response to the concern fell short of treating it as disqualifying for all aviation-adjacent employment, which in turn makes it considerably less surprising, though no less consequential, that the concern did not travel with him as a permanent, career-ending mark when he later sought pilot employment elsewhere. An airline that itself continued employing someone in a different capacity after flagging a concern about them is a different, more ambiguous institutional signal than an airline that terminated someone outright and formally barred them from any future role.

Why Israel's Own Security Apparatus Investigating "How He Came to Be Part of the Crew" Is the Most Revealing Detail

The fact that Shin Bet, Mossad, Israel's military and its Transportation Ministry are all separately examining how an Omani national ended up crewing a flight into Tel Aviv, a country Oman does not formally recognise diplomatically, points to a security vetting question that exists independent of whatever Oman Air's internal 2024 personnel decision actually involved. Israel's own aviation security framework, widely regarded as among the most stringent in the world for flights into Ben Gurion Airport, evidently did not independently flag or block this specific crew assignment either, despite the diplomatic sensitivity inherent in an Omani national, a citizen of a country with no formal relations with Israel, operating a flight deck position on a route into Tel Aviv. That gap, sitting alongside whatever happened or did not happen between Oman Air and Flydubai's own hiring process, suggests multiple layers of the international aviation security system that one might assume would have surfaced a flag of this kind each had no actual mechanism positioned to catch it.

What Flydubai Has and Has Not Said

Flydubai's public statements throughout this episode have been carefully limited to confirming the operational facts of the incident itself, the flight number, the route, the diversion to Saudi Arabia, and the characterisation of events as an "altercation" in the flight deck, a word choice that drew its own separate controversy after the New York Times used similar language and faced backlash from readers who felt it understated the severity of an alleged stabbing and attempted crash. The airline has not, in any reporting reviewed, commented specifically on Alhamami's prior employment history, what background checks were conducted during his recruitment, or whether any information about his Oman Air departure was known to Flydubai's hiring team at the time. That silence should not be read as an admission of wrongdoing, there is currently no public evidence establishing that Flydubai knew about, or should reasonably have discovered, the concerns Oman Air reportedly held. It should be read as exactly what it is: an airline that has not yet addressed the central question this entire story raises, likely because the UAE-led investigation into the incident itself has not yet concluded.