Skip to content
worldfires
ZA · South Africa · →

Thaba Chweu fire, 27 August 2016 Thaba Chweu, Greater Tubatse/Fetakgomo

Out · last detection 30 Aug 2016, 11:03 UTC

The fire started on 27 August 2016 in Thaba Chweu, South Africa, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,257 hectares from heat detections, spread across 2 municipalities.

It is the 164th largest in Mpumalanga since 2016 (of 214 with a page). Number 60 in South Africa in 2016, of 71.

Compare with…
Burnt area
2,257ha
GWIS perimeter (Copernicus)
Duration
4days
27 Aug 2016 – 30 Aug 2016
Municipalities hit
2
municipalities
Started on
27 Aug
2016
Heat detections
65
in a single hotspot: 179 MW
Average daily power
130MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 27 Aug30 Aug
30 Aug 2016

How it evolved, day by day

27 Aug 2016 · 57 MW · 20 28 Aug 2016 · 180 MW · 33 29 Aug 2016 · 88 MW · 9 30 Aug 2016 · 193 MW · 2
27 Aug 28 Aug 29 Aug 30 Aug

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

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 1.4% of the area of London (23 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. Thaba Chweu where it started
    1,603 ha reached on 26 Aug
    0.3 %
  2. 663 ha reached on 27 Aug
    0.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 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

Before and after, from space

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

Before · 20 Aug 2016
After · 6 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 · 65Every 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 Thaba Chweu fire last?
GWIS (Copernicus) dates it between 27 August 2016 and 30 August 2016: 4 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 2,257 hectares (22.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Thaba Chweu (1,603 ha, 0.3 %); Greater Tubatse/Fetakgomo (663 ha, 0.1 %).
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 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

No changes since 24 October 2026.

RSS Changes to this page

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 from the perimeter: the VIIRS detections inside it did not change them. 65 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • 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.