Skip to content
worldfires
ZA · South Africa · →

Overstrand fire, January 2019 Overstrand, City of Cape Town

Out · last detection 12 Jan 2019, 12:23 UTC

The fire started on 2 January 2019 in Overstrand, South Africa, and satellites saw it burning for 11 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 11,405 hectares from heat detections, spread across 2 municipalities.

It is the 29th largest in Western Cape since 2016 (of 164 with a page). Number 4 in South Africa in 2019, of 130.

Compare with…
Burnt area
11,405ha
GWIS perimeter (Copernicus)
Duration
11days
2 Jan 2019 – 12 Jan 2019
Municipalities hit
2
municipalities
Started on
2 Jan
2019
Heat detections
487
in a single hotspot: 489 MW
Danger at start
5
Very low · FWI index
Average daily power
954MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 2 Jan12 Jan
12 Jan 2019

How it evolved, day by day

2 Jan 2019 · 4,292 MW · 76 3 Jan 2019 · 281 MW · 28 4 Jan 2019 · 1,783 MW · 62 5 Jan 2019 · 635 MW · 33 6 Jan 2019 · 977 MW · 128 7 Jan 2019 · 74 MW · 26 8 Jan 2019 · 438 MW · 40 9 Jan 2019 · 156 MW · 18 10 Jan 2019 · 1 MW · 1 11 Jan 2019 · 1,858 MW · 74 12 Jan 2019 · 4 MW · 1
2 Jan 4 Jan 6 Jan 8 Jan 10 Jan 12 Jan

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

The weather it burned in

23°high
92km/h · peak gust
44%lowest humidity

It had gone 0 days without rain (1 mm or more) when it started. Rain came after the fire: 7.3 mm on 18 Jan.

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 7.2% of the area of London (114 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. Overstrand where it started
    9,143 ha reached on 2 Jan
    5.4 %
  2. 2,235 ha reached on 6 Jan
    0.9 %

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 2020
Built-up area25 ha
Residents≈ 450

Inside the perimeter there were about 25 hectares of built-up land and about 450 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)
2 Jan 17.6 °C 53 % 66 km/h 0.1 mm Very low 5
3 Jan 22.7 °C 44 % 65 km/h 0.0 mm Low 9
4 Jan 20.2 °C 61 % 38 km/h 0.0 mm Low 5
5 Jan 18.5 °C 60 % 44 km/h 0.0 mm Low 6
6 Jan 21.5 °C 47 % 49 km/h 0.0 mm Low 8
7 Jan 19.1 °C 64 % 44 km/h 0.0 mm Low 6
8 Jan 19.3 °C 57 % 48 km/h 0.0 mm Low 7
9 Jan 19.6 °C 65 % 46 km/h 0.8 mm Very low 5
10 Jan 18.1 °C 59 % 53 km/h 0.0 mm Low 7
11 Jan 19.2 °C 52 % 92 km/h 10.4 mm Very low 3
12 Jan 16.9 °C 52 % 57 km/h 0.0 mm Very low 3
13 Jan after 19.0 °C 55 % 50 km/h 0.0 mm Very low 5
14 Jan after 18.0 °C 57 % 36 km/h 0.0 mm Very low 4
15 Jan after 18.4 °C 63 % 51 km/h 0.0 mm Low 6
16 Jan after 23.4 °C 49 % 53 km/h 0.0 mm Low 9
17 Jan after 20.8 °C 63 % 33 km/h 0.0 mm Low 6
18 Jan after 16.1 °C 64 % 60 km/h 7.3 mm Very low 0

Before and after, from space

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

Before · 26 Dec 2018
After · 19 Jan 2019

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 · 487Every 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 Overstrand fire last?
GWIS (Copernicus) dates it between 2 January 2019 and 12 January 2019: 11 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 11,405 hectares (114.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Overstrand (9,143 ha, 5.4 %); City of Cape Town (2,235 ha, 0.9 %).
What was the weather like?
During the fire the temperature reached 22.7 °C, humidity dropped to 44 % and gusts hit 92 km/h. The fire danger index (FWI) reached 9, class Low.
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; 2 polygons grouped in this page.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 487 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.

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.