Pebane fire, 6 September 2020 Pebane
The fire started on 6 September 2020 in Pebane, Mozambique, and satellites saw it burning for 28 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 12,694 hectares from heat detections, spread across a single municipality.
It is the 125th largest in Zambézia since 2016 (of 839 with a page). Number 20 in Mozambique in 2020, of 193.
Compare with…
Suggestions: Pebane · 2016Pebane · 2018Pebane · 2017Pebane · 2017
- Burnt area
- 12,694ha
- GWIS perimeter (Copernicus)
- Duration
- 28days
- 6 Sept 2020 – 3 Oct 2020
- Municipalities hit
- 1
- districts
- Started on
- 6 Sept
- 2020
- Heat detections
- 607
- in a single hotspot: 55 MW
- Danger at start
- 14
- Moderate · FWI index
- Average daily power
- 227MW
- 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 2 days without rain (1 mm or more) when it started. Rain came after the fire: 2.3 mm on 12 Oct.
This area had burned before
83% of the perimeter overlaps earlier fires recorded since 2016: 7,594 ha in 2016, 7,943 ha in 2017, 6,562 ha in 2018, 5,004 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 10,563 ha that had burned before.
- 4,816 ha Pebane fire, September 2016 10,511 ha in total; the hectares shown are those it shares with this fire
- 4,211 ha Pebane fire, September 2018 6,535 ha in total; the hectares shown are those it shares with this fire
- 3,061 ha Pebane fire, October 2017 5,856 ha in total; the hectares shown are those it shares with this fire
- 1,776 ha Pebane fire, October 2017 4,121 ha in total; the hectares shown are those it shares with this fire
- 1,765 ha Pebane fire, September 2018 3,023 ha in total; the hectares shown are those it shares with this fire
- 1,391 ha Pebane fire, October 2019 4,009 ha in total; the hectares shown are those it shares with this fire
- 942 ha Pebane fire, October 2017 4,157 ha in total; the hectares shown are those it shares with this fire
- 566 ha Pebane fire, October 2017 3,498 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
-
Pebane where it started12,782 ha reached on 6 Sept1.3 %
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 2020Inside the perimeter there were about 8.2 hectares of built-up land and about 1,200 residents (GHSL 2020, 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)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 6 Sept | 25.1 °C | 48 % | 37 km/h | 0.0 mm | Moderate 14 |
| 7 Sept | 25.0 °C | 57 % | 41 km/h | 0.3 mm | Moderate 15 |
| 8 Sept | 26.2 °C | 47 % | 43 km/h | 0.3 mm | Moderate 16 |
| 9 Sept | 27.1 °C | 51 % | 38 km/h | 0.1 mm | Moderate 15 |
| 10 Sept | 26.3 °C | 56 % | 35 km/h | 0.0 mm | Moderate 15 |
| 11 Sept | 27.2 °C | 57 % | 40 km/h | 0.0 mm | Moderate 16 |
| 12 Sept | 27.5 °C | 58 % | 37 km/h | 0.0 mm | Moderate 16 |
| 13 Sept | 28.7 °C | 53 % | 35 km/h | 0.0 mm | Moderate 16 |
| 14 Sept | 31.4 °C | 47 % | 34 km/h | 0.0 mm | Moderate 18 |
| 15 Sept | 35.8 °C | 22 % | 38 km/h | 0.0 mm | High 33 |
| 16 Sept | 34.5 °C | 28 % | 42 km/h | 0.0 mm | High 34 |
| 17 Sept | 34.7 °C | 29 % | 42 km/h | 0.0 mm | High 35 |
| 18 Sept | 31.7 °C | 41 % | 41 km/h | 0.0 mm | High 29 |
| 19 Sept | 31.3 °C | 41 % | 34 km/h | 0.0 mm | High 27 |
| 20 Sept | 32.0 °C | 40 % | 42 km/h | 0.0 mm | High 29 |
| 21 Sept | 33.6 °C | 24 % | 45 km/h | 0.0 mm | High 36 |
| 22 Sept | 28.3 °C | 53 % | 48 km/h | 2.6 mm | Low 9 |
| 23 Sept | 26.8 °C | 59 % | 50 km/h | 1.9 mm | Low 8 |
| 24 Sept | 26.1 °C | 56 % | 36 km/h | 0.0 mm | Low 11 |
| 25 Sept | 31.2 °C | 44 % | 42 km/h | 0.0 mm | Moderate 20 |
| 26 Sept | 36.5 °C | 19 % | 43 km/h | 0.0 mm | Very high 38 |
| 27 Sept | 37.3 °C | 24 % | 43 km/h | 0.0 mm | Very high 39 |
| 28 Sept | 36.3 °C | 27 % | 44 km/h | 0.0 mm | Very high 41 |
| 29 Sept | 35.7 °C | 24 % | 50 km/h | 0.0 mm | Very high 44 |
| 30 Sept | 32.3 °C | 44 % | 51 km/h | 0.0 mm | High 32 |
| 1 Oct | 33.0 °C | 42 % | 41 km/h | 0.0 mm | High 30 |
| 2 Oct | 34.6 °C | 36 % | 48 km/h | 0.0 mm | High 33 |
| 3 Oct | 31.6 °C | 48 % | 43 km/h | 0.0 mm | High 29 |
| 4 Oct after | 32.2 °C | 41 % | 45 km/h | 0.0 mm | High 29 |
| 5 Oct after | 29.0 °C | 58 % | 42 km/h | 0.1 mm | High 22 |
| 6 Oct after | 28.5 °C | 53 % | 41 km/h | 0.0 mm | High 23 |
| 7 Oct after | 27.1 °C | 58 % | 41 km/h | 0.0 mm | High 22 |
| 8 Oct after | 27.7 °C | 55 % | 34 km/h | 0.0 mm | High 21 |
| 9 Oct after | 29.8 °C | 46 % | 42 km/h | 0.0 mm | High 24 |
| 10 Oct after | 36.0 °C | 37 % | 43 km/h | 0.0 mm | High 31 |
| 11 Oct after | 35.0 °C | 39 % | 54 km/h | 0.0 mm | High 35 |
| 12 Oct after | 28.2 °C | 69 % | 42 km/h | 2.3 mm | Low 7 |
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.
Detections table · 607Every 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 Pebane fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 6 September 2020 to 3 October 2020 (28 days). The perimeter dates it from 13 September 2020 to 28 September 2020.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 12,694 hectares (126.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Pebane (12,782 ha, 1.3 %).
- What was the weather like?
- During the fire the temperature reached 37.3 °C, humidity dropped to 19 % and gusts hit 51 km/h. The fire danger index (FWI) reached 44, 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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Last day with fire: 28 September 2020 → 3 October 2020.
- Start date: 13 September 2020 → 6 September 2020.
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 13 September 2020 to 28 September 2020. 607 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 2020, 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.