Israel Received Pilot's Data Before Dubai Flight Incident
Translated & summarized from Bizportal by baba
The story in 5 lines · by baba
- Israel possessed data on the Flydubai co-pilot before the incident.
- A security division failed to utilize crew data for two years.
- Existing laws require airlines to submit crew data for screening.
- The incident highlights a shift in aviation security focus to pilots.
- Authorities are re-evaluating crew screening protocols.
An investigation into a Flydubai flight incident, initially seen as a potential airline malfunction, is now revealing systemic failures within Israel's own security apparatus. The co-pilot, Haitham Al-Hajjam, an Omani national suspected of attempting to crash the plane, had his details known to Israeli authorities before the flight departed Dubai. The information, including his identification, nationality, and travel documents, was provided by the airline to Israel's National Passenger Data Analysis Center (MALAN), which operates under the Tax Authority. However, the fact that Al-Hajjam held Omani citizenship only became a focus after the attempted attack.
Israel has a law from 2023 requiring airlines to submit crew data, including nationality and passport information, to MALAN for security screening, aimed at preventing terrorism and serious crime. Various Israeli security agencies are authorized to access this data. Despite this legal framework, a significant gap has emerged between the collection of this data and its actual utilization. Senior officials involved in the investigation claim that for approximately two years, the Ministry of Transport's security division has rarely accessed MALAN's database for foreign flight crew information, even though this division is responsible for security assessments of foreign flights arriving in Israel.
The Ministry of Transport counters that its role is primarily security and regulation, with broader intelligence capabilities residing with other agencies, leading to a complex division of responsibilities. This situation is particularly concerning given Al-Hajjam's background. Omani authorities had previously identified concerns about his ideological extremism and restricted his flight activities. He later moved to the UAE, joined Flydubai, and passed standard checks, working on the route to Israel for about eight months.
The incident has shifted the focus of aviation security from passengers to the pilots themselves, highlighting the potential for a pilot to weaponize the aircraft. The investigation is now considering how to transform crew lists from mere data files into active screening mechanisms. Potential solutions include automated alerts for crew members with passports from security-sensitive countries or requiring airlines to submit lists further in advance to allow for cross-referencing with security services and former employers.
Israel is also expanding its investigation to determine if other crew members with nationalities from countries like Iran, Syria, or Iraq have entered the country, or if individuals held undisclosed secondary citizenships. The immediate aftermath saw a halt in Flydubai's operations to Israel and Emirates suspending connecting flights that involved Flydubai. Authorities now face the challenge of defining what constitutes a security alert, who receives it, and who has the authority to prevent a crew member from boarding, especially when crucial information was available but remained unutilized.
Read the original at BizportalMentioned
