Loreto fire, 5 September 2024 Loreto, San Andrés
The fire started on 5 September 2024 in Loreto, Bolivia, and satellites saw it burning for 34 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 36,765 hectares from heat detections, spread across 2 municipalities.
It is the 16th largest in Beni since 2016 (of 902 with a page). Number 14 in Bolivia in 2024, of 295.
Compare with…
Suggestions: Loreto · 2022Loreto · 2019Loreto · 2016Loreto · 2022
- Burnt area
- 36,765ha
- GWIS perimeter (Copernicus)
- Duration
- 34days
- 5 Sept 2024 – 8 Oct 2024
- Municipalities hit
- 2
- municipalities
- Started on
- 5 Sept
- 2024
- Heat detections
- 1,971
- in a single hotspot: 0 MW
- Danger at start
- 37
- High · FWI index
- Average daily power
- 805MW
- 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 11 days without rain (1 mm or more) when it started. Rain came after the fire: 8.2 mm on 9 Oct.
This area had burned before
28% of the perimeter overlaps earlier fires recorded since 2016: 4,539 ha in 2016, 217 ha in 2017, 2,454 ha in 2018, 4,584 ha in 2019, 5 ha in 2020, 1,353 ha in 2021, 6,440 ha in 2022, 1,982 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 10,242 ha that had burned before.
- 3,057 ha Loreto fire, September 2022 3,736 ha in total; the hectares shown are those it shares with this fire
- 2,363 ha Loreto fire, September 2019 3,339 ha in total; the hectares shown are those it shares with this fire
- 2,024 ha Loreto fire, September 2016 3,359 ha in total; the hectares shown are those it shares with this fire
- 713 ha Loreto fire, August 2022 4,926 ha in total; the hectares shown are those it shares with this fire
- 215 ha Loreto fire, September 2019 4,232 ha in total; the hectares shown are those it shares with this fire
- 5 ha San Andrés fire, October 2020 9,980 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
-
31,807 ha4.6 %
-
San Andrés 15,570 inhabitants5,171 ha0.5 %
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) |
|---|---|---|---|---|---|
| 5 Sept | 30.0 °C | 32 % | 54 km/h | 0.0 mm | High 37 |
| 6 Sept | 30.1 °C | 34 % | 21 km/h | 0.0 mm | High 26 |
| 7 Sept | 34.9 °C | 31 % | 36 km/h | 0.0 mm | High 30 |
| 8 Sept | 36.5 °C | 33 % | 31 km/h | 0.0 mm | High 27 |
| 9 Sept | 37.4 °C | 31 % | 30 km/h | 0.0 mm | High 29 |
| 10 Sept | 37.5 °C | 32 % | 33 km/h | 0.0 mm | High 30 |
| 11 Sept | 37.6 °C | 33 % | 44 km/h | 0.0 mm | High 35 |
| 12 Sept | 31.4 °C | 62 % | 38 km/h | 9.3 mm | Very low 3 |
| 13 Sept | 36.0 °C | 48 % | 42 km/h | 0.0 mm | Moderate 12 |
| 14 Sept | 31.4 °C | 54 % | 45 km/h | 11.6 mm | Very low 4 |
| 15 Sept | 25.3 °C | 45 % | 41 km/h | 1.4 mm | Low 6 |
| 16 Sept | 29.3 °C | 40 % | 36 km/h | 0.5 mm | Moderate 14 |
| 17 Sept | 32.6 °C | 39 % | 18 km/h | 0.0 mm | Moderate 15 |
| 18 Sept | 35.2 °C | 41 % | 32 km/h | 0.0 mm | Moderate 17 |
| 19 Sept | 36.8 °C | 39 % | 45 km/h | 0.0 mm | Moderate 21 |
| 20 Sept | 37.2 °C | 42 % | 42 km/h | 0.1 mm | Moderate 21 |
| 21 Sept | 37.0 °C | 44 % | 34 km/h | 0.1 mm | Moderate 20 |
| 22 Sept | 38.1 °C | 36 % | 38 km/h | 0.0 mm | High 24 |
| 23 Sept | 37.1 °C | 42 % | 45 km/h | 0.0 mm | High 26 |
| 24 Sept | 37.5 °C | 41 % | 42 km/h | 0.0 mm | High 24 |
| 25 Sept | 37.9 °C | 41 % | 41 km/h | 0.1 mm | High 25 |
| 26 Sept | 34.7 °C | 51 % | 42 km/h | 9.0 mm | Very low 5 |
| 27 Sept | 27.6 °C | 51 % | 43 km/h | 2.4 mm | Low 5 |
| 28 Sept | 32.6 °C | 43 % | 16 km/h | 0.0 mm | Low 10 |
| 29 Sept | 35.7 °C | 40 % | 24 km/h | 0.1 mm | Moderate 16 |
| 30 Sept | 36.7 °C | 44 % | 42 km/h | 0.3 mm | Moderate 20 |
| 1 Oct | 37.1 °C | 39 % | 48 km/h | 0.0 mm | High 23 |
| 2 Oct | 36.6 °C | 44 % | 35 km/h | 0.0 mm | Moderate 20 |
| 3 Oct | 31.1 °C | 37 % | 44 km/h | 1.3 mm | Moderate 17 |
| 4 Oct | 33.5 °C | 36 % | 33 km/h | 0.0 mm | Moderate 21 |
| 5 Oct | 37.3 °C | 32 % | 24 km/h | 0.0 mm | High 23 |
| 6 Oct | 38.1 °C | 35 % | 28 km/h | 0.0 mm | High 25 |
| 7 Oct | 36.9 °C | 42 % | 41 km/h | 0.0 mm | High 28 |
| 8 Oct | 37.3 °C | 43 % | 50 km/h | 2.2 mm | Moderate 15 |
| 9 Oct after | 34.6 °C | 48 % | 38 km/h | 8.2 mm | Very low 4 |
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 5 October 2024 the air beside the fire reached 726 µg/m³ of PM2.5. That day averaged 423: 28 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 · 0Every 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 Loreto fire last?
- GWIS (Copernicus) dates it between 5 September 2024 and 8 October 2024: 34 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 36,765 hectares (367.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Loreto (31,807 ha, 4.6 %); San Andrés (5,171 ha, 0.5 %).
- What was the weather like?
- During the fire the temperature reached 38.1 °C, humidity dropped to 31 % and gusts hit 54 km/h. The fire danger index (FWI) reached 37, 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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 31 August 2024 → 5 September 2024.
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; 3 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. No 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.