Rio Sono fire, October 2024 Rio Sono
The fire started on 13 October 2024 in Rio Sono, Brazil, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,698 hectares from heat detections, spread across a single municipality.
It is the 650th largest in Tocantins since 2016 (of 1243 with a page). Number 740 in Brazil in 2024, of 1301.
Compare with…
- Burnt area
- 4,698ha
- GWIS perimeter (Copernicus)
- Duration
- 3days
- 13 Oct 2024 – 15 Oct 2024
- Municipalities hit
- 1
- municipalities
- Started on
- 13 Oct
- 2024
- Heat detections
- 69
- in a single hotspot: 103 MW
- Danger at start
- 55
- Extreme · FWI index
- Average daily power
- 341MW
- 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 more than two months without rain (1 mm or more) when it started. Rain came after the fire: 6.4 mm on 17 Oct.
This area had burned before
82% of the perimeter overlaps earlier fires recorded since 2016: 2,000 ha in 2016, 2,656 ha in 2020, 985 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 3,858 ha that had burned before.
- 2,656 ha Rio Sono fire, September 2020 19,971 ha in total; the hectares shown are those it shares with this fire
- 79 ha Rio Sono fire, August 2016 4,661 ha in total; the hectares shown are those it shares with this fire
- 14 ha Rio Sono fire, August 2016 5,269 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
-
4,733 ha reached on 13 Oct0.7 %
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 were about 0.14 hectares of 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) |
|---|---|---|---|---|---|
| 13 Oct | 40.6 °C | 15 % | 40 km/h | 0.0 mm | Extreme 55 |
| 14 Oct | 39.6 °C | 20 % | 32 km/h | 0.0 mm | Extreme 53 |
| 15 Oct | 36.4 °C | 31 % | 40 km/h | 0.0 mm | Very high 48 |
| 16 Oct after | 33.1 °C | 42 % | 34 km/h | 0.6 mm | High 29 |
| 17 Oct after | 32.0 °C | 47 % | 28 km/h | 6.4 mm | Low 6 |
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 17 October 2024 the air beside the fire reached 70 µg/m³ of PM2.5. That day averaged 40: 2.7 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 · 69Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 19,971 haRio Sono3 September 2020 · 11 days · 5 km away
- 10,355 haLizarda7 September 2019 · 6 days · 19 km away
- 14,656 haLizarda23 October 2025 · 8 days · 20 km away
- 11,622 haLizarda23 August 2022 · 17 days · 25 km away
- 10,550 haLizarda8 September 2026 · 14 days · 31 km away
- 11,542 haRio Sono3 September 2024 · 11 days · 33 km away
Frequently asked questions
- How long did the Rio Sono fire last?
- GWIS (Copernicus) dates it between 13 October 2024 and 15 October 2024: 3 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 4,698 hectares (47.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Rio Sono (4,733 ha, 0.7 %).
- What was the weather like?
- During the fire the temperature reached 40.6 °C, humidity dropped to 15 % and gusts hit 40 km/h. The fire danger index (FWI) reached 55, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Brazil (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: 193 · 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.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 69 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 ADM2 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.