Skip to content
worldfires
SS · South Sudan · →

Pibor fire, 9 January 2016 Pibor

Out · last detection 11 Jan 2016, 23:01 UTC

The fire started on 9 January 2016 in Pibor, South Sudan, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,091 hectares from heat detections, spread across a single municipality.

It is the 224th largest in Jonglei since 2016 (of 427 with a page). Number 130 in South Sudan in 2016, of 244.

Burnt area
7,091ha
GWIS perimeter (Copernicus)
Duration
3days
9 Jan 2016 – 11 Jan 2016
Municipalities hit
1
counties
Started on
9 Jan
2016
Heat detections
201
in a single hotspot: 119 MW
Danger at start
37
High · FWI index
Energy released
3.4GW
sum of detected power

Where it burned

11 Jan 2016
HOTSPOTS BY DAY 9 Jan11 Jan

How it evolved, day by day

91011

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

The weather it burned in

39°high
40km/h · peak gust
16%lowest humidity

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

What happened to each town

  1. Pibor where it started
    7,128 ha reached on 9 Jan
    0.2 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.

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)
9 Jan 38.2 °C 24 % 38 km/h 0.0 mm High 37
10 Jan 38.9 °C 16 % 30 km/h 0.0 mm Very high 40
11 Jan 38.3 °C 25 % 40 km/h 0.0 mm Very high 42
12 Jan after 37.9 °C 26 % 50 km/h 0.0 mm Extreme 51
13 Jan after 37.1 °C 26 % 45 km/h 0.0 mm Very high 46
14 Jan after 38.4 °C 25 % 33 km/h 0.1 mm Very high 39
15 Jan after 36.2 °C 31 % 42 km/h 0.6 mm High 36
16 Jan after 36.8 °C 31 % 37 km/h 0.3 mm High 33
17 Jan after 35.9 °C 31 % 33 km/h 0.0 mm High 31
18 Jan after 37.0 °C 25 % 23 km/h 0.0 mm High 32
19 Jan after 37.9 °C 14 % 26 km/h 0.0 mm Very high 40
20 Jan after 36.4 °C 17 % 28 km/h 0.0 mm Very high 43
21 Jan after 35.7 °C 25 % 24 km/h 0.0 mm High 37

Before and after, from space

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

Before · 2 Jan 2016
After · 18 Jan 2016

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 · 201Every 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 9 January 2016 and 11 January 2016: 3 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 7,091 hectares (70.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Pibor (7,128 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 38.9 °C, humidity dropped to 16 % and gusts hit 40 km/h. The fire danger index (FWI) reached 42, 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

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.

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.