Skip to content
worldfires
IN · India · →

Jirang fire, April 2016 Jirang, Mairang, Palasbari

Out · last detection 15 Apr 2016, 07:23 UTC

The fire started on 8 April 2016 in Jirang, India, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,883 hectares from heat detections, spread across 3 municipalities.

It is the 6th largest in Meghālaya since 2016 (of 13 with a page). Number 26 in India in 2016, of 47.

Burnt area
6,883ha
GWIS perimeter (Copernicus)
Duration
7days
8 Apr 2016 – 14 Apr 2016
Municipalities hit
3
subdistricts
Started on
8 Apr
2016
Heat detections
215
in a single hotspot: 102 MW
Danger at start
7
Low · FWI index
Energy released
2.8GW
sum of detected power

Where it burned

15 Apr 2016
HOTSPOTS BY DAY 8 Apr14 Apr

How it evolved, day by day

89101112131415

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

The weather it burned in

33°high
60km/h · peak gust
37%lowest humidity

It had gone 0 days without rain (1 mm or more) when it started. Rain came after the fire: 21.2 mm on 16 Apr.

This area had burned before

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

What happened to each town

  1. Jirang where it started
    6,087 ha reached on 8 Apr
    9.5 %
  2. 820 ha reached on 8 Apr
    1.1 %
  3. 0 ha
    0.0 %

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)
8 Apr 31.4 °C 45 % 59 km/h 0.0 mm Low 7
9 Apr 32.3 °C 44 % 50 km/h 0.0 mm Low 9
10 Apr 32.6 °C 50 % 41 km/h 0.0 mm Low 8
11 Apr 32.5 °C 51 % 49 km/h 0.6 mm Low 9
12 Apr 33.0 °C 38 % 60 km/h 0.0 mm Moderate 15
13 Apr 32.8 °C 39 % 48 km/h 0.0 mm Moderate 14
14 Apr 32.4 °C 37 % 40 km/h 0.4 mm Moderate 13
15 Apr after 28.5 °C 73 % 45 km/h 5.2 mm Very low 0
16 Apr after 25.5 °C 79 % 47 km/h 21.2 mm Very low 0

Before and after, from space

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

Before · 1 Apr 2016
After · 21 Apr 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 · 215Every 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 Jirang fire last?
GWIS (Copernicus) dates it between 8 April 2016 and 14 April 2016: 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 6,883 hectares (68.8 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 3 municipalities: Jirang (6,087 ha, 9.5 %); Mairang (820 ha, 1.1 %); Palasbari (0 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 33.0 °C, humidity dropped to 37 % and gusts hit 60 km/h. The fire danger index (FWI) reached 15, class Moderate.
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

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

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.