Mike
False flags en andere geheime operaties
- Onderwerp starter 100leven
- Startdatum
Mike
Mike
Mike
Here is what we know so far about Flydubai Flight FZ1073 from Dubai to Israel:
1- The plane was carrying Israelis. No reports say whether they were ordinary Israeli citizens or Israeli army personnel vacationing in the UAE.
Israeli army personnel have previously posted about vacations in the UAE following their service in Gaza (photo 1)
2- The Flydubai pilot was an Indian Hindu named Smit Machchhar. Initial Hebrew media reports described him as Emirati citizen.
3- The co-pilot is Omani. He allegedly stabbed the pilot and attempted to dive and crash the plane with Israeli passengers, resulting in a fight between the 2 pilots. Smit eventually managed to unlock the cockpit door.
4- Passengers intervened and subdued the Omani co-pilot, while additional pilots aboard the flight took control of the plane and landed it safely at Tabuk Airport in Saudi Arabia.
5- The Israeli passengers received care from a Saudi crew after landing in Saudi Arabia.
6- The Emirati based Indian pilot, Smit Machchhar, was hospitalized after suffering stab wounds, but his condition has not been officially disclosed.
The Omani co-pilot was arrested, and Saudi authorities are interrogating him. Mossad is reportedly involved in the broader investigation, but there is no confirmation that Mossad interrogated him in Saudi Arabia. (Hebrew media)
7- Israeli media initially reported that El Al was planning to evacuate the Israeli passengers from Saudi Arabia to Israel, which would have marked the first overt El Al flight between the 2 countries. However, reportedly Flydubai later sent a replacement aircraft that evacuated the Israeli passengers from Tabuk, Saudi Arabia, directly to Israel.
Mike
1- The plane was carrying Israelis. No reports say whether they were ordinary Israeli citizens or Israeli army personnel vacationing in the UAE.
Israeli army personnel have previously posted about vacations in the UAE following their service in Gaza (photo 1)
2- The Flydubai pilot was an Indian Hindu named Smit Machchhar. Initial Hebrew media reports described him as Emirati citizen.
3- The co-pilot is Omani. He allegedly stabbed the pilot and attempted to dive and crash the plane with Israeli passengers, resulting in a fight between the 2 pilots. Smit eventually managed to unlock the cockpit door.
4- Passengers intervened and subdued the Omani co-pilot, while additional pilots aboard the flight took control of the plane and landed it safely at Tabuk Airport in Saudi Arabia.
5- The Israeli passengers received care from a Saudi crew after landing in Saudi Arabia.
6- The Emirati based Indian pilot, Smit Machchhar, was hospitalized after suffering stab wounds, but his condition has not been officially disclosed.
The Omani co-pilot was arrested, and Saudi authorities are interrogating him. Mossad is reportedly involved in the broader investigation, but there is no confirmation that Mossad interrogated him in Saudi Arabia. (Hebrew media)
7- Israeli media initially reported that El Al was planning to evacuate the Israeli passengers from Saudi Arabia to Israel, which would have marked the first overt El Al flight between the 2 countries. However, reportedly Flydubai later sent a replacement aircraft that evacuated the Israeli passengers from Tabuk, Saudi Arabia, directly to Israel.
Mike
Mike
Mike
Mike
> Netanyahu expected to lose election
> He’s still facing 7 criminal charges
> He takes a trip to the UAE this week
> He returns to Israel after 6 hour meeting
> He warns of terror plot before elections
> Iranians respond saying they are not planning attack & Netanyahu is just trying to cancel the elections
> 24 hours later flight FZ1073 takes off from UAE to Israel
> Attempted hijacking & 9/11-style terrorist attack on flight
> Israeli special ops on board thwart attack
> Netanyahu immediately convenes security cabinet meeting
All too predictable…
Mike
> He’s still facing 7 criminal charges
> He takes a trip to the UAE this week
> He returns to Israel after 6 hour meeting
> He warns of terror plot before elections
> Iranians respond saying they are not planning attack & Netanyahu is just trying to cancel the elections
> 24 hours later flight FZ1073 takes off from UAE to Israel
> Attempted hijacking & 9/11-style terrorist attack on flight
> Israeli special ops on board thwart attack
> Netanyahu immediately convenes security cabinet meeting
All too predictable…
Mike
Mike
|The Flydubai False Flag: Israel’s Clown Show to Blame IranThe official narrative is already collapsing. And the actors are tripping over their own script.
First, the setup.
Israeli intelligence leaks: “A few days ago, we received intelligence indicating that Iran is planning to hijack or shoot down a U.S. passenger plane.”
Translation: They told you an attack was coming. Then an “attack” happened. Convenient. Predictable. And entirely fabricated.
Then, the casting call.
Israeli Channel 12: “Authorities are investigating the possibility that the Omani pilot held dual citizenship, which allowed him to board the flight to Israel. Sources indicate that he had been working for the company for less than a year.”
So Mossad the agency that can sniff out a Hamas tunnel from 50 meters underground, that can assassinate a scientist in Tehran, that can plant a pager bomb in a Hezbollah commander’s pocket somehow missed the fact that a pilot with dual citizenship, working for less than a year, was an Iranian agent?
Mossad can find a needle in a haystack. But it couldn’t vet the pilot of a flight to Tel Aviv?
This is not intelligence. This is a children’s story. And they expect you to clap.
Now, the real plan.
Iranian intelligence sources: “Mossad is planning a terrorist operation in the region, potentially targeting an aircraft or airport, and intends to attribute responsibility to Iran in an effort to create a new wave of international pressure and consensus against the country.”
This is not a theory. This is a warning. Iranian intelligence is actively working to prevent it. And the Flydubai incident is the first attempt.
The missing rudder. The 14,000-foot drop in 30 seconds. The 7500 code. The contradictory explanations: “pilot brawl,” “stabbing,” “hijacking,” “terror attack.”
No Iranian link. No evidence. Just Netanyahu and his media dogs barking “Iran.”
Why now? Because Netanyahu is desperate.
Elections are in four weeks. He cannot secure 61 seats. His rivals cannot form a government either. The political system is deadlocked.
So he needs a security crisis.
Link Flydubai to Iran. Create a case against Iran. Then, if the crisis escalates, shift the election from domestic politics to military confrontation. It’s the oldest trick in the book: when you can’t win on your record, start a war.
And the claims that Iran will “pay a heavy price” are now appearing in the child-killers’ media. They are preparing the ground for another attack on Iran. Another false flag. Another war.
The warning you must hear:
If they cannot sell the Flydubai story, they may target flights from third countries Pakistan, Russia, or even China. They want a bigger stage. They want a global crisis. They want to drag the world into their war.
Iran must crush this vampire before it rises.
The world must see the clown show for what it is.
Netanyahu is not a leader. He is a fugitive. He is a war criminal. He is a fraud.
And this false flag the missing rudder, the made-up pilot, the pre-written intelligence report is his last gamble.
Don’t believe the narrative. The real terrorists are in Tel Aviv. The real threat is Mossad. The real danger is Netanyahu.
And the passengers on Flydubai FZ1073 were not victims of Iranian terrorism. They were victims of Israeli theater.
Mike
• A few days ago, Netanyahu met with MBZ in the UAE.
• Netanyahu held a meeting with 10 countries, including Saudi Arabia and Oman.
• Today, an attempted hijacking of a "Flydubai" plane occurred, with an Omani pilot and Israeli passengers on board.
• The plane made an emergency landing in Saudi Arabia.
Everything is planned.
Mike
• Netanyahu held a meeting with 10 countries, including Saudi Arabia and Oman.
• Today, an attempted hijacking of a "Flydubai" plane occurred, with an Omani pilot and Israeli passengers on board.
• The plane made an emergency landing in Saudi Arabia.
Everything is planned.
Mike
Mike
Mike
Mike
Mike
Mike
Mike
BREAKING: flydubai FZ1073, Dubai to Tel Aviv
Nobody kicked that cockpit door in.
That line is already racing around the internet. It is also the wrong line. A Boeing 737 MAX flight-deck door is certified so people in the cabin cannot force it open. If anyone from the cabin got onto that deck over northwest Saudi Arabia, one of two things happened. Someone inside unlocked it. Or a crewmember who knew the airline emergency code typed it, the 30-to-60-second timer ran out, and nobody hit DENY before the five-second unlock window. Random passengers do not know that code. Deadheading company pilots do. Flydubai itself says on-duty company crew already travelling on the flight secured the aircraft and landed it.
Here is what is solid.
On 30th September 2026, flight FZ1073 left Dubai at 03:05 UTC for Tel Aviv on a 737 MAX 8 registered A6-FKF. About two hours later the jet left cruise. Flightradar24’s tight sample shows a drop from 30,875 feet to 16,750 feet in 29 seconds. That is more than 14,000 feet in half a minute. A wider window used by CNN and BBC is different: about 17,000 to 17,400 feet net from around 34,000 feet in under two minutes. Those are two measurements, not one dramatic number. The aircraft then climbed, dropped again, and wandered near 15,000 feet. It transmitted squawk 7700, then 7500, then 7700 again. It briefly entered Jordanian airspace, turned back, and landed at Tabuk around 06:45 UTC. Israel scrambled fighters after the unlawful-interference code. Tabuk’s airport operator says both the captain and the co-pilot were hurt and taken to hospital. All passengers were accounted for. There were no passenger fatalities. The airline says there was an altercation in the flight deck and that motives remain under investigation.
Here is what is not solid yet.
Israeli leaders later described a stabbing and an apparent attempt to crash the aircraft. Early the same day, a PMO spokesman told Reuters it was not believed to be a hijacking. Those are official statements. They are not a closed investigation. Flydubai has not confirmed a knife, a crew nationality, or a motive. Named passenger accounts and TV briefings point toward a fight between the operating pilots, with help from people who then entered the deck. That is the working public story. It is not a charge sheet. Claims that a named first officer carried out a planned political crash, or that civilian passengers alone landed the jet, go past what the operator and the public record have locked down.
One timing detail matters. The hard dump starts around 05:21 UTC. The first emergency squawk shows at 05:28:48. Roughly seven minutes. That gap fits a cockpit already in chaos before anyone could reach the transponder. It also fits enough time for an emergency-code cycle. It does not tell you which door path fired.
Germanwings is the wrong analogy if you use it as a copy. There, the first officer locked the captain out and the door did what post-9/11 hardening was built for: keep a cabin-side threat outside. On FZ1073 the danger was already inside the protected volume. The two-person rule does not solve two pilots fighting in a closed deck. The residual layer becomes whoever is in the forward cabin with the procedure, and whether anyone inside can still reach DENY.
A same-day “second diversion” claim on another flydubai Tel Aviv flight was a tracking glitch. Strip that off the pile.
So the honest ultra is not a hero movie and not a finished terror verdict.
It is this: a violent flight-deck altercation on an Israel-bound jet, an extreme altitude excursion on public ADS-B, distress then unlawful-interference codes, a safe landing at Tabuk with both pilots hospitalised, an airline that still says motives are unknown, and a cockpit door that could only have opened by the system’s own allowed paths, not by force.
The hard lesson is not “build a thicker door.”
It is what happens when the last safety layer is a timer, a code, and the people sitting just outside.
Mike
Nobody kicked that cockpit door in.
That line is already racing around the internet. It is also the wrong line. A Boeing 737 MAX flight-deck door is certified so people in the cabin cannot force it open. If anyone from the cabin got onto that deck over northwest Saudi Arabia, one of two things happened. Someone inside unlocked it. Or a crewmember who knew the airline emergency code typed it, the 30-to-60-second timer ran out, and nobody hit DENY before the five-second unlock window. Random passengers do not know that code. Deadheading company pilots do. Flydubai itself says on-duty company crew already travelling on the flight secured the aircraft and landed it.
Here is what is solid.
On 30th September 2026, flight FZ1073 left Dubai at 03:05 UTC for Tel Aviv on a 737 MAX 8 registered A6-FKF. About two hours later the jet left cruise. Flightradar24’s tight sample shows a drop from 30,875 feet to 16,750 feet in 29 seconds. That is more than 14,000 feet in half a minute. A wider window used by CNN and BBC is different: about 17,000 to 17,400 feet net from around 34,000 feet in under two minutes. Those are two measurements, not one dramatic number. The aircraft then climbed, dropped again, and wandered near 15,000 feet. It transmitted squawk 7700, then 7500, then 7700 again. It briefly entered Jordanian airspace, turned back, and landed at Tabuk around 06:45 UTC. Israel scrambled fighters after the unlawful-interference code. Tabuk’s airport operator says both the captain and the co-pilot were hurt and taken to hospital. All passengers were accounted for. There were no passenger fatalities. The airline says there was an altercation in the flight deck and that motives remain under investigation.
Here is what is not solid yet.
Israeli leaders later described a stabbing and an apparent attempt to crash the aircraft. Early the same day, a PMO spokesman told Reuters it was not believed to be a hijacking. Those are official statements. They are not a closed investigation. Flydubai has not confirmed a knife, a crew nationality, or a motive. Named passenger accounts and TV briefings point toward a fight between the operating pilots, with help from people who then entered the deck. That is the working public story. It is not a charge sheet. Claims that a named first officer carried out a planned political crash, or that civilian passengers alone landed the jet, go past what the operator and the public record have locked down.
One timing detail matters. The hard dump starts around 05:21 UTC. The first emergency squawk shows at 05:28:48. Roughly seven minutes. That gap fits a cockpit already in chaos before anyone could reach the transponder. It also fits enough time for an emergency-code cycle. It does not tell you which door path fired.
Germanwings is the wrong analogy if you use it as a copy. There, the first officer locked the captain out and the door did what post-9/11 hardening was built for: keep a cabin-side threat outside. On FZ1073 the danger was already inside the protected volume. The two-person rule does not solve two pilots fighting in a closed deck. The residual layer becomes whoever is in the forward cabin with the procedure, and whether anyone inside can still reach DENY.
A same-day “second diversion” claim on another flydubai Tel Aviv flight was a tracking glitch. Strip that off the pile.
So the honest ultra is not a hero movie and not a finished terror verdict.
It is this: a violent flight-deck altercation on an Israel-bound jet, an extreme altitude excursion on public ADS-B, distress then unlawful-interference codes, a safe landing at Tabuk with both pilots hospitalised, an airline that still says motives are unknown, and a cockpit door that could only have opened by the system’s own allowed paths, not by force.
The hard lesson is not “build a thicker door.”
It is what happens when the last safety layer is a timer, a code, and the people sitting just outside.
Mike
Forum statistieken
