FZ1073: What really happened on the flydubai Dubai–Tel Aviv Flight

By Francesco Jerace
Oct 5 2026

FZ1073 flydubai Dubai–Tel Aviv Flight

FZ1073: What really happened on the flydubai Dubai–Tel Aviv Flight

An attack inside the cockpit, a descent of more than 16,000 feet, and four pilots on board.

On September 30, 2026, flight FZ1073, operated by flydubai on the Dubai–Tel Aviv route, was involved in one of the most unusual and delicate incidents ever to occur aboard a modern airliner. According to findings made public by the authorities of the United Arab Emirates, the co-pilot allegedly attacked the captain inside the cockpit using the aircraft’s emergency axe and attempted to take control of the aircraft.

The Boeing 737-8 MAX, registration A6-FKF, departed Dubai at 03:05 UTC and reached a cruising altitude of approximately 34,000 feet. A little more than two hours later, while flying through Saudi Arabian airspace, the flight experienced abrupt changes in heading and altitude. During the most critical phase, the aircraft lost more than 16,000 feet in just over 30 seconds before recovering and stabilizing. The flight was subsequently diverted to Tabuk, Saudi Arabia, where it landed safely at 09:45 local time. (Reuters)

According to Saudi authorities, there were 174 passengers and eight crew members on board. However, a discrepancy in the numbers reported during the first few days should immediately be noted. Other communications, including a subsequent flydubai statement reported by Flightradar24, gave a total of 172 people. It is therefore not prudent to treat any one of the figures circulating publicly as definitive until the final official manifest is available. This discrepancy does not alter the essential fact that everyone on board survived. (Okaz)

Security incident

This was therefore not an ordinary aircraft accident in the traditional sense. Based on the information currently available, there was no loss of control attributed to a mechanical failure or weather conditions. Instead, the event was treated as a security incident, meaning an occurrence in which the safety of an aircraft was allegedly deliberately compromised by a person on board.

The UAE General Civil Aviation Authority initially described it precisely as a “security incident”, emphasizing that the causes and circumstances were still under investigation. On October 3, however, the UAE Attorney General provided a much more detailed account, stating that the co-pilot allegedly attacked the captain with the emergency axe and attempted to take control of the aircraft. The Emirati judicial authority classified the action as an attempt to commit a terrorist act, while making clear that the investigation into the motive, possible connections and circumstances was still ongoing. (WAM)

This distinction is fundamental. The fact that the UAE Attorney General has classified the incident as an attempted terrorist act is established as a matter of official reporting. It would go beyond the evidence currently available, however, to claim that the motive, any organization involved, or the complete preceding planning are already known.

The Flight Sequence

The most solid reconstruction comes from combining tracking data, official statements and eyewitness accounts. FZ1073 departed Dubai at 03:05 UTC and climbed to approximately 34,000 feet, continuing normally for a significant portion of the route. At around 05:21 UTC, according to data examined by Reuters, the aircraft made a sharp change of heading and began an extremely rapid descent. During the steepest part of the descent, it lost more than 16,000 feet in just over 30 seconds, with Reuters reporting a maximum vertical speed in the order of 544 feet per second, or approximately 166 metres per second. (Reuters)

This was not a normal descent. Airliners can, of course, perform very rapid descents, particularly in response to depressurization or another emergency, but the trajectory recorded for FZ1073 was highly unusual. The flight path is therefore one of the most important objective elements in reconstructing what happened.

Investigation

The transponder subsequently transmitted 7700, the international code associated with a general emergency. It was then set to 7500, the code used to indicate unlawful interference with an aircraft, a category that includes hijacking, before returning to 7700. (Flightradar24) This sequence does not, by itself, prove what happened inside the cockpit. A transponder is not a camera and cannot tell investigators who physically selected the controls or exactly what was taking place at that moment. It is nevertheless significant because an extremely abnormal loss of altitude, followed by an emergency code and then the code associated with unlawful interference, is consistent with the circumstances later described by witnesses and authorities.

At one point the aircraft also lost contact with some forms of tracking. Reuters reported, citing an Israeli official, that the transponder was switched off for almost half an hour. This element will also have to be verified through technical data and ATC recordings. (Reuters) The aircraft was subsequently diverted to Tabuk. At 05:44 UTC, Tabuk air traffic control received the request for an emergency landing, and the Boeing eventually landed safely. The captain and co-pilot were injured and taken to hospital, while the other passengers were assisted on the ground and subsequently transferred to Tel Aviv on another aircraft. (Anadolu Agency)

An investigation was immediately opened by the relevant Saudi transport safety authority in coordination with the authorities of the United Arab Emirates. (Anadolu Agency)

What Happened in the Cockpit?

The picture became considerably more precise as additional information emerged. In the first hours after landing, reports spoke generically of an “altercation” in the cockpit. flydubai initially provided no detailed account of the circumstances and urged against premature conclusions. (flydubai) Later, passenger testimony and statements from Israeli and Saudi authorities produced a much more serious picture: the co-pilot allegedly attacked the captain.

Some early reports referred to a knife, but this version was not confirmed by subsequent official information. On October 3, the UAE Attorney General specified that the weapon used was the emergency axe located in the cockpit. (Reuters) This clarification is important because it addressed one of the first questions raised online: how could the co-pilot have brought a weapon onto the aircraft? The available account indicates that he did not need to bring one with him. The axe was already part of the aircraft’s equipment.

Commercial aircraft carry such tools for use in certain emergencies. That means an object intended as emergency equipment can, under exceptional circumstances, become a weapon in the hands of someone who is already authorized to be in the cockpit. This illustrates one of the inherent limitations of aviation security: it is impossible to remove every object that could potentially be used as a weapon while still retaining the equipment required to deal with genuine emergencies.

The Reinforced Cockpit Door: How does it Really Work?

The cockpit door on a modern airliner is not simply an “armoured door” in the cinematic sense. It is a security system integrated into the aircraft and designed primarily to prevent a person in the passenger cabin from forcibly entering the flight deck.

Following the September 11, 2001 attacks, the requirements for flight-deck intrusion resistance were considerably strengthened. The FAA establishes specific requirements concerning the resistance of the flight-deck structure to intrusion and forced entry, and the door forms only one part of a broader barrier that also includes bulkheads, access controls and operating procedures. (FAA)

On the Boeing 737, the flight-deck door is designed to resist forced entry and incorporates ballistic and intrusion-resistance features. It also has a controlled-access system and an emergency-access mechanism intended to allow entry if the pilots become incapacitated. (Boeing 737 operational documentation)

The crucial point, and one that is frequently misunderstood, is that the door is not designed to be impossible to open. It must be possible to open it from inside the cockpit. Otherwise, in the event of fire, smoke, decompression, incapacitation or another emergency requiring evacuation, the pilots themselves could become trapped.

Door opened from inside

The system therefore provides normal controlled access from the cockpit and an emergency-access mechanism from the passenger side. The latter is designed to allow access when the pilots are incapacitated, but it does not mean that anyone can simply enter a code and immediately open the door. The emergency system includes a keypad on the cabin side; an emergency-access request generates an alert in the cockpit and initiates a timed procedure. Depending on the system configuration, the pilot can authorize or deny access, while a lack of response can allow the procedure to continue. The specific procedures and codes are, naturally, not disclosed as operational security information. (Boeing 737 operational documentation)

This is crucial to understanding FZ1073. The captain did not need to “break through” the reinforced door. According to the available reconstruction, the injured captain opened it from the cockpit side, allowing people in the cabin to intervene. Reuters reported that the captain, injured and on the cockpit floor during one of the descent phases, managed to open the door; other accounts likewise describe the action as the captain activating the door-opening mechanism from inside. (Reuters)

There is therefore no contradiction between a reinforced door, a closed and protected cockpit, passengers being unable to open it through normal access, and the captain being able to open it from inside. Those characteristics are precisely what the system is intended to provide. The reinforced cockpit door was not breached; it was opened from inside by a person authorized to open it.

FZ1073: What really happened on the flydubai Dubai–Tel Aviv Flight
FlyDubai Boeing 737 MAX 8 A6-FKF at Dubai International Airport, 2 Jan 2026. This aircraft was later involved in the incident of Flydubai Flight 1073.

Why did the Reinforced Door not Prevent the Attack?

Because it was designed primarily to solve a different problem. The door is intended to prevent a person outside the cockpit from entering the flight deck. In the FZ1073 case, however, the person who allegedly posed the threat was already inside the cockpit.

This is the fundamental difference between an external threat and an insider threat. If an armed passenger attempts to enter the flight deck, the reinforced door is an extremely important barrier. If one of the two flight crew members suddenly becomes a threat, the door cannot physically remove that person from the cockpit.

This is why aviation security cannot be reduced to the strength of the cockpit door. It also depends on personnel selection and screening, training, Crew Resource Management, medical and psychological assessments, access-control procedures, security systems, ATC communications, tracking, incapacitated-pilot procedures, the ability of the other pilot to intervene, cabin crew and, in extreme circumstances, the intervention of other people on board. The FAA itself describes the flight-deck door as one component of a broader protection system rather than an absolute solution to every possible threat. (FAA)

What about the two Off-Dury Pilots?

Another issue generated a large number of comments along the lines of “What a coincidence that there were two other pilots on board.” The explanation, however, is much less mysterious than it may initially appear.

Commercial airlines routinely use a practice known as deadheading, or more generally crew positioning. A pilot may need to reach a particular city in order to operate a subsequent flight. Rather than travelling there on a separate service, the airline can have that pilot travel as a passenger on another flight in its network. In other words, this is not simply a passenger who happens to have previous flying experience; it is a company crew member being repositioned for operational reasons. Airlines routinely use this system to position personnel where they will be needed for subsequent duties. (The National)

In the FZ1073 case, two other flydubai pilots were travelling as passengers. This does not mean that the aircraft normally had four pilots assigned to the flight. The operational configuration was normal; the two additional pilots were travelling to be available for subsequent duties.

Their presence nevertheless became extremely important. Once the injured captain managed to open the cockpit door, passengers intervened to neutralize the attacker. A passenger was able to contribute temporarily to stabilizing the aircraft, after which the two pilots travelling in the cabin could reach the cockpit and take control, eventually flying the aircraft to Tabuk.

flydubai described the individuals as company personnel travelling on the aircraft who contributed to securing it, while media reports described them as off-duty or deadheading pilots. These descriptions are not necessarily contradictory: they were off duty with respect to that particular flight segment, but remained operational company personnel travelling for work. (Flightradar24)

Was it Just “Luck?”

The presence of two qualified pilots on board was certainly a favorable circumstance, but it should be distinguished from the operational reason they were there. There is no evidence that they had been deliberately placed on the flight to deal with an attack or that anyone knew what was going to happen. Deadheading exists independently of FZ1073 because airlines have to move crews between locations.

What was extraordinary was that two pilots happened to be travelling on that particular aircraft at precisely the moment when their presence became critically important. An ordinary logistical feature of airline operations was transformed by an unforeseen emergency into a decisive factor in the outcome. That was a fortunate coincidence, not evidence of premeditation.

Did a Passenger really “Fly” the Boeing 737?

This issue has also been reported in an excessively cinematic way. According to Reuters, a passenger contributed to stabilizing the aircraft after the attacker had been neutralized, before the two flydubai pilots travelling on board took over the controls. The passenger said he was familiar with emergency procedures through a television programme dedicated to aircraft accidents. (Reuters)

That does not mean an untrained passenger suddenly learned how to fly a 737 MAX. A modern airliner is not a video game, and there is an important distinction between temporarily helping to stabilize an aircraft and independently conducting a commercial flight.

In a situation where an aircraft is rapidly losing altitude, a person without formal flight training can, under certain circumstances and with appropriate guidance, contribute to stopping a loss-of-control situation. Complete flight management, however, including navigation, communications, aircraft configuration and landing, requires professional skills. That is why the presence of the two additional pilots was so important.

Does the 7500 Code prove that it was a Hijacking?

It establishes that the transponder transmitted the code associated with unlawful interference, but it does not by itself establish who selected it or precisely why it was selected at that moment. Code 7500 is used internationally to indicate unlawful interference with an aircraft, including a hijacking situation, while 7700 indicates a general emergency.

In FZ1073, the sequence 7700 → 7500 → 7700 is particularly significant because it corresponds to a changing emergency situation: first a general emergency, then a specific indication of unlawful interference, followed by another general emergency. (Flightradar24) The transponder should nevertheless not be treated as a “black box”. Establishing exactly who selected each code requires examination of technical data, available recordings and other evidence.

Was the Co-Pilot really Hamam Al-Hammami?

Several media organizations identified the co-pilot as Hammam al-Hammami, an Omani citizen. Reuters specified that his identity had not been formally confirmed publicly by authorities at the time of its reporting, although the identification had been provided by two informed sources. Other outlets subsequently published additional biographical information. (Reuters)

His name is therefore widely reported, but a rigorous reconstruction should preserve the distinction between an identification reported by investigative sources and an identification formally released by a judicial authority through a complete official record. This distinction is particularly important when dealing with a person accused of an extremely serious crime.

What is known About his Background?

This is an even more sensitive issue. Several sources have reported that al-Hammami had previously worked or received training with Oman Air and that he was removed from flying duties because of concerns relating to alleged extremist views. The accounts do not agree perfectly on dates and circumstances. Some reports refer to extremist material allegedly found in 2024, while others place his removal from flight training at a later date. According to several reconstructions, he subsequently had professional dealings with Royal Air Maroc, which allegedly rejected his application, before joining flydubai. (Indian Express)

Reuters also reported that Royal Air Maroc confirmed that it had rejected his application. (Reuters)

This is a genuinely important issue for the investigation, not because it automatically proves the existence of a prior terrorist plan, but because it raises a concrete question: what information was available to the airlines that employed him, and what checks were carried out before he was assigned to a flight-crew position?

That question is very different from claiming that an airline “knew everything and put him on the flight anyway”. At present, there is not enough publicly available evidence to make that assertion.

FZ1073: What really happened on the flydubai Dubai–Tel Aviv Flight

Flydubai Flight 1073 altitude and speed

Why was He Allowed to Fly to Israel?

This issue has also attracted considerable discussion. Israel applies strict security procedures to passengers and personnel entering the country, and Reuters reported that the matter became particularly sensitive because Oman does not maintain formal diplomatic relations with Israel. The fact that an Omani citizen was part of the crew of a flight to Tel Aviv therefore attracted attention from Israeli authorities. (Reuters)

This does not mean that the co-pilot was simply “discovered at the airport and allowed through”. A pilot operating professionally on an international route is not necessarily processed in exactly the same manner as an ordinary passenger, because specific procedures exist for flight crews and aviation personnel.

The concrete question for investigators is therefore how information concerning a pilot previously removed from flying duties for security-related reasons is shared between airlines, aviation authorities and security services. That is an issue the investigation will have to clarify.

Was it a Terrorist Attack?

The most accurate formulation as of October 3, 2026 is that the judicial authorities of the United Arab Emirates classify the action as an attempted terrorist act. The Attorney General stated that the co-pilot used the emergency axe to attack the captain and attempted to take control of the aircraft, while also stating that the investigation was continuing to determine the circumstances, motive and possible connections. (The National)

This does not mean that the organizational structure, if any, behind the act is already known. Reuters reported that Israeli authorities had not identified Iranian involvement at the time of its reporting. (Reuters)

It is therefore possible to state that the action is officially being investigated as a terrorist act. It is not yet justified to claim that investigators already know who ordered it, on whose behalf it was carried out, or precisely why it occurred. Those questions remain part of the investigation.

What was the Motive?

The motive remains one of the major unresolved questions. Information has been reported concerning alleged extremist views held by the co-pilot, statements attributed to Israeli officials and material allegedly found or published on his accounts, but the full motive has not yet been publicly established.

An investigation must distinguish between ideology, radicalization, criminal intent and the organization of a terrorist attack. These are related but distinct concepts, and the connection between them has to be demonstrated by evidence rather than inferred from isolated pieces of information.

Conspiracy Theories: What is True?

The incident immediately generated a second phenomenon: a wave of misinformation. Several false claims can already be identified because fact-checkers examined them.

One of the most prominent theories claimed that Mossad was behind the incident. There is no public evidence linking the Israeli intelligence service to the event. A video apparently attributed to the BBC circulated claiming that Israeli intelligence was responsible for a covert operation and that an Indian citizen named Raghav Menon had been used to hijack the aircraft. BBC Verify confirmed that the material was not an authentic BBC broadcast and that its audio and subtitles had been generated or manipulated using AI. The video also contained images taken from stock-photo libraries. RTVE reconstructed the fabrication and found no evidence supporting the claim of Mossad involvement. (RTVE)

The same fake video generated the claim that the “real hijacker” was an Indian passenger named Raghav Menon. There is no publicly available evidence establishing such a person as being responsible for the incident, and the material presenting him as the perpetrator was manipulated. This is not simply an alternative interpretation of the available evidence; it is a fabricated narrative designed to look like a news report. (RTVE)

Another claim stated that a Russian and a Ukrainian pilot happened to be on board and saved the aircraft. RTVE’s fact-check found no evidence supporting this account. The people who actually intervened were flydubai pilots travelling as passengers. One was identified as Yaniv Hayoun; information concerning the second has varied, but there is no evidence that they were Russian and Ukrainian. (RTVE) The story appears to have transformed a real fact — the presence of off-duty pilots on board — into a more spectacular narrative.

No concealed weapon

A further recurring claim was that the cockpit door could not be opened from inside. That is incorrect. The door must be capable of being opened from the cockpit, among other reasons because the pilots must be able to leave the flight deck in an emergency and the system must permit flight-deck evacuation. Boeing 737 technical documentation explicitly describes manual opening from the cockpit side. (Boeing 737 operational documentation) The door is designed to prevent unauthorized access from outside, not to imprison the pilots inside.

The related claim that passengers could not have entered because the door was reinforced is based on the same misunderstanding. The available reconstruction does not require the passengers to have broken through the barrier. The captain opened the door from inside, which is entirely compatible with the design of the system. (Reuters)

The question of how the co-pilot obtained an axe also has a straightforward explanation. The UAE Attorney General specifically stated that the emergency axe from the cockpit was used. There is therefore no need to assume that a concealed weapon was carried through security. (The National) The incident may nevertheless raise legitimate questions about insider threats and the security management of equipment that must remain accessible to flight crews; those questions are different from evidence of a conspiracy.

The presence of two off-duty pilots on board is similarly explainable through normal airline operations. Airlines routinely reposition crews, a practice known as deadheading. The extraordinary element was that these two pilots happened to be travelling on this particular flight when their presence became critically important. (The National) That is a fortunate coincidence, not evidence of premeditation.

flydubai Pilots on Board

The claim that it would be impossible for a passenger to stabilize a 737 is also an oversimplification. Sources report that a passenger helped stabilize the aircraft temporarily before the flydubai pilots on board took over. This does not mean that the passenger independently flew the aircraft for the remainder of the flight. The distinction between briefly assisting with aircraft control and conducting a complete commercial flight is essential.

Likewise, the transmission of code 7500 does not prove that every aspect of the event had been planned in advance. It indicates that the unlawful-interference code was transmitted, but it does not establish who selected it or when every individual decision was made. Its presence is nevertheless consistent with an internal threat and with the subsequent reconstruction provided by authorities. Determining exactly who entered the code requires examination of technical data and available recordings.

The disappearance of an aircraft from a particular online tracking display is not evidence that it was shot down or deliberately hidden. ADS-B coverage depends on the location and availability of terrestrial receivers and is not uniform, particularly over remote areas. Reuters also reported that the transponder was switched off for a period, according to an Israeli official. That must be distinguished from the disappearance of a particular tracking-system feed. (Reuters) A gap on a flight-tracking website therefore does not automatically represent a gap in ATC or military radar coverage.

Absence of continuous footage

The absence of continuous footage of the attack is likewise not evidence that the incident was fabricated. There are tracking data, communications, eyewitness accounts, official statements, images from inside the cabin and documentation concerning the landing. Reuters verified videos filmed on board showing the injured captain, the co-pilot and traces of blood. (Reuters) What does not exist is a continuous video recording of the entire confrontation inside the cockpit, which is entirely unsurprising: commercial aircraft are not equipped with cameras that record every second of every flight from every angle.

Social-media videos also cannot be treated as a single body of evidence. RTVE identified a fake BBC report generated using AI, an old video of passengers dancing inside an aircraft that was unrelated to FZ1073, and footage falsely used to support the story about Russian and Ukrainian pilots. (RTVE) ABC News likewise documented the circulation of false and decontextualized videos and claims. (ABC News Verify) The existence of fake material online does not prove that the underlying event was fake; it demonstrates that false material was produced and circulated around a real event.

Is the Discrepancy in the Number of Passengers Suspicious?

FZ1073: What really happened on the flydubai Dubai–Tel Aviv Flight
Prime Minister Narendra Modi spoke with the brave pilot Captain Smit Machchhar and wished him a speedy recovery.

The discrepancy should be acknowledged, but there is no basis for treating it as evidence of manipulation. Early reports used different figures, with Saudi authorities giving 174 passengers and eight crew members while other sources referred to 172 people in total.

Such discrepancies can arise during an emergency because initial information may come from different manifests, preliminary counts, airport communications, airline statements or security authorities. Moreover, “passengers”, “people on board” and “passengers plus crew” are not interchangeable categories.

The appropriate conclusion is therefore simply that public sources were not perfectly consistent regarding the headcount and that Saudi authorities provided the figure of 174 passengers plus eight crew members. The discrepancy should neither be concealed nor transformed into evidence of a conspiracy without further evidence.

Why did flydubai Initially speak only of an “Altercation”?

ecause that was the prudent approach while the facts were still being established. Immediately after a serious incident, an airline does not necessarily possess a complete reconstruction. flydubai confirmed that an incident had occurred during the flight and that the aircraft had diverted to Tabuk, subsequently referring to an altercation in the flight deck and the intervention of company personnel. The airline also urged people to avoid premature speculation while authorities gathered information. (flydubai)

That is compatible with normal communication procedures during an investigation. The fact that a company does not immediately announce that its co-pilot attempted to bring down the aircraft does not in itself indicate that information is being concealed. It may simply mean that the evidence was not yet sufficient to support such a statement.

What does the Investigation still have to Establish?

A great deal remains to be reconstructed. Investigators will need to establish the exact timeline, including when the attack began, who controlled the aircraft at each point during the descent, what inputs were made on the flight controls, who selected the 7700 and 7500 codes, how long the co-pilot retained access to the controls, how much time passed between the attack and the opening of the door, who entered the cockpit first and when the two additional pilots assumed control.

These questions can be addressed by combining Flight Data Recorder and Cockpit Voice Recorder information with aircraft-system data, ADS-B records, ATC communications, radar recordings, maintenance records, witness statements, passenger videos, physical and forensic evidence, electronic devices and the co-pilot’s professional records. The UAE Attorney General explicitly stated that physical and digital evidence was also being examined. (The National)

The Most Serious Issue: the Insider Threat

Beyond the political and conspiratorial narratives surrounding the event, FZ1073 raises a genuine problem for civil aviation. Modern cockpit security was developed primarily with an external threat in mind. After 9/11, one of the central priorities was to prevent people in the passenger cabin from entering the flight deck and taking control of an aircraft.

FZ1073 represents the opposite scenario: the person who allegedly posed the threat was already authorized to be inside the cockpit. That changes the security problem fundamentally. A stronger cockpit door would not have prevented the alleged attack by the co-pilot, because the threat was already on the protected side of the barrier. At the same time, aviation cannot simply remove every tool that could potentially be used as a weapon, because crews must have access to equipment required for genuine emergencies, nor can every pilot be treated as a permanent suspect.

The response therefore has to be systemic. It involves background checks, information sharing between operators and authorities, reporting procedures, assessment of behavioural anomalies, management of information received from previous employers, CRM, and procedures for situations in which a crew member becomes a threat. The industry may also need to examine access arrangements and intervention procedures. These are the substantive security questions raised by the incident.

The Most Important Lesson of FZ1073 flydubai Dubai–Tel Aviv Flight

FZ1073 demonstrates something often forgotten when aviation safety is discussed: a safe system is not a system without vulnerabilities. The cockpit door apparently performed the function for which it was designed by preventing unauthorized access from the cabin, but the alleged threat originated from someone who was already authorized to be inside the flight deck.

At the same time, several other layers of the system became relevant. The deadheading arrangement happened to place two qualified pilots on board. Emergency procedures allowed the situation to be signalled. Despite his injuries, the captain managed to open the door, passengers intervened, the additional pilots took over the controls, the flight was diverted and air traffic control and Tabuk airport managed the emergency response.

The fact that no one was killed does not mean that the risk was small. Rather, it means that a series of technical, procedural and human barriers prevented a potentially catastrophic situation from becoming a catastrophe.

Facts, Reported Claims and What Remains to be Proven

As of October 3, 2026, the situation can be divided into several levels of certainty. Strongly documented elements include the fact that FZ1073 was a Boeing 737-8 MAX flying from Dubai to Tel Aviv, that the aircraft experienced a severe descent, that codes 7700 and 7500 were transmitted, that the aircraft diverted to Tabuk and landed safely, and that both the captain and co-pilot were injured. Available accounts also indicate that the captain opened the cockpit door, after which passengers and company personnel intervened, while two flydubai pilots travelling as passengers contributed to managing the flight and landing. The UAE Attorney General stated that the co-pilot attacked the captain with the emergency axe and attempted to take control of the aircraft, and Emirati authorities are investigating the incident as an attempted terrorist act. (The National)

Other information has been reported by investigative sources but still requires further confirmation. This includes the co-pilot’s identification as Hammam al-Hammami, his previous professional relationships with Oman Air and Royal Air Maroc, the reasons why he was allegedly removed from flying duties in Oman, the information that may have been passed between airlines, the precise circumstances of his alleged radicalization, the exact sequence of flight-control inputs during the descent, who selected the transponder codes and whether any suicidal intent was involved. (Reuters)

By contrast, there is currently no established public evidence of Mossad involvement, Iranian involvement, government planning, an Israeli or Emirati hoax, the participation of Russian or Ukrainian pilots, a second hijacker, the involvement of an Indian passenger named Raghav Menon, or deliberate manipulation of the flight data. Several of these claims originated directly from false or AI-generated material. (RTVE)

FZ1073 flydubai Dubai–Tel Aviv Flight: Conclusion

The story of FZ1073 is extraordinary enough without adding a conspiracy theory. A Boeing 737 MAX flying at approximately 34,000 feet was involved in an attack inside the cockpit. The captain was allegedly injured with an emergency axe, the aircraft entered an extremely rapid descent and code 7500, normally associated with unlawful interference, appeared on the transponder. Despite his injuries, the captain managed to open the cockpit door, allowing passengers to intervene and help restrain the attacker. Two flydubai pilots happened to be travelling as passengers because of a normal crew-repositioning requirement, and they were subsequently able to take over the controls and bring the aircraft safely to Tabuk.

There is no need to invent a conspiracy to explain why the aircraft survived, but neither is it correct to claim that every detail is already known. The essential sequence is now strongly documented, while the most important unresolved questions concern the complete forensic reconstruction: the precise sequence of control inputs, the motive, the degree of planning, any prior information concerning the co-pilot, and how that information was handled as he moved between different airlines and authorities.

Those are the questions that should matter most to aviation. The central issue is not simply how one person allegedly managed to attack the captain, but how a system designed primarily to protect an aircraft from an external threat must adapt when the threat originates inside the cockpit itself.

That legitimate security question should also be kept separate from the disinformation that accompanied the incident. FZ1073 already contains enough extraordinary elements in reality. There is no need to add invented ones.

Main Sources

  • flydubai, official updates concerning flight FZ1073 on September 30, 2026.
  • UAE General Civil Aviation Authority, statement concerning the security incident.
  • UAE Office of the Attorney General, October 3, 2026 statements, reported by The National.
  • Reuters, What do we know about flydubai flight 1073?, October 2, 2026.
  • Reuters, reconstruction of the incident and passenger testimony.
  • Flightradar24, flight data and reconstruction of the 7700–7500–7700 sequence.
  • Saudi National Transport Safety Center, investigation into the emergency landing at Tabuk.
  • Saudi Ministry of Interior / airport authorities, passenger, crew and landing figures.
  • The National, analysis of deadheading and the two pilots travelling as passengers.
  • Indian Express, reporting concerning the co-pilot and the additional pilots.
  • FAA, AC 25.795-1A, flight-deck intrusion-resistance requirements.
  • Boeing 737 operational documentation concerning the flight-deck door and emergency-access systems.
  • RTVE / VerificaRTVE, analysis of fake videos, deepfakes and conspiracy theories concerning FZ1073.
  • ABC News Verify, analysis of misinformation circulated after the incident.
  • Al Jazeera, reports concerning the identity and professional background of the co-pilot, with relevant caveats.
  • Government of Israel, official statement concerning the initial report of the incident.
flydubai Boeing 737 model
This model is available to order from AirModels – CLICK HERE TO GET YOURS.

Photo credit: PMO India and Flickr via Wikipedia

Francesco Jerace

Francesco Jerace

Francesco Jerace is an Officer and commercial pilot, with a solid personal and professional military and civilian background, built through education, travel, missions, training and flight activities. His expertise ranges from flight activities and the technical and operational aspects of aviation to safety, regulations and the environmental implications of air and space transportation. He also has experience in firefighting and aerial operations related to wildfire management. This has allowed him to directly observe the relationship between aeronautical activities, territory, weather conditions and emergency management, developing a particular interest in the effects that climate evolution may have on the frequency, intensity and management of extreme events. He has also developed expertise in the healthcare and emergency and disaster management fields, examining in depth the issues connected to responding to complex events and protecting the population in crisis situations. This interest integrates with the study of climate change and its possible effects on public health, emergency management and the resilience of healthcare and rescue systems, with particular attention to phenomena such as heat waves, wildfires, extreme weather events and other situations that may result in health and humanitarian emergencies. Alongside his aeronautical activities, he is involved in the dissemination and in-depth study of scientific, environmental, aeronautical and legal topics, with particular interest in climate change, climate geoengineering, artificial intelligence, space medicine and aerospace technologies. He particularly examines the scientific evidence concerning the climate system, extreme weather events, wildfires and interactions between the atmosphere and aeronautical activities, with attention to mitigation and adaptation strategies. He is also involved in aviation law and Space Law, with particular attention to the regulatory and legislative aspects related to aerospace activities, the use of new civilian and military technologies, the evolution of space deterrence, and cooperation between government entities and private companies in the sector. His interest in space medicine concerns the physiological and operational aspects of human activities in extreme environments and future space missions, while in the field of artificial intelligence he examines applications in the aeronautical, scientific, environmental and technological sectors, with a particular focus on the integration and fusion between humans and machines. In his articles, he integrates operational experience, aeronautical expertise, scientific knowledge and healthcare and legal aspects, adopting a multidisciplinary approach based on the analysis of data, specialized literature and regulatory sources. His work in scientific dissemination focuses primarily on the intersection between aviation, firefighting, climate, environment, disaster management, health, geoengineering, space, medicine, artificial intelligence, transhumanism and law, with the aim of making complex topics accessible as well and distinguishing documented evidence from simplifications, unsupported interpretations and disinformation.

Francesco Jerace: All articles

Back to top