How long did the Oudtshoorn fire last?

GWIS (Copernicus) dates it between 6 July 2017 and 9 July 2017: 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,400 hectares (24.0 km²). It is an estimate: official national figures may differ.

Which municipalities burned?

The fire only entered Oudtshoorn (2,402 ha, 0.7 %).

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.

ZA · South Africa · 2017-07-06 → 2017-07-09

Oudtshoorn fire, July 2017 Oudtshoorn

Out · last detection 8 Jul 2017, 23:10 UTC

The fire started on 6 July 2017 in Oudtshoorn, South Africa, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,400 hectares from heat detections, spread across a single municipality.

It is the 143th largest in Western Cape since 2016 (of 164 with a page). Number 97 in South Africa in 2017, of 128.

Compare with…

Suggestions: Kannaland · 2017 Oudtshoorn · 2024 Prince Albert · 2016 Prince Albert · 2019

Burnt area: 2,400ha; GWIS perimeter (Copernicus)
Duration: 4days; 6 Jul 2017 – 9 Jul 2017
Municipalities hit: 1; municipalities
Started on: 6 Jul; 2017
Heat detections: 95; in a single hotspot: 110 MW
Average daily power: 356MW; detected power per day, on average

HOTSPOTS BY DAY 6 Jul9 Jul

Play back 8 Jul 2017

How it evolved, day by day

6 Jul 7 Jul 8 Jul

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?

It burned the equivalent of 1.5% of the area of London (24 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

Oudtshoorn where it started

2,402 ha reached on 6 Jul

0.7 %

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.

Before and after, from space

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

↔

Before · 29 Jun 2017

After · 16 Jul 2017

Before After

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 · 95Every 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 time	Satellite	FRP (MW)	Lat	Lon

Other fires nearby

All fires in South Africa ›

Frequently asked questions

How long did the Oudtshoorn fire last?: GWIS (Copernicus) dates it between 6 July 2017 and 9 July 2017: 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,400 hectares (24.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?: The fire only entered Oudtshoorn (2,402 ha, 0.7 %).
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

NASA FIRMS ↗
GWIS · Copernicus ↗

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?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

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. 95 Suomi-NPP VIIRS detections on those dates.
We have not matched this page with any official record.

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.

Where it burned