Khop fire, March 2026 Khop, Xienghone
The fire started on 22 March 2026 in Khop, Laos, and satellites saw it burning for 31 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,899 hectares from heat detections, spread across 2 municipalities.
It is the 26th largest in Xaignabouli since 2016 (of 160 with a page). Number 55 in Laos in 2026, of 308.
Compare with…
Suggestions: Song Khwae · 2020Khop · 2025Khop · 2018Khop · 2019
- Burnt area
- 7,899ha
- GWIS perimeter (Copernicus)
- Duration
- 31days
- 22 Mar 2026 – 21 Apr 2026
- Municipalities hit
- 2
- districts
- Started on
- 22 Mar
- 2026
- Heat detections
- 290
- in a single hotspot: 262 MW
- Danger at start
- 17
- Moderate · FWI index
- Average daily power
- 175MW
- 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 8 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
85% of the perimeter overlaps earlier fires recorded since 2016: 1,425 ha in 2016, 1,269 ha in 2017, 1,724 ha in 2018, 3,028 ha in 2019, 4,629 ha in 2020, 1,125 ha in 2021, 1,249 ha in 2022, 3,799 ha in 2023, 3,180 ha in 2024, 5,477 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 6,714 ha that had burned before.
- 1,685 ha Song Khwae fire, March 2020 1,351 ha in total; the hectares shown are those it shares with this fire
- 1,491 ha Khop fire, March 2025 3,369 ha in total; the hectares shown are those it shares with this fire
- 1,007 ha Khop fire, March 2018 2,187 ha in total; the hectares shown are those it shares with this fire
- 430 ha Khop fire, March 2019 2,118 ha in total; the hectares shown are those it shares with this fire
- 7 ha Khop fire, March 2023 2,304 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
-
Khop where it started6,778 ha reached on 23 Mar9.7 %
-
892 ha reached on 30 Mar0.8 %
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 0.19 hectares of built-up land and about 60 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) |
|---|---|---|---|---|---|
| 22 Mar | 34.0 °C | 38 % | 44 km/h | 0.5 mm | Moderate 17 |
| 23 Mar | 35.0 °C | 29 % | 33 km/h | 0.0 mm | Moderate 19 |
| 24 Mar | 35.0 °C | 30 % | 30 km/h | 0.0 mm | Moderate 20 |
| 25 Mar | 35.4 °C | 29 % | 37 km/h | 0.0 mm | High 22 |
| 26 Mar | 35.1 °C | 29 % | 33 km/h | 0.0 mm | High 22 |
| 27 Mar | 35.8 °C | 28 % | 38 km/h | 0.0 mm | High 24 |
| 28 Mar | 36.3 °C | 30 % | 34 km/h | 0.0 mm | High 25 |
| 29 Mar | 36.0 °C | 28 % | 45 km/h | 0.1 mm | High 28 |
| 30 Mar | 35.6 °C | 32 % | 36 km/h | 0.0 mm | High 26 |
| 31 Mar | 35.5 °C | 34 % | 35 km/h | 0.0 mm | High 27 |
| 1 Apr | 35.5 °C | 39 % | 26 km/h | 0.0 mm | High 24 |
| 2 Apr | 36.2 °C | 36 % | 35 km/h | 0.0 mm | High 27 |
| 3 Apr | 36.5 °C | 34 % | 32 km/h | 0.0 mm | High 26 |
| 4 Apr | 35.5 °C | 39 % | 32 km/h | 0.0 mm | High 27 |
| 5 Apr | 36.1 °C | 40 % | 34 km/h | 0.0 mm | High 27 |
| 6 Apr | 36.1 °C | 41 % | 31 km/h | 0.0 mm | High 25 |
| 7 Apr | 36.0 °C | 43 % | 33 km/h | 0.0 mm | High 26 |
| 8 Apr | 36.2 °C | 36 % | 32 km/h | 0.0 mm | High 26 |
| 9 Apr | 35.7 °C | 35 % | 36 km/h | 0.0 mm | High 28 |
| 10 Apr | 36.1 °C | 30 % | 38 km/h | 0.0 mm | High 31 |
| 11 Apr | 36.0 °C | 32 % | 41 km/h | 0.0 mm | High 32 |
| 12 Apr | 36.1 °C | 26 % | 30 km/h | 0.0 mm | High 31 |
| 13 Apr | 36.8 °C | 32 % | 31 km/h | 0.0 mm | High 32 |
| 14 Apr | 37.2 °C | 34 % | 30 km/h | 0.0 mm | High 32 |
| 15 Apr | 37.9 °C | 28 % | 37 km/h | 0.0 mm | High 35 |
| 16 Apr | 37.4 °C | 28 % | 32 km/h | 0.0 mm | High 33 |
| 17 Apr | 36.2 °C | 36 % | 27 km/h | 0.0 mm | High 31 |
| 18 Apr | 35.9 °C | 43 % | 30 km/h | 0.1 mm | High 29 |
| 19 Apr | 36.4 °C | 36 % | 35 km/h | 0.5 mm | High 30 |
| 20 Apr | 34.6 °C | 45 % | 37 km/h | 0.2 mm | High 29 |
| 21 Apr | 36.8 °C | 39 % | 35 km/h | 0.0 mm | High 28 |
| 22 Apr after | 37.6 °C | 38 % | 36 km/h | 0.0 mm | High 28 |
| 23 Apr after | 34.5 °C | 46 % | 34 km/h | 1.4 mm | Moderate 17 |
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 210 µg/m³ of PM2.5. That day averaged 144: 9.6 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 · 290Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,933 haChiang Kham เชียงคำMarch 2020 · 16 days · 14 km away
- 13,685 haPhu Sang ภูซางMarch 2026 · 20 days · 16 km away
- 11,173 haSong Khwae สองแควMarch 2023 · 28 days · 22 km away
- 6,363 haThung Chang ทุ่งช้าง22 March 2020 · 18 days · 27 km away
- 6,923 haXienghone17 March 2020 · 23 days · 36 km away
- 12,675 haXienghone3 April 2026 · 19 days · 37 km away
Frequently asked questions
- How long did the Khop fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 22 March 2026 to 21 April 2026 (31 days). The perimeter dates it from 22 March 2026 to 17 April 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 7,899 hectares (79.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Khop (6,778 ha, 9.7 %); Xienghone (892 ha, 0.8 %).
- What was the weather like?
- During the fire the temperature reached 37.9 °C, humidity dropped to 26 % and gusts hit 45 km/h. The fire danger index (FWI) reached 35, class 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; 2 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 22 March 2026 to 17 April 2026. 290 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.