Skip to content
worldfires
IN · India · –

Bagha Purana fire, October 2016 Bagha Purana, Jaitu, Dharamkot

Out · last detection 21 Nov 2016, 07:00 UTC

The fire started on 19 October 2016 in Bagha Purana, India, and satellites saw it burning for 34 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 48,651 hectares from heat detections, spread across 9 municipalities.

It is the 2th largest in Punjab since 2016 (of 33 with a page). Number 2 in India in 2016, of 47.

Burnt area
48,651ha
GWIS perimeter (Copernicus)
Duration
34days
19 Oct 2016 – 21 Nov 2016
Municipalities hit
9
subdistricts
Started on
19 Oct
2016
Heat detections
5,591
in a single hotspot: 102 MW
Danger at start
42
Very high · FWI index
Average daily power
1.3GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 19 Oct21 Nov
21 Nov 2016

How it evolved, day by day

19 Oct 2016 · 65 MW · 9 20 Oct 2016 · 39 MW · 4 21 Oct 2016 · 80 MW · 10 22 Oct 2016 · 67 MW · 17 23 Oct 2016 · 136 MW · 17 24 Oct 2016 · 231 MW · 33 25 Oct 2016 · 465 MW · 67 26 Oct 2016 · 694 MW · 73 27 Oct 2016 · 1,037 MW · 100 28 Oct 2016 · 1,263 MW · 127 29 Oct 2016 · 1,099 MW · 115 30 Oct 2016 · 351 MW · 52 31 Oct 2016 · 4,041 MW · 442 1 Nov 2016 · 3,865 MW · 478 2 Nov 2016 · 1,074 MW · 200 3 Nov 2016 · 2,252 MW · 335 4 Nov 2016 · 2,525 MW · 359 5 Nov 2016 · 3,110 MW · 354 6 Nov 2016 · 5,826 MW · 721 7 Nov 2016 · 5,926 MW · 795 8 Nov 2016 · 3,686 MW · 352 9 Nov 2016 · 3,014 MW · 342 10 Nov 2016 · 1,111 MW · 195 11 Nov 2016 · 1,795 MW · 203 12 Nov 2016 · 527 MW · 65 13 Nov 2016 · 215 MW · 26 14 Nov 2016 · 261 MW · 31 15 Nov 2016 · 150 MW · 21 16 Nov 2016 · 127 MW · 21 17 Nov 2016 · 111 MW · 15 18 Nov 2016 · 33 MW · 3 19 Nov 2016 · 8 MW · 3 20 Nov 2016 · 21 MW · 5 21 Nov 2016 · 3 MW · 1
19 Oct 26 Oct 2 Nov 7 Nov 16 Nov

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

The weather it burned in

35°high
31km/h · peak gust
21%lowest humidity

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

How big is it?

10 km
It burned the equivalent of 31% of the area of London (487 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. Bagha Purana where it started
    22,932 ha reached on 19 Oct
    38 %
  2. 5,738 ha reached on 19 Oct
    14 %
  3. 4,790 ha reached on 25 Oct
    8.6 %
  4. 4,620 ha reached on 24 Oct
    6.2 %
  5. 4,265 ha reached on 20 Oct
    6.6 %
  6. 3,825 ha reached on 21 Oct
    11 %
  7. 2,497 ha reached on 19 Oct
    3.6 %
  8. 180 ha reached on 24 Oct
    0.2 %
  9. 34 ha reached on 25 Oct
    0.0 %

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 area297 ha
Residents≈ 42,000

Inside the perimeter there were about 297 hectares of built-up land and about 42,000 residents (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)
19 Oct 35.4 °C 21 % 28 km/h 0.0 mm Very high 42
20 Oct 34.0 °C 30 % 21 km/h 0.0 mm High 34
21 Oct 34.2 °C 33 % 21 km/h 0.0 mm High 32
22 Oct 33.7 °C 32 % 20 km/h 0.0 mm High 32
23 Oct 33.6 °C 30 % 26 km/h 0.0 mm High 36
24 Oct 33.7 °C 26 % 24 km/h 0.0 mm High 35
25 Oct 33.2 °C 30 % 19 km/h 0.0 mm High 30
26 Oct 32.9 °C 28 % 19 km/h 0.0 mm High 32
27 Oct 33.1 °C 25 % 28 km/h 0.0 mm Very high 39
28 Oct 32.8 °C 24 % 24 km/h 0.0 mm High 38
29 Oct 32.5 °C 25 % 23 km/h 0.0 mm High 35
30 Oct 31.6 °C 29 % 16 km/h 0.0 mm High 29
31 Oct 30.8 °C 30 % 17 km/h 0.0 mm High 26
1 Nov 30.3 °C 35 % 19 km/h 0.0 mm High 27
2 Nov 30.3 °C 40 % 16 km/h 0.0 mm High 23
3 Nov 30.1 °C 38 % 20 km/h 0.0 mm High 23
4 Nov 30.2 °C 38 % 31 km/h 0.0 mm High 26
5 Nov 29.6 °C 35 % 20 km/h 0.0 mm High 25
6 Nov 29.6 °C 35 % 17 km/h 0.0 mm High 23
7 Nov 29.6 °C 32 % 31 km/h 0.0 mm High 32
8 Nov 30.8 °C 26 % 31 km/h 0.0 mm High 36
9 Nov 31.4 °C 25 % 21 km/h 0.0 mm High 31
10 Nov 30.0 °C 30 % 16 km/h 0.0 mm High 28
11 Nov 30.6 °C 24 % 26 km/h 0.0 mm High 36
12 Nov 27.4 °C 35 % 31 km/h 0.2 mm High 30
13 Nov 28.1 °C 34 % 21 km/h 0.0 mm High 31
14 Nov 27.9 °C 29 % 18 km/h 0.0 mm High 28
15 Nov 27.6 °C 33 % 24 km/h 0.0 mm High 33
16 Nov 27.6 °C 29 % 25 km/h 0.0 mm High 34
17 Nov 27.7 °C 29 % 29 km/h 0.0 mm High 38
18 Nov 28.4 °C 28 % 27 km/h 0.0 mm High 36
19 Nov 28.3 °C 28 % 19 km/h 0.0 mm High 30
20 Nov 28.9 °C 28 % 22 km/h 0.0 mm High 31
21 Nov 30.0 °C 25 % 23 km/h 0.0 mm High 33
22 Nov after 29.6 °C 28 % 19 km/h 0.0 mm High 30
23 Nov after 27.8 °C 31 % 23 km/h 0.0 mm High 31
24 Nov after 27.6 °C 26 % 28 km/h 0.0 mm High 34
25 Nov after 29.1 °C 20 % 33 km/h 0.0 mm Very high 43
26 Nov after 28.8 °C 25 % 31 km/h 0.0 mm Very high 44
27 Nov after 29.4 °C 20 % 32 km/h 0.0 mm Very high 45
28 Nov after 29.1 °C 16 % 29 km/h 0.0 mm Very high 45
29 Nov after 28.8 °C 26 % 14 km/h 0.0 mm High 31
30 Nov after 27.4 °C 36 % 21 km/h 0.0 mm High 32
1 Dec after 25.9 °C 46 % 17 km/h 0.0 mm High 22

Its twins: fires that started in the same weather

It started with an FWI of 42.2, a minimum humidity of 21% and 47 days without rain. Fires in the area that started in weather like this since 2017: 5.

FWI at the start 42.2
Minimum humidity 21 %
Days without rain 47
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Mansa fire, October 2020
10,862 ha 19 days FWI 40.8 Min. humidity 21 % 68 km away, in 2020

First rain (1 mm or more) after it ended: 18.8 mm on 15 Nov.

What happened to them

Fires in the area that started in similar weather: 5. With fewer than 15 we give no figures: they would be more noise than signal.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

—first rain
—no rain in ten days
31km/h · max. gust

It was considered over on 21 Nov, and not even 1 mm fell in the following ten days: it went out without rain.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2017.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 12 Oct 2016
After · 28 Nov 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 · 5,591Every 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 India

Frequently asked questions

How long did the Bagha Purana fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 19 October 2016 to 21 November 2016 (34 days). The perimeter dates it from 26 October 2016 to 14 November 2016.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 48,651 hectares (486.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 9 municipalities: Bagha Purana (22,932 ha, 38 %); Jaitu (5,738 ha, 14 %); Dharamkot (4,790 ha, 8.6 %); Zira (4,620 ha, 6.2 %); Moga (4,265 ha, 6.6 %); Kotakpura (3,825 ha, 11 %); Rampura Phul (2,497 ha, 3.6 %); Faridkot (180 ha, 0.2 %); Firozpur (34 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 35.4 °C, humidity dropped to 21 % and gusts hit 31 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 India (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: 112 · Emergency number and official warnings

Satellite cross-check

History of this page · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Last day with fire: 14 November 2016 → 21 November 2016.
  2. Start date: 26 October 2016 → 19 October 2016.

RSS Changes to this page With cross-checks and a citable version

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 112.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 5 polygons grouped in this page.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 26 October 2016 to 14 November 2016. 5,591 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.