Chun fire, 27 February 2026 Chun, Dok Khamtai
The fire started on 27 February 2026 in Chun, Thailand, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,365 hectares from heat detections, spread across 2 municipalities.
It is the 78th largest in Phayao Province since 2016 (of 125 with a page). Number 587 in Thailand in 2026, of 880.
The power measured by the satellite is low (3.5 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
- Burnt area
- 1,365ha
- GWIS perimeter (Copernicus)
- Duration
- 8days
- 27 Feb 2026 – 6 Mar 2026
- Municipalities hit
- 2
- districts
- Started on
- 27 Feb
- 2026
- Heat detections
- 28
- in a single hotspot: 3 MW
- Danger at start
- 22
- High · FWI index
- Energy released
- 42MW
- sum of detected power
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 more than two months without rain (1 mm or more) when it started. Rain came after the fire: 7.6 mm on 12 Mar.
This area had burned before
95% of the perimeter overlaps earlier fires recorded since 2016: 618 ha in 2017, 1,097 ha in 2019, 642 ha in 2020, 377 ha in 2023, 309 ha in 2024, 727 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 1,298 ha that had burned before.
What happened to each town
-
Chun where it started932 ha reached on 27 Feb1.8 %
-
442 ha reached on 2 Mar0.6 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
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) |
|---|---|---|---|---|---|
| 21 Feb | 33.4 °C | 42 % | 26 km/h | 0.2 mm | High 22 |
| 22 Feb | 30.4 °C | 49 % | 22 km/h | 0.0 mm | High 21 |
| 23 Feb | 30.2 °C | 50 % | 23 km/h | 0.0 mm | Moderate 20 |
| 24 Feb | 29.7 °C | 48 % | 24 km/h | 0.0 mm | Moderate 20 |
| 25 Feb | 26.1 °C | 56 % | 30 km/h | 1.3 mm | Low 10 |
| 26 Feb | 29.8 °C | 47 % | 17 km/h | 2.4 mm | Low 5 |
| 27 Feb | 33.0 °C | 34 % | 20 km/h | 0.0 mm | Moderate 17 |
| 28 Feb | 34.0 °C | 31 % | 22 km/h | 0.0 mm | High 24 |
| 1 Mar | 34.0 °C | 26 % | 22 km/h | 0.0 mm | High 26 |
| 2 Mar | 32.7 °C | 31 % | 19 km/h | 0.0 mm | High 27 |
| 3 Mar | 33.1 °C | 29 % | 20 km/h | 0.0 mm | High 26 |
| 4 Mar | 34.4 °C | 31 % | 18 km/h | 0.0 mm | High 28 |
| 5 Mar | 34.2 °C | 32 % | 31 km/h | 0.0 mm | High 31 |
| 6 Mar | 32.7 °C | 44 % | 29 km/h | 0.1 mm | High 27 |
| 7 Mar after | 34.2 °C | 39 % | 25 km/h | 0.0 mm | High 26 |
| 8 Mar after | 34.4 °C | 38 % | 27 km/h | 0.0 mm | High 26 |
| 9 Mar after | 35.1 °C | 37 % | 30 km/h | 0.0 mm | High 27 |
| 10 Mar after | 29.4 °C | 54 % | 24 km/h | 0.4 mm | Moderate 21 |
| 11 Mar after | 28.0 °C | 52 % | 26 km/h | 0.0 mm | Moderate 19 |
| 12 Mar after | 31.0 °C | 42 % | 25 km/h | 7.6 mm | Very low 4 |
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 4 March 2026 the air beside the fire reached 111 µg/m³ of PM2.5. That day averaged 59: 3.9 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 · 28Every 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 Chun fire last?
- GWIS (Copernicus) dates it between 27 February 2026 and 6 March 2026: 8 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 1,365 hectares (13.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Chun (932 ha, 1.8 %); Dok Khamtai (442 ha, 0.6 %).
- What was the weather like?
- During the fire the temperature reached 34.4 °C, humidity dropped to 26 % and gusts hit 31 km/h. The fire danger index (FWI) reached 31, 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
Satellite cross-check
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
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.