Bilozerka fire, 22 June 2026 Білозерський район · Bilozerka
The fire started on 22 June 2026 in Bilozerka, Ukraine, and satellites saw it burning for 14 days. Copernicus mapped a burnt perimeter of 1,966 hectares from satellite imagery, spread across a single municipality.
We are reviewing this page: some of its data look inconsistent (the place, the dates or the area), so treat them with caution.
The power measured by the satellite is low (20.8 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 1,966ha
- Copernicus perimeter
- Duration
- ≈ 14days
- 22 Jun 2026 – 5 Jul 2026
- Municipalities hit
- 1
- districts
- Started on
- 22 Jun
- 2026
- Heat detections
- 35
- in a single hotspot: 21 MW
- Average daily power
- 60MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
This area had burned before
47% of the perimeter overlaps earlier fires recorded since 2016: 194 ha in 2022, 42 ha in 2023, 803 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 923 ha that had burned before.
- 423 ha Vitovka fire, July 2025 483 ha in total; the hectares shown are those it shares with this fire
- 369 ha Ochakiv fire, June 2025 476 ha in total; the hectares shown are those it shares with this fire
- 112 ha Vitovka fire, July 2022 131 ha in total; the hectares shown are those it shares with this fire
- 42 ha Bilozerka fire, September 2023 364 ha in total; the hectares shown are those it shares with this fire
- 35 ha Bilozerka fire, July 2022 133 ha in total; the hectares shown are those it shares with this fire
- 11 ha Bilozerka fire, June 2025 122 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Kyiv boundary: geoBoundaries · OpenStreetMap, Wambacher · © OpenStreetMap contributors (ODbL 1.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
22 ha0.0 %
Burnt area inside each municipality, from crossing the official perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.
What burned
- Agricultural areas93 %
- Other natural land5.7 %
- Mixed forest0.7 %
Land cover inside the perimeter as reported by Copernicus EFFIS (outside the Corine Land Cover area).
People and buildings inside the perimeter
GHSL 2025Inside the perimeter there were about 2.2 hectares of built-up land and about 30 residents (GHSL 2025, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 3 July 2026 the air beside the fire reached 14 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 35Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,113 haHolo Prystan Скадовський районApril 2022 · 7 days · 20 km away
- 2,881 haHolo Prystan Скадовський район7 July 2024 · 6 days · 21 km away
- 3,083 haHolo Prystan Скадовський район6 August 2025 · 11 days · 25 km away
- 2,323 haHolo Prystan Скадовський район6 July 2023 · 6 days · 31 km away
- 3,629 haHolo Prystan Скадовський район6 June 2025 · 6 days · 39 km away
- 2,338 haHolo Prystan Скадовський район12 August 2026 · 6 days · 39 km away
Frequently asked questions
- How long did the Bilozerka fire last?
- The official perimeter only gives the start date (29 June 2026). The end comes from the heat detections inside the perimeter: it burned until 5 July 2026 (14 days from 22 June 2026), the last day with detections before more than 10 days in a row without any, so it is approximate.
- How much area did it burn?
- The perimeter Copernicus measured from satellite imagery is 1,966 hectares (19.7 km²). Official national figures may differ.
- Which municipalities burned?
- The fire only entered Bilozerka (22 ha, 0.0 %).
- Did the fire reach a town?
- The fire started in Bilozerka and came within 20.3 km of its centre. That is the distance from the perimeter, or the nearest hotspot, to the point marking the centre; it does not mean it entered the houses.
- Where does this data come from?
- From the EFFIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Ukraine (geoBoundaries). It is not an official report.
Where to verify it
A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.
Emergency number: 101 · 112 · Emergency number and official warnings ›
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
Does something look wrong on this page?
This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.
Report an error
How we know this
- Perimeter: EFFIS (Copernicus), mapped on satellite imagery.
- The official perimeter has no end date: the end is the last day with VIIRS detections inside the perimeter before a gap of more than 10 days (150 days at most), so it is approximate. 35 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
Where this data comes from
The perimeter and land cover come from the Copernicus European Forest Fire Information System (EFFIS), measured on MODIS and Sentinel-2 imagery and published under CC BY 4.0. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM2 (Public Domain). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from each country’s official figure.