As of the morning of 30 September, not all the details of the unusual incident on the Flydubai flight from Dubai to Israel are known. What has been reported so far is that a physical confrontation took place between the pilots during the flight, emergency signals were transmitted, the aircraft was diverted to Tabuk in Saudi Arabia, and all passengers landed safely. The precise reason for the confrontation, what preceded it, and what happened during the critical minutes inside the cockpit are still being examined. Precisely for that reason, firm conclusions would be premature. At the same time, the investigation should not be confined too quickly to the simplest and most convenient explanation.
One point, however, should not be lost amid the questions. I have no doubt that the United Arab Emirates will do everything required to protect the safety of passengers, establish the facts, and address any security weakness that the investigation may identify. The UAE has built its international aviation sector on connectivity, reliability, and passenger confidence, and it has every interest in treating an incident of this nature with the seriousness it deserves. Raising difficult security possibilities should therefore not be interpreted as criticism of the Emirati authorities or of Flydubai. On the contrary, it is precisely because passenger safety must remain paramount that every credible line of inquiry should be examined thoroughly.
A personal dispute that escalated out of control is certainly one possibility. It may ultimately prove to be the entire story. Yet an incident in which two pilots physically struggle during a flight to Israel, while emergency signals trigger initial fears of unlawful interference, warrants a much broader examination. Investigators should ask not only what happened but also why it happened, who initiated the confrontation, what each member of the crew was trying to do at the time, and whether any outside actor influenced the event in any way.
One possibility that, in my view, must be examined alongside other explanations is an insider threat: the recruitment, coercion, manipulation, or activation of an aircrew member by a hostile actor. Within that line of inquiry, possible Iranian involvement should also be examined. It must be stated with complete clarity that there is currently no public evidence linking Iran to this incident. This is not a factual allegation. It is a security hypothesis that deserves examination. A serious investigation does not look only at what has already been proved. It also tests plausible scenarios that could explain an abnormal event with potentially catastrophic consequences.
Based on my professional experience in the security field, I do not regard such a scenario as fanciful. In recent years, Western governments and security authorities have publicly warned about Iranian security services using intermediaries, local networks, and proxy actors for surveillance, intimidation, sabotage, and violent operations. That record does not establish any connection to this particular flight, but it does explain why the possibility should not be dismissed without examination. From the perspective of a hostile intelligence service, recruiting someone who already holds trusted access to a sensitive system can be far more effective than trying to penetrate that system from outside.
In aviation, security is usually discussed in terms of terminal access, passenger screening, baggage checks, suspicious travellers, cargo controls, and airport protection. All of these are essential. None of them fully answers the question of what happens when the potential threat is already inside the cockpit. A commercial pilot has a level of access and control that almost no other person aboard the aircraft possesses. If a hostile actor succeeds in recruiting, blackmailing, threatening, or otherwise influencing such a person, external security measures may become far less relevant at the decisive moment.
This leads to an important lesson that can already be discussed before every detail of the incident is known. On sensitive routes, particularly during periods of heightened regional tension, there is a strong case for reviewing how aircrew in critical positions are screened and periodically reassessed. This must never become automatic suspicion based on nationality, religion, or ethnicity. Such an approach would be both unprofessional and dangerous. The focus should be on risk indicators and behaviour: unusual contact with hostile actors, unexplained financial changes, abnormal travel or communication patterns, signs of coercion or blackmail, significant behavioural changes, and relevant intelligence information.
A background check conducted when an employee is first hired may not always be enough for a highly sensitive role. Hostile states and terrorist organisations can work patiently over long periods and search for human vulnerabilities. For positions with exceptional access, periodic reliability reviews should therefore be considered, subject to law, privacy safeguards, and clear professional standards. The same principle can apply not only to pilots, but also to maintenance personnel, ground staff, and others with critical access. At the same time, information sharing among airlines, civil aviation authorities, and security services should be strengthened where legally appropriate, particularly on routes assessed as unusually sensitive.
Airlines themselves should also be willing to ask uncomfortable questions. How are cockpit crews paired on sensitive flights? What relevant information is available before departure? What is the procedure when an abnormal confrontation develops in the cockpit? Are intervention mechanisms fast enough? Can an airline identify signs of unusual pressure, coercion, or security risk in a person who may hold practical control over an aircraft carrying hundreds of passengers? None of these questions assumes wrongdoing. They are simply part of responsible risk management in an era when the human factor can be exploited as deliberately as any technical vulnerability.
It may well emerge at the end of the investigation that the Flydubai incident was the result of a serious personal confrontation between two crew members, with no connection whatsoever to terrorism or any hostile state. If that is what the evidence shows, it should be stated clearly. But until the facts are established, it would be equally unwise to rule out an insider threat simply because the scenario sounds extreme. In security work, unusual scenarios are not accepted as truth merely because they are possible. They are examined, tested against evidence, and either substantiated or discarded.
The lesson is not that every pilot should be viewed with suspicion, nor that every flight should become an arena of fear. The lesson is that modern security must look beyond the terminal gate. An aircraft can be well protected against someone trying to enter from outside and still remain vulnerable if a hostile actor manages to reach someone who already has legitimate access. After an incident as extraordinary as this one, the continuing assessment of personnel in sensitive aviation roles deserves to be part of the security discussion, not an afterthought once an emergency has already begun.
Author’s note: This article is based on public information available at the time of writing. The circumstances of the incident remain under investigation and may change as additional facts emerge.