Burned area
satellite only7,545ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 1 Apr 2017 – 16 Apr 2017
+− cross-check
No official record is matched to this page to compare it with.
IN · India · –
Pipariya fire, April 2017 Pipariya, Bankhedi
Out · last detection 16 Apr 2017, 20:28 UTC
The fire started on 1 April 2017 in Pipariya, India, and satellites saw it burning for 16 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,545 hectares from heat detections, spread across 2 municipalities.
It is the 21th largest in Madhya Pradesh since 2016 (of 44 with a page). Number 7 in India in 2017, of 27.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-26matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only16days
1 Apr 2017 to 16 Apr 2017: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 16 Apr 2017, 20:28 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only1 Apr 2017
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 1 Apr 2017
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only390
VIIRS detections at 375 m. Most intense hotspot: 51 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 1 Apr 2017 – 16 Apr 2017
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only382MW
Total radiative power on 3 April 2017; hotspots that day: 85.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 3 Apr 2017
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model59.0FWI · extreme
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 48.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 1 Apr 2017, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model42.3°C · 12% RH
High of 42.3 °C and minimum humidity of 12% on 15 April 2017; gusts of 44 km/h on 5 April 2017.
- Source
- weather model at the fire’s grid cell
- Date
- 1 Apr 2017 – 16 Apr 2017
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
Living inside
model≈ 8,200people
Estimated residents inside the perimeter and 31 ha of built-up area (100 m grid, epoch 2015).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
logLast day with fire: 9 April 2017 → 16 April 2017.
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 26 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 7,545 ha
- Dates
- 1 Apr 2017 – 16 Apr 2017
- Name
- Pipariya
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/pipariya-madhya-pradesh-2017-04?v=2026-10-26A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire pipariya-madhya-pradesh-2017-04.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-04-01 | 3 | 19 | 40.6 | 24.6 | 13 | 13 | 32 | 0 | 59 | extremo | 1 |
| 2017-04-02 | 9 | 6 | 39.9 | 24.8 | 16 | 15.2 | 36.4 | 0 | 63.7 | extremo | 1 |
| 2017-04-03 | 85 | 382 | 40.2 | 23.9 | 15 | 18.8 | 43.6 | 0 | 65 | extremo | 1 |
| 2017-04-04 | 19 | 58 | 39.9 | 24.3 | 17 | 18.8 | 43.2 | 0 | 66.8 | extremo | 1 |
| 2017-04-05 | 32 | 156 | 39.4 | 23.9 | 18 | 19.6 | 43.9 | 0 | 63.6 | extremo | 1 |
| 2017-04-06 | 74 | 255 | 39.9 | 25.9 | 17 | 13.4 | 32 | 0 | 57.8 | extremo | 1 |
| 2017-04-07 | 61 | 216 | 38.3 | 23.3 | 18 | 19.7 | 40.3 | 0 | 60.7 | extremo | 1 |
| 2017-04-08 | 61 | 168 | 38.1 | 21.2 | 13 | 9.4 | 24.8 | 0 | 47.5 | muy_alto | 1 |
| 2017-04-09 | 18 | 204 | 37.5 | 21.6 | 15 | 13.2 | 32.8 | 0 | 53.1 | extremo | 1 |
| 2017-04-10 | 4 | 9 | 36.6 | 20.2 | 10 | 15.1 | 35.6 | 0 | 73.1 | muy_extremo | 1 |
| 2017-04-11 | 10 | 8 | 37.9 | 19.6 | 13 | 12.7 | 31.7 | 0 | 67 | extremo | 1 |
| 2017-04-12 | 3 | 12 | 40 | 20.2 | 12 | 11.9 | 30.6 | 0 | 65.5 | extremo | 1 |
| 2017-04-13 | 5 | 10 | 40.5 | 23.1 | 11 | 9.7 | 27 | 0 | 57.4 | extremo | 1 |
| 2017-04-14 | 0 | 0 | 41.4 | 25.1 | 10 | 10.4 | 28.8 | 0 | 66 | extremo | 1 |
| 2017-04-15 | 5 | 34 | 42.3 | 22.4 | 12 | 14.3 | 33.8 | 0 | 71.9 | muy_extremo | 1 |
| 2017-04-16 | 1 | 0 | 41.8 | 24.2 | 13 | 11 | 27.4 | 0 | 56.7 | extremo | 1 |
| 2017-04-17 | 0 | 0 | 41.7 | 24 | 15 | 11.2 | 30.6 | 0 | 62.4 | extremo | 0 |
| 2017-04-18 | 0 | 0 | 42.3 | 25.2 | 14 | 13.6 | 32.8 | 0 | 70 | muy_extremo | 0 |
| 2017-04-19 | 0 | 0 | 42 | 25.4 | 13 | 16.2 | 38.5 | 0 | 77.3 | muy_extremo | 0 |
| 2017-04-20 | 0 | 0 | 41.1 | 25.8 | 14 | 20.4 | 44.6 | 0 | 82.1 | muy_extremo | 0 |
| 2017-04-21 | 0 | 0 | 41.5 | 28.2 | 16 | 18.8 | 42.8 | 0 | 82.4 | muy_extremo | 0 |
| 2017-04-22 | 0 | 0 | 40.5 | 28.2 | 16 | 19.1 | 46.1 | 0 | 80 | muy_extremo | 0 |
| 2017-04-23 | 0 | 0 | 38.6 | 25.3 | 17 | 19.4 | 43.6 | 0 | 74.2 | muy_extremo | 0 |
| 2017-04-24 | 0 | 0 | 38.1 | 24.9 | 17 | 15.5 | 35.6 | 0 | 65.2 | extremo | 0 |
| 2017-04-25 | 0 | 0 | 37.7 | 24.4 | 21 | 14.5 | 33.1 | 0 | 59.5 | extremo | 0 |
| 2017-04-26 | 0 | 0 | 38.5 | 25.7 | 15 | 16.6 | 38.2 | 0 | 60.3 | extremo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 7,545ha
- GWIS perimeter (Copernicus)
- Duration
- 16days
- 1 Apr 2017 – 16 Apr 2017
- Municipalities hit
- 2
- subdistricts
- Started on
- 1 Apr
- 2017
- Heat detections
- 390
- in a single hotspot: 51 MW
- Danger at start
- 59
- Extreme · FWI index
- Average daily power
- 103MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
1 Apr16 Apr
16 Apr 2017
How it evolved, day by day
3 Apr
7 Apr
10 Apr
13 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
44km/h · peak gust
10%lowest humidity
It had gone 48 days without rain (1 mm or more) when it started.
This area had burned before
47% of the perimeter overlaps earlier fires recorded since 2016: 3,700 ha in 2016.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Pipariya where it started6,791 ha reached on 1 Apr6.1 %
-
795 ha reached on 1 Apr1.2 %
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 2015Built-up area31 ha
Residents≈ 8,200
Inside the perimeter there were about 31 hectares of built-up land and about 8,200 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)
Started with Very dry air: 8.7 % of the area in India
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 1 Apr | 40.6 °C | 13 % | 32 km/h | 0.0 mm | Extreme 59 |
| 2 Apr | 39.9 °C | 16 % | 36 km/h | 0.0 mm | Extreme 64 |
| 3 Apr | 40.2 °C | 15 % | 44 km/h | 0.0 mm | Extreme 65 |
| 4 Apr | 39.9 °C | 17 % | 43 km/h | 0.0 mm | Extreme 67 |
| 5 Apr | 39.4 °C | 18 % | 44 km/h | 0.0 mm | Extreme 64 |
| 6 Apr | 39.9 °C | 17 % | 32 km/h | 0.0 mm | Extreme 58 |
| 7 Apr | 38.3 °C | 18 % | 40 km/h | 0.0 mm | Extreme 61 |
| 8 Apr | 38.1 °C | 13 % | 25 km/h | 0.0 mm | Very high 48 |
| 9 Apr | 37.5 °C | 15 % | 33 km/h | 0.0 mm | Extreme 53 |
| 10 Apr | 36.6 °C | 10 % | 36 km/h | 0.0 mm | Very extreme 73 |
| 11 Apr | 37.9 °C | 13 % | 32 km/h | 0.0 mm | Extreme 67 |
| 12 Apr | 40.0 °C | 12 % | 31 km/h | 0.0 mm | Extreme 66 |
| 13 Apr | 40.5 °C | 11 % | 27 km/h | 0.0 mm | Extreme 57 |
| 14 Apr | 41.4 °C | 10 % | 29 km/h | 0.0 mm | Extreme 66 |
| 15 Apr | 42.3 °C | 12 % | 34 km/h | 0.0 mm | Very extreme 72 |
| 16 Apr | 41.8 °C | 13 % | 27 km/h | 0.0 mm | Extreme 57 |
| 17 Apr after | 41.7 °C | 15 % | 31 km/h | 0.0 mm | Extreme 62 |
| 18 Apr after | 42.3 °C | 14 % | 33 km/h | 0.0 mm | Very extreme 70 |
| 19 Apr after | 42.0 °C | 13 % | 38 km/h | 0.0 mm | Very extreme 77 |
| 20 Apr after | 41.1 °C | 14 % | 45 km/h | 0.0 mm | Very extreme 82 |
| 21 Apr after | 41.5 °C | 16 % | 43 km/h | 0.0 mm | Very extreme 82 |
| 22 Apr after | 40.5 °C | 16 % | 46 km/h | 0.0 mm | Very extreme 80 |
| 23 Apr after | 38.6 °C | 17 % | 44 km/h | 0.0 mm | Very extreme 74 |
| 24 Apr after | 38.1 °C | 17 % | 36 km/h | 0.0 mm | Extreme 65 |
| 25 Apr after | 37.7 °C | 21 % | 33 km/h | 0.0 mm | Extreme 60 |
| 26 Apr after | 38.5 °C | 15 % | 38 km/h | 0.0 mm | Extreme 60 |
Its twins: fires that started in the same weather
It started with an FWI of 59.0, a minimum humidity of 13% and 48 days without rain. Fires in the area that started in weather like this since 2016: 16.
FWI at the start
59.0
Minimum humidity
13 %
Days without rain
48
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Pipariya fire, April 2017
7,545 ha
16 days
FWI 59.0
Min. humidity 13 %
Dhimarkheda fire, March 2018
6,407 ha
9 days
FWI 57.5
Min. humidity 13 %
230 km away, in 2018
First rain (1 mm or more) after it ended: none in the following ten days.
Seoni-Malwa fire, March 2019
7,576 ha
10 days
FWI 64.3
Min. humidity 15 %
104 km away, in 2019
First rain (1 mm or more) after it ended: 1.7 mm on 15 Apr.
Dolariya fire, March 2022
19,673 ha
11 days
FWI 56.1
Min. humidity 18 %
88 km away, in 2022
First rain (1 mm or more) after it ended: none in the following ten days.
Pipariya fire, March 2022
32,531 ha
15 days
FWI 53.0
Min. humidity 17 %
9 km away, in 2022
First rain (1 mm or more) after it ended: none in the following ten days.
Pipariya fire, April 2021
13,129 ha
7 days
FWI 54.9
Min. humidity 12 %
9 km away, in 2021
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
- 9 days
- median duration
- 7,013 ha
- median area
- 25 %
- went past 10,000 ha
- 1.6 mm
- rain at the end (median; 6 of 16 had it)
It burned an area similar to its twins (7,545 ha against a median of 7,013 ha) and lasted 16 days, against 9 days.
In 10 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 1.6 mm.
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
44km/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. Twins with rain when they ended: 6 of 16, with a median of 1.6 mm.
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.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 25 Mar 2017
After · 23 Apr 2017
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 390Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Pipariya fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 1 April 2017 to 16 April 2017 (16 days). The perimeter dates it from 1 April 2017 to 9 April 2017.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 7,545 hectares (75.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Pipariya (6,791 ha, 6.1 %); Bankhedi (795 ha, 1.2 %).
- What was the weather like?
- During the fire the temperature reached 42.3 °C, humidity dropped to 10 % and gusts hit 44 km/h. The fire danger index (FWI) reached 73, class Very 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.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 16. Their median duration was 9 days and their median area 7,013 ha; 25 % went past 10,000 ha. In 10 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 1.6 mm.
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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Last day with fire: 9 April 2017 → 16 April 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
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 1 April 2017 to 9 April 2017. 390 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.
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.