Phu Sing fire, January 2026 Thailand
The fire started on 30 January 2026 in Phu Sing, Thailand, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,150 hectares from heat detections, spread across a single municipality.
It is the 26th largest in Si Sa Ket Province since 2016 (of 26 with a page). Number 742 in Thailand in 2026, of 880.
The power measured by the satellite is low (21.3 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,150ha
- GWIS perimeter (Copernicus)
- Duration
- 3days
- 30 Jan 2026 – 1 Feb 2026
- Municipalities hit
- 0
- districts
- Started on
- 30 Jan
- 2026
- Heat detections
- 18
- in a single hotspot: 21 MW
- Danger at start
- 21
- High · FWI index
- Energy released
- 93MW
- 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 46 days without rain (1 mm or more) when it started.
This area had burned before
95% of the perimeter overlaps earlier fires recorded since 2016: 477 ha in 2016, 426 ha in 2017, 229 ha in 2018, 838 ha in 2019, 973 ha in 2020, 129 ha in 2021, 835 ha in 2022, 48 ha in 2023, 1 ha in 2024, 395 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 1,095 ha that had burned before.
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) |
|---|---|---|---|---|---|
| 30 Jan | 33.0 °C | 39 % | 25 km/h | 0.0 mm | High 21 |
| 31 Jan | 32.8 °C | 36 % | 27 km/h | 0.0 mm | High 24 |
| 1 Feb | 31.4 °C | 43 % | 28 km/h | 0.0 mm | High 25 |
| 2 Feb after | 31.4 °C | 44 % | 35 km/h | 0.0 mm | High 26 |
| 3 Feb after | 31.8 °C | 45 % | 33 km/h | 0.0 mm | High 26 |
| 4 Feb after | 32.6 °C | 42 % | 27 km/h | 0.0 mm | High 25 |
| 5 Feb after | 34.4 °C | 39 % | 20 km/h | 0.0 mm | High 22 |
| 6 Feb after | 35.4 °C | 38 % | 18 km/h | 0.0 mm | High 22 |
| 7 Feb after | 33.7 °C | 51 % | 14 km/h | 0.1 mm | Moderate 20 |
| 8 Feb after | 31.3 °C | 54 % | 32 km/h | 0.2 mm | High 22 |
| 9 Feb after | 33.0 °C | 41 % | 29 km/h | 0.0 mm | High 22 |
| 10 Feb after | 33.5 °C | 42 % | 24 km/h | 0.0 mm | High 22 |
| 11 Feb after | 34.8 °C | 41 % | 28 km/h | 0.0 mm | High 23 |
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 29 January 2026 the air beside the fire reached 33 µg/m³ of PM2.5. That day averaged 23: 1.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 · 18Every 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 Phu Sing fire last?
- GWIS (Copernicus) dates it between 30 January 2026 and 1 February 2026: 3 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,150 hectares (11.5 km²). It is an estimate: official national figures may differ.
- What was the weather like?
- During the fire the temperature reached 33.0 °C, humidity dropped to 36 % and gusts hit 28 km/h. The fire danger index (FWI) reached 25, 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.