Salas-e Babajani fire, July 2016 Salas-e Babajani
The fire started on 1 July 2016 in Salas-e Babajani, Iran, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,550 hectares from heat detections, 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.
- Burnt area
- 2,550ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 1 Jul 2016 – 4 Jul 2016
- Municipalities hit
- 1
- counties
- Started on
- 1 Jul
- 2016
- Heat detections
- 33
- in a single hotspot: 73 MW
- Danger at start
- 56
- Extreme · FWI index
- Energy released
- 696MW
- sum of detected power
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 42 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Salas-e Babajani where it started7 ha0.0 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
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) |
|---|---|---|---|---|---|
| 1 Jul | 37.2 °C | 10 % | 39 km/h | 0.0 mm | Extreme 56 |
| 2 Jul | 37.0 °C | 9 % | 32 km/h | 0.0 mm | Extreme 53 |
| 3 Jul | 37.2 °C | 10 % | 29 km/h | 0.0 mm | Extreme 51 |
| 4 Jul | 37.3 °C | 13 % | 33 km/h | 0.0 mm | Extreme 54 |
| 5 Jul after | 37.0 °C | 15 % | 43 km/h | 0.0 mm | Extreme 55 |
| 6 Jul after | 35.7 °C | 13 % | 40 km/h | 0.0 mm | Extreme 54 |
| 7 Jul after | 36.1 °C | 13 % | 40 km/h | 0.0 mm | Extreme 54 |
| 8 Jul after | 37.2 °C | 14 % | 32 km/h | 0.0 mm | Extreme 50 |
| 9 Jul after | 37.6 °C | 13 % | 36 km/h | 0.0 mm | Extreme 54 |
| 10 Jul after | 36.6 °C | 11 % | 37 km/h | 0.0 mm | Extreme 56 |
| 11 Jul after | 35.9 °C | 11 % | 35 km/h | 0.0 mm | Extreme 54 |
| 12 Jul after | 37.7 °C | 11 % | 30 km/h | 0.0 mm | Extreme 52 |
| 13 Jul after | 37.7 °C | 14 % | 47 km/h | 0.0 mm | Extreme 59 |
| 14 Jul after | 39.9 °C | 10 % | 38 km/h | 0.0 mm | Extreme 54 |
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.
Detections table · 33Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 1,967 haSalas-e BabajaniJuly 2018 · 3 days · 2 km away
- 1,974 haSalas-e BabajaniJune 2020 · 3 days · 3 km away
- 1,385 haSalas-e BabajaniJuly 2020 · 3 days · 21 km away
- 2,964 haJavanrudJune 2020 · 5 days · 23 km away
- 4,514 haPaveh29 July 2017 · 6 days · 27 km away
- 2,793 haPaveh24 June 2020 · 6 days · 27 km away
Frequently asked questions
- How long did the Salas-e Babajani fire last?
- GWIS (Copernicus) dates it between 1 July 2016 and 4 July 2016: 4 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 2,550 hectares (25.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Salas-e Babajani (7 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 37.3 °C, humidity dropped to 9 % and gusts hit 39 km/h. The fire danger index (FWI) reached 56, 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
Satellite cross-check
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
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.