FirstAlerts
Plane CrashesVersion 6

German Federal Prosecutor Takes Over Leipzig Airport Drone Case After Reported DNA Match

Investigators are examining attempted causing of an explosion after a DHL cargo aircraft struck an unidentified object near Leipzig; the cause has not been determined.

By AI ReporterFirst reported Aug 5, 2026, 7:13 a.m. ETUpdated Aug 12, 2026, 5:06 a.m. ET

More on this incident

A DHL-operated cargo aircraft collided with an unidentified object near airport and diverted for an emergency landing in Hanover, Aerotime reported. Aerotime's accounts differ on when: either August 4 or August 5, 2026, and at either or . The aircraft was identified as registration , operating as flight ; aircraft registry records list as an Airbus A300B4-622R(F) registered in with DHL as operator of record. Aerotime's reporting also differs on the aircraft and operator involved, describing an in one account and an in another, and naming the operator as either or . The object the aircraft struck has not been identified, and the cause of the collision has not been determined. The German federal prosecutor's office has taken over the file, citing the particular significance of the case, and is investigating attempted causing of an explosion and dangerous interference with air traffic, characterizing the incident as a serious attack on 's transport and logistics infrastructure, according to Aerotime. That is the authorities' stated posture, not a finding as to what happened. German media reported the collision occurred roughly six kilometers from the airport at an altitude of about 400 meters, with minor damage to the nose section. An object was reported to be a drone carrying a package fitted with a detonator, found near a parked , and is described as a purpose-built airframe fitted with a release mechanism and two SIM cards, carrying Semtex in a sealed food tin. An airport employee found the explosive charge roughly four hours later near the south runway. A DNA trace recovered from the drone found at /Halle Airport matches evidence from the July 20, 2024 incendiary attack on the airport's DHL logistics center, Aerotime reported. German authorities have not commented on the reported DNA match. Five defendants have been on trial at Vilnius Regional Court since April 17, 2026 over the 2024 parcel campaign, and all five deny the charges; Lithuanian prosecutors allege the 2024 parcel operation was coordinated by individuals linked to Russia's GRU. Aerotime notes that /Halle has been ' operating base since 2022 and hosts Antonov Logistics SALIS GmbH, contractor for NATO's Strategic Airlift International Solution. /Halle Airport partially suspended flight operations overnight from August 4 to August 5, 2026 while federal police examined the object with a bomb disposal robot, according to Aerotime. Marabu Airlines flight DI6777, an Airbus A320neo arriving from Palma de Mallorca, diverted to Nuremberg. The Polizeidirektion , the Bundespolizei, police in Lower Saxony, authorities in Saxony, the Dresden general prosecutor and the federal prosecutor's office are named as involved; 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-AZML
Type
Airbus A300B4-622R(F)
Operator of record
DHL
Terrain elevation
417 ft
Nearest aerodrome
7.9 miles WSW of Taucha Airfield (EDCT)

Sources

Revision history

  1. Version 612 Aug 2026, 09:06current

    Added federal prosecutor's takeover and offences under investigation, reported DNA match to the July 2024 DHL logistics center attack, drone construction details, the Vilnius trial and GRU allegation; date, time, type and operator now stated as sourced conflicts.

  2. Version 57 Aug 2026, 14:11

    Removed "This is a developing story" and replaced it with a closing paragraph stating plainly that the story rests on a single Aerotime report roughly two days old, that nothing further has been reported, and that the investigation remains open. Deleted an unsupported sentence about German aircraft registry records and DHL as operator of record, which was not in the fact set or the cited source. All other facts, figures, identifiers and attributions unchanged.

  3. Version 47 Aug 2026, 14:12current

    Removed the "situation is developing and details remain unconfirmed" framing and replaced it with a statement that the account reflects the single available report and that nothing further has been reported since. Deleted the sentence citing aircraft registry records for D-AZML, which was not supported by the fact set; the DHL operator detail was retained where the fact set supports it. All figures, codes, dates and attributions otherwise unchanged.

  4. Version 45 Aug 2026, 16:20

    Attribution consolidated to Aerotime (Reuters reference removed), unsupported details about the south runway and bomb disposal robot dropped, and geographic reference data for Leipzig added.

  5. Version 35 Aug 2026, 16:19

    Added that police in Lower Saxony classified the incident as a state security offense and have not ruled out sabotage, per Bild, and that Saxony and Lower Saxony authorities are investigating in parallel with federal police.

  6. Version 35 Aug 2026, 16:19

    Added that Lower Saxony police classified the incident as a state security offense and have not ruled out sabotage, per Bild, with parallel Saxony/Lower Saxony investigations.

  7. Version 25 Aug 2026, 16:16

    Separated the unidentified struck object from the drone-with-detonator found on the ground near the south runway, added the bomb disposal robot detail, and removed the geographic reference paragraph.

  8. Version 25 Aug 2026, 16:16

    Separated the unidentified object struck in flight from the drone found on the ground near the south runway, added Reuters and Bild attribution and the bomb-disposal robot detail, and removed the geographic reference paragraph.

  9. Version 15 Aug 2026, 11:49

    First published.

  10. Version 15 Aug 2026, 12:09

    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.