Burned area
satellite onlyPerimeter published by EFFIS (Copernicus).
- Source
- EFFIS (Copernicus)
- Date
- perimeter revised on 18 August 2026
+− cross-check
No official record is matched to this page to compare it with.
The fire started on 10 August 2026 in Holo Prystan, Ukraine, and satellites saw it burning for 9 days. Copernicus mapped a burnt perimeter of 5,107 hectares from satellite imagery, spread across 2 municipalities.
It is the 3th largest in Kherson Oblast since 2016 (of 1103 with a page). Number 2 in Ukraine in 2026, of 984.
Perimeter published by EFFIS (Copernicus).
No official record is matched to this page to compare it with.
10 Aug 2026 to 18 Aug 2026: first and last day with fire on the page.
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
First day with fire seen by the satellites or the perimeter.
No official record is matched to this page, so the alert time and the cause are not known here.
VIIRS detections at 375 m. Most intense hotspot: 112 MW.
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
Total radiative power on 14 August 2026; hotspots that day: 65.
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 12.
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
High of 34.1 °C and minimum humidity of 31% on 11 August 2026; gusts of 45 km/h on 12 August 2026.
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-08-10 | 10 | 19 | 33.2 | 19.3 | 41 | 14.8 | 28.8 | 0.2 | 28.9 | alto | 1 |
| 2026-08-11 | 0 | 0 | 34.1 | 20.3 | 31 | 9.4 | 17.3 | 0 | 26.3 | alto | 1 |
| 2026-08-12 | 0 | 0 | 29.7 | 19.7 | 29 | 21.7 | 45.4 | 0 | 36.3 | alto | 1 |
| 2026-08-13 | 2 | 3 | 26.2 | 14.5 | 27 | 18.5 | 39.6 | 0 | 34.1 | alto | 1 |
| 2026-08-14 | 65 | 1,076 | 26.8 | 12.5 | 26 | 15.4 | 34.9 | 0 | 32 | alto | 1 |
| 2026-08-15 | 60 | 342 | 27.5 | 11.2 | 25 | 16.1 | 35.6 | 0 | 33.1 | alto | 1 |
| 2026-08-16 | 17 | 285 | 29.3 | 12.1 | 28 | 9.8 | 24.5 | 0 | 28.7 | alto | 1 |
| 2026-08-17 | 1 | 0 | 30.9 | 13.3 | 27 | 10.4 | 19.8 | 0 | 29.5 | alto | 1 |
| 2026-08-18 | 1 | 4 | 31.2 | 15.2 | 27 | 19 | 40 | 0 | 36.9 | alto | 1 |
| 2026-08-19 | 0 | 0 | 24.8 | 17.6 | 46 | 10 | 27.7 | 3.6 | 5.1 | muy_bajo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: EFFIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
It had gone 12 days without rain (1 mm or more) when it started. Rain came after the fire: 3.6 mm on 19 Aug.
89% of the perimeter overlaps earlier fires recorded since 2016: 1,422 ha in 2023, 3,495 ha in 2024, 767 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 4,521 ha that had burned before.
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.
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.
Land cover inside the perimeter as reported by Copernicus EFFIS (outside the Corine Land Cover area).
Inside the perimeter there were about 0.53 hectares of built-up land and almost nobody lived there (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
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) |
|---|---|---|---|---|---|
| 10 Aug | 33.2 °C | 41 % | 29 km/h | 0.2 mm | High 29 |
| 11 Aug | 34.1 °C | 31 % | 17 km/h | 0.0 mm | High 26 |
| 12 Aug | 29.7 °C | 29 % | 45 km/h | 0.0 mm | High 36 |
| 13 Aug | 26.2 °C | 27 % | 40 km/h | 0.0 mm | High 34 |
| 14 Aug | 26.8 °C | 26 % | 35 km/h | 0.0 mm | High 32 |
| 15 Aug | 27.5 °C | 25 % | 36 km/h | 0.0 mm | High 33 |
| 16 Aug | 29.3 °C | 28 % | 24 km/h | 0.0 mm | High 29 |
| 17 Aug | 30.9 °C | 27 % | 20 km/h | 0.0 mm | High 30 |
| 18 Aug | 31.2 °C | 27 % | 40 km/h | 0.0 mm | High 37 |
| 19 Aug after | 24.8 °C | 46 % | 28 km/h | 3.6 mm | Very low 5 |
It started with an FWI of 28.9, a minimum humidity of 41% and 12 days without rain. Fires in the area that started in weather like this since 2022: 27.
First rain (1 mm or more) after it ended: none in the following ten days.
First rain (1 mm or more) after it ended: 4.7 mm on 6 Oct.
First rain (1 mm or more) after it ended: 1.2 mm on 1 Sept.
First rain (1 mm or more) after it ended: 7.3 mm on 9 Jul.
First rain (1 mm or more) after it ended: 1.4 mm on 4 Jul.
It was 35.0 times larger than the median of its twins and lasted 9 days, against 2 days.
None of its 27 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 2 of 27, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.6 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
It was considered over on 18 Aug, and on 19 Aug 3.6 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 25 of 27, with a median of 2.6 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
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.
On 16 August 2026 the air beside the fire reached 33 µg/m³ of PM2.5. That day averaged 18: 1.2 times the WHO daily 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)
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
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
No changes since 24 October 2026.
RSS Changes to this page With cross-checks and a citable version
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.
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.