← The Signal Report Work with me

Report 262 · Defense Tech

Why one drone sighting can close a runway

On the evenings of 30 and 31 October, drone reports stopped arrivals at Jersey Airport. Flights turned back to the UK, one went to Paris, and the RAF was called in. No operator has been named in any reporting I could find, and at least one drone outlet doubts there were drones at all. Both things can be true at once. Here is why a report, not a confirmed drone, is enough to close a runway, using the playbook Europe's aviation-safety agency wrote for exactly this.

What happened in Jersey

According to a States of Jersey Police statement reported by DroneLife, the first report came in at about 8:20 pm on Friday 30 October, and the drone activity went on until about 10:30 pm, inside restricted airspace and active flight paths. Three inbound aircraft were diverted; one later landed at about 11:45 pm. The next evening, at 20:05 GMT, the airport reported more disruption to inbound flights. A police inspector told the BBC that officers believed "two or three" drones had entered restricted airspace that night and that the activity was not thought to be linked to terrorism. Police appealed for dashcam, doorbell and CCTV footage from the island's west and had not identified an operator.

The Ministry of Defence confirmed to sUAS News that the UK Department for Transport is leading counter-drone measures in Jersey, with the RAF responding to a Military Aid to the Civil Authorities request. Jersey's chief minister, Lyndon Farnham, said the government was "working closely with UK authorities and specialist agencies to explore additional operational support, enhanced detection capability and counter-drone technology."

sUAS News also published the skeptical case: the weather was clear both nights, accounts of how many drones there were conflicted, and in its view the sightings lined up with times aircraft were passing overhead at altitude. That is the outlet's analysis, not an official finding, and it may be wrong. But it is the right question, and the answer explains a lot about how airports handle drones.

Why the runway stops first

The best public explanation is a 2021 manual from EASA, the European Union Aviation Safety Agency, called Drone Incident Management at Aerodromes. Jersey is not in the EU, so this is not its rulebook. It is a clear description of the problem every airport controller faces, written with input from airports, controllers, pilots and police. (Only Part 1 is public. Parts 2 and 3, with the threat-zone maps and response forms, are restricted.)

The core of it fits in four facts from the manual:

  • Controllers have no rule for spacing aircraft from drones. The manual notes that the EU Rules of the Air provide no separation minima between drones and crewed aircraft. Controllers still have to keep traffic safe, so their tools are traffic warnings, wider spacing, a runway change, and finally no more take-off or landing clearances.
  • They usually can't see the drone. Small drones carry no transponder, so they don't appear on the controller's radar display.
  • There isn't much time. The manual points out that a race drone at 80 km/h can go from outside a 5 km protection zone to the runway in under four minutes.
  • A sighting is hard to confirm. In the manual's words, "it is often difficult to confirm reliably a sighting." Drones can't be individually identified, so it's unclear whether one or several were involved, and the pilot is hard to find at airports that rely on people, not sensors, to spot drones.

Put those together and the logic is unavoidable. A controller who gets a credible report in the approach path has no rule that says how close is too close, no radar track to watch, and minutes to act. Stopping landings is the only option that is safe under every version of the facts. The manual says operators "often have no option but to stop or restrict runway operations."

A sighting is not an incident

The manual is careful about words, and the distinction matters for reading the news. A sighting becomes a "drone incident" only once the drone is verified, has no clearance, and is inside the restricted zone around the airport. A sighting that is never verified, or is too far away to matter, is logged as an "occurrence without safety impact." The response is meant to move through stages: gather information, verify it, assess the threat against a map of the airport's zones, and repeat until the threat is resolved.

The catch is that the runway decision often comes before verification can finish. That's why "the airport closed because of drones" and "nobody has proven there were drones" are not contradictions. The closure is a precaution taken under uncertainty. Whether the uncertainty resolves later is a separate question, and in many past cases it never fully does.

Why it costs so much

The manual's benchmark is Gatwick in December 2018: 115 reported sightings over three days, the single runway closed for 33 hours, more than 1,000 flights cancelled and about 140,000 passengers affected, at an estimated cost to the industry of up to €64 million. Short closures add up too. For Europe's ten largest airports, the manual estimates the delay cost of a 30-minute runway closure at €325,000 to €514,000. Germany's air navigation service, DFS, had counted more than 500 drone events since 2015.

That asymmetry is the whole problem. A cheap drone, or a misread light, can impose a six-figure cost in half an hour, and the airport can't refuse to pay it without taking a collision risk it can't measure.

What a counter-drone team adds, from someone who ran jammers

This part is my own experience as an electronic-warfare officer, not the manual. When people hear "the RAF has been called in," they picture a jammer, and a jammer is the least useful part of the picture for this problem. A jammer is an effector. It breaks the radio link between a drone and its pilot, which the manual files under "non-kinetic" measures alongside hacking. It tells you nothing about whether a drone was there.

What actually closes the gap is detection: a sensor that turns "someone saw a light" into a track with a position, a heading and, ideally, a location for the pilot. Each kind has limits I've written about before. Radar has to tell a drone from a bird. RF detectors hear the control link only if the drone is transmitting. Remote ID only works on drones that broadcast it. And a person on the ground looking at a moving light at night has no reliable way to judge its size or distance, which is exactly the kind of report the skeptics say Jersey was running on.

One more caution. If the incidents stop once a military counter-drone team is on the island, that will not prove which side was right. It is consistent with an operator being deterred, and equally consistent with there having been nothing to deter. From outside, you can't tell those apart without the sensor data.

What to watch for

The useful questions for Jersey, or the next airport, are concrete. Was any sighting verified by a sensor, or only by eye? Did detection gear record a track or a control signal? Was an operator found? If the States of Jersey Police or the UK government publish findings, I'll add them here in place, whichever way they point.

Sources

  1. European Union Aviation Safety Agency, Drone Incident Management at Aerodromes, Part 1: The challenge of unauthorised drones in the surroundings of aerodromes, Cologne, 8 March 2021. (Primary source; 35-page PDF read. Source of the runway-restriction logic, the absence of drone separation minima, the transponder and radar point, the 80 km/h and four-minute example, the difficulty of confirming sightings, the definitions of drone incident, sighting and non-kinetic, the response phases, the restricted Parts 2 and 3, the Gatwick and DFS figures, the closure-cost estimates and the quoted phrases.)
  2. Ian McNabb, "Drone Activity Disrupts Jersey Airport for Two Consecutive Nights," DroneLife, 2 November 2026. (Source of the timeline from the States of Jersey Police statement, the diversions, the "two or three" drones and terrorism remarks attributed to the BBC, the police appeal and the chief minister's quote. The BBC reports and the police statement themselves were not opened.)
  3. Ian Hudson, "sUAS News confirmed: RAF deploys to Jersey under MACA request after rogue drone incursions," sUAS News, November 2026. (Source of the Ministry of Defence confirmation about the Department for Transport lead and the MACA request, and of the outlet's skeptical analysis about weather, conflicting counts and overflying aircraft. The analysis is the outlet's opinion.)

The point that a night observer can't judge a light's size or distance, and the section on jammers versus detection, are my own experience and framing, not claims from the sources. EASA's manual is guidance for aerodromes under EU rules; Jersey, a Crown Dependency, is not bound by it, and I use it only to explain the general mechanism.

Onur Oncer
Onur Oncer

U.S. Army combat veteran (Counter-IED / Electronic Warfare), peer-reviewed researcher in microwave spectroscopy, and founder & CEO of Shroombiosis. Consults on laboratory operations, AI, and supplement formulation.

← All reports