Nam Pat fire, 27 March 2026 น้ำปาด · Thong Saen Khan, Nam Pat, Chat Trakan
The fire started on 27 March 2026 in Nam Pat, Thailand, and satellites saw it burning for 26 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 16,993 hectares from heat detections, spread across 3 municipalities.
It is the 3th largest in Uttaradit Province since 2016 (of 104 with a page). Number 35 in Thailand in 2026, of 689.
Compare with…
- Burnt area
- 16,993ha
- GWIS perimeter (Copernicus)
- Duration
- 26days
- 27 Mar 2026 – 21 Apr 2026
- Municipalities hit
- 3
- districts
- Started on
- 27 Mar
- 2026
- Heat detections
- 389
- in a single hotspot: 69 MW
- Danger at start
- 26
- High · FWI index
- Average daily power
- 60MW
- 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 14 days without rain (1 mm or more) when it started. Rain came after the fire: 1.0 mm on 24 Apr.
This area had burned before
84% of the perimeter overlaps earlier fires recorded since 2016: 3,411 ha in 2016, 1,808 ha in 2017, 1,132 ha in 2018, 5,414 ha in 2019, 4,400 ha in 2020, 5,894 ha in 2021, 6,063 ha in 2023, 2,995 ha in 2024, 2,572 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 14,190 ha that had burned before.
- 2,276 ha Nam Pat fire, February 2021 2,485 ha in total; the hectares shown are those it shares with this fire
- 1,561 ha Thong Saen Khan fire, March 2023 5,219 ha in total; the hectares shown are those it shares with this fire
- 1,152 ha Nam Pat fire, March 2019 1,341 ha in total; the hectares shown are those it shares with this fire
- 1,146 ha Thong Saen Khan fire, April 2024 1,138 ha in total; the hectares shown are those it shares with this fire
- 1,098 ha Chat Trakan fire, March 2023 1,726 ha in total; the hectares shown are those it shares with this fire
- 988 ha Thong Saen Khan fire, March 2019 1,704 ha in total; the hectares shown are those it shares with this fire
- 946 ha Thong Saen Khan fire, March 2021 1,164 ha in total; the hectares shown are those it shares with this fire
- 887 ha Thong Saen Khan fire, March 2023 1,545 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
-
Thong Saen Khan ทองแสนขัน12,638 ha reached on 27 Mar17 %
-
2,334 ha reached on 27 Mar1.6 %
-
Chat Trakan ชาติตระการ2,110 ha reached on 2 Apr1.3 %
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.33 hectares of built-up land and almost nobody lived there (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) |
|---|---|---|---|---|---|
| 27 Mar | 36.8 °C | 43 % | 35 km/h | 0.1 mm | High 26 |
| 28 Mar | 36.1 °C | 43 % | 34 km/h | 0.0 mm | High 26 |
| 29 Mar | 36.8 °C | 37 % | 33 km/h | 0.3 mm | High 26 |
| 30 Mar | 36.0 °C | 38 % | 34 km/h | 0.0 mm | High 26 |
| 31 Mar | 36.2 °C | 38 % | 31 km/h | 0.0 mm | High 26 |
| 1 Apr | 36.9 °C | 37 % | 27 km/h | 0.0 mm | High 26 |
| 2 Apr | 37.5 °C | 36 % | 31 km/h | 0.0 mm | High 27 |
| 3 Apr | 36.6 °C | 36 % | 32 km/h | 0.0 mm | High 28 |
| 4 Apr | 35.8 °C | 42 % | 30 km/h | 0.0 mm | High 26 |
| 5 Apr | 36.1 °C | 41 % | 33 km/h | 0.0 mm | High 28 |
| 6 Apr | 36.9 °C | 40 % | 32 km/h | 0.0 mm | High 28 |
| 7 Apr | 37.1 °C | 41 % | 32 km/h | 0.0 mm | High 29 |
| 8 Apr | 37.6 °C | 33 % | 33 km/h | 0.0 mm | High 30 |
| 9 Apr | 37.1 °C | 33 % | 34 km/h | 0.0 mm | High 30 |
| 10 Apr | 37.8 °C | 27 % | 34 km/h | 0.0 mm | High 33 |
| 11 Apr | 37.3 °C | 35 % | 37 km/h | 0.0 mm | High 36 |
| 12 Apr | 36.8 °C | 34 % | 29 km/h | 0.0 mm | High 33 |
| 13 Apr | 37.1 °C | 34 % | 31 km/h | 0.0 mm | High 34 |
| 14 Apr | 37.9 °C | 34 % | 29 km/h | 0.0 mm | High 33 |
| 15 Apr | 38.0 °C | 31 % | 33 km/h | 0.0 mm | High 36 |
| 16 Apr | 38.5 °C | 29 % | 28 km/h | 0.0 mm | High 34 |
| 17 Apr | 37.8 °C | 34 % | 26 km/h | 0.0 mm | High 34 |
| 18 Apr | 37.3 °C | 38 % | 28 km/h | 0.0 mm | High 33 |
| 19 Apr | 36.5 °C | 44 % | 34 km/h | 0.0 mm | High 31 |
| 20 Apr | 36.8 °C | 39 % | 31 km/h | 0.0 mm | High 30 |
| 21 Apr | 37.1 °C | 39 % | 32 km/h | 0.0 mm | High 31 |
| 22 Apr after | 37.3 °C | 45 % | 34 km/h | 0.0 mm | High 31 |
| 23 Apr after | 36.4 °C | 53 % | 33 km/h | 0.0 mm | High 26 |
| 24 Apr after | 36.5 °C | 44 % | 24 km/h | 1.0 mm | Moderate 21 |
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 86 µg/m³ of PM2.5. That day averaged 72: 4.8 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 · 389Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 5,886 haNam Pat น้ำปาด8 April 2026 · 16 days · 13 km away
- 5,219 haThong Saen Khan ทองแสนขัน25 March 2023 · 24 days · 14 km away
- 7,850 haChat Trakan ชาติตระการ4 April 2026 · 18 days · 18 km away
- 13,219 haNam Pat น้ำปาด1 April 2026 · 23 days · 32 km away
- 8,797 haTha Pla ท่าปลา24 March 2026 · 16 days · 39 km away
- 6,945 haChat Trakan ชาติตระการ3 April 2026 · 19 days · 39 km away
Frequently asked questions
- How long did the Nam Pat fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 27 March 2026 to 21 April 2026 (26 days). The perimeter dates it from 27 March 2026 to 20 April 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 16,993 hectares (169.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Thong Saen Khan (12,638 ha, 17 %); Nam Pat (2,334 ha, 1.6 %); Chat Trakan (2,110 ha, 1.3 %).
- What was the weather like?
- During the fire the temperature reached 38.5 °C, humidity dropped to 27 % and gusts hit 37 km/h. The fire danger index (FWI) reached 36, 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.
- Last day with fire: 20 April 2026 → 21 April 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; 4 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 27 March 2026 to 20 April 2026. 389 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.