Badi fire, March 2026 Badi, Budni, Baraily
The fire started on 27 March 2026 in Badi, India, and satellites saw it burning for 17 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 20,769 hectares from heat detections, spread across 5 municipalities.
It is the 11th largest in Madhya Pradesh since 2016 (of 60 with a page). Number 7 in India in 2026, of 58.
Compare with…
Suggestions: Badi · 2020Baraily · 2020Babai · 2021Babai · 2020
- Burnt area
- 20,769ha
- GWIS perimeter (Copernicus)
- Duration
- 17days
- 27 Mar 2026 – 12 Apr 2026
- Municipalities hit
- 5
- subdistricts
- Started on
- 27 Mar
- 2026
- Heat detections
- 564
- in a single hotspot: 62 MW
- Danger at start
- 47
- Very high · FWI index
- Average daily power
- 246MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 6 days without rain (1 mm or more) when it started. Rain came after the fire: 1.2 mm on 20 Apr.
This area had burned before
96% of the perimeter overlaps earlier fires recorded since 2016: 8,588 ha in 2016, 8,132 ha in 2017, 6,560 ha in 2018, 6,767 ha in 2019, 11,356 ha in 2020, 8,461 ha in 2021, 7,361 ha in 2022, 3,216 ha in 2023, 2,303 ha in 2024, 5,921 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 19,935 ha that had burned before.
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
-
Badi where it started14,024 ha reached on 27 Mar28 %
-
6,313 ha reached on 3 Apr11 %
-
465 ha reached on 3 Apr0.8 %
-
54 ha reached on 2 Apr0.1 %
-
1 ha reached on 6 Apr0.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.
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) |
|---|---|---|---|---|---|
| 27 Mar | 38.2 °C | 20 % | 37 km/h | 0.0 mm | Very high 47 |
| 28 Mar | 36.8 °C | 25 % | 23 km/h | 0.0 mm | Very high 38 |
| 29 Mar | 37.0 °C | 32 % | 30 km/h | 1.5 mm | High 27 |
| 30 Mar | 37.5 °C | 28 % | 42 km/h | 0.0 mm | Very high 43 |
| 31 Mar | 36.8 °C | 31 % | 30 km/h | 0.0 mm | High 34 |
| 1 Apr | 37.4 °C | 28 % | 28 km/h | 0.0 mm | High 35 |
| 2 Apr | 36.6 °C | 33 % | 30 km/h | 1.3 mm | High 29 |
| 3 Apr | 36.4 °C | 31 % | 32 km/h | 0.3 mm | Very high 38 |
| 4 Apr | 34.8 °C | 32 % | 32 km/h | 2.1 mm | Moderate 20 |
| 5 Apr | 34.4 °C | 23 % | 32 km/h | 0.0 mm | High 35 |
| 6 Apr | 36.3 °C | 23 % | 17 km/h | 0.0 mm | High 31 |
| 7 Apr | 34.9 °C | 26 % | 36 km/h | 0.0 mm | Very high 40 |
| 8 Apr | 32.9 °C | 38 % | 45 km/h | 1.2 mm | High 27 |
| 9 Apr | 34.0 °C | 30 % | 28 km/h | 0.0 mm | High 29 |
| 10 Apr | 35.2 °C | 22 % | 28 km/h | 0.0 mm | High 36 |
| 11 Apr | 37.1 °C | 19 % | 20 km/h | 0.0 mm | High 38 |
| 12 Apr | 39.6 °C | 21 % | 26 km/h | 0.0 mm | Very high 40 |
| 13 Apr after | 38.3 °C | 21 % | 28 km/h | 0.0 mm | Very high 41 |
| 14 Apr after | 40.0 °C | 20 % | 20 km/h | 0.0 mm | Very high 40 |
| 15 Apr after | 40.1 °C | 18 % | 33 km/h | 0.0 mm | Very high 48 |
| 16 Apr after | 40.5 °C | 21 % | 17 km/h | 0.0 mm | Very high 40 |
| 17 Apr after | 41.3 °C | 22 % | 24 km/h | 0.0 mm | Very high 43 |
| 18 Apr after | 40.6 °C | 22 % | 21 km/h | 0.0 mm | Very high 46 |
| 19 Apr after | 41.9 °C | 19 % | 17 km/h | 0.0 mm | Very high 43 |
| 20 Apr after | 39.9 °C | 20 % | 37 km/h | 1.2 mm | Very high 47 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 4 April 2026 the air beside the fire reached 47 µg/m³ of PM2.5. That day averaged 32: 2.1 times the WHO daily guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 564Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Badi fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 27 March 2026 to 12 April 2026 (17 days). The perimeter dates it from 1 April 2026 to 9 April 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 20,769 hectares (207.7 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 5 municipalities: Badi (14,024 ha, 28 %); Budni (6,313 ha, 11 %); Baraily (465 ha, 0.8 %); Babai (54 ha, 0.1 %); Sohagpur (1 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 39.6 °C, humidity dropped to 19 % and gusts hit 45 km/h. The fire danger index (FWI) reached 47, 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.
- Last day with fire: 9 April 2026 → 12 April 2026.
- Start date: 1 April 2026 → 27 March 2026.
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 2026 to 9 April 2026. 564 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.
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.