Xanakharm fire, March 2026 Xanakharm, Mad
The fire started on 17 March 2026 in Xanakharm, Laos, and satellites saw it burning for 37 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 45,327 hectares from heat detections, spread across 2 municipalities.
It is the largest fire in Vientiane since 2016 (of 87 with a page). Number 7 in Laos in 2026, of 308.
Compare with…
- Burnt area
- 45,327ha
- GWIS perimeter (Copernicus)
- Duration
- 37days
- 17 Mar 2026 – 22 Apr 2026
- Municipalities hit
- 2
- districts
- Started on
- 17 Mar
- 2026
- Heat detections
- 1,830
- in a single hotspot: 182 MW
- Danger at start
- 20
- Moderate · FWI index
- Average daily power
- 392MW
- 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 7 days without rain (1 mm or more) when it started. Rain came after the fire: 1.4 mm on 23 Apr.
This area had burned before
49% of the perimeter overlaps earlier fires recorded since 2016: 611 ha in 2016, 738 ha in 2017, 3,041 ha in 2019, 5,443 ha in 2020, 20,601 ha in 2023, 1,116 ha in 2024, 1,824 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 22,031 ha that had burned before.
- 18,988 ha Xanakharm fire, March 2023 34,889 ha in total; the hectares shown are those it shares with this fire
- 3,392 ha Xanakharm fire, March 2020 3,999 ha in total; the hectares shown are those it shares with this fire
- 1,824 ha Mad fire, March 2025 2,022 ha in total; the hectares shown are those it shares with this fire
- 1,816 ha Xanakharm fire, April 2019 4,815 ha in total; the hectares shown are those it shares with this fire
- 1,018 ha Mad fire, March 2020 2,049 ha in total; the hectares shown are those it shares with this fire
- 738 ha Xanakharm fire, April 2017 5,134 ha in total; the hectares shown are those it shares with this fire
- 191 ha Xanakharm fire, April 2016 2,765 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
-
Xanakharm where it started40,807 ha reached on 17 Mar22 %
-
4,771 ha reached on 19 Mar3.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.
People and buildings inside the perimeter
GHSL 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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) |
|---|---|---|---|---|---|
| 20 Mar | 34.8 °C | 34 % | 19 km/h | 0.0 mm | Moderate 20 |
| 21 Mar | 35.0 °C | 34 % | 24 km/h | 0.0 mm | High 22 |
| 22 Mar | 33.6 °C | 46 % | 32 km/h | 0.5 mm | Moderate 21 |
| 23 Mar | 36.2 °C | 27 % | 28 km/h | 0.0 mm | High 26 |
| 24 Mar | 37.1 °C | 25 % | 24 km/h | 0.0 mm | High 28 |
| 25 Mar | 36.2 °C | 39 % | 26 km/h | 0.1 mm | High 25 |
| 26 Mar | 37.9 °C | 28 % | 28 km/h | 0.0 mm | High 28 |
| 27 Mar | 37.6 °C | 28 % | 33 km/h | 0.0 mm | High 31 |
| 28 Mar | 37.2 °C | 32 % | 29 km/h | 0.1 mm | High 29 |
| 29 Mar | 36.3 °C | 30 % | 38 km/h | 0.3 mm | High 31 |
| 30 Mar | 37.6 °C | 25 % | 33 km/h | 0.0 mm | High 33 |
| 31 Mar | 37.2 °C | 28 % | 30 km/h | 0.0 mm | High 32 |
| 1 Apr | 37.8 °C | 30 % | 25 km/h | 0.0 mm | High 31 |
| 2 Apr | 37.9 °C | 29 % | 27 km/h | 0.0 mm | High 34 |
| 3 Apr | 37.9 °C | 29 % | 31 km/h | 0.0 mm | High 34 |
| 4 Apr | 36.8 °C | 32 % | 31 km/h | 0.0 mm | High 34 |
| 5 Apr | 37.6 °C | 31 % | 33 km/h | 0.0 mm | High 35 |
| 6 Apr | 38.6 °C | 27 % | 30 km/h | 0.0 mm | High 35 |
| 7 Apr | 38.5 °C | 27 % | 30 km/h | 0.0 mm | High 36 |
| 8 Apr | 38.8 °C | 22 % | 33 km/h | 0.0 mm | Very high 39 |
| 9 Apr | 38.6 °C | 21 % | 38 km/h | 0.0 mm | Very high 41 |
| 10 Apr | 39.0 °C | 17 % | 37 km/h | 0.0 mm | Very high 44 |
| 11 Apr | 38.1 °C | 24 % | 38 km/h | 0.0 mm | Very high 46 |
| 12 Apr | 38.6 °C | 22 % | 27 km/h | 0.0 mm | Very high 44 |
| 13 Apr | 38.9 °C | 25 % | 29 km/h | 0.0 mm | Very high 43 |
| 14 Apr | 39.4 °C | 23 % | 26 km/h | 0.0 mm | Very high 41 |
| 15 Apr | 39.8 °C | 21 % | 30 km/h | 0.0 mm | Very high 45 |
| 16 Apr | 39.9 °C | 17 % | 28 km/h | 0.0 mm | Very high 43 |
| 17 Apr | 39.4 °C | 22 % | 23 km/h | 0.0 mm | Very high 41 |
| 18 Apr | 36.7 °C | 35 % | 27 km/h | 0.1 mm | High 33 |
| 19 Apr | 34.6 °C | 46 % | 32 km/h | 0.9 mm | High 24 |
| 20 Apr | 36.6 °C | 34 % | 28 km/h | 0.2 mm | High 29 |
| 21 Apr | 37.0 °C | 32 % | 26 km/h | 0.0 mm | High 31 |
| 22 Apr | 37.7 °C | 39 % | 29 km/h | 0.0 mm | High 32 |
| 23 Apr after | 35.7 °C | 44 % | 27 km/h | 1.4 mm | Moderate 19 |
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 17 April 2026 the air beside the fire reached 212 µg/m³ of PM2.5. That day averaged 140: 9.3 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 · 1,830Every 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 Xanakharm fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 17 March 2026 to 22 April 2026 (37 days). The perimeter dates it from 20 March 2026 to 19 April 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 45,327 hectares (453.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Xanakharm (40,807 ha, 22 %); Mad (4,771 ha, 3.0 %).
- What was the weather like?
- During the fire the temperature reached 39.9 °C, humidity dropped to 17 % and gusts hit 38 km/h. The fire danger index (FWI) reached 46, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Laos (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.
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; 5 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 20 March 2026 to 19 April 2026. 1,830 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 ADM2 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.