FlyDubai Co-Pilot Identified as Security Risk Prior to Attempted Flight Interference

The co-pilot accused of attempting to crash a FlyDubai flight bound for Israel on Wednesday, 29-year-old Hamam Al Hammami, was previously identified as a security risk and suspended by Oman Air in 2024 after being found in possession of extremist materials. UAE authorities have confirmed Al Hammami assaulted the captain with a crash axe and attempted to seize control of the aircraft, characterizing the incident as a terrorist act. Al Hammami, transferred to the UAE from Saudi Arabia, is reportedly cooperating with investigators and indicated an intent to crash the plane in Israel. Investigations are ongoing to determine how Al Hammami was permitted to fly for FlyDubai despite being flagged as a security risk.

Senior intelligence and law enforcement officials identified Al Hammami as the suspect. While working as a co-pilot trainee for Oman Air, he was found to possess extremist materials but was subsequently allowed to continue in an administrative role, according to sources. The UAE Attorney General Hamad Saif Al Shamsi stated the co-pilot used a crash axe in the assault on the pilot. FlyDubai stated it is fully committed to supporting the ongoing investigation and coordinating with authorities. Representatives for Oman Air and the Omani Embassy did not respond to requests for comment.

Officials are still investigating how Al Hammami was able to fly for FlyDubai and serve as first officer on the flight to Israel. The incident raises questions about screening procedures and security protocols within the airline industry.

Where they differ

• ABC News provided more detail on the investigation, including the suspect’s transfer from Saudi Arabia to the UAE and his reported cooperation with authorities.
• The Washington Times focused on the fact that the co-pilot had been previously flagged as a security risk, emphasizing the unanswered question of how he ended up in the cockpit.

What is not yet known

• The specific extremist materials found in Al Hammami’s possession have not been disclosed.
• The full extent of the security protocols at Oman Air and FlyDubai, and how they failed to prevent Al Hammami from flying, remains under investigation.

Background

• FlyDubai is an airline based in Dubai, UAE, operating flights to Israel among other destinations [Fact Refinery, 2026-09-30].
• On multiple occasions in late September 2026, FlyDubai flights traveling from Dubai to Tel Aviv experienced mid-flight emergencies requiring landings in Saudi Arabia [Fact Refinery, 2026-09-30].
• Prior to this incident, a flydubai co-pilot was identified as an Omani national and was subdued by passengers and crew after attempting to crash a flight to Israel [Fact Refinery, 2026-09-30].
• Saudi Arabia and Israel do not maintain official diplomatic relations, making the landing of an Israeli-bound flight in the country unusual [Fact Refinery, 2026-09-30].

Our reading

Our reading is that this incident represents a serious and potentially deliberate security breach. The fact that the co-pilot was previously identified as a security risk and possessed extremist materials, yet was still permitted to fly, suggests systemic failures in vetting procedures. The characterization of the event as a terrorist act by UAE authorities, coupled with the reported intent to crash the plane in Israel, points to a planned attack rather than a spontaneous altercation.

What to watch

• The findings of the ongoing investigation into how Al Hammami was permitted to fly for FlyDubai despite being flagged as a security risk [article text].
• Disclosure of the specific extremist materials found in Al Hammami’s possession [article text].
• Any response from Oman Air or the Omani Embassy regarding the initial security concerns raised about Al Hammami [article text].

Was this useful? 👍 0 👎 0

---

Read the original coverage