DHL Boeing 757 Damaged in Contact With Unidentified Object Near Leipzig
German prosecutors and state police have taken over the investigation after a cargo jet was damaged and an explosive-laden drone was found beside the runway at Leipzig Halle Airport.
A DHL was damaged in contact with an unidentified object near , , on 4 August 2026, according to Simple Flying. The event is developing and the cause has not been determined.
Simple Flying reported that the aircraft, registered , was arriving from Marseille Provence Airport and diverted about 130 miles northwest to Hannover Airport, where inspectors found slight damage around the forward section after landing. The phase of flight was recorded as . No injuries were reported. Separately, a quadcopter drone with an improvised explosive device attached was found beside the runway at Halle Airport after a tour guide pushed it to the ground, the outlet reported; testing of the device detected traces of PETN and Semtex, according to NDR, WDR and Süddeutsche Zeitung, as cited by Simple Flying. Airport operations were suspended and the southern runway closed, affecting 19 cargo aircraft and one passenger flight.
Saxony's authorities have described what the aircraft encountered as a "presumed second unidentified flying object" rather than confirming that it was another drone. The Dresden General Prosecutor's Office, the Central Office for Extremism in Saxony and the Saxony state criminal police have taken over the investigation and are attempting to identify the object and determine any links to the explosive-laden drone. That is the authorities' stated posture; no cause or finding has been established. German air navigation provider DFS recorded 18 drone-related incidents at in the first half of 2026, Simple Flying reported.
According to aircraft registry records, is a Boeing 757-23NPCF/W, a twin-engine jet landplane with two Rolls-Royce RB211-535E4 engines, serial number 29330, first flown on 16 December 1998 and 27 years old. The registry lists the operator of record as European Air Transport and the registered owner as Eat Gmbh; the owner of record is not necessarily the operator of the flight, the pilot, or otherwise connected to it. DHL's own published company material describes EAT GmbH as a wholly owned subsidiary of DHL Group within DHL Express, founded in November 2005 and operating from /Halle Airport since spring 2008, with over 1,200 staff and a fleet of Boeing and Airbus freighters. Its listed management board comprises chairman Christoph Hofmann and members Jochen Timm, Malcolm Macbeth, Markus Otto, Oliver Weiss and Srinivas Venkatakrishnan; the investigation has made no finding connecting any of them to this event.
As a matter of record, one earlier case involving the same operator is listed: a Boeing 757 registered D-ALER at Brussels, Belgium, on 16 January 2025, case number DCA25WA098. That history says nothing about the cause of this event. The investigation remains open.
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
Registration
D-ALEU
Type
Boeing 757-23NPCF/W — twin-engine jet landplane
Engines
2x RR RB211-535E4
Built
1998-12-16 (27 years old)
Operator of record
European Air Transport
Registered owner
Eat Leipzig GmbhThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Added the reported phase of flight (climb) to the opening paragraph.
Version 27 Aug 2026, 13:36current
Corrected owner-background paragraph to DHL's published company material (founding date, 2008 start of Leipzig operations, 1,200+ staff, freighter fleet) and completed the list of management board members.
Version 16 Aug 2026, 04:24
First published.
Version 16 Aug 2026, 04:24
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.