Late-evening flights between Portugal and Ireland rarely make headlines. The Boeing 737 carrying passengers from Porto to Dublin on the night of Tuesday, 22 September was, by all appearances, behaving like any other short-haul Ryanair service. It departed Francisco Sá Carneiro Airport at 10.55pm, a mercifully late hour for travellers who hoped to sleep through the short crossing and land in Ireland ready for the day ahead. The aircraft climbed into the dark sky, heading north along the coast, and many of the passengers probably switched off their reading lights and closed their eyes. But somewhere over northern Portugal, just before the flight reached the Portuguese-Spanish border, the ordinary rhythm of the journey was shattered. The aircraft made a sudden U-turn, banked back toward Porto, and, instead of continuing toward Dublin, began a quiet, hurried descent. What had gone wrong? The answer, as it emerged, was alarming in a way that only aviation emergencies can be. The crew had apparently transmitted a universal distress code known as squawk 7500, the signal used to indicate a hijack or an unlawful intrusion into the flight deck. The flight had been airborne for only about fifteen minutes. For the people inside the cabin, there may have been no immediate explanation. The seatbelt signs may have blinked on; the pilot’s voice may have said something reassuring and vague. But far below, air traffic controllers, security agencies, and possibly military authorities were already reacting to an aircraft that had just declared itself in peril. The plane landed back in Porto about thirty-five minutes after takeoff, just before 1am. Ryanair later described the entire episode as a false security report. For the airline, it was a problem to be resolved; for the passengers, it was a night that began with one destination and almost ended before it truly began.
The sequence of events, pieced together from aviation reports, is now relatively clear. Flight FR7073 climbed out of Porto at 10.55pm, bound for Dublin, a journey that normally takes about two hours. After heading north for roughly fifteen minutes, somewhere short of the Portuguese-Spanish border, the aircraft turned around. According to aviation news network Air Live, the captain transmitted squawk code 7500 into the aircraft’s transponder—a four-digit code that, by international convention, immediately tells air traffic control that the flight has been hijacked or that the cockpit is under unlawful interference. The transmission does not necessarily mean a conversation has taken place; it is a silent signal, often used when the crew cannot speak freely. The effect, however, is anything but silent. Once a squawk 7500 code is received, controllers begin emergency protocols, clearing airspace, alerting police, military units, and security services, and preparing for worst-case scenarios. In this case, the flight turned back to Porto and landed without apparent incident. The landing occurred at around 11.30pm local time, some thirty-five minutes after departure, though the exact time was reported as just before 1am in later accounts—likely reflecting a period of taxiing, hold, and on-ground security checks. Thirty minutes later, the same aircraft took off again for Dublin, and it finally landed in Ireland just after 3am. Ryanair later confirmed that the flight had returned to Porto due to a false security report, which, in the airline’s words, was “quickly resolved” before the journey resumed. The total delay was two hours and thirty-three minutes. For a short flight, that is a significant interruption, but for the crews and security personnel who had to assume the worst, it was a small price to pay for an outcome that could have been catastrophic.
To understand why a false security report creates such turbulence, it helps to understand the strange, coded language of aviation transponders. Every commercial aircraft carries a transponder, a device that automatically responds to radar queries by broadcasting identifying information: flight number, altitude, speed, and a four-digit code assigned by air traffic control. That code is normally a squawk, one of a handful of standard settings. A typical code indicates the aircraft is operating normally, while certain codes are reserved for emergencies. The best known is squawk 7700, which means a general emergency. Squawk 7600 indicates a radio failure. And squawk 7500 is reserved for the most serious threat of all: a hijacking or unlawful interference with the flight deck. These codes are not meant to replace verbal communication; they are meant to supplement it, especially in situations where the crew cannot talk openly. A pilot who transmits 7500 is expected to be under duress, perhaps with an intruder in the cockpit. It is a signal designed to bypass the perpetrator and alert ground authorities without making the situation worse. In this case, the trigger was not an actual hijacker but a false security report, a phrase that leaves many questions unanswered. Did someone aboard the plane say or do something that made the crew fear an attack? Did a bag match some hidden profile? Did the crew receive a worrying message from the ground? Ryanair did not specify, and it is possible that the airline itself did not fully understand what had happened until after the aircraft landed. What remains certain is that a code designed to be used only under threat was transmitted, and that every emergency mechanism on the ground responded accordingly. The fact that it was false does not make it trivial. In the world of aviation security, a false alarm is always preferable to an ignored one.
This is not the first time such an alarming false alarm has occurred. In July of the same year, a LOT Polish Airlines flight, Flight 155, operated by Bulgaria’s Electra Airways, was carrying 180 passengers from Warsaw to Tel Aviv when it inadvertently transmitted squawk 7500. That aircraft, too, was not actually under attack. But the response was swift and overwhelming. Israeli authorities immediately scrambled fighter jets to intercept the passenger plane, and Bulgaria and Turkey also launched aircraft to respond to what appeared to be a hijacking in progress. The Israeli military later said the fighters had been dispatched because of a lack of contact with the aircraft; contact was soon re-established, and the plane landed safely in Bulgaria. LOT’s spokesperson, Krzysztof Moczulski, explained that the transponder had been set incorrectly. He called it “most likely human error” and described the episode as an “absolutely exceptional event.” Exceptional it was—but the comparison with the Ryanair flight is difficult to ignore. In both cases, a coded signal intended to protect a flight from a hijacker created a short-lived but very real security emergency. In both cases, no hijacker was found. And in both cases, the aircraft and all of its passengers landed safely. The difference is that the LOT incident involved a simple technical mistake, while the Ryanair incident involved a “false security report,” a phrase that suggests something more than an incorrectly dialled code. Yet the outcomes were the same: a frightened crew, a worried ground control network, and a night that was delayed but ultimately uneventful.
For the passengers on Flight FR7073, however, the experience was deeply human. Imagine sitting in the darkness of a cabin, perhaps watching a film or drifting off to sleep, when the plane begins to turn. You might think the route is changing, that the pilots are avoiding bad weather. But then the descent begins, and the familiar sensations of a landing arrive far too early for a two-hour flight. The aircraft touches down at the same airport you left less than an hour ago. There is no cheerful announcement about a tourist bonus or a layover. Instead, there is silence, followed by the presence of security personnel, police, perhaps even military vehicles around the aircraft. Passengers may be asked to remain seated while authorities board. They may be taken to a terminal room for questioning. They may wait in confusion, wondering whether someone among them was the cause of the disruption. The crew has to manage a situation that is both urgent and uncertain. They have to keep the cabin calm while also taking every threat seriously. In the end, the threat proved to be nothing. But that outcome was not known at the moment of transmission. It was only after the plane was safely on the ground, after the aircraft was thoroughly searched, after every passenger and every piece of luggage was accounted for, that the all-clear could be given. Thirty minutes later, the same plane lifted off again for Dublin, but the passengers did not simply resume their night. They carried with them the knowledge that their flight had been the subject of an emergency response, that their plane had turned back under a hijacking alert, and that they would be arriving late, tired, and unsettled into an Irish morning that had already begun without them.
Such incidents are a reminder of the paradox that lies at the heart of modern aviation security. The same systems that allow aircraft to move safely through crowded skies are also capable of creating immense anxiety at the smallest misstep. A single digit, a misplaced transponder setting, a false report, a misunderstood radio call—any of these can trigger fighter jets, emergency vehicles, and a cascade of protocol that treats every threat as real. It is a philosophy that has made air travel significantly safer than it otherwise would be, but it also means that false alarms are part of the system’s cost. If every squawk 7500 were ignored, a genuine hijacking could go unnoticed. So the system errs on the side of caution, and passengers sometimes pay with delays, lost sleep, and nervous minutes on the tarmac. The Ryanair flight and the LOT flight both ended safely, and no one was harmed. That is the story’s most reassuring thread. But they also show that safety and anxiety are forever intertwined. When a routine flight suddenly turns back, when a code meant for emergencies cuts through the silence of the night, the ordinary world of travel is momentarily visible as what it truly is: a carefully managed attempt to keep hundreds of strangers safe while moving them across the planet. On that September night, the attempt worked. The false report was resolved, the aircraft was cleared, and the passengers arrived in Dublin just after 3am. They were late, but they were safe—and in the unpredictable world of aviation, that is the only outcome that truly matters.