Three days of developments bring injuries, flight suspensions, a UAE investigation and fresh findings.
What initially emerged as reports of an unexplained altercation inside the cockpit of flydubai flight FZ1073 has since developed into a major security investigation, with UAE prosecutors saying the co-pilot attempted to carry out a terrorist act.
The Israel-bound flight departed Dubai on September 30 but was diverted to Tabuk in Saudi Arabia after the aircraft experienced sudden changes in altitude, transmitted emergency transponder signals and issued a distress call.
Over the following days, authorities gradually disclosed further details about the events inside the cockpit, the injuries sustained by those involved and the investigation launched into the incident.
Here is what is known so far.
What happened to flight FZ1073?
Flight-tracking data provides a timeline of the aircraft’s movements during the emergency, although the data alone does not indicate what was taking place inside the cockpit.
- 7.05am UAE time — Departure from DubaiFlight FZ1073 departs Dubai International Airport for Ben Gurion International Airport in Tel Aviv.According to Flightradar24 data, the aircraft climbs to an altitude of approximately 34,000 feet.
- 9.21am — Sudden descentThe aircraft begins a significant descent before climbing sharply and then descending steeply again.By around 9.33am, the aircraft is flying at approximately 15,000 feet.
- 9.28am — Emergency code transmittedWhile flying near the Saudi-Jordanian border, the aircraft transmits transponder code 7700, the internationally recognised code for a general emergency.
- 9.35am — Unlawful interference codeThe transponder changes to 7500, the international code used to indicate unlawful interference.The aircraft then turns west, briefly enters Jordanian airspace and subsequently turns back towards Saudi Arabia.As FZ1073 approaches Tabuk, its transponder switches back to emergency code 7700.
- 9.44am — Distress call receivedAir traffic controllers in Tabuk receive a distress call from FZ1073 requesting an emergency landing.The call is received at 8.44am Saudi time.
- 10.45am UAE time — Emergency landingFZ1073 lands safely at Prince Sultan bin Abdulaziz International Airport in Tabuk at 9.45am Saudi time.Tabuk airport later said the captain and first officer had sustained injuries and were taken to hospital for medical treatment.
- 10.58am — Flight tracking endsFlightradar24 receives the final tracking signal from the aircraft at Tabuk airport.
- 6.40pm UAE time — Passengers leave TabukAll passengers later depart Tabuk on an alternative aircraft provided by flydubai, according to a statement from the airport.The departure takes place at 5.40pm Saudi time.
How the story developed
September 30
flydubai confirms flight-deck altercation
The first significant official account came from flydubai, which confirmed that an “altercation occurred in the flight deck” of FZ1073 while the aircraft was operating from Dubai International Airport to Ben Gurion International Airport.
The airline said flydubai crew members travelling on the flight intervened to secure the aircraft, which was then diverted and landed safely in Tabuk.
At the time, flydubai said the reasons and motives behind the incident remained unknown and urged the public to avoid speculation while authorities carried out their investigation.
Later that day, the UAE’s General Civil Aviation Authority (GCAA) described the event as a “security incident” and confirmed that crew members had sustained injuries.
The GCAA said its investigation teams were examining both the operational and security aspects of the incident.
The event also disrupted air connections between the UAE and Israel.
Emirates suspended its codeshare operations with flydubai on services to and from Tel Aviv with immediate effect and until further notice.
flydubai also suspended flights to and from Israel while authorities investigated the incident, saying the decision would remain under review.
October 1
Captain identified as UAE launches judicial investigation
The injured captain was identified as Captain Smit Machchhar, an Indian national and Dubai-based flydubai pilot.
As more information about the events on board emerged, attention increasingly turned to Machchhar’s actions during the emergency.
The case also entered a formal judicial phase after UAE authorities announced a separate investigation into the incident.
Attorney-General Counsellor Dr Hamad Al Shamsi ordered the formation of a specialised Public Prosecution team to investigate the circumstances surrounding the incident and determine its causes.
UAE authorities said the country had jurisdiction over the case because the aircraft is registered in the UAE and operates under the UAE flag.
The judicial investigation was being conducted separately from the aviation and operational inquiries previously announced by the GCAA and the relevant Saudi authorities.
October 2
Saudi Arabia releases its account of the incident
Saudi Arabia’s Ministry of Interior provided further official details about the emergency landing and the authorities’ response.
According to Saudi authorities, preliminary investigations found that the first officer had assaulted the captain, leaving both pilots injured.
The aircraft was granted permission to make an emergency landing in Tabuk, where the captain and first officer were taken to hospital for treatment.
Passengers later continued their journey on an alternative aircraft provided by the airline.
Both pilots remained in hospital until they were medically cleared to leave Saudi Arabia for Abu Dhabi on October 1.
Captain speaks publicly
Indian Prime Minister Narendra Modi spoke directly with Machchhar following the incident and praised the pilot’s actions during the emergency.
Machchhar also gave his first public account of the incident, explaining why he continued to act despite suffering injuries during the confrontation.
“I was doing this for my life, but at the same time, I knew that I couldn’t let everybody else die,” he said.
The captain also emphasised that others on board played a crucial role in helping bring the situation under control.
Recognition for Machchhar, the crew and passengers continued to grow throughout the day.
Dr Anwar Gargash, Diplomatic Adviser to the UAE President, praised Machchhar for the courage and sense of responsibility he displayed during the incident.
flydubai CEO Ghaith Al Ghaith also expressed his appreciation to the captain, other pilots, cabin crew and passengers for their actions during the emergency.
The GCAA similarly commended Machchhar, the crew and passengers, saying their swift response helped contain the situation and prevent more serious consequences.
October 3
UAE says co-pilot attempted ‘terrorist act’
The investigation took a significant turn on October 3 when the UAE Attorney-General announced that investigators had established that the co-pilot attempted to carry out a terrorist act.
Counsellor Dr Hamad Saif Al Shamsi said the co-pilot assaulted the captain inside the cockpit with a crash axe and attempted to take control of the aircraft’s flight controls.
The Attorney-General said investigators were continuing their work to determine the full circumstances surrounding the incident, including the motive and whether there were any associated links.
Authorities were also conducting technical examinations and analysing physical and digital evidence as part of the investigation.
The final findings will be released through official channels once all required investigative procedures have been completed.
Captain ‘recovering well’
Meanwhile, the Indian Embassy in the UAE said Machchhar was “recovering well” while receiving medical treatment.
The embassy said it remained in contact with the captain’s family and UAE authorities, while expressing its appreciation for the support and medical care provided to him.
Indian Ambassador to the UAE Dr Deepak Mittal also visited Machchhar and his family at the hospital following the captain’s transfer to the UAE.
The investigation remains ongoing, with further official findings expected to be announced once the relevant procedures have been completed.
