- Category
- World
German Police Suspect State Interference After Drone Disrupts Hanover Airport

An unidentified drone intrusion triggered repeated runway and airspace closures at Hanover-Langenhagen Airport, Der Spiegel reported on August 11.
This prompted German authorities to investigate a potential foreign state-sponsored attack.
We bring you stories from the ground. Your support keeps our team in the field.
The airspace breach follows a security incident on August 4 at Leipzig Airport, where an FPV drone carrying a Semtex explosive charge struck the wing of a Ukrainian Antonov An-124 cargo aircraft near its fuel tanks. The drone failed to detonate upon impact and lay unnoticed on the tarmac for four hours before being discovered by a tour bus driver.
US and German officials have linked the failed strike to Russian intelligence services. The incident, occurring at a key European logistics hub frequently used for NATO military transport, has heightened concerns that foreign state actors are conducting hybrid attacks against critical aviation infrastructure.
The incident at Hanover-Langenhagen Airport caused significant disruptions over two hours, forcing the diversion of a cargo aircraft and the postponement of multiple scheduled departures and landings. The intrusion comes as investigators are already working frantically to uncover the origins of a suspected drone attack at Leipzig/Halle Airport just days prior.

An internal police report obtained by Der Spiegel noted that given the targeting of critical infrastructure, “the presence of hybrid activity cannot be ruled out.” The term “hybrid activity” refers to incidents where foreign state actors deliberately interfere with public or critical infrastructure.
While the report stated it is currently unclear if there is a direct connection to the Leipzig drone attack, the similarities are raising major security concerns.
Crucially, the Hanover incident exposed vulnerabilities in the airport’s defenses. The report revealed that the Federal Police (Bundespolizei) were unable to protect the airport using their existing anti-drone technology, Der Spiegel noted.
Although airport employees repeatedly spotted the drone visually, the Federal Police’s warning systems registered nothing. Despite having a drone detection device actively in operation, no alerts were triggered.
German Air Traffic Control (Deutsche Flugsicherung) was also unable to track the device on its radar. Because the drone bypassed all technical detection measures and remained airborne for approximately two hours, the Federal Police strongly suspect the device was not a standard commercial drone, Der Spiegel wrote.

The disruption began when an employee at the freight company DB Schenker first spotted the drone hovering about 25 meters above the firm’s premises, inside the airport’s strict no-fly zone. Authorities immediately closed the southern runway and rerouted air traffic. Shortly after, several police patrols visually confirmed the drone near the airport perimeter, prompting authorities to place the entire facility under lockdown at around 4:00 a.m.
Although officials briefly reopened the northern runway after the drone appeared to drift away, the threat quickly returned. At 4:21 a.m., the drone reappeared directly over the TUI Fly building before hovering above the active apron, forcing another immediate halt to all flight operations.
Der Spiegel reported that the drone was last spotted around 4:40 a.m. over several freight forwarding sites, with the airport finally resuming normal operations at 5:20 a.m.
In the wake of the previous Leipzig incident, Germany’s main aviation industry association (BDL) praised the rollout of anti-drone defenses across the country’s eight designated critical airports. BDL Managing Director Joachim Lang noted that political decisions to centralize drone detection under the Federal Police and install specialized modular equipment were enacted at “light speed,” leaving Germany “exceptionally well-positioned by international standards.”
Discuss this article:
-9a7b3a98ed5c506e0b77a6663f5727c5.png)
-72b63a4e0c8c475ad81fe3eed3f63729.jpeg)


-c439b7bd9030ecf9d5a4287dc361ba31.jpg)


