From 7700 to 7500: The Flydubai Emergency Landing at Tabuk and Four Conflicting Accounts of One Incident

No transponder code is ever visible in the sky. But when 7700 and 7500 light up in sequence on the same flight, they stop being merely technical signals. They become the opening of an international incident, every step of which later turns into a matter of verification. A Flydubai flight bound from Dubai to Tel Aviv first broadcast 7700 in the air — the code for a general emergency. The code then changed to 7500, which signals unlawful interference with the aircraft. By the clock, the aircraft descended roughly fourteen thousand feet in barely thirty seconds. It finally landed at Tabuk airport in Saudi Arabia. What emerged in the hours after that landing is not the account of one incident. It is the account of at least four mutually contradictory incidents. And when those four accounts sit side by side inside the same news story, only one question is really left in front of the reader — which one is true, and who is saying it? The incident occurred on a route where politics and aviation are threaded on the same string. Dubai to Tel Aviv — the United Arab Emirates to Israel. Even after relations between the two countries normalised, every detail of such a flight remains diplomatically sensitive. On top of that, when the aircraft lands on Saudi soil, three states — the Emirates, Israel and Saudi Arabia — are pulled into the same event. Under international aviation rules, when an aircraft makes an emergency landing on another country's territory, a complex process of responsibility and information-sharing runs between that country's authorities, the operating company, and the state of registration. Every step of that process carries legal caution, and that caution is precisely why initial statements usually give the least information. Flydubai's first words were brief and careful — an incident occurred, the aircraft landed safely. There is a hint buried in that language. The airline is not yet certain what actually happened. And when an airline itself is not certain, the burden of verifying whatever everyone else says falls onto the reader's shoulders. In the first few hours of an emergency landing, the information that arrives is almost always incomplete. The only reliable sources — the cockpit voice recorder, the flight data recorder, and the official investigation — all take time. That empty stretch of time gets filled by testimony, speculation, and claims carried by unnamed sources. Now to those four accounts, which read together explain why reaching a conclusion right now is dangerous. One account says there was a fistfight between the two pilots in the cockpit. In this version there is no weapon, no attempted hijacking. There is only professional conflict that slipped out of control. Another account is graver. It says the co-pilot stabbed the pilot. This is where a dramatic image surfaces — a photograph of a blood-covered passenger, which spread across social media within hours. A third account walks a different path. It says this was a suicide attempt, in which someone tried to deliberately put the aircraft into the ground. And the fourth account is the heaviest. It speaks of a possible terror attack or an attempted hijacking takeover, foiled by a passenger's intervention. Behind these four versions sit different sources, different interests, and different standards of verification. Of the four, the fourth — the passenger-hero story — is the most attractive, because it carries drama, the extraordinary act of an ordinary person. Newsrooms love that shape. But the story that feels best is often the least verified — a rule worth keeping in mind. Who took the photograph of the blood-covered passenger, and when — that is not certain. Reuters stated plainly that it could not independently verify the image. In other words, the item that spread the most is the item that was verified the least. Such an inversion does not happen by accident. When an image spreads before it is verified, there is usually a demand behind it — the audience's emotion, and the newsroom's speed. The phrase "terror attack" has an even narrower source. It comes via three Israeli officials who were not named. Neither Flydubai nor the Saudi authorities have confirmed that label. In other words, the largest accusation rests on the weakest source. This is where the question of sourcing becomes most urgent — who is the information coming from, and what does that source stand to gain? Reuters is an international news agency, yet even it drew a limit around its own reporting — "could not be verified." The passenger testimony and photograph arriving via Israeli media are mid-tier sources, unverified. And the terror claim carried by unnamed officials is the weakest source of all, because it has no public, accountable backing. The technical side of an aviation emergency deserves to be seen separately here. Code 7700 is used for a general emergency — mechanical failure, a medical crisis, or any danger. Code 7500 is used only when there is unlawful interference inside the aircraft. The difference between these two codes is the very centre of this incident. The shift from 7700 to 7500 means the pilot judged that the situation had turned from ordinary danger into criminal interference. But what the pilot judged and what actually happened are not the same thing. A transponder is a record of the pilot's decision, not of the truth. And the descent of fourteen thousand feet in thirty seconds is the hardest and most verifiable data point of all. It can be matched against flight-tracking records. But even this hard fact does not explain the cause. It only says the aircraft descended fast. Why it descended, the number does not say. This is where the counter-argument arrives, the one usually skipped. We tend to assume that when an event happens, it has one true version, and journalists gradually approach that truth. But this incident is walking the opposite way. The event is fixed — it has happened. But the accounts keep multiplying, and each new account fails to match the one before. The Israeli prime minister's spokesperson first said something cautious — this is not a hijacking, it is a different incident. But moments later, other officials began speaking of a possible terror attack. Two arms of the same state are giving two different readings of the same event. In journalism's language this is a crisis. In analysis's language it is a signal — the state narrative has not yet settled. Another gap appears over the pilots' nationalities. Early reports gave different nationalities. This kind of inconsistency proves the information is still emerging from a preliminary, unverified environment. When a report cannot even agree on a basic identity, how durable its deeper explanation will be is easy to guess. And the biggest question usually nobody asks — who gains from this news race? A news organisation gains from speed — the advantage of being first. A state gains from the account that supports its political position. And an airline gains from the language that keeps it free of liability. These three interests are active at the same time. That is precisely why the photograph spread unverified, and why the word "terror" was used without a document. What is needed now is not faster news — it is slower truth. Over the coming days, a few things should be watched. The final investigation report — when Israel, Saudi Arabia or the Emirates officially confirms or dismisses the terror claim. The evolution of Flydubai's statement — when the airline moves from the word "incident" toward a specific cause. And the verification of the photograph — if confirmed, the account of passenger heroism strengthens; if debunked, that account collapses. The transponder code 7500 burned for a few minutes. But the stories born from those few minutes will burn far longer. Some as truth, some as falsehood. And the work of journalism is to separate which is which — not by painting a picture, but by holding to the documents.