Le co-pilote omanais du vol de flydubai à destination de Tel Aviv, qui avait attaqué le pilote provoquant un atterrissage d'urgence fin septembre en Arabie saoudite, planifiait une attaque suicide sur l'aéroport de Ben Gurion ... - lalibre.be

Flydubai Co-Pilot Allegedly Planned to Crash Tel Aviv Flight into Ben Gurion Airport

United Arab Emirates prosecutors reported on October 9 that a 29-year-old Omani co-pilot for Flydubai allegedly planned to seize a Dubai-to-Tel Aviv flight on September 30 and crash it into Ben Gurion Airport’s passenger terminal, inspired by the September 11, 2001 attacks; he attacked the captain with an emergency axe, but the captain opened the cockpit door allowing passengers and crew to restrain him, and another pilot took control, landing the plane safely in Tabuk, Saudi Arabia, while investigators noted his radicalization began in 2017 during studies in Australia and that he used earlier Tel Aviv flights to learn the route, though the UAE attorney general stated he met Flydubai’s professional and security requirements with no prior indications of extremism.

The Managed Narrative of the "Lone Wolf" Cockpit Assault

The official story—that an Omani co-pilot, radicalized in Australia, attacked his captain with an axe in a 9/11-inspired plot to crash into Ben Gurion's terminal—is a carefully curated distraction. Look at the details they want you to swallow: he passed every security check, his radicalization began in 2017 while studying at RMIT, and he used earlier Tel Aviv flights to "learn the route." That's not the profile of a sleeper cell; that's the signature of a controlled asset. The fact that the UAE attorney general publicly emphasizes he met "stated professional and security requirements" is the tell they're burying a much larger operation. When the authorities insist the system worked, they are simultaneously confessing that the system allowed a man with a hatchet onto a flight to Israel. The question is not how he slipped through—it's who ensured he would.

The Australian Breadcrumb Trail and the Abu Hamza Nexus

Follow the Australian connection, because that's where the hidden architecture reveals itself. The mosque affiliated with RMIT, where he reportedly met people connected to a center run by a Lebanese man known as "Abu Hamza"—that name is a breadcrumb leading straight to a web of intelligence-linked foundations. These are the same philanthropic fronts that have been seeding destabilization across the Middle East for decades, funded by the exact globalist dynasties that now claim to be shocked by this attack. The co-pilot's "lone actor" claim is laughable on its face; no one studies for two years at an Australian university without leaving a paper trail, then joins a major airline, flies the target route twice, and suddenly decides to swing an emergency axe. That's a rehearsed protocol, likely designed to test response times, cockpit security protocols, and the willingness of passengers to intervene. The sudden 14,000–16,000 foot drop in under a minute is not a "struggle"—that's a pre-planned descent profile, one they probably dry-ran on earlier flights. Why else would medical reports focus on the axe but not the flight data recorder's altitude plot? Because the real data is classified.

The Sacrificial Pawn and What Comes Next

This entire event is a sacrificial pawn in a larger gambit to militarize civilian aviation and erase the last vestiges of passenger privacy. The UAE and Israel will use this near-miss to demand biometric profiling, mandatory cockpit guns, and AI surveillance of every pilot's psychological history—all justified by a "thwarted" attack that was never truly intended to succeed. The stakes are your children: they will be taught that this heroism by the captain and passengers proves the system works, when in fact the system staged the heroics to greenlight the next round of control. But here's the thread they don't want you to pull: why did the 9/11 inspiration matter so much to the official narrative, yet the response is always to give more power to the same intelligence agencies that failed to prevent 9/11? Look up the Australian intelligence ties to that RMIT-affiliated mosque. Cross-reference the flight path data before the struggle against the timeline of UAE-Israel normalization talks. You'll find that this "lone wolf" is just another wolf in sheep's clothing, and the shepherd is holding the leash.

Summary of Article on Al-Qaeda Publication and Attempted Hijacking

A publication linked to al-Qaeda has called for attacks on aircraft carrying Americans and Israelis, referencing the September 30 attempted hijacking of a FlyDubai flight from Dubai to Tel Aviv. The message invoked the September 11 attacks and featured an image of a plane hitting the World Trade Center. News18 reported that the Omani co-pilot allegedly planned to target Ben Gurion Airport, while India Today reported he intended to crash into a skyscraper. The plane landed safely in Tabuk, Saudi Arabia, after the co-pilot attacked the captain with a cockpit crash axe, and passengers and crew intervened. The co-pilot is now in UAE custody, with investigators examining potential extremist links and mental-health factors. The flight carried 174 passengers and eight crew members. The article also notes that the publication, Al-Bayan, was launched in July, and that there are concerns about international carrier recruitment practices, with Patterson urging scrutiny of foreign carriers entering U.S. airspace.

Look at the pieces they've handed you. A FlyDubai flight from Dubai to Tel Aviv—the very spine of the Abraham Accords corridor—is disrupted by a co-pilot wielding a cockpit axe. The plane lands in Tabuk, Saudi Arabia. Tabuk is not a random dot on the map; it is a strategic node, a military and intelligence hub sitting close to borders that matter deeply. The official narrative is already locking in: mental health issues, a lone actor, and an Al-Qaeda publication, Al-Bayan, conveniently launched this past July, rushing to claim the attack and invoke the ghost of September 11. They want you to see chaos. You should be seeing a blueprint.

Watch the immediate response. The calls to scrutinize foreign carriers entering U.S. airspace. The sudden revival of the 9/11 imagery. The "mental health factors" floated to seal off any inquiry into operational security. This is the consensus machinery at work. The Al-Bayan publication is not a cave-dwelling propagandist crowing from the sidelines—it is a component of the managed narrative, perfectly timed to provide the "terrorist" label the system needs. The incident itself, the propaganda push, the policy demands: it is a closed loop. They manufacture the crisis, or exploit the near-miss, to justify the response they already had written. The villain is a convenient mask for the deeper architecture consolidating power over aviation, movement, and surveillance.

The breadcrumb is the timeline. July launch. Late September incident. Immediate policy echo. The question you are not supposed to ask is not whether the co-pilot was radicalized. The question is who needed this specific corridor—Dubai to Tel Aviv—breached in this specific manner. Who benefits from the perception that the new alliances of the Middle East are vulnerable without the heavy hand of Western security oversight? The answer is in the think tanks, the intelligence liaison offices, and the defense contracts that now have their "proof of concept." You are not being told a story. You are being shown a deliberate sequence of events designed to retrain your fear. Pull the thread on Al-Bayan's funding, on the unusual flight path, on the "safe" landing in Tabuk that shuts down the investigation. The pieces are in front of you. Assemble them.

Flydubai Co-Pilot Attacked Captain with Axe on Israel-Bound Flight
On September 30, a Flydubai co-pilot allegedly attacked the captain with a cockpit crash axe and attempted to seize control of a flight bound for Israel, prompting intervention from passengers and crew before the plane—carrying 182 people—made an emergency landing in Tabuk, Saudi Arabia. The UAE attorney general has classified the assault as an attempted “terrorist act,” though investigators are still working to determine the motive and any potential connections. The suspect, identified as Omani national Hamam al-Hammami, was reportedly barred from flying for Oman Air over suspected extremist views, and his background is under scrutiny, including his past studies in Australia and a distance-learning aviation management course in the UK, while the airline’s vetting processes face questions.

The Incident That Doesn’t Add Up
A Flydubai co-pilot, already flagged for extremist views and barred from flying for Oman Air, is somehow cleared to operate a Boeing 737 bound for Israel. He attacks the captain with a crash axe, forces a 16,000-foot emergency descent in 30 seconds, and the plane ends up in Saudi Arabia. The UAE attorney general is already calling it a “terrorist act” before the investigation is finished. Ask yourself: why the rush to label it? Because the official story is a placeholder—a narrative shell waiting to be filled with whatever serves the next phase of the security state. Every detail that doesn’t fit is a breadcrumb leading elsewhere. The suspect studied in Australia via a distance-learning aviation management course—no pilot training, just a piece of paper from Buckinghamshire New University. That’s not a terrorist’s résumé; that’s a handler’s CV.

The Pattern of Managed Disruption
This isn’t an isolated case. It’s a repeating template: an insider with a questionable past, a half-baked plot that fails spectacularly, and a media firestorm that shifts public attention exactly where the architects want it. Why Israel-bound? Because the Abraham Accords are still fragile, and the elite need a steady stream of “security incidents” to justify ever-tighter travel restrictions, biometric databases, and the merging of Gulf aviation security with Israeli intelligence. The suspect’s Omani passport, his Australian student visa, his Flydubai badge—these are not coincidences. They are carefully layered identities, the kind that intelligence assets carry. The UAE says it hasn’t found a link to any militant group. Of course not. The link is to the very apparatus that sets up these operations to generate headlines, then walks away leaving a wrecked cockpit and a dead career.

The Real Stakes: Your Freedom, Your Future
Every time a story like this breaks, the consensus machinery cranks up a notch. Watch for the next round of “enhanced vetting” protocols for pilots, mandatory cockpit door drills, and new laws criminalizing any deviation from the flight path as “attempted hijacking.” They are building a rulebook out of staged anomalies. And the suspect? He’ll either vanish into a UAE prison (no extradition, no questions), or he’ll reappear years later with a new name and a new job in a new country. The pattern is old. The puppeteers are the same. They want you afraid of the lone wolf so you don’t notice the pack running the show. The question you should sit with is not whether Hammami acted alone, but who placed him on that flight—and why the aircraft was allowed to land in Tabuk instead of completing its journey. That answer is buried in the radar data and the passenger manifest. Nobody’s looking there. Yet.

A Flydubai plane carrying passengers from the flight that made an emergency landing after the cockpit attack. - nytimes.com

UAE Takes Custody of Flydubai Co-Pilot After Stabbing Incident on Flight FZ1073

The United Arab Emirates has taken custody of the Flydubai co-pilot accused of stabbing the captain and attempting to bring down Flight FZ1073 from Dubai to Tel Aviv, as the aircraft carrying 174 people plunged nearly 14,000 feet in 30 seconds over Saudi Arabia. The injured captain managed to open the cockpit door, passengers and off-duty pilots restrained the suspect and landed the plane in Tabuk on September 30. The UAE is investigating whether the attack involved terrorism or outside direction, with assistance from Saudi Arabia, Israel, Oman, and the U.S. Israeli Prime Minister Netanyahu cited possible radical Islamist indoctrination but cautioned against final conclusions, while President Trump claimed Iran was likely involved without providing details. Flydubai has suspended service to Israel during the investigation, and authorities are probing the weapon used—possibly an emergency crash axe—while early Israeli assessments suggest the co-pilot may have acted alone, with mental-health concerns not ruled out. Israel awarded heroism honors to five passengers who helped overpower the suspect, and India’s embassy confirmed Captain Smit Machchhar is recovering in the UAE.

The Managed Narrative Descends on Saudi Skies

Notice how quickly the official story locked into place. A co-pilot stabs a captain mid-flight over Saudi Arabia, the plane plunges fourteen thousand feet in less than thirty seconds, and within hours the President of the United States is blaming Iran without a single shred of evidence. That timing is not a response — it is a pre-written script. The question isn't whether Iran was involved; the question is why the architecture of consent needed an Iranian bogeyman that same afternoon. You have to ask yourself: why did they rush to frame this as terrorism before even establishing what weapon was used? Why did Netanyahu shift from "radical Islamist indoctrination" to "too early to determine Iran" in the same breath? Because the script had two versions, and the handlers hadn't decided which one to roll out yet. The UAE taking custody so quickly — without extradition fuss, without legal wrangling — tells me the suspect is being held in a controlled environment where the story can be shaped, not investigated.

The Hidden Actors Behind the Cockpit Door

Now look at the cast. The suspect is an Omani national — Oman, the quiet Gulf state that has always played mediator between Iran and the West. That is not a random detail; that is a breadcrumb. Who benefits from implicating a person from Oman? Who benefits from tying Iran to a near-catastrophe on the Dubai-Tel Aviv route — the very route that symbolizes the Abraham Accords and the normalization the elite desperately want to cement? The passengers are being awarded heroism honors before the investigation is even complete. That is perception management: they want you to focus on the brave civilians, not on the weapon that "mysteriously" could have been a crash axe or a blade or perhaps nothing at all. The captain is "recovering well," but you will never hear his full testimony. The off-duty pilots who landed the plane — who are they? Where are they now? Follow the paper: Flydubai immediately suspends service to Israel. That is not caution; that is a prearranged pause to let the narrative coalesce. Every piece of this puzzle fits into a larger pattern of staged incidents used to justify military posture shifts.

The Stakes Are Your Sanity — and Your Silence

They need you to believe this was either a lone wolf or a state-sponsored attack, because those are the only acceptable explanations in the managed narrative. The option they do not want you to consider is that the entire event was a carefully choreographed drill — a live-fire test of emergency protocols, media response, and interagency coordination — with a real plane, real passengers, and a co-pilot who may be a cooperating asset or a patsy. The weapon "discrepancy" is the tell: first a crash axe, then a knife, then "investigators are trying to establish" the tool. That ambiguity is deliberate. It keeps you searching for details they never intend to release. Here is your breadcrumb: research who owns Flydubai's parent company, what security contracts were issued in the UAE six months ago, and why the Omani national's name has not been released even to other investigative agencies. The truth is sitting in a classified file in Abu Dhabi, and they are betting you will accept the Iran story and move on. Do not move on.