A Flydubai cockpit attack raises questions about foreign crew vetting, uneven security rules, and who pays for Israel’s aviation protection.
An attempted hijacking on a Flydubai flight has sharpened a question that Israel’s aviation system handles differently for domestic and foreign carriers: who is responsible for security when the passengers are Israeli, but the airline is not? The pilot was an Omani national, who was barred under Israeli regulations from flying to Israel because Israel has no diplomatic relations with Oman. The incident is under investigation; the article says dozens of Omani pilots may have flown to Israel for Emirati airlines using dual passports. That possibility is not a confirmed finding. Read the account of the incident and security arrangements.

Israeli airlines operate within a purpose-built security structure. The Ofek unit is responsible for passenger screening and aircraft security on the ground and in flight, under Shin Bet authority and supervision, with operational and logistical management handled through El Al. It also works with local security agencies in countries where Israeli airlines operate. The details of procedures and deployments are not public. That secrecy is understandable in a security system, but it also makes it harder for passengers to compare protections across carriers.
The distinction matters because a passenger’s nationality does not determine which airline’s security framework governs a flight. The article says Flydubai and Etihad continued operating between the UAE and Israel while Israeli airlines were barred from Dubai following a dispute. The Shin Bet had raised concerns about procedures at Dubai airport. That creates a practical gap: Israeli passengers could travel on a foreign carrier subject to a different set of rules. For a related question about how foreign pilots are vetted, see this report on independent vetting.
The incident may help break the deadlock over Israeli airlines returning to Dubai, potentially under stricter security protocols. But reopening a route is not, by itself, evidence that the underlying concern has been resolved. Another relevant follow-up is reporting on whether aviation procedures changed after the attempt. We should separate a diplomatic or commercial breakthrough from an operational one: the first changes who can fly a route; the second concerns how risks are assessed and handled.
There is also a funding question. The state covered 97.5% of Israeli aviation security costs in 2024; its share fell to 95% in 2025 and is 94% in 2026, with a planned decline to 92.5% by 2029. The budget framework allocates about NIS 8 billion in state participation from 2025 through 2031, but that covers security for Israeli airlines as a whole, not just Ofek. Meanwhile, the four airlines’ combined security spending is estimated at NIS 66 million in 2026. Those figures describe different things, not competing estimates of one bill.
We have seen how easily “the safest airline” becomes shorthand for a system whose protections are difficult to inspect from the outside. This episode makes the useful question more precise: which authority checks the crew, which agency oversees the airport environment, and who is accountable when those layers meet? Until the investigation answers more of that, I would treat the attempted return to Dubai as a possible policy adjustment—not proof that the security gap has closed.
Further reading: Ctech Testimonials.
Timeline
- Calcalistech reports that, following an attempted hijacking, Israel has not changed any of its aviation security procedures. The article was published on October 4, 2026. calcalistech.com
- Flydubai Incident Highlights Uneven Aviation Security Rules
Original sources: calcalistech.com · calcalistech.com
Produced with AI support and reviewed by the newsroom



Comentarios
Publicar un comentario