How long did the Bilozerka fire last?

The official perimeter only gives the start date (21 June 2026). The end comes from the heat detections inside the perimeter: it burned until 22 June 2026 (2 days from 21 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 545 hectares (5.4 km²). Official national figures may differ.

Which municipalities burned?

The fire only entered Bilozerka (219 ha, 0.2 %).

Did the fire reach a town?

The fire started in Bilozerka and came within 17.2 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.

What was the weather like?

During the fire the temperature reached 29.7 °C, humidity dropped to 33 % and gusts hit 38 km/h. The fire danger index (FWI) reached 27, class High.

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.

UA · Ukraine · 2026-06-21 → 2026-06-22

Bilozerka fire, 21 June 2026 Білозерський район · Bilozerka

Out · last detection 21 Jun 2026, 10:30 UTC

The fire started on 21 June 2026 in Bilozerka, Ukraine, and satellites saw it burning for 2 days. Copernicus mapped a burnt perimeter of 545 hectares from satellite imagery, spread across a single municipality.

It is the 185th largest in Kherson Oblast since 2016 (of 1103 with a page). Number 115 in Ukraine in 2026, of 984.

Compare with…

Suggestions: Bilozerka · 2025 Holo Prystan · 2024 Holo Prystan · 2022 Holo Prystan · 2025

Burnt area: 545ha; Copernicus perimeter
Duration: ≈ 2days; 21 Jun 2026 – 22 Jun 2026
Municipalities hit: 1; districts
Started on: 21 Jun; 2026
Heat detections: 5; in a single hotspot: 53 MW
Danger at start: 23; High · FWI index
Average daily power: 89MW; detected power per day, on average

HOTSPOTS BY DAY 21 Jun22 Jun

How it evolved, day by day

21 Jun 2026 · 89 MW · 5

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

30°high

38km/h · peak gust

33%lowest humidity

It had gone 9 days without rain (1 mm or more) when it started.

This area had burned before

71% of the perimeter overlaps earlier fires recorded since 2016: 386 ha in 2025.

386 ha Bilozerka fire, June 2025 578 ha in total; the hectares shown are those it shares with this fire

How big is it?

It burned the equivalent of 0.3% of the area of London (5.4 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

Bilozerka Білозерський район 64,790 inhabitants · 17.2 km from the centre where it started

219 ha reached on 21 Jun

0.2 %

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 areas79 %
Other natural land18 %
Mixed forest2.9 %
Artificial surfaces0.6 %

Land cover inside the perimeter as reported by Copernicus EFFIS (outside the Corine Land Cover area).

People and buildings inside the perimeter

GHSL 2025

Built-up area3.8 ha

Residents≈ 50

Inside the perimeter there were about 3.8 hectares of built-up land and about 50 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

The weather day by day

ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.

Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

Day	High	Min. humidity	Peak gust	Rain	Danger (FWI)
21 Jun	29.3 °C	33 %	26 km/h	0.0 mm	High 23
22 Jun	29.7 °C	33 %	38 km/h	0.0 mm	High 27
23 Jun after	31.5 °C	37 %	27 km/h	0.9 mm	Moderate 20
24 Jun after	30.2 °C	44 %	21 km/h	0.0 mm	Moderate 20
25 Jun after	31.1 °C	30 %	26 km/h	0.0 mm	High 27
26 Jun after	28.7 °C	39 %	33 km/h	0.8 mm	High 23
27 Jun after	28.4 °C	32 %	28 km/h	0.0 mm	High 27
28 Jun after	33.3 °C	35 %	35 km/h	0.0 mm	High 28
29 Jun after	32.6 °C	28 %	23 km/h	0.0 mm	High 29
30 Jun after	35.1 °C	41 %	27 km/h	0.0 mm	High 32
1 Jul after	33.0 °C	34 %	32 km/h	0.0 mm	High 34
2 Jul after	32.9 °C	28 %	31 km/h	0.0 mm	High 33

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

↔

Before · 14 Jun 2026

After · 29 Jun 2026

Before After

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 · Copernicus

On 24 June 2026 the air beside the fire reached 8 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak8 µg/m³

Days over the guideline0 days

PM108 µg/m³

Optical depth0.31

192021222324

Good Fair Moderate Poor Very poor Extremely poor

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 · 5Every satellite heat detection, one by one, with time, satellite, power and coordinates.

⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.

Date and time	Satellite	FRP (MW)	Lat	Lon

Other fires nearby

All fires in Ukraine ›

Frequently asked questions

How long did the Bilozerka fire last?: The official perimeter only gives the start date (21 June 2026). The end comes from the heat detections inside the perimeter: it burned until 22 June 2026 (2 days from 21 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 545 hectares (5.4 km²). Official national figures may differ.
Which municipalities burned?: The fire only entered Bilozerka (219 ha, 0.2 %).
Did the fire reach a town?: The fire started in Bilozerka and came within 17.2 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.
What was the weather like?: During the fire the temperature reached 29.7 °C, humidity dropped to 33 % and gusts hit 38 km/h. The fire danger index (FWI) reached 27, class High.
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 ›

ДСНС · State Emergency Service ↗

Satellite cross-check

NASA FIRMS ↗
EFFIS · Copernicus ↗

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.

RSS Changes to this page

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

What do you think is wrong?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 101 · 112.

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. 5 Suomi-NPP VIIRS detections on those dates.
We have not matched this page with any official record.
Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
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.

How we build fire pages: methodology ›

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.

Where it burned