CRASH IT INSIDE ISRAEL? Investigators Probe Whether Flydubai Co-Pilot Planned to Seize Jet Over Jordan and Carry Out Mass-Casualty Attack
Israeli security officials are investigating whether the Omani co-pilot who allegedly stabbed the captain of a flydubai flight on Wednesday intended to seize complete control of the aircraft while it was over Jordan and then deliberately crash the passenger jet at high speed inside Israel. The theory is one of several being examined and has not yet been established as the attacker’s actual plan.
The new line of investigation comes as Israeli security agencies intensify their examination of the attempted takeover of flydubai Flight FZ1073, which was carrying 174 passengers from Dubai to Tel Aviv when violence erupted in the cockpit.
The aircraft was flying through Jordanian airspace and approaching Israel when the co-pilot allegedly attacked Captain Smit Machchhar, an experienced Indian pilot, stabbing him during a struggle for control of the Boeing 737 MAX 8.
The jet subsequently plunged thousands of feet, at one point losing roughly half its cruising altitude in less than two minutes. Emergency transponder codes were transmitted from the cockpit, including 7500, the international signal for hijacking or unlawful interference.
The incident triggered an immediate Israeli security response, including the scrambling of fighter jets amid fears that the aircraft had been hijacked and could pose a threat as it approached Israeli airspace.
Passengers and crew members ultimately forced their way into the cockpit and subdued the alleged attacker. Other pilots who were traveling aboard the flight then helped stabilize the aircraft and divert it to Tabuk, Saudi Arabia, where it landed safely.
Saudi authorities took the suspected attacker into custody and are questioning him as investigators seek to determine his motive, whether he acted alone and whether any state or terrorist organization was involved.
The possibility now being examined by Israeli officials is particularly alarming: that the co-pilot intended to wait until the aircraft was over Jordan, take control of the plane and continue toward Israel before deliberately crashing it on Israeli territory.
No evidence establishing that scenario as fact has yet been made public, and flydubai has said that the underlying reasons and motive behind the cockpit incident remain subject to a formal investigation.
The episode is also drawing new attention to a security dispute that had been unfolding for months before Wednesday’s attack.
According to a Channel 12 report, Shin Bet Director David Zini had repeatedly warned that existing security arrangements involving flights from the United Arab Emirates were inadequate.
The Shin Bet and Israeli airlines had been locked in a significant dispute in recent months over restrictions preventing Israeli carriers from operating flights to Dubai because security requirements had not been resolved.
The Shin Bet extended the restriction on Israeli airlines flying to the UAE through the end of October amid heightened regional tensions and concerns involving Iran. El Al, Arkia and Israir consequently remained off the route even as Emirati carriers continued flying between the two countries.
Security officials say Zini resisted considerable pressure to relax the restrictions, maintaining that Israeli carriers should not resume UAE service until additional safeguards were put in place.
The security concerns that prompted those restrictions were not necessarily focused on a rogue pilot attempting to commandeer an aircraft. Intelligence assessments had concentrated more heavily on other potential threats, including missile attacks, attacks against airports and threats to aircraft while on the ground.
A scenario in which a credentialed commercial pilot already inside the cockpit would allegedly attempt to seize and deliberately crash an Israel-bound passenger aircraft had not been a central feature of the security discussions.
The division of responsibility surrounding the route is also receiving renewed scrutiny. The Shin Bet is responsible for security arrangements involving Israeli airlines, while the Mossad plays a central role in preventing threats to foreign carriers operating abroad.
Because flydubai is an Emirati airline, the security structure surrounding its operations differs substantially from that governing El Al and other Israeli carriers.
The incident has therefore raised difficult questions about how Israel can protect passengers on foreign airlines when it does not exercise the same control over recruitment, vetting and security procedures for foreign flight crews.
Israeli authorities are examining the background of the alleged attacker, how an Omani national came to be assigned to an Israel-bound flight, and whether there were warning signs that could have been detected beforehand.
The case has also prompted questions about whether the attack was specifically intended to damage the relationship between Israel and the UAE. Israeli diplomatic officials have raised the possibility that an Emirati airline was deliberately chosen because direct flights between the two countries have become one of the most visible symbols of the Abraham Accords.
Investigators have not established whether the alleged attacker had organizational backing. Saudi authorities are continuing to interrogate him, while Israel is awaiting information from the investigation.
Israeli officials are simultaneously examining the possibility of Iranian involvement or assistance from an Iranian proxy, though no evidence publicly released thus far has established such a connection.
{Matzav.com}
