Shushtar fire, May 2026 Shushtar, Shush
The fire started on 13 May 2026 in Shushtar, Iran, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,216 hectares from heat detections, spread across 2 municipalities.
It is the 16th largest in Khuzestan since 2016 (of 27 with a page). Number 7 in Iran in 2026, of 11.
Compare with…
Suggestions: Shush · 2025Shush · 2026Ahvaz · 2025Hamidieh · 2020
- Burnt area
- 1,216ha
- GWIS perimeter (Copernicus)
- Duration
- 8days
- 13 May 2026 – 20 May 2026
- Municipalities hit
- 2
- counties
- Started on
- 13 May
- 2026
- Heat detections
- 32
- in a single hotspot: 127 MW
- Danger at start
- 51
- Extreme · FWI index
- Average daily power
- 125MW
- 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.
The weather it burned in
It had gone 14 days without rain (1 mm or more) when it started.
This area had burned before
36% of the perimeter overlaps earlier fires recorded since 2016: 56 ha in 2016, 32 ha in 2021, 274 ha in 2023, 249 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 443 ha that had burned before.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.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).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Shushtar where it started1,220 ha reached on 13 May0.5 %
-
0 ha0.0 %
Burnt area inside each municipality, from crossing the GWIS 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.
People and buildings inside the perimeter
GHSL 2025Inside the perimeter there were about 1.0 hectares of built-up land and about 80 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) |
|---|---|---|---|---|---|
| 13 May | 40.0 °C | 13 % | 30 km/h | 0.0 mm | Extreme 51 |
| 14 May | 39.1 °C | 7 % | 41 km/h | 0.0 mm | Extreme 62 |
| 15 May | 39.9 °C | 11 % | 27 km/h | 0.0 mm | Very high 48 |
| 16 May | 36.1 °C | 14 % | 46 km/h | 0.0 mm | Extreme 62 |
| 17 May | 34.4 °C | 13 % | 39 km/h | 0.0 mm | Extreme 56 |
| 18 May | 36.2 °C | 15 % | 28 km/h | 0.0 mm | Extreme 55 |
| 19 May | 37.5 °C | 18 % | 44 km/h | 0.0 mm | Extreme 60 |
| 20 May | 35.2 °C | 14 % | 32 km/h | 0.0 mm | Extreme 56 |
| 21 May after | 39.8 °C | 12 % | 30 km/h | 0.0 mm | Extreme 55 |
| 22 May after | 36.7 °C | 12 % | 29 km/h | 0.0 mm | Extreme 56 |
| 23 May after | 38.6 °C | 10 % | 27 km/h | 0.0 mm | Extreme 50 |
| 24 May after | 44.0 °C | 10 % | 31 km/h | 0.0 mm | Extreme 62 |
| 25 May after | 39.5 °C | 7 % | 35 km/h | 0.0 mm | Extreme 65 |
| 26 May after | 41.9 °C | 9 % | 26 km/h | 0.0 mm | Extreme 58 |
| 27 May after | 43.9 °C | 9 % | 22 km/h | 0.0 mm | Extreme 56 |
| 28 May after | 46.8 °C | 10 % | 19 km/h | 0.0 mm | Extreme 55 |
| 29 May after | 46.4 °C | 9 % | 41 km/h | 0.0 mm | Very extreme 73 |
| 30 May after | 39.2 °C | 9 % | 31 km/h | 0.0 mm | Extreme 66 |
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 22 May 2026 the air beside the fire reached 232 µg/m³ of PM2.5. That day averaged 121: 8.1 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)
Detections table · 32Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Shushtar fire last?
- GWIS (Copernicus) dates it between 13 May 2026 and 20 May 2026: 8 days between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,216 hectares (12.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Shushtar (1,220 ha, 0.5 %); Shush (0 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 40.0 °C, humidity dropped to 7 % and gusts hit 46 km/h. The fire danger index (FWI) reached 62, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Iran (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: 125 · 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: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 32 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.
Where this data comes from
The perimeter comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. 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 (Open Data Commons Open Database License 1.0). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.