Skip to content
worldfires
NA · Namibia · –

Omuthiyagwiipundi fire, August 2017 Omuthiyagwiipundi

Out · last detection 21 Aug 2017, 13:11 UTC

The fire started on 18 August 2017 in Omuthiyagwiipundi, Namibia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,355 hectares from heat detections, spread across a single municipality.

It is the 75th largest in Oshikoto since 2016 (of 83 with a page). Number 94 in Namibia in 2017, of 123.

The power measured by the satellite is low (18.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Burnt area
2,355ha
GWIS perimeter (Copernicus)
Duration
4days
18 Aug 2017 – 21 Aug 2017
Municipalities hit
1
constituencies
Started on
18 Aug
2017
Heat detections
81
in a single hotspot: 18 MW
Danger at start
92
Very extreme · FWI index
Average daily power
116MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 18 Aug21 Aug
21 Aug 2017

How it evolved, day by day

18 Aug 2017 · 251 MW · 46 19 Aug 2017 · 26 MW · 7 20 Aug 2017 · 133 MW · 17 21 Aug 2017 · 53 MW · 11
18 Aug 19 Aug 20 Aug 21 Aug

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

The weather it burned in

31°high
48km/h · peak gust
8%lowest humidity

It had gone more than two months 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.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

  1. Omuthiyagwiipundi where it started
    2,371 ha reached on 18 Aug
    0.2 %

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 2015
Built-up area0.89 ha
Residents≈ 40

Inside the perimeter there were about 0.89 hectares of built-up land and about 40 residents (GHSL 2015, 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)

Started with Extreme FWI: 91 % of the area in Namibia Very dry air: 81 % of the area in Namibia 60 days without rain: 88 % of the area in Namibia

Day High Min. humidity Peak gust Rain Danger (FWI)
18 Aug 25.7 °C 10 % 48 km/h 0.0 mm Very extreme 92
19 Aug 27.8 °C 10 % 41 km/h 0.0 mm Very extreme 78
20 Aug 29.9 °C 8 % 34 km/h 0.0 mm Extreme 68
21 Aug 30.9 °C 12 % 33 km/h 0.0 mm Extreme 64
22 Aug after 31.5 °C 12 % 26 km/h 0.0 mm Extreme 55
23 Aug after 31.7 °C 13 % 34 km/h 0.0 mm Very extreme 70
24 Aug after 31.9 °C 13 % 26 km/h 0.0 mm Extreme 64
25 Aug after 33.3 °C 8 % 31 km/h 0.0 mm Extreme 68
26 Aug after 32.9 °C 8 % 34 km/h 0.0 mm Extreme 64
27 Aug after 33.8 °C 9 % 33 km/h 0.0 mm Very extreme 77
28 Aug after 33.3 °C 13 % 35 km/h 0.0 mm Very extreme 78
29 Aug after 31.9 °C 12 % 38 km/h 0.0 mm Very extreme 79
30 Aug after 33.2 °C 12 % 35 km/h 0.0 mm Very extreme 80
31 Aug after 33.7 °C 12 % 33 km/h 0.0 mm Very extreme 78

Its twins: fires that started in the same weather

It started with an FWI of 92.3, a minimum humidity of 10% and more than two months without rain. Fires in the area that started in weather like this since 2016: 26.

FWI at the start 92.3
Minimum humidity 10 %
Days without rain 60+
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Okahao fire, September 2017
3,146 ha 3 days FWI 91.3 Min. humidity 11 % 211 km away, in 2017

First rain (1 mm or more) after it ended: none in the following ten days.

What happened to them

4 days
median duration
3,752 ha
median area
8 %
went past 10,000 ha
1.4 mm
rain at the end (median; 5 of 26 had it)

It stayed below its twins: 2,355 ha against a median of 3,752 ha. It lasted 4 days, against 4 days.

In 21 of 26, 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 1.4 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
48km/h · max. gust

It was considered over on 21 Aug, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 5 of 26, with a median of 1.4 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 · 11 Aug 2017
After · 28 Aug 2017

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 · 81Every 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 Namibia

Frequently asked questions

How long did the Omuthiyagwiipundi fire last?
GWIS (Copernicus) dates it between 18 August 2017 and 21 August 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,355 hectares (23.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Omuthiyagwiipundi (2,371 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 30.9 °C, humidity dropped to 8 % and gusts hit 48 km/h. The fire danger index (FWI) reached 92, class Very extreme.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Namibia (OCHA COD-AB). 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: 26. Their median duration was 4 days and their median area 3,752 ha; 8 % went past 10,000 ha. In 21 of 26, 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 1.4 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. 81 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 2015, 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 OCHA COD-AB (Namibia Statistics Agency (NSA)) (Creative Commons Attribution for Intergovernmental Organisations (CC BY-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.