Skip to content
worldfires
PK · Pakistan · →

KAMOKE fire, May 2017 KAMOKE

Out · last detection 7 May 2017, 20:31 UTC

The fire started on 5 May 2017 in KAMOKE, Pakistan, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,168 hectares from heat detections, spread across a single municipality.

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

Burnt area
1,168ha
GWIS perimeter (Copernicus)
Duration
3days
5 May 2017 – 7 May 2017
Municipalities hit
1
subdistricts
Started on
5 May
2017
Heat detections
49
in a single hotspot: 79 MW
Danger at start
48
Very high · FWI index
Energy released
838MW
sum of detected power

Where it burned

7 May 2017
HOTSPOTS BY DAY 5 May7 May

How it evolved, day by day

567

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

The weather it burned in

43°high
32km/h · peak gust
9%lowest humidity

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

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. KAMOKE where it started
    1,173 ha reached on 4 May
    1.7 %

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)
5 May 39.4 °C 15 % 32 km/h 0.0 mm Very high 48
6 May 41.4 °C 9 % 29 km/h 0.1 mm Extreme 52
7 May 43.0 °C 11 % 31 km/h 0.0 mm Extreme 56
8 May after 43.5 °C 12 % 28 km/h 0.9 mm Extreme 53
9 May after 41.8 °C 12 % 31 km/h 0.2 mm Extreme 51
10 May after 40.1 °C 21 % 35 km/h 0.2 mm Extreme 52
11 May after 38.7 °C 19 % 32 km/h 0.0 mm Extreme 52
12 May after 41.1 °C 19 % 29 km/h 0.2 mm Very high 48
13 May after 41.7 °C 19 % 41 km/h 0.6 mm Very high 47
14 May after 42.6 °C 18 % 33 km/h 0.5 mm Very high 49
15 May after 42.7 °C 17 % 35 km/h 3.9 mm High 35

Before and after, from space

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

Before · 28 Apr 2017
After · 14 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 · 49Every 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 KAMOKE fire last?
GWIS (Copernicus) dates it between 5 May 2017 and 7 May 2017: 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 1,168 hectares (11.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered KAMOKE (1,173 ha, 1.7 %).
What was the weather like?
During the fire the temperature reached 43.0 °C, humidity dropped to 9 % and gusts hit 32 km/h. The fire danger index (FWI) reached 56, 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

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

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.