Haflong fire, 1 April 2026 Haflong
The fire started on 1 April 2026 in Haflong, India, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 11,086 hectares from heat detections, spread across a single municipality.
It is the 4th largest in Assam since 2016 (of 12 with a page). Number 16 in India in 2026, of 65.
- Burnt area
- 11,086ha
- GWIS perimeter (Copernicus)
- Duration
- 6days
- 1 Apr 2026 – 6 Apr 2026
- Municipalities hit
- 1
- subdistricts
- Started on
- 1 Apr
- 2026
- Heat detections
- 145
- in a single hotspot: 89 MW
- Danger at start
- 4
- Very low · FWI index
- Energy released
- 1.8GW
- 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 one day without rain (1 mm or more) when it started. Rain came after the fire: 4.1 mm on 14 Apr.
This area had burned before
93% of the perimeter overlaps earlier fires recorded since 2016: 1,248 ha in 2016, 3,091 ha in 2017, 2,162 ha in 2018, 3,195 ha in 2019, 3,585 ha in 2020, 6,227 ha in 2021, 6,023 ha in 2022, 5,108 ha in 2023, 1,685 ha in 2024, 2,614 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 10,303 ha that had burned before.
What happened to each town
-
Haflong where it started11,127 ha reached on 1 Apr2.3 %
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) |
|---|---|---|---|---|---|
| 25 Mar | 25.6 °C | 53 % | 47 km/h | 0.4 mm | Very low 4 |
| 26 Mar | 27.4 °C | 40 % | 28 km/h | 0.3 mm | Very low 5 |
| 27 Mar | 27.3 °C | 42 % | 28 km/h | 0.0 mm | Low 7 |
| 28 Mar | 19.9 °C | 81 % | 22 km/h | 4.3 mm | Very low 0 |
| 29 Mar | 22.2 °C | 69 % | 38 km/h | 1.7 mm | Very low 0 |
| 30 Mar | 22.7 °C | 76 % | 37 km/h | 8.9 mm | Very low 0 |
| 31 Mar | 23.3 °C | 86 % | 34 km/h | 18.5 mm | Very low 0 |
| 1 Apr | 26.8 °C | 63 % | 44 km/h | 1.3 mm | Very low 0 |
| 2 Apr | 27.5 °C | 67 % | 59 km/h | 2.6 mm | Very low 0 |
| 3 Apr | 27.1 °C | 66 % | 42 km/h | 3.6 mm | Very low 0 |
| 4 Apr | 27.7 °C | 62 % | 53 km/h | 1.7 mm | Very low 0 |
| 5 Apr | 25.3 °C | 65 % | 52 km/h | 3.3 mm | Very low 0 |
| 6 Apr | 27.8 °C | 51 % | 44 km/h | 0.4 mm | Very low 2 |
| 7 Apr after | 25.8 °C | 61 % | 33 km/h | 8.4 mm | Very low 0 |
| 8 Apr after | 26.0 °C | 51 % | 30 km/h | 7.0 mm | Very low 0 |
| 9 Apr after | 21.9 °C | 71 % | 37 km/h | 2.7 mm | Very low 0 |
| 10 Apr after | 22.2 °C | 70 % | 34 km/h | 5.7 mm | Very low 0 |
| 11 Apr after | 25.4 °C | 48 % | 28 km/h | 0.2 mm | Very low 0 |
| 12 Apr after | 25.4 °C | 55 % | 40 km/h | 2.5 mm | Very low 1 |
| 13 Apr after | 26.4 °C | 53 % | 53 km/h | 2.4 mm | Very low 1 |
| 14 Apr after | 27.3 °C | 60 % | 42 km/h | 4.1 mm | Very low 0 |
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 30 March 2026 the air beside the fire reached 73 µg/m³ of PM2.5. That day averaged 53: 3.5 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 · 145Every 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 Haflong fire last?
- GWIS (Copernicus) dates it between 1 April 2026 and 6 April 2026: 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 11,086 hectares (110.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Haflong (11,127 ha, 2.3 %).
- What was the weather like?
- During the fire the temperature reached 27.8 °C, humidity dropped to 40 % and gusts hit 59 km/h. The fire danger index (FWI) reached 7, class Low.
- 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.