Skip to content
worldfires
ZA · South Africa · –

Mogalakwena fire, 1 September 2016 Mogalakwena

Out · last detection 11 Sept 2016, 23:32 UTC

The fire started on 1 September 2016 in Mogalakwena, South Africa, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 9,774 hectares from heat detections, spread across a single municipality.

It is the 8th largest in Limpopo since 2016 (of 161 with a page). Number 9 in South Africa in 2016, of 71.

The power measured by the satellite is low (14.0 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Burnt area
9,774ha
GWIS perimeter (Copernicus)
Duration
12days
1 Sept 2016 – 12 Sept 2016
Municipalities hit
1
municipalities
Started on
1 Sept
2016
Heat detections
327
in a single hotspot: 14 MW
Danger at start
51
Extreme · FWI index
Average daily power
96MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 1 Sept12 Sept
11 Sept 2016

How it evolved, day by day

1 Sept 2016 · 20 MW · 10 2 Sept 2016 · 132 MW · 52 3 Sept 2016 · 221 MW · 68 4 Sept 2016 · 164 MW · 38 5 Sept 2016 · 200 MW · 58 6 Sept 2016 · 92 MW · 34 7 Sept 2016 · 32 MW · 13 8 Sept 2016 · 82 MW · 22 9 Sept 2016 · 31 MW · 11 10 Sept 2016 · 60 MW · 14 11 Sept 2016 · 24 MW · 7
3 Sept 7 Sept 10 Sept

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

35°high
50km/h · peak gust
13%lowest humidity

It had gone 35 days without rain (1 mm or more) when it started. Rain came after the fire: 4.3 mm on 19 Sept.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 6.2% of the area of London (98 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Mogalakwena where it started
    9,812 ha reached on 1 Sept
    1.6 %

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 2015
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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)
1 Sept 25.7 °C 15 % 31 km/h 0.0 mm Extreme 51
2 Sept 26.3 °C 21 % 27 km/h 0.0 mm Very high 45
3 Sept 27.6 °C 19 % 20 km/h 0.0 mm Very high 38
4 Sept 28.3 °C 18 % 27 km/h 0.0 mm Very high 43
5 Sept 29.6 °C 15 % 27 km/h 0.0 mm Very high 46
6 Sept 31.1 °C 13 % 32 km/h 0.0 mm Extreme 56
7 Sept 32.3 °C 15 % 34 km/h 0.0 mm Extreme 58
8 Sept 33.3 °C 15 % 38 km/h 0.0 mm Extreme 58
9 Sept 34.7 °C 14 % 34 km/h 0.0 mm Extreme 58
10 Sept 28.0 °C 28 % 50 km/h 0.0 mm Extreme 64
11 Sept 25.5 °C 37 % 45 km/h 0.0 mm Very high 45
12 Sept 28.4 °C 27 % 39 km/h 0.0 mm Very high 45
13 Sept after 32.0 °C 12 % 47 km/h 0.0 mm Extreme 57
14 Sept after 24.8 °C 37 % 52 km/h 0.0 mm Extreme 54
15 Sept after 30.2 °C 23 % 42 km/h 0.0 mm Very high 50
16 Sept after 34.5 °C 14 % 45 km/h 0.0 mm Very extreme 72
17 Sept after 31.0 °C 13 % 38 km/h 0.5 mm Extreme 59
18 Sept after 18.0 °C 61 % 41 km/h 0.6 mm High 22
19 Sept after 17.6 °C 72 % 29 km/h 4.3 mm Very low 5

Its twins: fires that started in the same weather

It started with an FWI of 50.6, a minimum humidity of 15% and 35 days without rain. Fires in the area that started in weather like this since 2016: 12.

FWI at the start 50.6
Minimum humidity 15 %
Days without rain 35
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Madibeng fire, August 2018
3,371 ha 2 days FWI 48.1 Min. humidity 15 % 162 km away, in 2018

First rain (1 mm or more) after it ended: none in the following ten days.

What happened to them

Fires in the area that started in similar weather: 12. With fewer than 15 we give no figures: they would be more noise than signal.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

4.3 mmfirst rain
19 Sept7 days after it ended
50km/h · max. gust

It was considered over on 12 Sept, and on 19 Sept 4.3 mm fell. We do not know whether the rain or the firefighters put it out.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 25 Aug 2016
After · 19 Sept 2016

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 · 327Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in South Africa

Frequently asked questions

How long did the Mogalakwena fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 1 September 2016 to 12 September 2016 (12 days). The perimeter dates it from 1 September 2016 to 11 September 2016.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 9,774 hectares (97.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Mogalakwena (9,812 ha, 1.6 %).
What was the weather like?
During the fire the temperature reached 34.7 °C, humidity dropped to 13 % and gusts hit 50 km/h. The fire danger index (FWI) reached 64, class Extreme.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of South Africa (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: 10177 · 112 · 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.
  1. Last day with fire: 11 September 2016 → 12 September 2016.

RSS Changes to this page With cross-checks and a citable version

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 10177 · 112.

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 1 September 2016 to 11 September 2016. 327 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 2015, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

How we build fire pages: methodology

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 (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.