Lower Orakzai fire, December 2019 Lower Orakzai
The fire started on 22 December 2019 in Lower Orakzai, Pakistan, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,250 hectares from heat detections, spread across a single municipality.
It is the 28th largest in Khyber Pakhtunkhwa since 2016 (of 46 with a page). Number 2 in Pakistan in 2019, of 3.
The power measured by the satellite is low (6.4 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 1,250ha
- GWIS perimeter (Copernicus)
- Duration
- 2days
- 22 Dec 2019 – 23 Dec 2019
- Municipalities hit
- 1
- subdistricts
- Started on
- 22 Dec
- 2019
- Heat detections
- 39
- in a single hotspot: 6 MW
- Danger at start
- 6
- Low · FWI index
- Average daily power
- 52MW
- 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
75% of the perimeter overlaps earlier fires recorded since 2016: 1,056 ha in 2016, 388 ha in 2017. Part of it burned more than once, so the yearly figures add up to more than the 941 ha that had burned before.
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
-
Lower Orakzai where it started1,253 ha reached on 22 Dec2.4 %
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) |
|---|---|---|---|---|---|
| 22 Dec | 14.0 °C | 28 % | 19 km/h | 0.0 mm | Low 6 |
| 23 Dec | 14.3 °C | 26 % | 20 km/h | 0.0 mm | Low 7 |
| 24 Dec after | 11.7 °C | 36 % | 20 km/h | 0.0 mm | Low 6 |
| 25 Dec after | 13.0 °C | 24 % | 20 km/h | 0.0 mm | Low 8 |
| 26 Dec after | 14.8 °C | 21 % | 20 km/h | 0.0 mm | Low 8 |
| 27 Dec after | 12.8 °C | 31 % | 18 km/h | 0.0 mm | Low 8 |
| 28 Dec after | 12.2 °C | 35 % | 19 km/h | 0.0 mm | Low 8 |
| 29 Dec after | 13.0 °C | 29 % | 18 km/h | 0.0 mm | Low 8 |
| 30 Dec after | 12.7 °C | 30 % | 23 km/h | 0.0 mm | Low 8 |
| 31 Dec after | 9.5 °C | 42 % | 31 km/h | 0.0 mm | Low 8 |
| 1 Jan after | 9.0 °C | 39 % | 27 km/h | 0.4 mm | Low 7 |
| 2 Jan after | 8.4 °C | 52 % | 32 km/h | 0.7 mm | Very low 4 |
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 · 39Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 1,262 haLower OrakzaiDecember 2021 · 4 days · 0 km away
- 1,412 haLower Orakzai13 November 2016 · 4 days · 1 km away
- 1,679 haKohatNovember 2016 · 5 days · 11 km away
- 1,971 haLower Orakzai30 November 2016 · 3 days · 12 km away
- 1,536 haFR KohatOctober 2020 · 4 days · 12 km away
- 1,354 haHanguOctober 2020 · 2 days · 25 km away
Frequently asked questions
- How long did the Lower Orakzai fire last?
- GWIS (Copernicus) dates it between 22 December 2019 and 23 December 2019: 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 1,250 hectares (12.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Lower Orakzai (1,253 ha, 2.4 %).
- What was the weather like?
- During the fire the temperature reached 14.3 °C, humidity dropped to 26 % and gusts hit 20 km/h. The fire danger index (FWI) reached 7, class Low.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Pakistan (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.
Emergency number: 1122 · 16 · Emergency number and official warnings ›
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. 39 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 ADM3 (Open Data Commons Open Database License 1.0). 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.