The aircraft, a flydubai 737‑800, was en route from Dubai to Tel Aviv when the co‑pilot, Omani national Hamam al‑Hammami, swung a crash‑axe at captain Smit Machchhar, forcing the pilot to wrestle control from the assailant. Passengers and crew rushed in, subdued the co‑pilot, and the plane made a safe emergency landing at Tabuk, Saudi Arabia, where both pilots received medical attention.
NewPARA Al‑Hammami had been suspended by Oman Air in 2024 after intelligence units found extremist material in his possession. He joined flydubai nine months earlier, with no red flag flagged by Dubai’s civil aviation authority. The attack has been labelled a terrorist act by UAE Attorney‑General Hamad Saif Al Shamsi, and the incident has sparked a review of inter‑regional pilot vetting procedures.
NewPARA Sanjay Lazar, citing the incident, called for a centralised, regulator‑to‑regulator alert system that would flag any pilot removed for suspected radicalisation. He blamed “brotherly camaraderie” in the industry for letting the co‑pilot’s background slip through the cracks, urging airlines and national authorities to share licensing data in real time.
NewPARA Israel’s Transport Ministry, which does not run intelligence checks on foreign pilots, has recently upgraded its passenger data protocols to the National Center for Passenger Information Analysis. Lazar noted that the same rigor could be applied to crew, especially on sensitive routes, and that cross‑border licensing gaps must be closed.
NewPARA Flydubai has halted all flights on its Israel corridor, and regulators in the UAE, Oman, and the UK are coordinating to assess whether a unified pilot‑record database is feasible. The next step will be a joint review meeting set for September, where the feasibility of a global alert system will be debated.