Flydubai FZ1073 cockpit attack: attempted takeover and safe diversion to Tabuk

What is established

Flydubai flight FZ1073 departed Dubai for Tel Aviv on 30 September 2026 and diverted to Tabuk, Saudi Arabia, after a violent incident in the flight deck. The airline says on-duty flydubai crew travelling aboard secured the aircraft and landed it safely. Its later statement thanked the captain, the pilots who landed, cabin crew and passengers who assisted. These statements establish a safe diversion, not a completed hijacking.

What investigators say happened

On 3 October, the UAE Attorney-General said the co-pilot attacked the captain with a cockpit crash axe and attempted to take control of the flight controls. The prosecutor described this as an attempted terrorist act. This is the current official investigative account, not a final court finding about motive, planning or responsibility. Saudi authorities had earlier said preliminary inquiries found an assault in which both pilots were injured. The captain and first officer received hospital treatment in Saudi Arabia and travelled to Abu Dhabi on 1 October after medical clearance, according to the Saudi Interior Ministry account reported by Gulf News. Flydubai says the captain returned to the UAE and all aboard were safe.

Flight-track sequence, with its limits

Flightradar24’s published tracking analysis says the flight left Dubai at 03:05 UTC and reached 34,000 feet. Its tracked altitude began a steep descent at about 05:21 UTC and was around 15,000 feet by 05:33 UTC. At 05:28:48 UTC the aircraft transmitted the general-emergency code 7700; at about 05:35 it transmitted 7500, the code for unlawful interference, before returning to 7700. Tracking data show aircraft movement and transmitted codes; they do not by themselves prove what happened inside the cockpit or precisely when an assault occurred. Saudi authorities reported a safe Tabuk landing at 9:45 a.m. local time.

The headcount discrepancy

The airline’s later statement says 172 passengers and crew were on board. Saudi Arabia’s Interior Ministry, as quoted by Gulf News, says 174 passengers plus eight crew, or 182 people. Those totals conflict by ten and the reviewed official statements do not reconcile them. This article does not select one as the verified total. The airline says everyone aboard was safe; the Saudi statement nevertheless reports injuries to both pilots. Safe arrival and injured crew are compatible descriptions.

Response and continuing questions

Saudi authorities cleared the emergency landing, provided care and arranged onward travel. Flydubai provided replacement aircraft and temporarily suspended its Tel Aviv service at the authorities’ request while the official inquiry proceeds. As of the 3 October review, the final investigative findings, any court outcome, full medical updates, reason for the conflicting manifests and the precise cause of any reported aircraft damage were not established in the primary records reviewed. Avoid treating early claims about ideology, security screening or aircraft damage as final findings.

Passenger safety lessons

This event illustrates the importance of trained crew, diversion coordination, emergency communications and post-landing care. It is not a model for passengers to improvise a response to unlawful interference. In an in-flight emergency, follow cabin-crew instructions and avoid spreading unverified claims. If an evacuation is ordered, the FAA’s general passenger guidance says listen to the crew, identify exits and leave bags behind. Those are broad evacuation practices, not claims about what prevented this incident. The Tabuk map shows the diversion airport area, not an in-flight attack location. The cover is AI-generated editorial artwork, not a photograph of FZ1073.