Pochalla fire, 25 January 2022 Pochalla
The fire started on 25 January 2022 in Pochalla, South Sudan, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,620 hectares from heat detections, spread across a single municipality.
It is the 345th largest in Jonglei since 2016 (of 427 with a page). Number 102 in South Sudan in 2022, of 124.
Compare with…
- Burnt area
- 5,620ha
- GWIS perimeter (Copernicus)
- Duration
- 6days
- 25 Jan 2022 – 30 Jan 2022
- Municipalities hit
- 1
- counties
- Started on
- 25 Jan
- 2022
- Heat detections
- 230
- in a single hotspot: 167 MW
- Danger at start
- 32
- High · FWI index
- Average daily power
- 814MW
- 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 7 days without rain (1 mm or more) when it started.
This area had burned before
87% of the perimeter overlaps earlier fires recorded since 2016: 2,402 ha in 2016, 373 ha in 2017, 1,235 ha in 2018, 2,856 ha in 2019, 92 ha in 2020, 2,154 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 4,863 ha that had burned before.
- 471 ha Pochalla fire, January 2021 7,069 ha in total; the hectares shown are those it shares with this fire
- 373 ha Pochalla fire, December 2017 14,517 ha in total; the hectares shown are those it shares with this fire
- 258 ha Pochalla fire, December 2018 27,715 ha in total; the hectares shown are those it shares with this fire
- 127 ha Pochalla fire, January 2021 13,739 ha in total; the hectares shown are those it shares with this fire
- 22 ha Pibor fire, December 2016 27,293 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
-
Pochalla where it started5,652 ha reached on 18 Jan0.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.
People and buildings inside the perimeter
GHSL 2020Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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) |
|---|---|---|---|---|---|
| 25 Jan | 37.1 °C | 23 % | 19 km/h | 0.0 mm | High 32 |
| 26 Jan | 36.6 °C | 25 % | 21 km/h | 0.0 mm | High 32 |
| 27 Jan | 37.1 °C | 20 % | 16 km/h | 0.0 mm | High 32 |
| 28 Jan | 36.6 °C | 24 % | 19 km/h | 0.0 mm | High 35 |
| 29 Jan | 37.1 °C | 22 % | 19 km/h | 0.0 mm | High 36 |
| 30 Jan | 36.7 °C | 21 % | 22 km/h | 0.0 mm | High 36 |
| 31 Jan after | 37.0 °C | 18 % | 18 km/h | 0.0 mm | High 36 |
| 1 Feb after | 37.1 °C | 19 % | 24 km/h | 0.0 mm | Very high 38 |
| 2 Feb after | 37.1 °C | 22 % | 18 km/h | 0.0 mm | High 36 |
| 3 Feb after | 36.7 °C | 21 % | 29 km/h | 0.0 mm | Very high 38 |
| 4 Feb after | 36.9 °C | 22 % | 24 km/h | 0.0 mm | High 37 |
| 5 Feb after | 38.1 °C | 17 % | 23 km/h | 0.1 mm | Very high 41 |
| 6 Feb after | 35.9 °C | 15 % | 23 km/h | 0.0 mm | Very high 42 |
| 7 Feb after | 36.4 °C | 16 % | 22 km/h | 0.0 mm | Very high 38 |
| 8 Feb after | 37.8 °C | 17 % | 26 km/h | 0.0 mm | Very high 40 |
| 9 Feb after | 38.2 °C | 18 % | 28 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.
Detections table · 230Every 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 Pochalla fire last?
- GWIS (Copernicus) dates it between 25 January 2022 and 30 January 2022: 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 5,620 hectares (56.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Pochalla (5,652 ha, 0.7 %).
- What was the weather like?
- During the fire the temperature reached 37.1 °C, humidity dropped to 20 % and gusts hit 22 km/h. The fire danger index (FWI) reached 36, class 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.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 230 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.