Ambassa fire, April 2026 Longtharai Valley, Ambassa, Gandacherra
The fire started on 10 April 2026 in Ambassa, India, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 15,588 hectares from heat detections, spread across 3 municipalities.
It is the 3th largest in Tripura since 2016 (of 13 with a page). Number 10 in India in 2026, of 58.
Compare with…
- Burnt area
- 15,588ha
- GWIS perimeter (Copernicus)
- Duration
- 12days
- 10 Apr 2026 – 21 Apr 2026
- Municipalities hit
- 3
- subdistricts
- Started on
- 10 Apr
- 2026
- Heat detections
- 339
- in a single hotspot: 115 MW
- Danger at start
- 6
- Low · FWI index
- Average daily power
- 627MW
- 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 one day without rain (1 mm or more) when it started. Rain came after the fire: 41.1 mm on 28 Apr.
This area had burned before
98% of the perimeter overlaps earlier fires recorded since 2016: 5,269 ha in 2016, 3,498 ha in 2017, 6,563 ha in 2018, 5,736 ha in 2019, 7,292 ha in 2020, 8,744 ha in 2021, 3,186 ha in 2022, 8,139 ha in 2023, 2,880 ha in 2024, 8,675 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 15,256 ha that had burned before.
- 3,450 ha Longtharai Valley fire, March 2020 10,443 ha in total; the hectares shown are those it shares with this fire
- 3,245 ha Ambassa fire, March 2021 8,641 ha in total; the hectares shown are those it shares with this fire
- 2,221 ha Ambassa fire, March 2025 5,965 ha in total; the hectares shown are those it shares with this fire
- 1,848 ha Ambassa fire, April 2023 8,538 ha in total; the hectares shown are those it shares with this fire
- 1,628 ha Longtharai Valley fire, April 2023 21,363 ha in total; the hectares shown are those it shares with this fire
- 356 ha Longtharai Valley fire, April 2016 5,038 ha in total; the hectares shown are those it shares with this fire
- 149 ha Gandacherra fire, March 2020 24,186 ha in total; the hectares shown are those it shares with this fire
- 25 ha Longtharai Valley fire, March 2021 15,481 ha in total; the hectares shown are those it shares with this fire
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
-
8,050 ha8.7 %
-
Ambassa where it started6,229 ha11 %
-
692 ha1.5 %
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 2025Inside the perimeter there were about 15 hectares of built-up land and about 2,700 residents (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
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) |
|---|---|---|---|---|---|
| 3 Apr | 34.4 °C | 46 % | 31 km/h | 0.0 mm | Low 6 |
| 4 Apr | 33.3 °C | 52 % | 38 km/h | 0.3 mm | Low 7 |
| 5 Apr | 30.6 °C | 64 % | 34 km/h | 6.1 mm | Very low 1 |
| 6 Apr | 33.1 °C | 43 % | 27 km/h | 0.2 mm | Very low 4 |
| 7 Apr | 29.2 °C | 61 % | 29 km/h | 9.2 mm | Very low 0 |
| 8 Apr | 31.6 °C | 34 % | 26 km/h | 2.2 mm | Very low 1 |
| 9 Apr | 24.7 °C | 78 % | 24 km/h | 6.6 mm | Very low 0 |
| 10 Apr | 30.3 °C | 41 % | 28 km/h | 1.2 mm | Very low 1 |
| 11 Apr | 32.7 °C | 32 % | 29 km/h | 0.0 mm | Low 8 |
| 12 Apr | 33.0 °C | 39 % | 42 km/h | 0.0 mm | Low 11 |
| 13 Apr | 34.2 °C | 43 % | 39 km/h | 0.1 mm | Moderate 12 |
| 14 Apr | 32.5 °C | 58 % | 35 km/h | 0.4 mm | Low 10 |
| 15 Apr | 33.5 °C | 50 % | 37 km/h | 3.1 mm | Very low 3 |
| 16 Apr | 32.0 °C | 54 % | 25 km/h | 0.3 mm | Low 6 |
| 17 Apr | 35.0 °C | 46 % | 24 km/h | 0.2 mm | Low 10 |
| 18 Apr | 32.5 °C | 59 % | 24 km/h | 1.3 mm | Very low 4 |
| 19 Apr | 31.5 °C | 68 % | 32 km/h | 3.0 mm | Very low 2 |
| 20 Apr | 34.1 °C | 54 % | 46 km/h | 1.0 mm | Low 7 |
| 21 Apr | 32.8 °C | 58 % | 52 km/h | 0.0 mm | Low 10 |
| 22 Apr after | 34.7 °C | 51 % | 47 km/h | 0.2 mm | Moderate 13 |
| 23 Apr after | 34.7 °C | 47 % | 19 km/h | 0.0 mm | Low 11 |
| 24 Apr after | 35.2 °C | 47 % | 22 km/h | 0.0 mm | Moderate 12 |
| 25 Apr after | 35.0 °C | 44 % | 25 km/h | 0.0 mm | Moderate 13 |
| 26 Apr after | 32.4 °C | 51 % | 31 km/h | 0.0 mm | Moderate 14 |
| 27 Apr after | 26.9 °C | 69 % | 59 km/h | 0.4 mm | Moderate 13 |
| 28 Apr after | 24.7 °C | 87 % | 41 km/h | 41.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 16 April 2026 the air beside the fire reached 96 µg/m³ of PM2.5. That day averaged 72: 4.8 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 · 339Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 21,363 haLongtharai ValleyApril 2023 · 14 days · 11 km away
- 24,186 haGandacherraMarch 2020 · 12 days · 15 km away
- 10,443 haLongtharai Valley25 March 2020 · 8 days · 15 km away
- 15,041 haGandacherraApril 2026 · 12 days · 23 km away
- 15,481 haLongtharai ValleyMarch 2021 · 10 days · 26 km away
- 14,583 haLongtharai Valley23 March 2020 · 11 days · 32 km away
Frequently asked questions
- How long did the Ambassa fire last?
- GWIS (Copernicus) dates it between 10 April 2026 and 21 April 2026: 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 15,588 hectares (155.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Longtharai Valley (8,050 ha, 8.7 %); Ambassa (6,229 ha, 11 %); Gandacherra (692 ha, 1.5 %).
- What was the weather like?
- During the fire the temperature reached 35.2 °C, humidity dropped to 32 % and gusts hit 52 km/h. The fire danger index (FWI) reached 13, class Moderate.
- 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 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 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; 2 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 339 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 2025, 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.