Skip to content
worldfires
SZ · Eswatini · –

Mahlangatja fire, 19 July 2019 Mahlangatja, Ngwempisi

Out · last detection 24 Jul 2019, 12:06 UTC

The fire started on 19 July 2019 in Mahlangatja, Eswatini, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,959 hectares from heat detections, spread across 2 municipalities.

It is the 2th largest in Manzini since 2016 (of 14 with a page). Number 5 in Eswatini in 2019, of 19.

Burnt area
1,959ha
GWIS perimeter (Copernicus)
Duration
6days
19 Jul 2019 – 24 Jul 2019
Municipalities hit
2
tinkhundla
Started on
19 Jul
2019
Heat detections
59
in a single hotspot: 31 MW
Danger at start
48
Very high · FWI index
Average daily power
43MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 19 Jul24 Jul
24 Jul 2019

How it evolved, day by day

19 Jul 2019 · 100 MW · 30 20 Jul 2019 · 75 MW · 9 22 Jul 2019 · 15 MW · 8 23 Jul 2019 · 23 MW · 11 24 Jul 2019 · 2 MW · 1
19 Jul 20 Jul 22 Jul 23 Jul 24 Jul

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

The weather it burned in

25°high
70km/h · peak gust
9%lowest humidity

It had gone 22 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.

How big is it?

10 km
It burned the equivalent of 1.2% of the area of London (20 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. Mahlangatja where it started
    1,720 ha reached on 19 Jul
    3.8 %
  2. 247 ha reached on 22 Jul
    0.4 %

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 area1.0 ha
Residents≈ 100

Inside the perimeter there were about 1.0 hectares of built-up land and about 100 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)
19 Jul 24.8 °C 9 % 61 km/h 0.0 mm Very high 48
20 Jul 20.3 °C 16 % 54 km/h 1.5 mm High 23
21 Jul 14.2 °C 25 % 29 km/h 0.0 mm Moderate 19
22 Jul 22.8 °C 18 % 44 km/h 0.0 mm High 31
23 Jul 24.9 °C 11 % 51 km/h 0.0 mm Very high 42
24 Jul 23.3 °C 14 % 70 km/h 0.0 mm Very high 50
25 Jul after 23.2 °C 19 % 32 km/h 0.0 mm High 35
26 Jul after 22.0 °C 19 % 41 km/h 0.0 mm Very high 38
27 Jul after 20.6 °C 34 % 31 km/h 0.0 mm High 27
28 Jul after 23.2 °C 14 % 30 km/h 0.0 mm High 33
29 Jul after 24.1 °C 17 % 26 km/h 0.0 mm High 32
30 Jul after 27.1 °C 14 % 40 km/h 0.0 mm Very high 39
31 Jul after 25.7 °C 17 % 36 km/h 0.0 mm Very high 39
1 Aug after 19.4 °C 42 % 32 km/h 0.0 mm High 26
2 Aug after 22.3 °C 38 % 35 km/h 0.0 mm High 26
3 Aug after 26.5 °C 19 % 35 km/h 0.0 mm High 33

Its twins: fires that started in the same weather

It started with an FWI of 48.2, a minimum humidity of 9% and 22 days without rain. Fires in the area that started in weather like this since 2016: 20.

FWI at the start 48.2
Minimum humidity 9 %
Days without rain 22
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Mahlangatja fire, August 2020
1,506 ha 2 days FWI 48.2 Min. humidity 11 % 3 km away, in 2020

First rain (1 mm or more) after it ended: 4.1 mm on 17 Aug.

What happened to them

2 days
median duration
2,380 ha
median area
100 %
went past 1,000 ha
2.0 mm
rain at the end (median; 14 of 20 had it)

It burned an area similar to its twins (1,959 ha against a median of 2,380 ha) and lasted 6 days, against 2 days.

In 6 of 20, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.0 mm.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

—first rain
—no rain in ten days
70km/h · max. gust

It was considered over on 24 Jul, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 14 of 20, with a median of 2.0 mm.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 12 Jul 2019
After · 31 Jul 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 · 59Every 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 Eswatini

Frequently asked questions

How long did the Mahlangatja fire last?
GWIS (Copernicus) dates it between 19 July 2019 and 24 July 2019: 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 1,959 hectares (19.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Mahlangatja (1,720 ha, 3.8 %); Ngwempisi (247 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 24.9 °C, humidity dropped to 9 % and gusts hit 70 km/h. The fire danger index (FWI) reached 50, class Very high.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Eswatini (geoBoundaries). It is not an official report.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 20. Their median duration was 2 days and their median area 2,380 ha; 100 % went past 1,000 ha. In 6 of 20, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.0 mm.

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.

Satellite cross-check

History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

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.

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. 59 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 ADM2 (Open Data Commons Open Database License 1.0). 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.