Thoen fire, 27 March 2026 เถิน · Thoen
The fire started on 27 March 2026 in Thoen, Thailand, and satellites saw it burning for 13 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 8,098 hectares from heat detections, spread across a single municipality.
It is the 10th largest in Lampang Province since 2016 (of 216 with a page). Number 77 in Thailand in 2026, of 689.
The power measured by the satellite is low (13.2 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…
Suggestions: Thoen · 2021Thoen · 2019Thoen · 2020Thoen · 2018
- Burnt area
- 8,098ha
- GWIS perimeter (Copernicus)
- Duration
- 13days
- 27 Mar 2026 – 8 Apr 2026
- Municipalities hit
- 1
- districts
- Started on
- 27 Mar
- 2026
- Heat detections
- 199
- in a single hotspot: 13 MW
- Danger at start
- 19
- Moderate · FWI index
- Average daily power
- 42MW
- 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.
This area had burned before
88% of the perimeter overlaps earlier fires recorded since 2016: 567 ha in 2016, 1,850 ha in 2017, 1,993 ha in 2018, 2,578 ha in 2019, 1,978 ha in 2020, 3,474 ha in 2021, 2,333 ha in 2023, 1,491 ha in 2024, 1,736 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 7,127 ha that had burned before.
- 1,477 ha Thoen fire, February 2021 2,305 ha in total; the hectares shown are those it shares with this fire
- 1,350 ha Thoen fire, February 2019 2,575 ha in total; the hectares shown are those it shares with this fire
- 1,206 ha Thoen fire, January 2020 2,893 ha in total; the hectares shown are those it shares with this fire
- 854 ha Thoen fire, March 2018 1,439 ha in total; the hectares shown are those it shares with this fire
- 336 ha Thoen fire, April 2023 1,335 ha in total; the hectares shown are those it shares with this fire
- 60 ha Thoen fire, February 2019 1,239 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).
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
-
8,144 ha4.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 1.6 hectares of built-up land and about 100 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 | 33.5 °C | 34 % | 32 km/h | 0.0 mm | Moderate 19 |
| 23 Mar | 34.4 °C | 25 % | 30 km/h | 0.0 mm | High 21 |
| 24 Mar | 35.0 °C | 23 % | 26 km/h | 0.0 mm | High 22 |
| 25 Mar | 35.2 °C | 26 % | 25 km/h | 0.0 mm | High 23 |
| 26 Mar | 35.9 °C | 26 % | 22 km/h | 0.0 mm | High 23 |
| 27 Mar | 35.7 °C | 26 % | 28 km/h | 0.0 mm | High 25 |
| 28 Mar | 35.1 °C | 29 % | 30 km/h | 0.0 mm | High 27 |
| 29 Mar | 35.1 °C | 28 % | 30 km/h | 0.0 mm | High 27 |
| 30 Mar | 35.4 °C | 28 % | 25 km/h | 0.0 mm | High 26 |
| 31 Mar | 35.4 °C | 29 % | 22 km/h | 0.0 mm | High 27 |
| 1 Apr | 35.4 °C | 30 % | 20 km/h | 0.0 mm | High 27 |
| 2 Apr | 35.9 °C | 29 % | 24 km/h | 0.0 mm | High 28 |
| 3 Apr | 35.8 °C | 28 % | 31 km/h | 0.0 mm | High 30 |
| 4 Apr | 34.7 °C | 34 % | 27 km/h | 0.0 mm | High 27 |
| 5 Apr | 35.2 °C | 35 % | 34 km/h | 0.0 mm | High 29 |
| 6 Apr | 35.9 °C | 32 % | 25 km/h | 0.0 mm | High 29 |
| 7 Apr | 35.9 °C | 30 % | 36 km/h | 0.0 mm | High 31 |
| 8 Apr | 36.1 °C | 27 % | 37 km/h | 0.0 mm | High 33 |
| 9 Apr after | 35.0 °C | 27 % | 36 km/h | 0.0 mm | High 34 |
| 10 Apr after | 36.0 °C | 26 % | 34 km/h | 0.0 mm | High 33 |
| 11 Apr after | 35.1 °C | 32 % | 37 km/h | 0.0 mm | High 35 |
| 12 Apr after | 36.1 °C | 27 % | 35 km/h | 0.0 mm | High 34 |
| 13 Apr after | 36.1 °C | 28 % | 28 km/h | 0.0 mm | High 33 |
| 14 Apr after | 36.6 °C | 25 % | 25 km/h | 0.0 mm | High 32 |
| 15 Apr after | 36.8 °C | 18 % | 37 km/h | 0.0 mm | Very high 42 |
| 16 Apr after | 37.4 °C | 17 % | 29 km/h | 0.0 mm | Very high 40 |
| 17 Apr after | 37.2 °C | 24 % | 22 km/h | 0.0 mm | Very high 39 |
| 18 Apr after | 37.2 °C | 24 % | 24 km/h | 0.0 mm | Very high 40 |
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 2 April 2026 the air beside the fire reached 83 µg/m³ of PM2.5. That day averaged 47: 3.1 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 · 199Every 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 Thoen fire last?
- GWIS (Copernicus) dates it between 27 March 2026 and 8 April 2026: 13 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 8,098 hectares (81.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Thoen (8,144 ha, 4.6 %).
- What was the weather like?
- During the fire the temperature reached 36.1 °C, humidity dropped to 23 % and gusts hit 37 km/h. The fire danger index (FWI) reached 33, 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 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. 199 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.