Reading Squawk 7700: How a News Story About an Emergency Landing Became 'True' Before It Was Verified

A transponder signal lights up in the sky — 7700. In aviation, those four digits mean one thing: a general emergency. If the signal becomes 7500, it means 'unlawful interference' — a hijacking. A Flydubai flight was flying from Dubai toward Tel Aviv. Before it reached its destination, it landed at Tabuk airport in Saudi Arabia. What followed was not a single event but a story that began to emerge in several versions on the same day, from different mouths.

The media's job is to verify, then report. But in emergency news, time is so short that verification often falls behind. With this flight, that is exactly what happened.

Context

The aircraft was a Boeing. Among the passengers were ordinary people — some travelling for work, some returning to family, some perhaps coming back at the end of a holiday. Suddenly an announcement came: the plane was being turned around. According to the information that surfaced in reports, the aircraft descended nearly 14,000 feet in about 30 seconds. By normal landing standards, that rate is unusually fast. Then the wheels touched down on the Tabuk runway.

The destination was Tel Aviv, but the landing was in Saudi Arabia. That single fact makes the event geopolitically sensitive. The Dubai–Tel Aviv route, with Saudi Arabia in between — the event stands at the meeting point of three different administrative and diplomatic spheres. So the story becomes not only a security matter but a symbolic one.

Core analysis: four versions of one event

Here is the biggest inconsistency. At least four different accounts emerged at the same time.

The first version says there was a fistfight between two pilots in the cockpit. The second claims a co-pilot was attacked with a knife. The third says the plane was forced down, possibly connected to a suicide attempt. The fourth describes the matter as an attempted hijacking or takeover of the aircraft.

Four versions — none matches another. One version excludes another. A fistfight is not a stabbing; a suicide attempt is not a hijacking. Yet all were broadcast with equal confidence.

What is happening here is an information crisis. In announcing the event, some are choosing the most dramatic version available to them rather than holding on to the patience of verification. This is nothing new in the media world, but the cost is always the same — the reader's trust.

The photo and anonymous sources

A photo circulated with the event, showing a blood-covered passenger. The US-based news agency Reuters stated clearly that it could not independently verify the photo. In other words, even the visual evidence is not certain here.

Then comes the 'terror attack' theory. But it is worth noting where this claim comes from. It comes from anonymous sources — three Israeli officials whose identities were not disclosed. Neither Flydubai nor Saudi authorities confirmed the theory.

There is another inconsistency. A spokesperson for the Israeli Prime Minister's office first said this was not a hijacking but 'a different incident'. But later, other officials began saying it could be a 'possible terror attack'. Two statements from the same government — one cautious, one dramatic.

There was also conflicting information about the pilots' nationalities. Such hesitation at an early stage is very common. But it means the core sources of the event had not yet stabilised.

Why the 'hero passenger' story spreads so fast

There is a deep psychological dimension here. 'An ordinary passenger stopped a knife-wielding attacker' — this narrative is structurally very attractive. It contains fear, heroism, and instant release. The human mind accepts such a story quickly.

But the relationship between a narrative's appeal and the truth is not always one-to-one. What seems to us a beautifully woven story is often built on a lack of verification. When the core source, timeline, and cause of an event all remain unclear, the narrative the media chooses is often not the event's true form but its most 'story-worthy' form.

With this flight, that is exactly what happened. Within hours, a complete narrative had taken shape — yet not a single part of it had been officially confirmed.

Where the risk lies

The biggest risk is not in the event but in the information flow. The first few hours of emergency news are the weakest. Sources are few, verification time is zero, and competition is fierce. So the chance of misinformation spreading is highest.

The second risk is the instability of official statements. When two branches of the same institution say two different things, it shows the narrative is still being built. And a narrative in the making is the most likely to be reversed later.

The third risk is reliance on anonymous sources. 'Three Israeli officials' said so — the more firm this sentence sounds, the weaker it is, because no one is taking responsibility for it.

What we should do

The lesson here is for the news consumer as much as the news producer. First, the claims of the first few hours should not be taken as final truth. Second, a photo is not proof — especially when the news agency itself admits the limits of verification. Third, the inconsistency within official statements is itself information the reader needs to know.

Looking ahead

The question is now in the hands of the investigation. The Tabuk runway, Boeing's flight data, the cockpit voice recorder — these three sources may together produce a timeline that does not fully match any of the four versions. History has seen this happen again and again.

And until then, the signal remains — 7700, sometimes 7500. These numbers in the sky announce an emergency, but they do not explain the cause. The investigation explains the cause. And the pace of investigation never matches the pace of news. Perhaps that is the biggest truth of this event — that the most dramatic version of an event is the least verified.