Skip to content
worldfires
ZA · South Africa · →

Overstrand fire, January 2016 Overstrand, Theewaterskloof

Out · last detection 19 Jan 2016, 12:43 UTC

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

It is the 125th largest in Western Cape since 2016 (of 164 with a page). Number 43 in South Africa in 2016, of 71.

Burnt area
2,804ha
GWIS perimeter (Copernicus)
Duration
4days
16 Jan 2016 – 19 Jan 2016
Municipalities hit
2
municipalities
Started on
16 Jan
2016
Heat detections
169
in a single hotspot: 355 MW
Danger at start
13
Moderate · FWI index
Energy released
4.4GW
sum of detected power

Where it burned

19 Jan 2016
HOTSPOTS BY DAY 16 Jan19 Jan

How it evolved, day by day

16171819

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

The weather it burned in

29°high
62km/h · peak gust
47%lowest humidity

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

This area had burned before

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

What happened to each town

  1. Overstrand where it started
    2,345 ha reached on 16 Jan
    1.4 %
  2. 461 ha reached on 16 Jan
    0.1 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.

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)
16 Jan 25.8 °C 50 % 62 km/h 0.0 mm Moderate 13
17 Jan 28.7 °C 47 % 51 km/h 0.0 mm Moderate 13
18 Jan 26.8 °C 54 % 42 km/h 0.3 mm Moderate 12
19 Jan 27.4 °C 48 % 53 km/h 0.0 mm Moderate 15
20 Jan after 26.6 °C 55 % 55 km/h 0.0 mm Moderate 16
21 Jan after 26.6 °C 55 % 61 km/h 0.0 mm Moderate 17
22 Jan after 23.8 °C 70 % 56 km/h 0.1 mm Moderate 12
23 Jan after 25.5 °C 65 % 44 km/h 0.0 mm Low 10
24 Jan after 22.2 °C 65 % 55 km/h 1.0 mm Low 8

Before and after, from space

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

Before · 9 Jan 2016
After · 26 Jan 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 · 169Every 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 16 January 2016 and 19 January 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,804 hectares (28.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Overstrand (2,345 ha, 1.4 %); Theewaterskloof (461 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 28.7 °C, humidity dropped to 47 % and gusts hit 62 km/h. The fire danger index (FWI) reached 15, class Moderate.
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

Satellite cross-check

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.

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.