Oudgi fire, March 2017 Oudgi
The fire started on 28 March 2017 in Oudgi, India, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,223 hectares from heat detections, spread across a single municipality.
It is the 26th largest in Chhattīsgarh since 2016 (of 37 with a page). Number 17 in India in 2017, of 27.
The power measured by the satellite is low (24.9 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
- Burnt area
- 6,223ha
- GWIS perimeter (Copernicus)
- Duration
- 6days
- 28 Mar 2017 – 2 Apr 2017
- Municipalities hit
- 1
- subdistricts
- Started on
- 28 Mar
- 2017
- Heat detections
- 225
- in a single hotspot: 25 MW
- Danger at start
- 32
- High · FWI index
- Energy released
- 829MW
- sum of detected power
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 9 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: 2,406 ha in 2016.
What happened to each town
-
Oudgi where it started6,251 ha reached on 27 Mar3.6 %
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) |
|---|---|---|---|---|---|
| 21 Mar | 31.3 °C | 17 % | 36 km/h | 0.0 mm | High 32 |
| 22 Mar | 33.5 °C | 20 % | 37 km/h | 0.0 mm | High 34 |
| 23 Mar | 34.7 °C | 19 % | 42 km/h | 0.0 mm | High 38 |
| 24 Mar | 36.2 °C | 21 % | 32 km/h | 0.0 mm | High 34 |
| 25 Mar | 36.7 °C | 19 % | 35 km/h | 0.0 mm | High 36 |
| 26 Mar | 35.6 °C | 18 % | 41 km/h | 0.0 mm | Very high 40 |
| 27 Mar | 36.0 °C | 17 % | 36 km/h | 0.0 mm | Very high 39 |
| 28 Mar | 37.3 °C | 18 % | 47 km/h | 0.0 mm | Very high 46 |
| 29 Mar | 38.0 °C | 15 % | 49 km/h | 0.0 mm | Extreme 50 |
| 30 Mar | 39.1 °C | 12 % | 44 km/h | 0.0 mm | Extreme 51 |
| 31 Mar | 38.9 °C | 14 % | 32 km/h | 0.0 mm | Very high 46 |
| 1 Apr | 39.1 °C | 13 % | 45 km/h | 0.0 mm | Extreme 54 |
| 2 Apr | 38.8 °C | 14 % | 40 km/h | 0.0 mm | Extreme 52 |
| 3 Apr after | 38.4 °C | 15 % | 31 km/h | 0.0 mm | Very high 47 |
| 4 Apr after | 39.1 °C | 16 % | 24 km/h | 0.0 mm | Very high 46 |
| 5 Apr after | 38.9 °C | 17 % | 35 km/h | 0.0 mm | Extreme 52 |
| 6 Apr after | 39.2 °C | 19 % | 32 km/h | 0.0 mm | Extreme 50 |
| 7 Apr after | 40.6 °C | 11 % | 34 km/h | 0.0 mm | Extreme 56 |
| 8 Apr after | 39.8 °C | 12 % | 33 km/h | 0.0 mm | Extreme 55 |
| 9 Apr after | 35.9 °C | 13 % | 32 km/h | 0.0 mm | Extreme 53 |
| 10 Apr after | 34.7 °C | 9 % | 41 km/h | 0.0 mm | Extreme 59 |
| 11 Apr after | 36.0 °C | 10 % | 42 km/h | 0.0 mm | Extreme 60 |
| 12 Apr after | 37.4 °C | 10 % | 39 km/h | 0.0 mm | Extreme 58 |
| 13 Apr after | 38.5 °C | 9 % | 38 km/h | 0.0 mm | Extreme 58 |
| 14 Apr after | 39.3 °C | 9 % | 29 km/h | 0.0 mm | Extreme 54 |
| 15 Apr after | 39.5 °C | 13 % | 43 km/h | 0.0 mm | Extreme 62 |
| 16 Apr after | 37.3 °C | 15 % | 44 km/h | 0.0 mm | Extreme 62 |
| 17 Apr after | 38.3 °C | 20 % | 25 km/h | 0.0 mm | Very high 47 |
| 18 Apr after | 39.6 °C | 18 % | 47 km/h | 0.0 mm | Extreme 59 |
| 19 Apr after | 40.4 °C | 8 % | 39 km/h | 0.2 mm | Extreme 63 |
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.
Detections table · 225Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Frequently asked questions
- How long did the Oudgi fire last?
- GWIS (Copernicus) dates it between 28 March 2017 and 2 April 2017: 6 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,223 hectares (62.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Oudgi (6,251 ha, 3.6 %).
- What was the weather like?
- During the fire the temperature reached 40.6 °C, humidity dropped to 11 % and gusts hit 49 km/h. The fire danger index (FWI) reached 56, 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
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
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.