Skip to content
worldfires
PK · Pakistan · →

Mianwali fire, April 2017 Mianwali

Out · last detection 4 May 2017, 09:05 UTC

The fire started on 28 April 2017 in Mianwali, Pakistan, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,711 hectares from heat detections, spread across a single municipality.

It is the 18th largest in Punjab since 2016 (of 48 with a page). Number 2 in Pakistan in 2017, of 5.

Compare with…
Burnt area
1,711ha
GWIS perimeter (Copernicus)
Duration
7days
28 Apr 2017 – 4 May 2017
Municipalities hit
1
subdistricts
Started on
28 Apr
2017
Heat detections
59
in a single hotspot: 108 MW
Danger at start
28
High · FWI index
Average daily power
168MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 28 Apr4 May
4 May 2017

How it evolved, day by day

28 Apr 2017 · 1 MW · 1 29 Apr 2017 · 122 MW · 6 30 Apr 2017 · 24 MW · 2 1 May 2017 · 181 MW · 11 3 May 2017 · 6 MW · 5 4 May 2017 · 676 MW · 30
28 Apr 29 Apr 30 Apr 1 May 3 May 4 May

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

The weather it burned in

42°high
59km/h · peak gust
14%lowest humidity

It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 1.7 mm on 15 May.

This area had burned before

11% of the perimeter overlaps earlier fires recorded since 2016: 188 ha in 2016.

How big is it?

10 km
It burned the equivalent of 1.1% of the area of London (17 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. Mianwali where it started
    1,715 ha reached on 25 Apr
    0.6 %

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

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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 Apr 35.0 °C 19 % 22 km/h 0.0 mm High 28
26 Apr 36.4 °C 22 % 35 km/h 0.0 mm High 34
27 Apr 36.9 °C 21 % 24 km/h 0.0 mm High 31
28 Apr 38.8 °C 21 % 18 km/h 0.0 mm High 32
29 Apr 33.7 °C 28 % 59 km/h 1.7 mm High 29
30 Apr 36.7 °C 14 % 31 km/h 0.0 mm High 36
1 May 37.2 °C 18 % 24 km/h 0.0 mm Very high 38
2 May 37.7 °C 20 % 37 km/h 0.0 mm Extreme 53
3 May 32.5 °C 31 % 34 km/h 0.0 mm Very high 38
4 May 36.3 °C 22 % 20 km/h 0.0 mm High 33
5 May after 38.9 °C 21 % 24 km/h 0.0 mm High 36
6 May after 40.5 °C 17 % 27 km/h 0.2 mm Very high 40
7 May after 41.1 °C 19 % 28 km/h 0.0 mm Very high 47
8 May after 42.0 °C 17 % 26 km/h 0.5 mm Very high 42
9 May after 42.2 °C 15 % 20 km/h 0.0 mm Very high 45
10 May after 41.0 °C 16 % 33 km/h 0.0 mm Extreme 54
11 May after 38.4 °C 19 % 31 km/h 0.0 mm Very high 45
12 May after 40.9 °C 21 % 27 km/h 0.1 mm Very high 46
13 May after 41.8 °C 21 % 31 km/h 0.4 mm Extreme 55
14 May after 42.5 °C 18 % 22 km/h 0.0 mm Very high 44
15 May after 40.9 °C 15 % 24 km/h 1.7 mm Very high 45

Before and after, from space

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

Before · 21 Apr 2017
After · 11 May 2017

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 · 59Every 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 Pakistan ›

Frequently asked questions

How long did the Mianwali fire last?
GWIS (Copernicus) dates it between 28 April 2017 and 4 May 2017: 7 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,711 hectares (17.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Mianwali (1,715 ha, 0.6 %).
What was the weather like?
During the fire the temperature reached 42.2 °C, humidity dropped to 14 % and gusts hit 59 km/h. The fire danger index (FWI) reached 54, class Extreme.
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.

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. This is not an emergency service: if there is a fire now, call 1122 · 16.

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. 59 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 2015, 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 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.