Pak Chom fire, 5 March 2019 ปากชม · Pak Chom, Sangkhom
The fire started on 5 March 2019 in Pak Chom, Thailand, and satellites saw it burning for 10 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,110 hectares from heat detections, spread across 2 municipalities.
It is the 39th largest in Loei Province since 2016 (of 113 with a page). Number 105 in Thailand in 2019, of 386.
The power measured by the satellite is low (29.9 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,110ha
- GWIS perimeter (Copernicus)
- Duration
- 10days
- 5 Mar 2019 – 14 Mar 2019
- Municipalities hit
- 2
- districts
- Started on
- 5 Mar
- 2019
- Heat detections
- 50
- in a single hotspot: 30 MW
- Danger at start
- 19
- Moderate · FWI index
- Average daily power
- 31MW
- 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 5 days without rain (1 mm or more) when it started. Rain came after the fire: 3.4 mm on 18 Mar.
This area had burned before
31% of the perimeter overlaps earlier fires recorded since 2016: 348 ha in 2016, 311 ha in 2018.
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,415 ha reached on 7 Mar1.4 %
-
Sangkhom สังคม709 ha reached on 10 Mar1.5 %
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 were about 0.16 hectares of 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) |
|---|---|---|---|---|---|
| 7 Mar | 34.6 °C | 30 % | 22 km/h | 0.0 mm | Moderate 19 |
| 8 Mar | 34.5 °C | 31 % | 31 km/h | 0.0 mm | High 23 |
| 9 Mar | 34.7 °C | 25 % | 38 km/h | 0.0 mm | High 25 |
| 10 Mar | 33.7 °C | 27 % | 33 km/h | 0.0 mm | High 24 |
| 11 Mar | 34.7 °C | 23 % | 26 km/h | 0.0 mm | High 23 |
| 12 Mar | 33.8 °C | 28 % | 19 km/h | 0.0 mm | High 24 |
| 13 Mar | 33.9 °C | 29 % | 21 km/h | 0.0 mm | High 23 |
| 14 Mar | 33.6 °C | 30 % | 18 km/h | 0.0 mm | High 25 |
| 15 Mar after | 30.9 °C | 48 % | 31 km/h | 0.0 mm | Moderate 19 |
| 16 Mar after | 31.7 °C | 47 % | 27 km/h | 0.0 mm | Moderate 19 |
| 17 Mar after | 33.1 °C | 44 % | 27 km/h | 0.0 mm | Moderate 18 |
| 18 Mar after | 33.2 °C | 47 % | 27 km/h | 3.4 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.
Detections table · 50Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 10,355 haSangthongMarch 2020 · 8 days · 17 km away
- 37,269 haPak Chom ปากชม8 April 2026 · 15 days · 19 km away
- 12,599 haNaxaithongMarch 2023 · 10 days · 26 km away
- 23,048 haNaxaithongApril 2026 · 18 days · 28 km away
- 8,857 haPhonhongMarch 2026 · 38 days · 38 km away
- 16,393 haHinherbMarch 2023 · 23 days · 40 km away
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 5 March 2019 to 14 March 2019 (10 days). The perimeter dates it from 7 March 2019 to 14 March 2019.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 2,110 hectares (21.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Pak Chom (1,415 ha, 1.4 %); Sangkhom (709 ha, 1.5 %).
- What was the weather like?
- During the fire the temperature reached 34.7 °C, humidity dropped to 23 % and gusts hit 38 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 · 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.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 7 March 2019 to 14 March 2019. 50 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.