Dihlabeng fire, March 2024 Dihlabeng
The fire started on 4 March 2024 in Dihlabeng, South Africa, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,234 hectares from heat detections, spread across a single municipality.
It is the 11th largest in Free State since 2016 (of 91 with a page). Number 35 in South Africa in 2024, of 121.
- Burnt area
- 4,234ha
- GWIS perimeter (Copernicus)
- Duration
- 6days
- 4 Mar 2024 – 9 Mar 2024
- Municipalities hit
- 1
- municipalities
- Started on
- 4 Mar
- 2024
- Heat detections
- 187
- in a single hotspot: 104 MW
- Danger at start
- 10
- Low · FWI index
- Energy released
- 1.6GW
- sum of detected power
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 8 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Dihlabeng where it started4,255 ha reached on 5 Mar0.9 %
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) |
|---|---|---|---|---|---|
| 4 Mar | 25.8 °C | 37 % | 44 km/h | 1.9 mm | Low 10 |
| 5 Mar | 26.7 °C | 27 % | 49 km/h | 0.0 mm | Moderate 19 |
| 6 Mar | 27.1 °C | 19 % | 41 km/h | 0.0 mm | High 22 |
| 7 Mar | 27.9 °C | 21 % | 49 km/h | 0.0 mm | High 27 |
| 8 Mar | 29.0 °C | 19 % | 37 km/h | 0.0 mm | High 24 |
| 9 Mar | 29.6 °C | 23 % | 36 km/h | 0.0 mm | High 25 |
| 10 Mar after | 30.5 °C | 23 % | 30 km/h | 0.0 mm | High 24 |
| 11 Mar after | 29.8 °C | 24 % | 32 km/h | 0.0 mm | High 26 |
| 12 Mar after | 28.9 °C | 25 % | 29 km/h | 0.1 mm | High 25 |
| 13 Mar after | 30.0 °C | 18 % | 44 km/h | 0.0 mm | High 32 |
| 14 Mar after | 27.2 °C | 12 % | 50 km/h | 0.0 mm | Very high 39 |
| 15 Mar after | 26.9 °C | 27 % | 46 km/h | 0.0 mm | High 33 |
| 16 Mar after | 31.0 °C | 13 % | 41 km/h | 0.0 mm | High 36 |
| 17 Mar after | 27.9 °C | 25 % | 49 km/h | 0.0 mm | High 37 |
| 18 Mar after | 27.6 °C | 29 % | 44 km/h | 0.4 mm | High 33 |
| 19 Mar after | 29.9 °C | 19 % | 44 km/h | 0.0 mm | Very high 41 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 10 March 2024 the air beside the fire reached 16 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 187Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Dihlabeng fire last?
- GWIS (Copernicus) dates it between 4 March 2024 and 9 March 2024: 6 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 4,234 hectares (42.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Dihlabeng (4,255 ha, 0.9 %).
- What was the weather like?
- During the fire the temperature reached 29.6 °C, humidity dropped to 19 % and gusts hit 49 km/h. The fire danger index (FWI) reached 27, class High.
- 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
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.