Flydubai Incident Raises Questions About Israeli Aviation Security System

Following an incident aboard a Flydubai flight to Israel, where the co-pilot, an Omani citizen, allegedly attempted to seize control of the aircraft, a review of Israel's aviation security protocols has been initiated. The core issue revolves around how the co-pilot, whose nationality should have been flagged in advance, was allowed to fly to Israel. Israeli regulations require foreign airlines to submit passenger and crew data, including identification and citizenship, to the National Passenger Data Analysis Center (MPDA) within the Tax Authority before a flight's arrival. This data is accessible to various government bodies, including the Ministry of Transport, Shin Bet, Mossad, and police, raising questions about where the system failed to detect the potential threat.

The Ministry of Transport stated it is not responsible for intelligence vetting of foreign pilots and lacks the capabilities of intelligence agencies, though its security division does assess foreign flights. An operational aviation security center within the ministry also coordinates flight arrivals. Initially, there was speculation the pilot might hold dual citizenship, which could explain the lack of flags, but this theory has reportedly not been confirmed. Investigators are now examining the entire data chain, from Flydubai's submission to the processing and vetting by Israeli agencies, to determine if there was a breakdown in transmission, processing, verification, or inter-agency cooperation.

Concerns have also been raised within the Knesset, with lawmakers demanding an urgent meeting of the Foreign Affairs and Defense Committee, including the head of the Shin Bet. This demand stems partly from reports of potential prior warnings regarding security issues on flights from the UAE and seeks to scrutinize the entire aviation security system and the actions of state bodies. The Flydubai plane ultimately made an emergency landing in Saudi Arabia. The incident is now being viewed not just as an isolated event but as a potential systemic failure in pre-flight threat detection.