Flydubai attack puts pilot screening under scrutiny across borders

The broadcaster described questions over crew lists and background checks, as agencies examined whether pilots with dual nationality had previously landed in Israel.

The investigation into an attack in a Flydubai cockpit is widening from what happened during the flight to how information about airline crews moves between employers and governments.

On October 3, the United Arab Emirates attorney general said the co-pilot of flight FZ1073 had attempted a terrorist act, attacking the captain with the cockpit's crash axe and trying to take control of the aircraft. The statement, carried by state news agency WAM, said investigators were still examining motives, possible connections and physical and digital evidence.

The flight from Dubai to Tel Aviv was diverted to Tabuk in Saudi Arabia on September 30. UAE officials said crew members traveling aboard intervened and secured the aircraft. An investigation team was formed with the country's General Civil Aviation Authority and other relevant agencies.

The UAE said its judicial authorities had jurisdiction because the aircraft was registered in the country. That provides the legal center of the inquiry even though the emergency unfolded on an international route and the aircraft landed in another state.

In Israel, N12 reported a review of whether foreign pilots with dual nationality had previously landed at Ben Gurion Airport, including people holding Iranian, Syrian or Iraqi citizenship. Nationality is not evidence of wrongdoing. The security question is what screening was required, what information existed and whether responsible authorities received it.

The broadcaster reported differing statements about crew lists: the Tax Authority said it had received one before the flight, while the Transport Ministry's security division denied receiving a list in advance. Because these are different agencies, the statements do not by themselves show which information moved between them.

N12 said the security division relied on checks by foreign airlines and assurances from companies and governments. It also reported that Israeli officials had not yet directly questioned the co-pilot and were receiving information through Saudi Arabia and the UAE.

AP reporting identified the suspect as an Omani national, citing people with knowledge of the case, and said he had previously been barred from flying in Oman over concerns about extremist views. That account depended on unnamed sources. It should not be confused with a published employment record or a final investigative finding.

Taken together, the reports point to two separate investigations: the criminal inquiry into the cockpit attack and scrutiny of the recruitment and information-sharing systems that preceded it. Establishing the first does not automatically prove a failure by every institution involved in the second.

The UAE prosecutor's statement remains preliminary. It establishes the authorities' current characterization of the attack, while leaving its wider connections unresolved. The next substantive answers will come from the evidence about the suspect's actions, his employment checks and any warnings that were—or were not—shared across borders.