Bilehsavar fire, July 2016 Bilehsavar
The fire started on 3 July 2016 in Bilehsavar, Iran, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,121 hectares from heat detections, spread across a single municipality.
Number 15 in Iran in 2016, of 21.
- Burnt area
- 1,121ha
- GWIS perimeter (Copernicus)
- Duration
- 2days
- 3 Jul 2016 – 4 Jul 2016
- Municipalities hit
- 1
- counties
- Started on
- 3 Jul
- 2016
- Heat detections
- 26
- in a single hotspot: 189 MW
- Danger at start
- 36
- High · FWI index
- Energy released
- 650MW
- 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 20 days without rain (1 mm or more) when it started. Rain came after the fire: 7.4 mm on 11 Jul.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Bilehsavar where it started1,123 ha0.6 %
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) |
|---|---|---|---|---|---|
| 3 Jul | 30.4 °C | 40 % | 52 km/h | 0.0 mm | High 36 |
| 4 Jul | 27.9 °C | 50 % | 43 km/h | 0.0 mm | High 28 |
| 5 Jul after | 29.7 °C | 38 % | 39 km/h | 0.0 mm | High 27 |
| 6 Jul after | 28.0 °C | 46 % | 36 km/h | 0.5 mm | High 27 |
| 7 Jul after | 29.7 °C | 46 % | 30 km/h | 0.0 mm | High 25 |
| 8 Jul after | 32.5 °C | 46 % | 31 km/h | 0.2 mm | High 24 |
| 9 Jul after | 28.5 °C | 46 % | 47 km/h | 0.3 mm | High 32 |
| 10 Jul after | 27.3 °C | 51 % | 35 km/h | 0.0 mm | High 24 |
| 11 Jul after | 22.5 °C | 73 % | 26 km/h | 7.4 mm | Very low 0 |
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 · 26Every 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 Bilehsavar fire last?
- GWIS (Copernicus) dates it between 3 July 2016 and 4 July 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,121 hectares (11.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Bilehsavar (1,123 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 30.4 °C, humidity dropped to 40 % and gusts hit 52 km/h. The fire danger index (FWI) reached 36, class High.
- 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.