Skip to content
worldfires
SS · South Sudan · →

Pibor fire, February 2024 Pibor

Out · last detection 29 Feb 2024, 22:53 UTC

The fire started on 28 February 2024 in Pibor, South Sudan, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 10,274 hectares from heat detections, spread across a single municipality.

It is the 115th largest in Jonglei since 2016 (of 427 with a page). Number 58 in South Sudan in 2024, of 180.

Compare with…
Burnt area
10,274ha
GWIS perimeter (Copernicus)
Duration
2days
28 Feb 2024 – 29 Feb 2024
Municipalities hit
1
counties
Started on
28 Feb
2024
Heat detections
227
in a single hotspot: 169 MW
Danger at start
59
Extreme · FWI index
Average daily power
3.9GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 28 Feb29 Feb
29 Feb 2024

How it evolved, day by day

28 Feb 2024 · 31 MW · 23 29 Feb 2024 · 7,674 MW · 203
28 Feb 29 Feb

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

The weather it burned in

41°high
39km/h · peak gust
15%lowest humidity

It had gone 27 days without rain (1 mm or more) when it started. Rain came after the fire: 2.3 mm on 6 Mar.

This area had burned before

62% of the perimeter overlaps earlier fires recorded since 2016: 3,218 ha in 2016, 2,092 ha in 2017, 2,347 ha in 2018, 1,111 ha in 2021, 1,722 ha in 2022, 42 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 6,351 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 6.5% of the area of London (103 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. Pibor where it started
    10,333 ha reached on 27 Feb
    0.3 %

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 2025
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.

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)
28 Feb 38.0 °C 22 % 39 km/h 0.0 mm Extreme 59
29 Feb 40.9 °C 15 % 34 km/h 0.0 mm Extreme 52
1 Mar after 39.5 °C 24 % 54 km/h 0.1 mm Extreme 66
2 Mar after 39.8 °C 19 % 50 km/h 0.2 mm Extreme 64
3 Mar after 41.1 °C 18 % 41 km/h 0.0 mm Extreme 55
4 Mar after 41.9 °C 18 % 31 km/h 0.0 mm Very high 46
5 Mar after 41.1 °C 22 % 53 km/h 0.8 mm Extreme 58
6 Mar after 38.7 °C 28 % 52 km/h 2.3 mm Very high 41

Before and after, from space

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

Before · 21 Feb 2024
After · 7 Mar 2024

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 · Copernicus

On 27 February 2024 the air beside the fire reached 65 µg/m³ of PM2.5. That day averaged 50: 3.4 times the WHO daily guideline (15).

PM2.5 peak65 µg/m³
Days over the guideline7 days
PM1095 µg/m³
Optical depth1.24
26272829123
Good Fair Moderate Poor Very poor Extremely poor

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 · 227Every 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 South Sudan ›

Frequently asked questions

How long did the Pibor fire last?
GWIS (Copernicus) dates it between 28 February 2024 and 29 February 2024: 2 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 10,274 hectares (102.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Pibor (10,333 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 40.9 °C, humidity dropped to 15 % and gusts hit 39 km/h. The fire danger index (FWI) reached 59, class Extreme.
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.

RSS Changes to this page

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. 227 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 2025, 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 (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.