A 7500 Signal, A Sudden Descent And Scrambling Fighter Jets: Inside The Flydubai Scare

A flydubai flight from Dubai to Tel Aviv was diverted to Saudi Arabia on Wednesday after a serious incident in the cockpit, forcing Israeli authorities to consider the possibility that an aircraft carrying Israeli passengers could have become a security threat.

Flight FZ1073 landed safely at Tabuk after the aircraft was brought back under control by members of its crew. Flydubai has described what happened only as an “altercation” in the flight deck and said its causes and motives remained under investigation. Israeli Prime Minister Benjamin Netanyahu, however, said one pilot stabbed the other and “apparently” tried to crash the aircraft. He said passengers and crew intervened and regained control.

The difference in the accounts is important. The incident has not yet been officially established as a hijacking or terrorist attack. The UAE has ordered an investigation into the circumstances, motives and any possible connection to terrorist activity or prior planning. But for Israel, the emergency signals and apparent loss of control were enough to trigger a contingency response.

What Happened On The Flight?

FZ1073 was flying from Dubai International Airport to Ben Gurion Airport when an incident occurred in the cockpit.

Flydubai said an altercation took place in the flight deck and that the aircraft was subsequently secured by other flydubai crew members travelling on the flight. The aircraft was diverted and landed safely at Tabuk Airport in north-western Saudi Arabia, with all passengers and crew accounted for. The airline has urged authorities and the public to avoid speculation while the investigation continues.

Israeli officials gave a more serious account. Netanyahu said one pilot stabbed the other and apparently tried to crash the aircraft by interfering with its systems. He said a passenger and a crew member entered the cockpit and subdued the attacker, after which other crew members helped stabilise the plane. Saudi authorities arrested the pilot accused of the stabbing, according to Netanyahu's statement.

Flight-tracking data showed the aircraft first transmitted a general emergency signal, followed by the 7500 code used for unlawful interference. The plane then made a steep descent before diverting to Tabuk.

Why Did Israel Treat It As A Threat?

The crucial factor was uncertainty.

When an aircraft sends an emergency signal and appears to lose control, authorities may not immediately know whether they are dealing with a technical problem, an onboard disturbance, unlawful interference or an attempt to take control of the aircraft.

In this case, the aircraft was also headed towards Israel and was carrying mostly Israeli passengers. Netanyahu said he had instructed Israel's security services to prepare for additional potential threats while situation assessments continued. The Prime Minister's Office later said the incident was under control and that measures were being taken to return the passengers safely to Israel.

Israeli Ambassador to India Reuven Azar later told PTI that Israel's civil aviation authorities, air force and political leadership were alerted and that fighter jets were sent into the air as a precaution. He said the assessment was shaped partly by Israel's relatively small geographic size and the possibility of an aircraft approaching its territory within a short period.

The jets therefore went up before the final nature of the incident was known. The response was about preparing for the worst-case possibility while more information was being established.

What Did The Jets Actually Do?

According to Azar, the fighter jets were airborne but never had to intervene against the aircraft.

“They didn't have to take action,” he told PTI, after describing how passengers and crew had regained control of the flight. He also said there could have been a situation in which the prime minister had to decide what action to take if control had not been restored. He did not publicly set out what that action would have been.

That distinction matters. The available public statements establish that fighters were put in the air as a contingency measure. They do not establish that Israel ordered an attack on the aircraft, authorised a shoot-down or prepared to use force against it.

By the time the flight was safely diverted to Saudi Arabia, the immediate uncertainty had diminished. Israel could shift from preparing for a possible airborne threat to arranging the return of its citizens. The Prime Minister's Office said the incident was under control.

How Does Israel Secure Its Airspace?

The fighter response was only one part of a larger aviation-security structure.

Israel's Ministry of Transport operates an Aviation Security Operations Center, or ASOC, which it describes as a 24-hour coordination point for security, defence, civil-aviation and government agencies involved in measures for aircraft arriving into and through Israeli airspace.

The centre's role illustrates why an aircraft security incident does not necessarily begin and end with the air force. Civil aviation and security authorities have systems for identifying aircraft, coordinating their arrival and sharing information with the agencies responsible for airspace security.

The ASOC also maintains continuous watch capability and handles security procedures for aircraft entering or passing through the Tel Aviv Flight Information Region. That provides an institutional link between aviation authorities and the wider national-security system.

The Flydubai episode therefore activated a broader security architecture in which an aircraft emergency can quickly become an issue involving civil aviation, intelligence and defence authorities.

What Happens With A Hostile Aircraft?

The public record is clearer about the existence of Israel's aviation-security framework than about the precise military rules governing an aircraft judged to be hostile.

Israel has legislation dealing with unlawful seizure and other offences involving aircraft, while aviation-security authorities maintain procedures for aircraft entering Israeli airspace. But the detailed operational rules governing the use of military force against a civilian aircraft are not set out in the public material supplied for this case.

That distinction is important because an aircraft can move through several stages of assessment. An emergency does not automatically mean a hijacking. A hijacking does not automatically establish that the aircraft poses a hostile threat to a state. And a military scramble does not by itself mean that force will be used.

The Flydubai incident demonstrates precisely that middle stage: Israel prepared for a possibility before the facts had been fully established.

Why Does Israel Have This History?

Israel's unusually developed concern with aircraft security has roots in earlier hijackings involving Israeli aircraft or passengers.

On 8 May 1972, Sabena Flight 571 was hijacked shortly after leaving Vienna and brought to Lod Airport, then Israel's main international airport. The IDF's official history records that the hostage situation ended with a commando operation by Sayeret Matkal, which entered the aircraft after Israeli authorities had gathered detailed information about the hijackers and the layout of the plane.

Four years later, on 4 July 1976, Air France Flight 139 was hijacked after leaving Tel Aviv and eventually taken to Entebbe in Uganda. Israel carried out a long-range military operation that rescued the hostages. The Defence Ministry archive describes the operation as one of the major military operations in the IDF's history.

These incidents are not direct precedents for an aircraft suddenly losing control in mid-air. Their importance is narrower: they help explain why aircraft security has long been treated in Israel as a national-security issue rather than solely as a civil-aviation matter.

How Is The Threat Assessed?

Modern aviation security depends on information as much as on the eventual military response.

Israel's Aviation Security Operations Center says it maintains a continuous watch and coordinates security measures involving multiple government, defence and aviation bodies. For aircraft entering Israeli-controlled airspace, the centre's published procedures include advance security notifications and identification measures.

In an incident such as FZ1073, the information available to authorities can change rapidly. An emergency transmission can indicate that something is wrong without immediately establishing why. Flight behaviour, communications with the aircraft and information from the crew can then alter the assessment.

That is what makes the fighter response significant without making it evidence of a planned military engagement. The aircraft did not have to be conclusively identified as hostile before Israel prepared for the possibility that it might be.

What Happened Once Control Returned?

The military contingency was overtaken by developments aboard the aircraft itself.

According to Netanyahu, passengers and crew entered the cockpit and subdued the pilot who had allegedly attacked the other pilot. Other crew members then helped stabilise the aircraft. Azar said two additional pilots travelling on the flight were able to take control and land the aircraft safely in Saudi Arabia. Flydubai's own statement confirms that its on-duty crew travelling on the aircraft secured the plane and diverted it to Tabuk.

The UAE has since ordered a formal investigation. Its Attorney-General said investigators would examine the causes, circumstances and motives, including any possible link to terrorist activity, prior planning or direction. Flydubai has also suspended flights to and from Israel while the investigation continues.

That means the central questions surrounding the incident remain open: what caused the cockpit confrontation, why it happened and whether it had any wider security dimension.

What Does The Flydubai Scare Show?

The significance of the fighter-jet response lies less in what the Israeli Air Force ultimately did than in what Israel prepared to do if the situation deteriorated.

An aircraft showing signs of unlawful interference and apparently losing control can present a national-security problem before authorities know whether they are dealing with a criminal act, a hijacking, a technical emergency or something else. Israel's response was therefore built around preserving options while the situation was still unclear.

The FZ1073 incident also shows why historical experience matters without making the current case a repeat of past hijackings. Israel has spent decades building systems that connect civil aviation, security agencies and military authorities around aircraft entering its airspace. The fighter jets were one element of that system, not the system itself.

In this case, the contingency stopped short of military action because control of the aircraft was restored and it was diverted safely to Saudi Arabia. The investigation will determine what happened inside the cockpit; what is already clear is that Israel treated the uncertainty itself as a reason to prepare for the worst-case scenario.