Pak Chom fire, February 2020 ปากชม · Pak Chom, Na Yung
The fire started on 18 February 2020 in Pak Chom, Thailand, and satellites saw it burning for 13 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,131 hectares from heat detections, spread across 2 municipalities.
It is the 38th largest in Loei Province since 2016 (of 113 with a page). Number 146 in Thailand in 2020, of 456.
The power measured by the satellite is low (8.3 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
- 2,131ha
- GWIS perimeter (Copernicus)
- Duration
- 13days
- 18 Feb 2020 – 1 Mar 2020
- Municipalities hit
- 2
- districts
- Started on
- 18 Feb
- 2020
- Heat detections
- 80
- in a single hotspot: 8 MW
- Danger at start
- 27
- High · FWI index
- Average daily power
- 24MW
- 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 more than two months without rain (1 mm or more) when it started. Rain came after the fire: 3.7 mm on 3 Mar.
This area had burned before
96% of the perimeter overlaps earlier fires recorded since 2016: 1,212 ha in 2016, 668 ha in 2017, 786 ha in 2018, 1,803 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 2,050 ha that had burned before.
- 794 ha Na Yung fire, March 2019 2,152 ha in total; the hectares shown are those it shares with this fire
- 556 ha Pak Chom fire, March 2016 6,354 ha in total; the hectares shown are those it shares with this fire
- 56 ha Pak Chom fire, March 2019 1,481 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
-
1,783 ha reached on 18 Feb1.8 %
-
Na Yung นายูง360 ha reached on 20 Feb0.7 %
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 2020Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, 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.
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) |
|---|---|---|---|---|---|
| 18 Feb | 27.5 °C | 41 % | 36 km/h | 0.0 mm | High 27 |
| 19 Feb | 30.0 °C | 40 % | 26 km/h | 0.0 mm | High 24 |
| 20 Feb | 30.7 °C | 40 % | 28 km/h | 0.0 mm | High 25 |
| 21 Feb | 30.3 °C | 37 % | 38 km/h | 0.0 mm | High 28 |
| 22 Feb | 30.2 °C | 37 % | 37 km/h | 0.0 mm | High 27 |
| 23 Feb | 30.7 °C | 37 % | 29 km/h | 0.0 mm | High 26 |
| 24 Feb | 30.6 °C | 38 % | 27 km/h | 0.0 mm | High 27 |
| 25 Feb | 33.0 °C | 32 % | 23 km/h | 0.0 mm | High 26 |
| 26 Feb | 33.2 °C | 32 % | 24 km/h | 0.0 mm | High 26 |
| 27 Feb | 31.9 °C | 36 % | 30 km/h | 0.0 mm | High 27 |
| 28 Feb | 32.0 °C | 37 % | 28 km/h | 0.0 mm | High 29 |
| 29 Feb | 34.0 °C | 36 % | 25 km/h | 0.0 mm | High 27 |
| 1 Mar | 34.8 °C | 38 % | 21 km/h | 0.0 mm | High 26 |
| 2 Mar after | 33.7 °C | 42 % | 24 km/h | 0.3 mm | High 26 |
| 3 Mar after | 32.1 °C | 52 % | 29 km/h | 3.7 mm | Very low 5 |
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.
Detections table · 80Every 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 Pak Chom fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 18 February 2020 to 1 March 2020 (13 days). The perimeter dates it from 18 February 2020 to 23 February 2020.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 2,131 hectares (21.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Pak Chom (1,783 ha, 1.8 %); Na Yung (360 ha, 0.7 %).
- What was the weather like?
- During the fire the temperature reached 30.7 °C, humidity dropped to 37 % and gusts hit 38 km/h. The fire danger index (FWI) reached 28, 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: 23 February 2020 → 1 March 2020.
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 18 February 2020 to 23 February 2020. 80 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 2020, 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.