Pol-e-Dokhtar fire, August 2016 Pol-e-Dokhtar
The fire started on 16 August 2016 in Pol-e-Dokhtar, Iran, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,093 hectares from heat detections, spread across a single municipality.
It is the 14th largest in Lorestan since 2016 (of 15 with a page). Number 17 in Iran in 2016, of 21.
The power measured by the satellite is low (13.9 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
- Burnt area
- 1,093ha
- GWIS perimeter (Copernicus)
- Duration
- 2days
- 16 Aug 2016 – 17 Aug 2016
- Municipalities hit
- 1
- counties
- Started on
- 16 Aug
- 2016
- Heat detections
- 34
- in a single hotspot: 14 MW
- Danger at start
- 53
- Extreme · FWI index
- Energy released
- 231MW
- 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 more than two months 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
-
Pol-e-Dokhtar where it started1,098 ha0.3 %
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) |
|---|---|---|---|---|---|
| 16 Aug | 37.4 °C | 12 % | 28 km/h | 0.0 mm | Extreme 53 |
| 17 Aug | 36.7 °C | 13 % | 31 km/h | 0.0 mm | Extreme 50 |
| 18 Aug after | 36.6 °C | 14 % | 37 km/h | 0.0 mm | Extreme 54 |
| 19 Aug after | 35.2 °C | 12 % | 35 km/h | 0.0 mm | Extreme 53 |
| 20 Aug after | 35.4 °C | 13 % | 25 km/h | 0.0 mm | Very high 49 |
| 21 Aug after | 35.8 °C | 14 % | 22 km/h | 0.0 mm | Very high 47 |
| 22 Aug after | 35.2 °C | 16 % | 20 km/h | 0.0 mm | Very high 46 |
| 23 Aug after | 35.4 °C | 15 % | 23 km/h | 0.0 mm | Very high 46 |
| 24 Aug after | 35.1 °C | 15 % | 24 km/h | 0.0 mm | Very high 47 |
| 25 Aug after | 35.8 °C | 15 % | 27 km/h | 0.0 mm | Very high 47 |
| 26 Aug after | 35.4 °C | 16 % | 27 km/h | 0.0 mm | Very high 48 |
| 27 Aug after | 37.9 °C | 12 % | 31 km/h | 0.0 mm | Very high 49 |
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 · 34Every 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 Pol-e-Dokhtar fire last?
- GWIS (Copernicus) dates it between 16 August 2016 and 17 August 2016: 2 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,093 hectares (10.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Pol-e-Dokhtar (1,098 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 37.4 °C, humidity dropped to 12 % and gusts hit 31 km/h. The fire danger index (FWI) reached 53, 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.