Ixiamas fire, 27 August 2023 Ixiamas
The fire started on 27 August 2023 in Ixiamas, Bolivia, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 15,781 hectares from heat detections, spread across a single municipality.
It is the 17th largest in La Paz since 2016 (of 117 with a page). Number 29 in Bolivia in 2023, of 248.
Compare with…
- Burnt area
- 15,781ha
- GWIS perimeter (Copernicus)
- Duration
- 9days
- 27 Aug 2023 – 4 Sept 2023
- Municipalities hit
- 1
- municipalities
- Started on
- 27 Aug
- 2023
- Heat detections
- 673
- in a single hotspot: 865 MW
- Danger at start
- 24
- High · FWI index
- Average daily power
- 1.6GW
- 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 13 days without rain (1 mm or more) when it started. Rain came after the fire: 12.7 mm on 5 Sept.
This area had burned before
81% of the perimeter overlaps earlier fires recorded since 2016: 4,171 ha in 2016, 5,734 ha in 2017, 308 ha in 2018, 8,556 ha in 2019, 3,322 ha in 2020, 11 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 12,847 ha that had burned before.
- 6,291 ha Ixiamas fire, August 2019 18,591 ha in total; the hectares shown are those it shares with this fire
- 2,986 ha Ixiamas fire, July 2016 8,828 ha in total; the hectares shown are those it shares with this fire
- 2,738 ha Ixiamas fire, July 2017 8,333 ha in total; the hectares shown are those it shares with this fire
- 687 ha Ixiamas fire, October 2020 3,398 ha in total; the hectares shown are those it shares with this fire
- 27 ha Ixiamas fire, August 2019 4,171 ha in total; the hectares shown are those it shares with this fire
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
-
15,882 ha reached on 27 Aug0.4 %
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 was no noticeable built-up land and almost nobody lived there (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) |
|---|---|---|---|---|---|
| 27 Aug | 29.4 °C | 36 % | 36 km/h | 0.7 mm | High 24 |
| 28 Aug | 34.0 °C | 31 % | 28 km/h | 0.0 mm | High 25 |
| 29 Aug | 37.4 °C | 36 % | 37 km/h | 0.0 mm | High 28 |
| 30 Aug | 37.7 °C | 39 % | 37 km/h | 0.0 mm | High 29 |
| 31 Aug | 37.9 °C | 40 % | 42 km/h | 0.4 mm | High 29 |
| 1 Sept | 37.9 °C | 40 % | 45 km/h | 0.0 mm | High 33 |
| 2 Sept | 37.5 °C | 39 % | 50 km/h | 0.6 mm | High 30 |
| 3 Sept | 34.7 °C | 50 % | 50 km/h | 13.3 mm | Very low 5 |
| 4 Sept | 33.6 °C | 53 % | 40 km/h | 0.0 mm | Moderate 12 |
| 5 Sept after | 33.7 °C | 56 % | 24 km/h | 12.7 mm | Very low 1 |
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 4 September 2023 the air beside the fire reached 284 µg/m³ of PM2.5. That day averaged 114: 7.6 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 · 673Every 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 Ixiamas fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 27 August 2023 to 4 September 2023 (9 days). The perimeter dates it from 29 August 2023 to 4 September 2023.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 15,781 hectares (157.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Ixiamas (15,882 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 37.9 °C, humidity dropped to 31 % and gusts hit 50 km/h. The fire danger index (FWI) reached 33, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Bolivia (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: 119 · 110 · 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; 2 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 29 August 2023 to 4 September 2023. 673 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 ADM3 (Public Domain). 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.