The FlyDubai cockpit and the threat that never left

Reports confirmed Monday that the FlyDubai co-pilot who attacked the captain on a flight from Dubai to Tel Aviv had planned to crash the aircraft into Ben Gurion International Airport or a nearby building. The attack, which took place in the flight deck at cruising altitude, was foiled when the captain physically overpowered the co-pilot; the aircraft landed with the attacker restrained and all passengers safe. Investigators have established that the co-pilot — a UAE-based national whose name has not been officially released — had researched the approach path and passenger density at Ben Gurion in the weeks before the flight. NPR confirmed that a person familiar with the investigation said the attack was intended as a deliberate mass-casualty kamikaze strike consistent with 9/11-style planning. The incident has triggered emergency security reviews across Gulf airlines and prompted renewed questions about the depth and consistency of crew psychological screening processes.

The received wisdom

The standard institutional response to incidents of this kind follows a familiar and unhelpful script. Aviation authorities will announce a review of psychological testing protocols. Airlines will tighten cockpit monitoring, probably through enhanced continuous background check requirements. Intelligence agencies will acknowledge that screening gaps exist and that corrective measures are being implemented. The broader political conversation — the one that asks what radicalisation pathway brought a credentialled commercial pilot to the point of planning a suicide attack on a civilian airport — will be handled with the maximum institutional delicacy and the minimum analytical specificity. The word “Islamism” will appear in security briefings and disappear from public statements. If a mental health framing is available, it will be preferred. The mainstream emphasis, in short, will be on the procedural failure (he passed his screening) rather than the ideological one (he believed mass civilian murder was a religious obligation).

A different read

The procedural failure is real. Aviation’s two-person cockpit rule, reintroduced after the Germanwings disaster in 2015, was apparently not enforced on this flight — or was insufficient in form, since the attack occurred with the co-pilot alone at the controls while the captain briefly left the cockpit. But focusing only on the procedural failure is a category error of the same kind that produced the post-9/11 era’s most notorious intelligence blind spots.

Consider what we actually know about the radicalisation timeline. The co-pilot had reportedly spent several weeks researching Ben Gurion’s approach geometry and expected casualty maximisation. This is not the behaviour of a person who snapped; it is the behaviour of a person engaged in operational planning. The cell — if there was one — or the online community that provided the ideological framing has not been publicly identified, which suggests either that investigators are still working the problem or that the trail involves platforms and jurisdictions that complicate disclosure. Either way, the pre-meditated nature of the attack is incompatible with a purely individual pathology reading.

The deeper point is about the persistence of the threat environment. The Western security consensus after 2015-2016’s wave of attacks in Paris, Brussels, and Nice gradually shifted from “Islamist terrorism is the primary threat” to a framework that distributed threat attention across right-wing extremism, environmental radicalisation, and lone-wolf violence of various types. This rebalancing was not wrong in itself — far-right terrorism killed significant numbers in Western countries during this period — but it was accompanied, in some institutional cultures, by a reluctance to name Islamist radicalisation with the same analytical directness applied to other extremisms. The FlyDubai incident follows several years of lower-profile attacks on Israeli-adjacent targets — including Houthi drone and missile campaigns and direct approaches to Israeli civilians by state-sponsored actors — suggesting a strategic and ideological ecosystem that remains active, adaptive, and capable of reaching into supposedly secure employment settings.

The historical parallel that matters here is not 9/11 but the 1994 Air France hijacking, when a GIA cell planned to crash the aircraft into the Eiffel Tower. The response then was a security surge that did substantially improve French aviation security for a decade. The response now risks being captured by the institutional reluctance to be seen as singling out any demographic — a reluctance that is understandable in political terms but corrosive in security ones. Screening for radicalisation is not the same as discrimination; it is targeted, evidence-based investigation into observable behavioural and communications patterns. The fact that it makes HR departments uncomfortable is not a reason to avoid it.

There is also the Gulf employment ecosystem to consider. Dubai’s airlines employ pilots and cabin crew from across the region, with screening standards that vary considerably from those applied to, say, British Airways or Lufthansa. The FlyDubai incident will accelerate pressure on ICAO and regional aviation bodies to standardise not just the technical but the vetting components of crew accreditation. Whether that pressure produces anything beyond a new documentation requirement, or whether it is absorbed into the institutional comfort of process-compliance without substance, will tell us something important about whether aviation security has genuinely learned its lessons.

What to watch

  • Identity of the cell or network: If investigators establish organisational support — financiers, ideological mentors, online community — the security implications extend well beyond aviation.
  • Gulf airline vetting reform: Whether Emirates, Etihad, and FlyDubai implement CCTV-in-cockpit and enhanced screening will be watched closely. The commercial stakes (tourism, Gulf hub status) create perverse incentives against transparency.
  • Israeli political response: Netanyahu’s government will use this incident domestically. Watch for accelerated screening of Ben Gurion approaches and potential expansion of Israeli air marshal programmes.
  • ICAO response timeline: The International Civil Aviation Organisation typically takes 18-36 months to produce new standards after incidents. Whether this one triggers an accelerated emergency protocol review is the metric to watch.

— J