Ezo fire, 22 December 2019 Ezo, Nagero, Nzara
The fire started on 22 December 2019 in Ezo, South Sudan, and satellites saw it burning for 25 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 72,777 hectares from heat detections, spread across 3 municipalities.
It is the 14th largest in Western Equatoria since 2016 (of 361 with a page). Number 3 in South Sudan in 2019, of 150.
Compare with…
Suggestions: Ezo · 2016Nzara · 2016Nagero · 2017Ezo · 2017
- Burnt area
- 72,777ha
- GWIS perimeter (Copernicus)
- Duration
- 25days
- 22 Dec 2019 – 15 Jan 2020
- Municipalities hit
- 3
- counties
- Started on
- 22 Dec
- 2019
- Heat detections
- 3,488
- in a single hotspot: 293 MW
- Danger at start
- 31
- High · FWI index
- Average daily power
- 1.8GW
- detected power per day, on average
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 6 days without rain (1 mm or more) when it started.
This area had burned before
73% of the perimeter overlaps earlier fires recorded since 2016: 38,910 ha in 2016, 30,115 ha in 2017, 6,985 ha in 2018, 177 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 53,357 ha that had burned before.
- 12,833 ha Ezo fire, December 2016 21,896 ha in total; the hectares shown are those it shares with this fire
- 8,711 ha Nzara fire, December 2016 156,948 ha in total; the hectares shown are those it shares with this fire
- 4,827 ha Nagero fire, December 2017 6,042 ha in total; the hectares shown are those it shares with this fire
- 1,686 ha Ezo fire, December 2017 5,669 ha in total; the hectares shown are those it shares with this fire
- 1,214 ha Nagero fire, December 2016 5,050 ha in total; the hectares shown are those it shares with this fire
- 1,017 ha Ezo fire, January 2016 5,810 ha in total; the hectares shown are those it shares with this fire
- 398 ha Nagero fire, January 2016 11,243 ha in total; the hectares shown are those it shares with this fire
- 202 ha Nagero fire, January 2018 5,940 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Ezo where it started46,211 ha reached on 22 Dec5.7 %
-
25,679 ha reached on 22 Dec2.8 %
-
1,411 ha reached on 22 Dec0.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 2020Inside the perimeter there were about 0.10 hectares of built-up land and about 550 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) |
|---|---|---|---|---|---|
| 22 Dec | 35.7 °C | 22 % | 30 km/h | 0.0 mm | High 31 |
| 23 Dec | 36.5 °C | 19 % | 27 km/h | 0.0 mm | High 33 |
| 24 Dec | 34.8 °C | 29 % | 27 km/h | 0.0 mm | High 32 |
| 25 Dec | 36.3 °C | 19 % | 34 km/h | 0.0 mm | High 36 |
| 26 Dec | 35.5 °C | 13 % | 36 km/h | 0.0 mm | Very high 41 |
| 27 Dec | 34.9 °C | 11 % | 32 km/h | 0.0 mm | Very high 42 |
| 28 Dec | 34.3 °C | 12 % | 35 km/h | 0.0 mm | Very high 44 |
| 29 Dec | 35.1 °C | 11 % | 32 km/h | 0.0 mm | Very high 42 |
| 30 Dec | 36.3 °C | 11 % | 33 km/h | 0.0 mm | Very high 43 |
| 31 Dec | 36.4 °C | 16 % | 31 km/h | 0.0 mm | Very high 43 |
| 1 Jan | 37.4 °C | 19 % | 31 km/h | 0.0 mm | Very high 42 |
| 2 Jan | 37.3 °C | 19 % | 38 km/h | 0.0 mm | Very high 46 |
| 3 Jan | 37.5 °C | 19 % | 39 km/h | 0.0 mm | Very high 48 |
| 4 Jan | 35.9 °C | 17 % | 34 km/h | 0.0 mm | Very high 45 |
| 5 Jan | 33.4 °C | 17 % | 35 km/h | 0.0 mm | Very high 47 |
| 6 Jan | 34.7 °C | 18 % | 34 km/h | 0.0 mm | Very high 46 |
| 7 Jan | 35.3 °C | 18 % | 36 km/h | 0.0 mm | Very high 47 |
| 8 Jan | 36.2 °C | 15 % | 38 km/h | 0.0 mm | Very high 49 |
| 9 Jan | 35.0 °C | 13 % | 39 km/h | 0.0 mm | Very high 50 |
| 10 Jan | 34.6 °C | 13 % | 35 km/h | 0.0 mm | Very high 48 |
| 11 Jan | 33.6 °C | 11 % | 35 km/h | 0.0 mm | Very high 49 |
| 12 Jan | 32.5 °C | 10 % | 36 km/h | 0.0 mm | Very high 50 |
| 13 Jan | 33.9 °C | 10 % | 31 km/h | 0.0 mm | Very high 46 |
| 14 Jan | 36.5 °C | 12 % | 32 km/h | 0.0 mm | Very high 47 |
| 15 Jan | 37.8 °C | 13 % | 26 km/h | 0.0 mm | Very high 46 |
| 16 Jan after | 38.8 °C | 17 % | 28 km/h | 0.0 mm | Very high 47 |
| 17 Jan after | 39.3 °C | 15 % | 35 km/h | 0.0 mm | Extreme 51 |
| 18 Jan after | 36.5 °C | 14 % | 34 km/h | 0.0 mm | Extreme 54 |
| 19 Jan after | 34.6 °C | 13 % | 35 km/h | 0.0 mm | Extreme 52 |
| 20 Jan after | 33.8 °C | 14 % | 38 km/h | 0.0 mm | Extreme 54 |
| 21 Jan after | 33.9 °C | 15 % | 39 km/h | 0.0 mm | Extreme 54 |
| 22 Jan after | 33.3 °C | 11 % | 38 km/h | 0.0 mm | Extreme 54 |
| 23 Jan after | 32.6 °C | 11 % | 38 km/h | 0.0 mm | Extreme 55 |
| 24 Jan after | 32.7 °C | 10 % | 37 km/h | 0.0 mm | Extreme 54 |
| 25 Jan after | 33.1 °C | 12 % | 38 km/h | 0.0 mm | Extreme 54 |
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.
Detections table · 3,488Every 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 Ezo fire last?
- GWIS (Copernicus) dates it between 22 December 2019 and 15 January 2020: 25 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 72,777 hectares (727.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Ezo (46,211 ha, 5.7 %); Nagero (25,679 ha, 2.8 %); Nzara (1,411 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 37.8 °C, humidity dropped to 10 % and gusts hit 39 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 South Sudan (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.
Satellite cross-check
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.
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
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 4 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 3,488 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.
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 (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.