ZINI WARNED THEM: Shin Bet Chief Flagged UAE Airport Security Gaps Weeks Before Flydubai Attack
Israeli investigators are examining whether the flydubai co-pilot accused of attacking the captain of Flight FZ1073 deliberately waited until the aircraft was near Jordan before attempting to seize control — potentially as part of a plan to crash the passenger jet inside Israel.
The disturbing possibility emerged alongside a new report that Shin Bet Director David Zini had spent weeks warning that security arrangements at airports in the United Arab Emirates were inadequate, and had insisted that Israeli airlines not resume service to the UAE until the deficiencies were addressed.
According to a report by Amit Segal on Channel 12, the Shin Bet had conducted its own assessment of the security perimeter surrounding Israeli airline operations in the Emirates and concluded that the existing arrangements did not provide sufficient protection.
That assessment reportedly triggered a significant dispute in recent weeks between Zini and Israeli airlines eager to resume service to the UAE. Zini resisted pressure to lift the restrictions, maintaining that Israeli carriers should remain grounded on the route until the security concerns were resolved.
The warnings have taken on new significance following Wednesday’s extraordinary events aboard flydubai Flight FZ1073 from Dubai to Ben Gurion Airport, when the co-pilot allegedly attacked and stabbed Captain Smit Machchhar before apparently attempting to send the Boeing 737 MAX into a catastrophic descent.
Flight-tracking data shows that the aircraft was cruising at approximately 34,000 feet before suddenly plunging. Publicly available data indicates that the jet lost roughly half of its altitude in less than two minutes during the most violent portion of the emergency.
The aircraft initially transmitted the emergency squawk code 7700, indicating a general emergency, and subsequently transmitted 7500 — the international transponder code indicating unlawful interference with an aircraft.
The plane briefly entered Jordanian airspace before turning back toward Saudi Arabia, where it ultimately landed safely in Tabuk after passengers and other crew members managed to overpower the alleged attacker.
Israel is now examining whether the location of the aircraft when the alleged takeover began was coincidental or whether it was itself part of the plan.
One scenario under investigation is that the co-pilot intended to gain control of the aircraft while it was over or near Jordan and then rapidly turn toward Israel, leaving Israeli authorities only a very short period to react before the aircraft could reach Israeli territory.
Officials have stressed that this remains an investigative theory and has not been established as the attacker’s actual plan. The motive for the cockpit attack has also not yet been officially determined, and investigators are examining whether the co-pilot acted alone or had assistance or direction from others.
The exact weapon used in the attack also remains unclear. Israeli reports have variously described it as a knife or a small ax, and investigators are expected to focus heavily on how any weapon capable of inflicting the captain’s injuries could have reached the cockpit.
That question is where Zini’s earlier concerns about airport security in the UAE could become particularly significant.
Although the incident occurred aboard a foreign airline and the alleged attacker was himself a member of the flight crew, Segal reported that Israeli aviation security procedures might have provided another layer of protection capable of detecting or preventing such an attack, particularly if investigators determine that the weapon was brought aboard before departure from Dubai.
Israel’s aviation-security system subjects flights and personnel to measures that go beyond the standard screening procedures used at many international airports. The flydubai incident is now expected to trigger a broader examination of the threat posed by insiders with authorized access to aircraft.
The security concerns raised before Wednesday’s attack reportedly did not center specifically on a rogue pilot attempting to seize his own aircraft. Instead, Israeli intelligence had been dealing with a sharp increase in general warnings about possible attacks, including concerns about an assault at an airport or missile fire targeting aviation.
According to Segal, a scenario in which a member of a flight crew would attack another pilot and attempt to use the aircraft itself as a weapon had not previously emerged in the discussions or threat scenarios known to him.
Wednesday’s incident has now placed that possibility squarely on the table.
Israeli fighter jets were scrambled during the emergency as authorities initially confronted the possibility that the Israel-bound aircraft had been hijacked. The plane ultimately turned toward Tabuk, Saudi Arabia, where it landed safely and the alleged attacker was taken into Saudi custody.
Nearly all of the roughly 170 passengers aboard were Israeli. Passengers and crew members who gained access to the cockpit subdued the co-pilot, while additional flydubai pilots who happened to be traveling aboard the aircraft subsequently helped bring the situation under control.
The UAE General Civil Aviation Authority has officially described what occurred aboard FZ1073 as a “security incident” and confirmed that crew members were injured and taken to a Saudi hospital. Emirati authorities said an investigation is underway into both the operational and security circumstances surrounding the incident.
Flydubai has likewise said that the motive and underlying circumstances remain under formal investigation and has cautioned against drawing conclusions before investigators establish the facts.
The incident is also highlighting the unusual division of responsibilities surrounding flights between Israel and foreign countries. Israel’s Transportation Ministry oversees regulatory aspects involving foreign airlines operating to and from Israel, while the Shin Bet is responsible for security surrounding Israeli airlines and their flights. The Mossad handles the broader effort to prevent international terrorist threats outside Israel.
That division helps explain why Zini’s warnings did not result in flydubai being barred from operating the Dubai-Israel route: his concerns had directly affected Israeli carriers whose security falls under the Shin Bet’s responsibility, while flydubai is a foreign airline operating under a different security framework.
The attack is now expected to force Israeli authorities to reassess that framework as well, including the screening of foreign flight crews, the security arrangements at airports serving Israel-bound flights and the possibility that someone with legitimate cockpit access could himself pose the threat.
The most ominous question remains what the alleged attacker intended to do had the passengers and crew not stopped him. Israeli investigators are now trying to determine whether the terrifying plunge aboard FZ1073 was simply an attempt to bring down the aircraft wherever it happened to be — or whether the jet’s proximity to Jordan and Israel was part of a far more calculated plan.
{Matzav.com}
