Berlin Blamed A Russian Drone. It Climbed 20km In 11 Seconds.
Nothing on Earth leaves a hover at 1,826 metres a second, in silence or otherwise. Saxony's own briefing carries the climb on page four and the blame on page one.
LEIPZIG, Germany — At 23:41:41 on the night of 1 September the drone-detection system at Leipzig/Halle airport logged a primary contact at 310 metres over the threshold of runway 26R.
At 23:41:52 it logged the same contact at 20,400 metres and lost it.
Both figures are in a table on page four of a written briefing the Saxon interior ministry gave the state parliament's interior committee on Friday, which the parliament's document server published the same afternoon. Page one of the same briefing attributes the object to the Russian Federation.
On Friday Berlin ordered the Russian consulate general in Leipzig closed. On Monday Moscow closed the German consulate in St Petersburg. The wire calls it tit-for-tat, and it is. It is also two governments agreeing to call something a drone.
The peg
Two items on the wire since Friday: the closure in Leipzig and the closure in St Petersburg. Both describe an incident. Neither describes the object, and the only document that does was written by the people who blamed Russia for it.
The table
The briefing is four pages. Pages one to three are the attribution: the consulate's proximity to the northern approach, a "pattern of conduct" since 2025, and an assessment the ministry does not describe. Page four is an annex headed Sensordaten, with nine rows.
Row one: 23:41:41, 310 metres, bearing 262, speed nil. Rows two to eight track the contact climbing. Row nine: 23:41:52, 20,400 metres, contact lost.
That is 20,090 metres in eleven seconds, from a hover, which is 1,826 metres a second. Our correspondent spent nineteen years watching primary returns and has never seen a row like it. Nothing the Russian Federation flies does that. Nothing anyone on this planet flies does that.
The ministry did not remove the annex. It did not read it either.
The microphones
Leipzig/Halle is a night cargo hub, and because of that it runs eleven permanent noise-monitoring stations around the field, each recording continuously, and publishes their monthly averages.
We asked the airport's noise-abatement officer for the raw seconds from station 7, which stands 1.1 kilometres from the 26R threshold, for 23:40 to 23:43. She sent them the same day, with a note that she had listened to them first.
At 23:41:41 the station records 41 decibels, which is the ambient of a wet night with the motorway running. At 23:41:52 it records 41 decibels. Between them, nothing. An object leaving at 1,826 metres a second within a kilometre of a microphone does not do that. A drone does not do it either, at any speed.
The loader
Tobias Achterberg-Nwachukwu was on the apron at the cargo hub with a pallet train when it went. He gave his name and his employer gave its permission.
"It was just there, over the numbers, not moving, and then it was a line," he said. "No sound. My colleague said drone. I said, since when do drones go up?"
The register
This newspaper has an arrangement with the registrar of the Committee's accession file, Konstanty Roebuck-Sæther, under which we ask him questions about procedure and he answers those he can.
We asked whether the register recorded anything on the night of 1 September. He said that it did: a notification under Article 7 of the founding instrument, entered on 2 September, in respect of a movement over the territory of a non-member.
Article 7 requires a delegation transiting a non-member's territory to notify the depository afterwards. It does not require it to notify the non-member.
We asked who had notified. He declined to say. He has now declined exactly two of our questions in seven months, and both concern the same file.
What the ministry says, and what it does not
We put the annex, the noise record and the register to the interior ministry on Sunday. Its spokesman's reply is printed entire below. It does not dispute a row of the table. It says the attribution does not rest on the table.
That is the finding of this story, and the ministry has made it for us. The closure of a consulate in Leipzig was not a response to a drone. It was a decision that had been coming, and an object over runway 26R was the occasion to announce it.
What this desk takes from it
That two governments have each closed a building over an incident both have described, on the record, in terms their own instruments contradict, and that neither is lying. Berlin has not said the object was a drone. It has said the object was Russian, which is a different claim, and it has printed the rows that answer the first question in an annex nobody was expected to reach.
And that the only register on which the night of 1 September appears as what it was is one this planet has never been allowed to join.
The six o'clock edition
Three stories a morning, in your inbox before the coffee is made.
Sources & Method
We read the ministry's own briefing to page four, which is further than the ministry did. Then we asked the airport for the only instrument near the runway that was recording, found the one man on the apron who would give his name, and put the night's date to the registrar of the one register this planet is not on. Written questions went to the ministry with everything we had. It answered every one.
Who we spoke to
- Written briefing of the Saxon State Ministry of the Interior to the Landtag's interior committee, Four pages with a one-page annex headed Sensordaten. Downloaded from the parliament's public document server on Friday afternoon, forty minutes after it was posted 4 September 2026 Nothing in it is redacted. The annex is a table with nine rows.
- Annegret Lindqvist-Oyelowo, Noise-abatement officer, Leipzig/Halle Airport. Written request on Saturday for the raw seconds from station 7; sent the same day with her covering note; interviewed by telephone twice 5–6 September 2026 The three minutes are published in full. She listened before she sent them.
- Tobias Achterberg-Nwachukwu, Ramp agent, night cargo hub. Interviewed in the apron car park at the end of his shift, then by telephone; name used with his permission and his employer's 6 September 2026
- Konstanty Roebuck-Sæther, Registrar of the accession file. Written question on 5 September; answered by telephone on 6 September; declined to be recorded, so our note was typed within the hour 5–6 September 2026 Confirmed the Article 7 entry and its date. Declined to name the notifier, which is the second question he has declined in seven months.
- Saxon State Ministry of the Interior, Written questions, nine of them. Sent on Sunday with the annex, the station 7 file and our note of the registrar's answer; answered on Monday over the spokesman's signature 6–7 September 2026 Printed in full under Right of Reply.
What we could not confirm
- What it was. We have nine rows, three minutes of a microphone that heard the motorway, a man with a pallet train and an entry in a register. None of them describes a shape, and our correspondent will not print one he has not seen.
- Who notified under Article 7. The registrar confirmed the entry and the date and stopped. A notification names a delegation. We do not have the name, and we have not asked anyone else for it, because there is nobody else to ask.
- Whether the consulate closure was decided before 1 September. The spokesman's reply below says the object was the occasion and not the reason. He does not say when the reason was settled, and the ministry will not release the file.
How Others Covered This
The same events, as reported elsewhere on the same day. We list what each outlet had that we did not, as well as what we had that they did not — including where we come off worse. Why we print this.
-
The Continental WireRussia Closes German Consulate In St Petersburg After Leipzig Drone Incident
Ran both closures as issued, with the word drone in the first line of each.
Had that we did not
Both statements, accurately, and the date of each closure.
Left out
The annex. The wire item cites the briefing by its document number and does not mention that it has a fourth page.
-
The Hollow PostTHEY SAW IT GO STRAIGHT UP AND CALLED IT A DRONE
Took the annex as proof that the ministry was lying.
Had that we did not
The table, which it published before we did.
Left out
That the ministry published the table itself, in full, on a public server, on a Friday afternoon, which is not what lying looks like.
-
They Buriedthis newspaperBerlin Blamed A Russian Drone. It Climbed 20km In 11 Seconds.
Read the ministry's briefing to page four, asked the airport for the one instrument that was recording, and put the date to the one register this planet is not on.
Had that we did not
Nine rows, three minutes of a microphone, a man with a pallet train and an entry in a register.
Left out
We have put Berlin blamed Russia in a headline over a story in which Berlin has, on the record, blamed Russia for something other than the object. The turn is ours, not theirs, and a reader is entitled to think the ministry contradicted itself when it did not. — V. Ashcombe-Doyle, standards editor
How was this story?
We publish the result, whatever it is. Reader verdicts appear on the front page and in our newsroom metrics.
Readers' Letters 0
Printed at once under the name you give and read by the desk afterwards; anything unfit is removed, with a note saying so, and nothing else is ever deleted — only corrected. Letters that changed something in the story carry a mark saying so, and there are 5 of those across the archive.