Flydubai FZ1073: A 2025 Clip and an Open Motive

A smiling cabin and a big speaker did the rounds as proof that Flydubai flight FZ1073 had just been saved. That clip is more than a year old. The dive, the distress codes and the cut captain are not. The gap between those two facts is where the story still sits.

Flydubai FZ1073: A 2025 Clip and an Open Motive

On the morning of 30 September 2026 a Flydubai jet left Dubai for Tel Aviv. About two hours later it dropped, sent the general emergency code and then the hijack code, and landed at Tabuk in north-west Saudi Arabia. Israeli leaders called it a stopped mass killing. The airline called it a fight in the flight deck and said the motive was not known. A party video then did the rounds as the “after” shot. It was not. Large desks mostly took the Israeli line. Smaller outlets mostly took the old clip and called the day a stage play. Neither reading matches the full record.

The clip that was not this flight

The video that broke the tidy story is easy to describe. A man walks the aisle with a large speaker. Faces are smiling. Seat-back screens are dark. No oxygen masks hang down. The aisle is clean. For a plane that had just fallen thousands of feet, the cabin looked oddly calm.

Sharp eyes then matched the seats, the ceiling and the bins to an older film. Fact-checker Lead Stories, in a piece dated 1 October 2026, traced the clip to August 2025. It had been posted by the Israeli sports channel Sport5. The people in it were members of Israel’s men’s basketball team on the way to the EuroBasket games, not passengers of FZ1073. The original Sport5 post sits more than a year before the Tabuk landing.

Lead Stories tied the false caption to an Instagram post on 30 September 2026, the same day as the flight. IBTimes UK, on 2 October, reported the same match and noted that the seats and overhead bins did not line up with other cabin shots from the diverted jet. The plain answer is the one the checkers gave: two different planes.

The party clip is from August 2025. It shows Israel’s basketball team. It does not show FZ1073.

That finding kills one claim. It does not kill the flight. A wrong label on a sports clip is not a staged crash. People who want a trick often stop at the speaker. People who want a clear terror case often skip the clip. Both leave out half the file. A year-old sports film traveled fast because, in the first hours, clips move faster than captions. Once a false “proof” is in the feed, later real cabin shots get thrown out with it.

What the flight track still shows

The track does not depend on the party clip. Flightradar24, updated through 2 October 2026, puts departure from Dubai at 03:05 UTC. The Boeing 737 MAX 8, reported as A6-FKF, climbed to about 34,000 feet. At 05:21 UTC the height began to jump: a steep drop, a sharp climb, then another steep drop. By about 05:33 UTC the jet was holding near 15,000 feet. It sent 7700, the general emergency code, at about 05:28 UTC near the Saudi–Jordan line. Around 05:35 UTC it sent 7500, the hijack code, turned west, crossed briefly into Jordan, turned back, and headed for Tabuk. Near the airport the code went back to 7700. Tabuk’s airport operator said a distress call asked for an emergency landing.

Those codes are a signal, not a verdict. Someone with the panel chose the hijack code rather than leaving the set on general emergency. That choice is one of the harder facts in the file, and one of the least explained. A 7500 does not prove a planned hijack.

The size of the drop is messier. Reuters described a fall of nearly 14,000 feet in under half a minute. CNN’s written recap put a loss of about 17,400 feet in just under two minutes. A CNN OutFront introduction used a still steeper figure. Planet Today’s 2 October piece, CNN Pilot Questions Flydubai Drop Numbers Israel Cites, noted that CNN pilot Aaron Murphy said some of those first numbers did not make sense, because a drop that fast should have broken the jet apart. Photos after landing showed most of the rudder gone. A missing rudder fits a jet that went past its design speed. It does not name who pushed the nose down.

What Israel said, and how fast

Israeli leaders did not wait for that report. Prime Minister Benjamin Netanyahu said one pilot stabbed the other and “apparently tried to crash the plane with everyone on board.” He named the wounded captain, Indian national Smit Machchhar, and said the captain opened the cockpit door while bleeding so others could stop the attacker. He said passengers had stopped “a 9/11 disaster.” Defence Minister Israel Katz called it an attempted jihadist terror attack.

On 1 October, Netanyahu went further in a Fox News interview, as Reuters reported the same day. He said the co-pilot had gone through “Islamist radical indoctrination,” that the man was suicidal, and that it was still too early to say if there was a link to Iran or to anyone else. He told viewers he did not want to lock a final view yet. The same day he described the escape as “Hollywood on steroids,” a line News18 carried: “You can’t make this up. You can’t believe that it actually happens in real life, but it did.”

“This is Hollywood on steroids. You can’t make this up. You can’t believe that it actually happens in real life, but it did.” — Benjamin Netanyahu, 1 October 2026

Read one way, that line is amazement that a film plot happened in the air. Read another way, it is a gift to anyone who already thinks the day was scripted. The words do not prove a stage play. They do show how fast a raw scare became a story with a villain, a hero, and a near-repeat of 11 September 2001.

The timing sits next to a vote. Israel’s election is set for 27 October 2026. A stopped attack, named as jihad before the airline would name a motive, is useful in a campaign. Use is not proof of invention. Leaders use real fires as well as made ones. The political gain is real. The public proof of a terror plan is not yet in a finished file.

Passenger accounts line up with parts of the Israeli telling, not with an empty cabin. A man filmed with blood on his face said they had held the attackers, were landing at Tabuk, and needed help. Reuters said it had checked cabin video of a wounded captain and a man already held down. That footage does not show the first blow. It does show injury after the fight. Indian officials said Captain Machchhar was recovering. Flydubai chief Ghaith Al Ghaith later said the captain had returned to the UAE after medical clearance.

What the airline and the Gulf states said

Flydubai’s own words are colder. A spokesperson said an altercation took place in the flight deck of FZ 1073 on 30 September. On-duty crew who were riding as passengers secured the plane, diverted it, and landed it at Tabuk. All on board were safe. Two relief jets were sent. Then the line ministers stepped past: “At this early stage, the underlying reasons and motives behind this event are unknown and remain subject to a formal investigation.” A later note from Al Ghaith called it a safety incident and said 172 passengers and crew were safe. Other reports put the passenger count at 174, most of them Israeli. That small gap is for a final list, not a hoax marker.

The UAE’s attorney general, Hamad Saif al-Shamsi, ordered a team to set out the facts, the motive, and whether the event was tied to terror activity or to any plan made in advance. That brief is the opposite of a closed case. Saudi officers held the suspect. A Saudi embassy spokesperson in the United States told NBC it was still not clear if this was a row between the pilots or an attack backed by Iran or the Houthis. Agencies in Israel, Oman, Saudi Arabia, the UAE and the United States are all in the inquiry. A first Saudi reading, as summarized in the running Wikipedia entry, was a deliberate try to crash the jet, with the motive still open.

The man accused in Israeli and press reports is an Omani first officer who had been with the airline for less than a year. He has not, as of 2 October, been convicted. Oman has not rushed to claim him or to clear him. Silence is not a confession and not an alibi. Under the UAE–Israel flying deal, crew from states with no ties to Israel were not meant to operate these sectors. Reports say he fell in that group. If that bar was real, his presence on a Tel Aviv flight is a security miss. A miss can be sloppy hiring. It can also be the crack a plot needs. It is not yet a document that proves either.

The other clips that were not this flight

The basketball film was not the only bad label. Full Fact, on 2 October 2026, checked a window clip said to show the Israel-bound jet in the dive. The ground in the picture matches Dubai Creek, not the Saudi border. The screams, Full Fact said, come from a 2022 film of rough air over the Andes. Picture from one flight, sound from another, caption from a third. A fake BBC bulletin also moved, with a real presenter’s face and a new script blaming Indian officials and Mossad. A familiar set does not make a deepfake true.

In a scare, three kinds of film appear at once: real cabin video from after the fight, old film with a new caption, and stitched fakes. Treat them as one “official video” and you will either believe too much or believe nothing. The basketball clip was pushed as aftermath. On the record we have, it was not a ministry evidence reel. The Instagram post Lead Stories archived is a social account. A government can gain from a mood without having cut the clip. A social account can spread a false caption without a minister in the room.

Who gains, and what that does not prove

Israel’s government gains a clear outside threat before the 27 October vote, a reason to tighten who may fly in, and a story of passengers as heroes. Flydubai has already paused Tel Aviv flights at the request of the authorities. If the inquiry later shows a lone violent man with no outside hand, those gains remain. They do not need a stage play to exist.

A false-flag reading gains a simple villain and a reason to bin passenger accounts. It leans on the old clip, on the “Hollywood” line, and on the speed of the jihad label. It has not produced a paper or a cabin record that shows the dive was ordered from the ground. IBTimes UK, on 2 October, said no credible evidence so far shows the emergency was staged. Iran, named early by some Israeli and American voices and not named by the airline, is in the same open box. Trump said Iran would be hit if a link was shown. Netanyahu said it was too early. A threat before a finding is a political fact. It is not a finding.

The public loses in both rushes. A borrowed sports clip teaches people that cabin video is a game. A terror label issued before the airline’s motive line teaches people that the label is the point.

What large desks left in the last paragraph

Most wire copy reported the diversion, the codes, the safe landing, and the Israeli claim. It was slower to hold the motive open once ministers had spoken, and slower to say in the same breath that the party clip was a 2025 sports film. Fact-check desks did that second job on 1 and 2 October. Breaking news carried the scare. The checkers carried the bad clip. Readers who live in only one of those streams got half a day.

Smaller outlets often did the reverse. They led with the speaker and the dark screens, then treated the track, the rudder and the blood as props. Planet Today’s 30 September piece, Flydubai Cockpit Stabbing: What Leaders Said and What Stays Unsaid, kept the split that still holds: the drop is on the track, the motive is not. The same desk has already had to peel captions off other Israel stories: a Katz line about lasers “above the Earth” retold as a finished orbital cage in this quote-versus-claim piece, and a tithe appeal retold as a tax to the Israeli treasury in the tape check. The FZ1073 party clip is the same move with a higher cost.

What is settled on 2 October, and what is not

Settled

FZ1073 left Dubai for Tel Aviv on 30 September 2026, dropped from cruise, sent 7700 and then 7500, and landed at Tabuk. Flydubai says there was a fight in the flight deck, that riding crew secured the jet, and that the motive is unknown pending inquiry. The captain was badly cut and has since been cleared to return to the UAE. A suspect was held in Saudi Arabia. The rudder was badly damaged. The party clip with the speaker is Sport5 basketball footage from August 2025. A separate window-and-scream clip is Dubai video plus 2022 Andes audio.

Not settled

Who struck first, with what, and why. Whether the first officer meant to crash the jet or lost control in a fight. Whether anyone outside the cockpit knew in advance. Whether the “radical indoctrination” line rests on a record the public can read. Whether the drop-rate figures will stand once the flight recorder is published. Whether the Omani officer should have been on that sector at all.

Until the cockpit voice tape, the data recorder and the charge sheet are public, both the terror label and the stage-play label are ahead of the file. Doubt about a borrowed clip is the check Lead Stories already did. Doubt about a motive named in a day is the gap the airline still prints on its own page.

A jet really diverted. People were really hurt. A year-old basketball film was really passed off as the celebration after. Israeli ministers really named jihad before the airline would name a reason. None of those sentences cancels the others. The next useful document is the recorder, the weapon finding, and the charge. Until then the clean question is the one the codes already force: who set 7500, and what did they think they were telling the ground?

Sources

Original source and date

This piece starts from the 2 October 2026 IBTimes UK report, “‘Faker Than the Moon Landing’: Flydubai FZ1073 ‘False Flag’ Claims Explode After Viral Video Exposed,” https://www.ibtimes.co.uk/flydubai-fz1073-false-flag-claim-debunked-1823302, and from the Lead Stories check of 1 October 2026. The added value is the split between the borrowed clip, the public track, and the still-open motive, checked against Flydubai’s own statement and the Flightradar24 log.

Note for fact-checkers

The 2025 Sport5 basketball match is a published fact-check, not a rumour: Lead Stories, 1 October 2026. The diversion, the 7700 and 7500 codes, and the airline’s “motive unknown” line are on Flightradar24 and on news.flydubai.com. Israeli terror wording is quoted from Netanyahu and Katz; it is a government claim, not a court finding. No public final report on the cockpit voice tape was available on 2 October 2026. This article does not say the emergency was staged, and it does not say a terror plan has been proved. Social posts are not treated as official evidence. Planet Today is an independent desk; readers should weigh the primary links above against any later recorder release.

Post a Comment

What do you think? Share your opinion below – every comment matters! Please be respectful. Spamming or advertising is not allowed.

Previous Post Next Post

Independent desk. No ads. If you stay to the end, the donate link is there.

Follow us on TruthSocial, X-Twitter, Gettr, Gab, VK, Anonup, Facebook and Telegram for interesting and mysterious bonus content!

This piece took hours to check against the primary record. Planet Today has no corporate desk and no ad network behind it. If it was useful, $5 keeps the next one free to read.

Support Planet Today

Contact form

Radio