Khon Sawan fire, 9 February 2026 คอนสวรรค์ · Khon Sawan, Kaeng Khro
The fire started on 9 February 2026 in Khon Sawan, Thailand, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,512 hectares from heat detections, spread across 2 municipalities.
It is the 59th largest in Chaiyaphum Province since 2016 (of 123 with a page). Number 420 in Thailand in 2026, of 689.
The power measured by the satellite is low (17.6 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 1,512ha
- GWIS perimeter (Copernicus)
- Duration
- 7days
- 9 Feb 2026 – 15 Feb 2026
- Municipalities hit
- 2
- districts
- Started on
- 9 Feb
- 2026
- Heat detections
- 35
- in a single hotspot: 18 MW
- Danger at start
- 22
- High · FWI index
- Average daily power
- 48MW
- 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 55 days without rain (1 mm or more) when it started. Rain came after the fire: 2.9 mm on 22 Feb.
This area had burned before
83% of the perimeter overlaps earlier fires recorded since 2016: 940 ha in 2016, 766 ha in 2019, 409 ha in 2023, 606 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 1,257 ha that had burned before.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Bangkok boundary: geoBoundaries · OpenStreetMap, Wambacher · © OpenStreetMap contributors (ODbL 1.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).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
1,151 ha reached on 10 Feb2.5 %
-
Kaeng Khro แก้งคร้อ370 ha reached on 14 Feb0.6 %
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 6.5 hectares of built-up land and about 250 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) |
|---|---|---|---|---|---|
| 5 Feb | 33.6 °C | 33 % | 24 km/h | 0.0 mm | High 22 |
| 6 Feb | 34.4 °C | 32 % | 27 km/h | 0.0 mm | High 22 |
| 7 Feb | 33.8 °C | 36 % | 17 km/h | 0.0 mm | High 24 |
| 8 Feb | 31.5 °C | 41 % | 34 km/h | 0.0 mm | High 26 |
| 9 Feb | 29.5 °C | 45 % | 40 km/h | 0.0 mm | High 26 |
| 10 Feb | 31.7 °C | 41 % | 27 km/h | 0.0 mm | High 23 |
| 11 Feb | 32.9 °C | 36 % | 30 km/h | 0.0 mm | High 24 |
| 12 Feb | 32.9 °C | 36 % | 24 km/h | 0.0 mm | High 23 |
| 13 Feb | 34.1 °C | 34 % | 19 km/h | 0.0 mm | High 23 |
| 14 Feb | 34.0 °C | 32 % | 23 km/h | 0.0 mm | High 25 |
| 15 Feb | 34.4 °C | 31 % | 19 km/h | 0.0 mm | High 25 |
| 16 Feb after | 34.9 °C | 34 % | 23 km/h | 0.0 mm | High 26 |
| 17 Feb after | 33.4 °C | 43 % | 32 km/h | 0.0 mm | High 28 |
| 18 Feb after | 31.2 °C | 46 % | 41 km/h | 0.0 mm | High 30 |
| 19 Feb after | 32.2 °C | 41 % | 40 km/h | 0.0 mm | High 30 |
| 20 Feb after | 31.5 °C | 42 % | 36 km/h | 0.0 mm | High 28 |
| 21 Feb after | 33.4 °C | 40 % | 18 km/h | 0.0 mm | High 22 |
| 22 Feb after | 34.5 °C | 41 % | 28 km/h | 2.9 mm | Low 10 |
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 February 2026 the air beside the fire reached 38 µg/m³ of PM2.5. That day averaged 22: 1.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 · 35Every 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 Khon Sawan fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 9 February 2026 to 15 February 2026 (7 days). The perimeter dates it from 12 February 2026 to 15 February 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,512 hectares (15.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Khon Sawan (1,151 ha, 2.5 %); Kaeng Khro (370 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 34.4 °C, humidity dropped to 31 % and gusts hit 40 km/h. The fire danger index (FWI) reached 26, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Thailand (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: 199 · 191 · Emergency number and official warnings ›
Satellite cross-check
History of this page · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Start date: 12 February 2026 → 9 February 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.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 12 February 2026 to 15 February 2026. 35 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.