Sanga fire, 4 October 2026 Sanga
The fire started on 4 October 2026 in Sanga, Mozambique, and satellites saw it burning for 17 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 14,231 hectares from heat detections, spread across a single municipality.
It is the 32th largest in Niassa since 2016 (of 589 with a page). Number 59 in Mozambique in 2026, of 552.
Compare with…
Suggestions: Sanga · 2016Sanga · 2023Sanga · 2018Sanga · 2022
- Burnt area
- 14,231ha
- GWIS perimeter (Copernicus)
- Duration
- 17days
- 4 Oct 2026 – 20 Oct 2026
- Municipalities hit
- 1
- districts
- Started on
- 4 Oct
- 2026
- Heat detections
- 305
- in a single hotspot: 143 MW
- Danger at start
- 24
- High · FWI index
- Average daily power
- 358MW
- 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 one day without rain (1 mm or more) when it started. Rain came after the fire: 1.0 mm on 29 Oct.
This area had burned before
87% of the perimeter overlaps earlier fires recorded since 2016: 6,742 ha in 2016, 1,977 ha in 2017, 2,133 ha in 2018, 938 ha in 2019, 3,534 ha in 2020, 2,319 ha in 2021, 1,913 ha in 2022, 1,355 ha in 2023, 1,146 ha in 2024, 3,402 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 12,392 ha that had burned before.
- 2,969 ha Sanga fire, October 2016 3,688 ha in total; the hectares shown are those it shares with this fire
- 556 ha Sanga fire, October 2023 4,331 ha in total; the hectares shown are those it shares with this fire
- 529 ha Sanga fire, September 2018 4,761 ha in total; the hectares shown are those it shares with this fire
- 367 ha Sanga fire, October 2022 4,063 ha in total; the hectares shown are those it shares with this fire
- 268 ha Sanga fire, October 2022 11,681 ha in total; the hectares shown are those it shares with this fire
- 90 ha Sanga fire, September 2025 3,319 ha in total; the hectares shown are those it shares with this fire
- 42 ha Sanga fire, October 2022 3,043 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
-
Sanga where it started14,302 ha reached on 4 Oct1.1 %
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) · forecast models, provisional until the ERA5 reanalysis arrives
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 4 Oct | 30.7 °C | 33 % | 38 km/h | 0.0 mm | High 24 |
| 5 Oct | 31.5 °C | 41 % | 40 km/h | 1.3 mm | Moderate 17 |
| 6 Oct | 33.1 °C | 28 % | 32 km/h | 0.0 mm | High 27 |
| 7 Oct | 34.2 °C | 29 % | 39 km/h | 0.0 mm | High 31 |
| 8 Oct | 34.6 °C | 24 % | 36 km/h | 0.0 mm | High 32 |
| 9 Oct | 34.3 °C | 27 % | 42 km/h | 0.0 mm | High 35 |
| 10 Oct | 33.6 °C | 30 % | 37 km/h | 0.0 mm | High 36 |
| 11 Oct | 33.2 °C | 31 % | 42 km/h | 0.6 mm | High 32 |
| 12 Oct | 33.1 °C | 27 % | 41 km/h | 0.9 mm | High 32 |
| 13 Oct | 32.2 °C | 32 % | 37 km/h | 0.7 mm | High 29 |
| 14 Oct | 33.2 °C | 27 % | 36 km/h | 0.0 mm | High 34 |
| 15 Oct | 33.0 °C | 27 % | 40 km/h | 0.3 mm | High 37 |
| 16 Oct | 33.0 °C | 25 % | 38 km/h | 0.1 mm | High 38 |
| 17 Oct | 32.6 °C | 27 % | 40 km/h | 0.2 mm | Very high 38 |
| 18 Oct | 31.7 °C | 30 % | 36 km/h | 0.0 mm | High 36 |
| 19 Oct | 34.8 °C | 29 % | 37 km/h | 0.0 mm | High 35 |
| 20 Oct | 36.5 °C | 24 % | 32 km/h | 0.0 mm | High 37 |
| 21 Oct after | 36.8 °C | 25 % | 31 km/h | 0.0 mm | Very high 38 |
| 22 Oct after | 38.7 °C | 15 % | 35 km/h | 0.0 mm | Very high 48 |
| 23 Oct after | 38.7 °C | 16 % | 34 km/h | 0.0 mm | Very high 48 |
| 24 Oct after | 36.2 °C | 22 % | 39 km/h | 0.0 mm | Very high 49 |
| 25 Oct after | 34.1 °C | 31 % | 39 km/h | 0.9 mm | High 33 |
| 26 Oct after | 35.0 °C | 29 % | 38 km/h | 0.6 mm | High 36 |
| 27 Oct after | 35.2 °C | 28 % | 36 km/h | 0.1 mm | High 37 |
| 28 Oct after | 36.3 °C | 21 % | 36 km/h | 0.0 mm | Very high 42 |
| 29 Oct after | 37.5 °C | 24 % | 30 km/h | 1.0 mm | High 35 |
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 9 October 2026 the air beside the fire reached 72 µ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 · 305Every 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 Sanga fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 4 October 2026 to 20 October 2026 (17 days). The perimeter dates it from 6 October 2026 to 13 October 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 14,231 hectares (142.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Sanga (14,302 ha, 1.1 %).
- Is the Sanga fire still active?
- No fire detections since 20 Oct 2026, 11:51 UTC. A lack of detections is not an official extinction.
- What was the weather like?
- During the fire the temperature reached 36.5 °C, humidity dropped to 24 % and gusts hit 42 km/h. The fire danger index (FWI) reached 38, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Mozambique (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.
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 adjusted with the VIIRS detections inside the perimeter, which said 6 October 2026 to 13 October 2026. 305 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives.
- 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.