Who Investigates Flydubai Flight FZ1073?

Flydubai flight FZ1073 diverted to Tabuk, Saudi Arabia, after a cockpit incident on September 30. That much is confirmed by the airline and the UAE’s General Civil Aviation Authority: the aircraft landed safely, crew members were injured, and a security incident was brought under control. Reuters and Israeli officials have reported far more serious allegations—that the first officer stabbed the captain and tried to crash the aircraft. Flydubai has said the underlying reasons remain unknown. That distinction matters.

The immediate public question is terrorism, sabotage or motive. The first aviation-safety question is more prosaic and more consequential: where, precisely, did the serious incident occur? Under ICAO Annex 13, that is the starting point for deciding who conducts the safety investigation.

What is confirmed versus alleged

Confirmed public statements establish a Dubai-to-Tel Aviv Flydubai service, a diversion and a safe landing at Tabuk with injured crew. Flight-tracking data reported by Reuters shows an abrupt descent and emergency transponder codes, including a code associated with unlawful interference. Those facts justify a serious investigation; they do not establish motive, criminal intent, a specific weapon, or a final account of cockpit actions.

The assertion that one pilot attempted to crash the aircraft comes from Israeli officials and accounts relayed to Reuters, not from a completed safety finding. A state criminal inquiry may ultimately test those claims. An Annex 13 safety inquiry has a narrower task: reconstruct what happened and identify measures that prevent recurrence. It does not assign blame or liability.

Where did the incident legally occur?

“State of Occurrence” is not shorthand for the country where the aircraft stopped. Annex 13 defines it as the state in whose territory an accident or incident occurs. The decisive evidence is likely to be the flight-data recorder, cockpit-voice recorder, air-traffic-control recordings, surveillance data and the aircraft’s timestamps—not the airport that received the emergency.

That means Tabuk is important without settling the issue. Public accounts place key moments variously over Saudi Arabia and near or over Jordanian airspace. If the qualifying event occurred in Saudi territory, Saudi Arabia is the presumptive State of Occurrence. If the operative event occurred over Jordan, Jordan has that role. If the evidence shows a continuous event across borders, the states will need to establish the factual sequence and agree practical arrangements. The landing state has custody, police and medical responsibilities either way; it does not acquire the Annex 13 lead merely by hosting the diversion.

The first jurisdictional fact is the aircraft’s position when the serious incident occurred, not where it ended.

Which country leads the safety investigation?

For a serious incident involving an aircraft above 2,250 kilograms, Annex 13 says the State of Occurrence must institute an investigation. It may delegate the work to another state or a regional accident-investigation organization. The independent safety authority leading that work can invite accredited representatives from the states of registry, operator, design and manufacture.

The aircraft’s registration must be confirmed from the official record, but Flydubai is a UAE operator and its Boeing 737 is expected to be UAE-registered. On that basis, the UAE would have substantial participation rights as State of Registry and State of the Operator even if Saudi Arabia or Jordan leads. The United States is ordinarily entitled to participate as State of Design and Manufacture for a Boeing-built aircraft. Those roles supply technical access and expertise; they do not displace the State of Occurrence’s initial responsibility.

This is why the incident is more than a dramatic diversion. Aviation disruptions become geopolitical systems when authorities control evidence and access. The custody chain for recorders, avionics data and cockpit access will shape what each investigation can independently verify.

Safety investigation versus terrorism or criminal investigation

Saudi authorities may investigate an alleged assault, unlawful interference or other offences because the aircraft and suspect arrived in their territory. The UAE and Israel can pursue their own security, regulatory or criminal interests within their legal authority. None of that makes a criminal inquiry a substitute for the safety inquiry.

Annex 13 expressly treats safety investigation as prevention, not fault-finding. In March, ICAO adopted Amendment 20 after concern that suspected unlawful interference could halt or compromise a safety investigation. The amendment strengthens expectations of independence and completion, but it is not applicable until November 23, 2028. It is therefore a policy signal, not the governing rule for FZ1073 today.

The existing Annex 13 framework anticipates coordination: states can make protocols covering evidence preservation, access and conflict resolution. The credible outcome is parallel work—a Saudi criminal/security file, potentially other national inquiries, and one independent safety inquiry sharing factual material under controlled rules.

Saudi Arabia, UAE, Israel and the United States have different lanes

Saudi Arabia is the landing state and may be the State of Occurrence; it controls immediate access to the aircraft, physical evidence, the alleged suspect and local witnesses. The UAE is central as Flydubai’s operator state and likely registry state, and its GCAA has already said it is investigating the security incident. Israel is the destination state and home to many passengers, but Annex 13 does not automatically grant it a lead role on that basis. It can provide information, security evidence or experts, which can support participation.

The United States has a technical rather than political role if Boeing is confirmed as the manufacturer: accredited representatives can examine design, production, maintenance and operational issues relevant to the 737. The 2026 amendment’s emphasis on delegation and observers is a reminder that legitimacy comes from transparent evidence access, not from the loudest government statement.

When a preliminary report should appear

Annex 13 recommends that investigations attracting heightened public attention publish a factual Preliminary Report within 30 days. It is a recommendation, not a promise that a public document will appear exactly on schedule. The report should contain established facts and progress, not a conclusion on motive.

For FZ1073, the useful first document would identify the lead authority, the aircraft’s verified route and timing, the recorders’ status, the custody arrangements and whether the occurrence is classified as a serious incident. If that material is absent after 30 days, it would not prove concealment. It would, however, leave the jurisdictional gap unfilled.

What evidence investigators will seek next

Investigators will correlate flight-data and cockpit-voice recordings with ATC audio, transponder data, radar tracks, maintenance records, crew schedules and medical evidence. They will examine cockpit-door operation, control inputs, autopilot and flight-control status, communications, passenger and crew statements, and any security screening or access history. The sequence matters: which inputs were made, when access was gained, and where the aircraft was at each moment.

The public should resist treating a preliminary reconstruction as a verdict. The durable question is not which country tells the most compelling story first. It is whether the states preserve the record, separate safety prevention from prosecution, and let the verified place of occurrence determine who writes the first authoritative account.