Skip to main content

Russian Officials Report Fire in Afipsky After Drone Debris Falls

Russian authorities said falling drone debris caused a fire at an enterprise in Afipsky, in the Seversky district of Krasnodar region, on November 6. The regional operational headquarters reported the incident in a morning statement. It did not identify the enterprise or describe the extent of the fire. “There are no casualties,” the headquarters said. It reported that operational and specialist services were working at the scene. Drone fragments also damaged windows in one apartment in a low-rise residential building, according to the same statement. The report described damage at both the industrial premises and the apartment. Afipsky has experienced earlier fires linked by regional officials to drone debris. On June 11, 2026, local time, the same headquarters reported a fire specifically at the Afipsky oil refinery. That earlier statement also described debris at three private-sector addresses, an outbuilding fire, broken windows and damage to a gas main. Its initial assessment reported no casualties. Ukraine has previously acknowledged targeting the refinery. In a statement dated November 29, 2025, the Ukrainian General Staff said its forces had struck the facility overnight and reported explosions followed by a fire. It described the refinery as helping supply Russian forces and presented the operation as part of efforts to reduce Russia’s military and economic capacity. That acknowledgment concerned the 2025 strike, a separate incident from the fire reported on November 6.

Sources

Telegram · @opershtab2312Telegram · @GeneralStaffZSUOpens in a new tab.
Courtroom-sketch editorial illustration of an archival August 2005 tree-lined street in Afipsky, Krasnodar Krai, with tall trees, a willow and overhead wires; geographic context, not a depiction of the November 2026 fire, damaged enterprise or falling debris, rendered in warm ochre and slate-blue pastel strokes.

Commentary

Add Your Voice
Loading comments…

Voices

Write about this

Something went wrong

We couldn't complete that action. Check your connection and try again.