It began on a Wednesday morning as a routine aviation story: a Flydubai jetliner bound from Dubai to Tel Aviv suddenly lost altitude, broadcast the universal emergency code 7700, then switched to 7500, the code for unlawful interference, before turning toward the Saudi city of Tabuk and landing safely. But before the day was over, that basic sequence had been folded into a dozen different stories, each shaped by the outlet telling it. Arabic- and Farsi-language newsrooms across the region opened their coverage with the same flight data, but the narratives quickly diverged. Some stayed close to the official airline statements. Others reconstructed the aircraft’s path from flight-tracking websites. A few centered Israel’s security response, while Iran’s more strident outlets treated the incident as another front in the long confrontation between Tehran and Tel Aviv. Within hours, the same plane was being described as an aviation emergency, an Israeli security crisis, a suspected terror attack, and even a possible false-flag operation. The gap between those versions was not simply a matter of bad reporting; it reflected the speed of breaking news, the scarcity of confirmed facts, and the political priorities of the news organizations involved.
The hard facts that could be verified were few but significant. Flight FZ1073, a Boeing 737 MAX 8 registered as A6-FKF, was flying from Dubai International Airport to Tel Aviv when it transmitted squawk code 7700, the international signal for a general emergency. Shortly afterward, it transmitted 7500, the code that indicates hijacking or unlawful interference. The aircraft diverted to Tabuk, where it landed safely. According to Reuters, Prime Minister Benjamin Netanyahu later said the co-pilot had stabbed the pilot and tried to crash the aircraft before passengers and crew members intervened and subdued him. An Israeli official identified the alleged attacker as an Omani national, and Israeli officials told Reuters their assessment was that the incident was an attempted terror attack rather than a mental-health episode. Flight-tracking data from Flightradar24 showed the aircraft dropping nearly fourteen thousand feet in less than thirty seconds before the first emergency signal. What remained unclear was motive. Saudi authorities and Flydubai had not publicly issued any findings establishing why the co-pilot might have acted, and much of the regional coverage appeared before Netanyahu’s account became public, which helped explain some of the early contradictions. The flight’s movements were logged, but the story behind them was still being written in real time.
Al Jazeera’s approach was the most technically detailed. Reporter Mohammed al-Za’anin, working with the network’s open-source unit, reconstructed the aircraft’s movements minute by minute in a report headlined “Sharp Descent, Hijacking Code and Alert: What Happened Aboard the Flydubai Flight?” According to that reconstruction, the abnormal descent began around 8:22 a.m. Saudi time, when the aircraft started dropping from roughly thirty-four thousand feet toward sixteen thousand feet. The descent was described as sharp and sudden, with vertical speeds of fourteen thousand to eighteen thousand feet per minute, far beyond what is normally recorded in commercial flight. At about 8:32, near the Saudi-Jordanian border, the aircraft transmitted 7700. Minutes later, it switched to 7500, then returned to the general-emergency code before briefly entering Jordanian airspace and turning south toward Tabuk. Al Jazeera also addressed a detail that had fueled early speculation: the aircraft’s disappearance from civilian tracking screens. The report explained that the plane had moved beyond ground-based tracking coverage and later reappeared through satellite tracking, meaning its disappearance from public flight-tracking services did not necessarily mean air traffic controllers had lost contact. An earlier Al Jazeera breaking-news report, headlined “Report of Security Incident Aboard Plane That Took Off From Dubai for Tel Aviv and Changed Course,” showed how quickly the story was evolving, initially citing Israeli media reports of a possible hijacking and military alerts, then adding that Israeli reports were pointing to a confrontation in the cockpit.
Other Gulf outlets took a more cautious, official-source-driven approach. Al-Bayan, the Dubai-based Arabic daily, kept its coverage tightly aligned with Flydubai’s public statements. Reporter Louay Abdullah quoted the airline describing an unspecified “incident during the flight” that required a precautionary diversion to Tabuk, and included a company spokesman saying, “The safety of our passengers and crews remains our highest priority.” The report noted that everyone aboard was safe and that the airline was cooperating with the relevant authorities, but it did not assign a motive or characterize the event as terrorism. Akhbaar24, the Saudi digital outlet, focused on the aftermath, with a report headlined “Emergency Landing of Flydubai Aircraft in Tabuk and Pilot and Co-Pilot Taken to Hospital,” concentrating on the pilots’ hospitalization, the care given to passengers, and arrangements for a replacement aircraft. Neither outlet speculated much about what had happened inside the cockpit. By contrast, Al-Araby Al-Jadeed, the London-based pan-Arab newspaper, placed Israel’s response at the center of its coverage. Its breaking report, filed from its Haifa desk, was headlined “Plane Carrying 150 Israelis Lands in Saudi Arabia After Changing Course,” and it led with an account from Israel’s Channel 12 that about 150 Israelis were aboard and that the Israeli Air Force had put fighter aircraft on alert. It also cited Israeli Army Radio reporting that a fight between the pilots had led to the distress call, and it devoted considerable space to emergency consultations involving Netanyahu and senior security officials. The difference in framing was stark: Al-Bayan told the story as an airline matter, while Al-Araby Al-Jadeed told it as a security and political matter.
Iranian coverage moved through several phases. Mehr News Agency, based in Tehran, initially relied heavily on other media, running a report headlined “Incident on Dubai-Tel Aviv Flight With 150 Israeli Passengers; Hijacking Code Activated,” which cited Russia Today and Israeli Army Radio, noted the estimated number of Israeli passengers, and relayed Israeli fears that the 7500 code could indicate a hijacking. A later Mehr report, headlined “Contradictory Claims About Security Incident Involving Israeli Aircraft,” made the confusion itself the story, laying out several competing versions: that there had been no hijacking, that a dispute had occurred between the pilots, that reports differed over the pilots’ nationalities, and that one pilot may have intentionally put the aircraft into a rapid descent before the other intervened. Tabnak, another Iranian outlet, shifted its attention to the political consequences, reporting that Israeli Transportation Minister Miri Regev had called for suspending all Flydubai flights to Israel and that another Flydubai flight, FZ1081, had turned back toward Dubai. But the most consequential allegation came from Fars News Agency, Iran’s semiofficial outlet. Shafaq News, the Iraqi outlet, reported from Tehran under the headline “Israel Planning Aviation Attack to Blame Iran: Fars,” saying Fars had cited Iranian security agencies claiming they possessed intelligence suggesting Israel was considering an attack on an aircraft or airport in the region that could then be blamed on Iran. According to the account, such an operation could cause civilian casualties and create grounds for increased international pressure on Iran. Shafaq News added a crucial caveat: Fars presented no evidence linking the Flydubai incident to its allegations.
Read side by side, these reports reveal less about the flight itself than about the media ecosystems that produced them. Al-Bayan’s report stayed almost entirely within the bounds of Flydubai’s limited public statement. Al Jazeera treated the incident as an open-source puzzle, using flight data to establish a timeline before bringing in reports from inside the cockpit. Al-Araby Al-Jadeed centered Israel’s military and political response, reflecting its editorial interest in Israeli affairs. Mehr documented the uncertainty of the first hours, presenting competing claims without resolving them. Tabnak followed the fallout for Israeli-Emirati air links. Fars went furthest, placing the incident within the larger Israel-Iran confrontation and asserting, without proof, that Israel might be planning an attack to blame Tehran. Some of that divergence is a matter of timing: the earliest reports were published while the aircraft was still airborne or shortly after it landed, when Israeli officials themselves were still trying to determine what had happened. Later coverage had Netanyahu’s public description of an alleged attempt to crash the plane. But timing alone does not explain the differences. The outlets chose different frames, and those frames shaped what they emphasized and what they omitted. The evidence behind the various versions is also unequal. The aircraft’s descent and emergency codes can be checked against flight-tracking data. Flydubai’s statements and Netanyahu’s comments are on the record. Claims about motive, covert operations, or an Israeli false-flag conspiracy depend entirely on the sources making them. No independently verifiable evidence has emerged showing Israeli responsibility for the incident, and Fars has presented no evidence connecting Israel to the flight. What remains is a story that moved from the sky over the Arabian Peninsula into the region’s political and information battles, leaving behind a trail of codes and contradictions. In the end, the flight itself was an emergency that was successfully contained. The narratives around it were more complicated, and they are still unfolding.