Flydubai flight FZ1073 was travelling from Dubai to Tel Aviv on September 30, 2026, when a serious incident inside the cockpit forced the aircraft to divert to Saudi Arabia. The Boeing 737 MAX 8 eventually landed safely at Tabuk, but the flight’s unusual movements and emergency signals raised questions about how air traffic controllers were alerted.
The Indian captain, Smit Machchhar, was reportedly injured during an altercation in the cockpit. While the full sequence of events remains under investigation, flight-tracking data showed that the aircraft transmitted different emergency transponder codes during the incident. These signals helped communicate the seriousness of the situation to air traffic control. <Cite refs={["turn666599search1","turn666599search2"]}/>
What Is a Squawk Code?
A squawk code is a four-digit number transmitted by an aircraft’s transponder. It allows air traffic controllers to identify and monitor a plane on radar. Certain codes have internationally recognised meanings and can alert controllers when an aircraft faces an emergency.
Two codes became particularly significant during the FZ1073 incident:
- 7700 – General emergency: This code indicates that an aircraft is experiencing an emergency requiring immediate attention.
- 7500 – Unlawful interference: This code is used to signal that an aircraft is facing unlawful interference, including a suspected hijacking situation.
These codes do not explain the exact nature of an incident. Instead, they provide a standardised alert so that air traffic controllers can respond and coordinate assistance. <Cite refs={["turn666599search0","turn666599search2"]}/>
How Did the Signals Help Alert Air Traffic Control?
Flight-tracking records showed that FZ1073 transmitted the general emergency code 7700 before switching to 7500. The aircraft later returned to 7700 as it continued towards an emergency landing.
A report discussing the incident suggested that Captain Machchhar may have changed the transponder settings while dealing with the unfolding cockpit emergency. US Senator and commercial pilot Tim Sheehy also said the captain may have used the code change to alert air traffic control while under attack.
However, publicly available information has not conclusively established who entered each code. The sequence recorded by tracking services confirms the signals, but it cannot independently identify the person who selected them or establish their precise intention. <Cite refs={["turn666599search1","turn666599search0"]}/>
What Happened to the Aircraft?
Flight data showed a dramatic change in altitude after the aircraft had reached cruising height. The plane reportedly descended by around 14,300 feet in approximately 37 seconds, followed by further changes in altitude.
The aircraft later diverted towards Tabuk in northwestern Saudi Arabia, where it made a safe emergency landing. Reports said passengers and crew members intervened during the cockpit incident, while a reserve crew member helped take control of the aircraft.
Authorities in the UAE, Saudi Arabia and Israel are examining the incident. Officials have shared different accounts of what happened, but the investigation is expected to establish the full sequence of events. <Cite refs={["turn666599news6","turn666599search4","turn666599search2"]}/>
Why the Incident Matters
The FZ1073 episode highlights the importance of standard emergency communication in aviation. A short transponder code can alert controllers to a serious situation even when the crew may be unable to provide a detailed explanation over the radio.
At the same time, flight-tracking data should not be treated as a complete account of events inside an aircraft. The signals and flight path offer important clues, but investigators must examine aircraft records, crew accounts and other evidence before reaching conclusions.
For now, the emergency codes transmitted by FZ1073 remain a key part of understanding how the aircraft’s distress was communicated—and how it was ultimately guided to a safe landing.
