Burned area
satellite only1,261ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 1 Sept 2016 – 9 Sept 2016
+− cross-check
No official record is matched to this page to compare it with.
IR · Iran · –
Khoramshahr fire, September 2016 Khoramshahr
Out · last detection 9 Sept 2016, 22:14 UTC
The fire started on 1 September 2016 in Khoramshahr, Iran, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,261 hectares from heat detections, spread across a single municipality.
It is the 10th largest in Khuzestan since 2016 (of 20 with a page). Number 8 in Iran in 2016, of 15.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only9days
1 Sept 2016 to 9 Sept 2016: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 9 Sept 2016, 22:14 UTC
+− cross-check
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.
Start
satellite only1 Sept 2016
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 1 Sept 2016
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only149
VIIRS detections at 375 m. Most intense hotspot: 182 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 1 Sept 2016 – 9 Sept 2016
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only1,477MW
Total radiative power on 2 September 2016; hotspots that day: 30.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 2 Sept 2016
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model66.0FWI · extreme
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 60.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 1 Sept 2016, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
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
Weather during the fire
model48.3°C · 10% RH
High of 48.3 °C and minimum humidity of 10% on 2 September 2016; gusts of 72 km/h on 6 September 2016.
- Source
- weather model at the fire’s grid cell
- Date
- 1 Sept 2016 – 9 Sept 2016
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
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.
Show
-
· reconstructed GHSLPopulation and built-up area computed
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 1,261 ha
- Dates
- 1 Sept 2016 – 9 Sept 2016
- Name
- Khoramshahr
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/khoramshahr-2016-09?v=2026-10-24A 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.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire khoramshahr-2016-09.csv · daily, no individual hotspots
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2016-09-01 | 6 | 52 | 46.3 | 30.4 | 19 | 18.4 | 33.1 | 0 | 66 | extremo | 1 |
| 2016-09-02 | 30 | 1,477 | 48.3 | 33 | 10 | 15.9 | 31.7 | 0 | 65.4 | extremo | 1 |
| 2016-09-03 | 13 | 477 | 47.9 | 30.1 | 10 | 18 | 32.8 | 0 | 68.8 | extremo | 1 |
| 2016-09-04 | 5 | 160 | 48.3 | 32 | 10 | 28.4 | 42.1 | 0 | 86.6 | muy_extremo | 1 |
| 2016-09-05 | 26 | 1,245 | 45.8 | 32.7 | 8 | 39.5 | 61.6 | 0 | 109.9 | muy_extremo | 1 |
| 2016-09-06 | 43 | 1,415 | 45.6 | 29.8 | 7 | 44.2 | 72 | 0 | 121.6 | muy_extremo | 1 |
| 2016-09-07 | 14 | 552 | 42.1 | 30 | 9 | 39.9 | 62.6 | 0 | 111.7 | muy_extremo | 1 |
| 2016-09-08 | 7 | 64 | 42.3 | 27.7 | 10 | 28 | 45.7 | 0 | 87.2 | muy_extremo | 1 |
| 2016-09-09 | 5 | 56 | 41.5 | 24.6 | 11 | 13.1 | 20.5 | 0 | 61.8 | extremo | 1 |
| 2016-09-10 | 0 | 0 | 41.9 | 24.9 | 12 | 12.6 | 20.5 | 0 | 60.4 | extremo | 0 |
| 2016-09-11 | 0 | 0 | 43.7 | 24.8 | 9 | 13.7 | 27.4 | 0 | 62.2 | extremo | 0 |
| 2016-09-12 | 0 | 0 | 44.9 | 25.7 | 7 | 23.4 | 36.7 | 0 | 77.4 | muy_extremo | 0 |
| 2016-09-13 | 0 | 0 | 43.6 | 27.3 | 8 | 22.9 | 32 | 0 | 76.9 | muy_extremo | 0 |
| 2016-09-14 | 0 | 0 | 43.3 | 26.5 | 8 | 15.6 | 22.7 | 0 | 65.8 | extremo | 0 |
| 2016-09-15 | 0 | 0 | 44.3 | 26.8 | 9 | 15.8 | 22 | 0 | 66.3 | extremo | 0 |
| 2016-09-16 | 0 | 0 | 45 | 27 | 10 | 17 | 30.2 | 0 | 68.4 | extremo | 0 |
| 2016-09-17 | 0 | 0 | 44.9 | 26.5 | 7 | 21.9 | 38.9 | 0 | 76.5 | muy_extremo | 0 |
| 2016-09-18 | 0 | 0 | 43 | 29.7 | 14 | 28.1 | 45.7 | 0 | 83.7 | muy_extremo | 0 |
| 2016-09-19 | 0 | 0 | 39.1 | 25.6 | 10 | 26.9 | 43.9 | 0 | 81.9 | muy_extremo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
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: GWIS (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
- Burnt area
- 1,261ha
- GWIS perimeter (Copernicus)
- Duration
- 9days
- 1 Sept 2016 – 9 Sept 2016
- Municipalities hit
- 1
- counties
- Started on
- 1 Sept
- 2016
- Heat detections
- 149
- in a single hotspot: 182 MW
- Danger at start
- 66
- Extreme · FWI index
- Average daily power
- 611MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
1 Sept9 Sept
9 Sept 2016
How it evolved, day by day
2 Sept
5 Sept
7 Sept
9 Sept
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
48°high
72km/h · peak gust
7%lowest humidity
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.
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
-
Khoramshahr where it started1,268 ha reached on 1 Sept0.6 %
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 2015Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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.
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)
Started with 60 days without rain: 27 % of the area in Iran
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 1 Sept | 46.3 °C | 19 % | 33 km/h | 0.0 mm | Extreme 66 |
| 2 Sept | 48.3 °C | 10 % | 32 km/h | 0.0 mm | Extreme 65 |
| 3 Sept | 47.9 °C | 10 % | 33 km/h | 0.0 mm | Extreme 69 |
| 4 Sept | 48.3 °C | 10 % | 42 km/h | 0.0 mm | Very extreme 87 |
| 5 Sept | 45.8 °C | 8 % | 62 km/h | 0.0 mm | Very extreme 110 |
| 6 Sept | 45.6 °C | 7 % | 72 km/h | 0.0 mm | Very extreme 122 |
| 7 Sept | 42.1 °C | 9 % | 63 km/h | 0.0 mm | Very extreme 112 |
| 8 Sept | 42.3 °C | 10 % | 46 km/h | 0.0 mm | Very extreme 87 |
| 9 Sept | 41.5 °C | 11 % | 20 km/h | 0.0 mm | Extreme 62 |
| 10 Sept after | 41.9 °C | 12 % | 20 km/h | 0.0 mm | Extreme 60 |
| 11 Sept after | 43.7 °C | 9 % | 27 km/h | 0.0 mm | Extreme 62 |
| 12 Sept after | 44.9 °C | 7 % | 37 km/h | 0.0 mm | Very extreme 77 |
| 13 Sept after | 43.6 °C | 8 % | 32 km/h | 0.0 mm | Very extreme 77 |
| 14 Sept after | 43.3 °C | 8 % | 23 km/h | 0.0 mm | Extreme 66 |
| 15 Sept after | 44.3 °C | 9 % | 22 km/h | 0.0 mm | Extreme 66 |
| 16 Sept after | 45.0 °C | 10 % | 30 km/h | 0.0 mm | Extreme 68 |
| 17 Sept after | 44.9 °C | 7 % | 39 km/h | 0.0 mm | Very extreme 76 |
| 18 Sept after | 43.0 °C | 14 % | 46 km/h | 0.0 mm | Very extreme 84 |
| 19 Sept after | 39.1 °C | 10 % | 44 km/h | 0.0 mm | Very extreme 82 |
Its twins: fires that started in the same weather
It started with an FWI of 66.0, a minimum humidity of 19% and more than two months without rain. Fires in the area that started in weather like this since 2016: 11.
FWI at the start
66.0
Minimum humidity
19 %
Days without rain
60+
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Khoramshahr fire, September 2016
1,261 ha
9 days
FWI 66.0
Min. humidity 19 %
Al-Kahla fire, September 2025
1,582 ha
41 days
FWI 69.2
Min. humidity 15 %
102 km away, in 2025
First rain (1 mm or more) after it ended: none in the following ten days.
Al-Chibayish fire, September 2023
1,098 ha
5 days
FWI 65.3
Min. humidity 11 %
145 km away, in 2023
First rain (1 mm or more) after it ended: none in the following ten days.
Suq Al-Shoyokh fire, September 2018
1,295 ha
13 days
FWI 68.0
Min. humidity 12 %
162 km away, in 2018
First rain (1 mm or more) after it ended: none in the following ten days.
Al-Kahla fire, August 2025
1,935 ha
17 days
FWI 70.9
Min. humidity 13 %
103 km away, in 2025
First rain (1 mm or more) after it ended: none in the following ten days.
Al-Mejar Al-Kabir fire, September 2018
1,054 ha
43 days
FWI 67.3
Min. humidity 9 %
84 km away, in 2018
First rain (1 mm or more) after it ended: 1.7 mm on 21 Oct.
What happened to them
Fires in the area that started in similar weather: 11. With fewer than 15 we give no figures: they would be more noise than signal.
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
How it ended
—first rain
—no rain in ten days
72km/h · max. gust
It was considered over on 9 Sept, and not even 1 mm fell in the following ten days: it went out without rain.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 25 Aug 2016
After · 16 Sept 2016
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 149Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV
Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Khoramshahr fire last?
- GWIS (Copernicus) dates it between 1 September 2016 and 9 September 2016: 9 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,261 hectares (12.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Khoramshahr (1,268 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 48.3 °C, humidity dropped to 7 % and gusts hit 72 km/h. The fire danger index (FWI) reached 122, class Very 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.
RSS Changes to this page With cross-checks and a citable version
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. 149 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 2015, 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.