A Danish military correction offers a useful case study for UAP researchers: changing the time of an event can change the comparison with known aircraft, even when officials retain their target assessment. The Defence Command's October 1, 2026 notice revisits gunfire at Borris on September 28, 2025. This article reviews that released correction; it is not a new November incident.

What changed in the record

The five-page reassessment moves the estimated firing interval from approximately 20:20 to between 20:06 and about 20:08. It cites a video recorded at 20:06 and a logged telephone call at 20:07:57, assessed to have followed the shooting. The document acknowledges that other parts of the sequence cannot be timed precisely enough.

The earlier timeline had been used to argue that no relevant aircraft passage coincided with the firing. With the correction, Defence Command accepts that an overlap with a civilian aircraft's passage cannot be excluded. That is a substantive change to the event reconstruction.

What the correction does not settle

The official notice retains the assessment that soldiers fired at one or more objects probably consisting of drones. It cites reported movement, direction and height, along with the soldiers' statements that they did not fire at an aircraft. The unit was guarding Ukrainian trainees. Those are the military's reported observations and assessment, not independently reproduced identifications.

The report separately gives its safety reasoning: the civilian aircraft's lowest altitude over the range was approximately 2,100 metres, and its closest straight-line distance from the shooters was about 2,700 metres. Defence Command concludes it could not have been struck. This review has not independently recalculated that assessment.

Euronews, reporting with AFP, corroborated the public correction and the military's continued probable-drone interpretation. Its coverage establishes that the revision was publicly reported; it does not provide an independent reconstruction of the objects.

Why this belongs in an evidence-first UAP file

The relevant connection is the handling of uncertain aerial observations. A report can contain a known aircraft, an unidentified target and differing witness estimates without establishing that all references concern the same object. Conversely, an official drone label should be read with the confidence and evidence the authority actually supplies.

Timing, identification and safety are separate questions. A corrected clock comparison may weaken one earlier argument without proving either an extraordinary craft or a mistaken attack on a passenger aircraft. Establishing either would require more than temporal overlap.

The next useful evidence would be the original recordings with reliable timestamps and a synchronized comparison of reported sightlines and aircraft tracks. The released correction supports a narrower conclusion now: the first timeline was wrong, the replacement has explicit limits, and the target assessment remains attributed to the military.

Hero image: original AI-generated editorial illustration. It does not depict evidence or an actual scene from the reported events.