Skip to content
worldfires
IN · India · –

Orchha fire, 5 April 2017 Orchha, Pakhanjur

Out · last detection 17 Apr 2017, 20:09 UTC

The fire started on 5 April 2017 in Orchha, India, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 13,976 hectares from heat detections, spread across 2 municipalities.

It is the 4th largest in Chhattīsgarh since 2016 (of 26 with a page). Number 3 in India in 2017, of 27.

Burnt area
13,976ha
GWIS perimeter (Copernicus)
Duration
12days
5 Apr 2017 – 16 Apr 2017
Municipalities hit
2
subdistricts
Started on
5 Apr
2017
Heat detections
613
in a single hotspot: 0 MW
Danger at start
45
Very high · FWI index
Average daily power
212MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 5 Apr16 Apr
17 Apr 2017

How it evolved, day by day

5 Apr 2017 · 31 MW · 7 6 Apr 2017 · 153 MW · 44 7 Apr 2017 · 66 MW · 23 8 Apr 2017 · 78 MW · 25 9 Apr 2017 · 286 MW · 41 10 Apr 2017 · 194 MW · 58 11 Apr 2017 · 742 MW · 144 12 Apr 2017 · 536 MW · 123 13 Apr 2017 · 244 MW · 56 14 Apr 2017 · 101 MW · 13 15 Apr 2017 · 94 MW · 13 16 Apr 2017 · 106 MW · 30 17 Apr 2017 · 122 MW · 36
5 Apr 8 Apr 11 Apr 14 Apr 17 Apr

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
46km/h · peak gust
4%lowest humidity

It had gone 2 days without rain (1 mm or more) when it started.

This area had burned before

39% of the perimeter overlaps earlier fires recorded since 2016: 5,554 ha in 2016.

How big is it?

10 km
It burned the equivalent of 8.8% of the area of London (140 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. Orchha where it started
    11,932 ha
    3.4 %
  2. 2,136 ha
    1.1 %

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≈ 30

Inside the perimeter there were about 0.07 hectares of built-up land and about 30 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)
5 Apr 39.0 °C 29 % 46 km/h 0.7 mm Very high 45
6 Apr 39.9 °C 23 % 36 km/h 0.0 mm Very high 40
7 Apr 39.6 °C 24 % 40 km/h 0.0 mm Very high 44
8 Apr 40.9 °C 18 % 27 km/h 0.0 mm Very high 42
9 Apr 41.3 °C 11 % 28 km/h 0.0 mm Extreme 51
10 Apr 40.1 °C 9 % 34 km/h 0.0 mm Extreme 59
11 Apr 39.7 °C 8 % 39 km/h 0.0 mm Extreme 65
12 Apr 40.8 °C 4 % 36 km/h 0.0 mm Extreme 69
13 Apr 41.1 °C 5 % 30 km/h 0.0 mm Extreme 63
14 Apr 41.3 °C 10 % 32 km/h 0.0 mm Extreme 64
15 Apr 41.2 °C 12 % 39 km/h 0.0 mm Extreme 58
16 Apr 42.4 °C 11 % 36 km/h 0.0 mm Extreme 58
17 Apr after 42.5 °C 12 % 41 km/h 0.0 mm Extreme 66
18 Apr after 42.0 °C 13 % 37 km/h 0.0 mm Extreme 52
19 Apr after 41.0 °C 18 % 40 km/h 0.0 mm Extreme 54
20 Apr after 41.2 °C 17 % 38 km/h 0.0 mm Extreme 51
21 Apr after 40.2 °C 18 % 40 km/h 0.0 mm Extreme 53
22 Apr after 42.1 °C 12 % 32 km/h 0.0 mm Extreme 56
23 Apr after 41.4 °C 13 % 36 km/h 0.0 mm Extreme 58
24 Apr after 41.0 °C 13 % 42 km/h 0.0 mm Extreme 66
25 Apr after 40.4 °C 15 % 45 km/h 0.0 mm Extreme 66
26 Apr after 41.4 °C 13 % 36 km/h 0.0 mm Extreme 63

Its twins: fires that started in the same weather

It started with an FWI of 45.1, a minimum humidity of 29% and 2 days without rain. Fires in the area that started in weather like this since 2016: 7.

FWI at the start 45.1
Minimum humidity 29 %
Days without rain 2
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Mulchera fire, March 2018
6,528 ha 8 days FWI 44.5 Min. humidity 28 % 92 km away, in 2018

First rain (1 mm or more) after it ended: 2.3 mm on 1 Apr.

What happened to them

Fires in the area that started in similar weather: 7. 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
46km/h · max. gust

It was considered over on 16 Apr, 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 2016.
  • 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 · 29 Mar 2017
After · 23 Apr 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 · 0Every 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 Orchha fire last?
GWIS (Copernicus) dates it between 5 April 2017 and 16 April 2017: 12 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 13,976 hectares (139.8 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Orchha (11,932 ha, 3.4 %); Pakhanjur (2,136 ha, 1.1 %).
What was the weather like?
During the fire the temperature reached 42.4 °C, humidity dropped to 4 % and gusts hit 46 km/h. The fire danger index (FWI) reached 69, class Extreme.
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 · 4 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Last day with fire: 23 April 2017 → 16 April 2017.
  2. Start date: 30 March 2017 → 5 April 2017.
  3. Last day with fire: 16 April 2017 → 23 April 2017.
  4. Start date: 5 April 2017 → 30 March 2017.

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.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. No 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.