Burned area
satellite only1,489ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 13 Feb 2020 – 21 Feb 2020
+− cross-check
No official record is matched to this page to compare it with.
TH · Thailand · –
Mueang Phetchabun fire, 13 February 2020 เมืองเพชรบูรณ์ · Lom Sak, Mueang Phetchabun
Out · last detection 20 Feb 2020, 18:48 UTC
The fire started on 13 February 2020 in Mueang Phetchabun, Thailand, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,489 hectares from heat detections, spread across 2 municipalities.
It is the 42th largest in Phetchabun Province since 2016 (of 84 with a page). Number 237 in Thailand in 2020, of 457.
The power measured by the satellite is low (7.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-26matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only9days
13 Feb 2020 to 21 Feb 2020: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 20 Feb 2020, 18:48 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only13 Feb 2020
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 13 Feb 2020
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only39
VIIRS detections at 375 m. Most intense hotspot: 7 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 13 Feb 2020 – 21 Feb 2020
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only57MW
Total radiative power on 15 February 2020; hotspots that day: 25.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 15 Feb 2020
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model26.2FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 18.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 13 Feb 2020, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model33.5°C · 30% RH
High of 33.5 °C and minimum humidity of 30% on 16 February 2020; gusts of 39 km/h on 14 February 2020.
- Source
- weather model at the fire’s grid cell
- Date
- 13 Feb 2020 – 21 Feb 2020
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
Living inside
model≈ 20people
Estimated residents inside the perimeter and 0.34 ha of built-up area (100 m grid, epoch 2020).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
logLast day with fire: 16 February 2020 → 21 February 2020.
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 26 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 1,489 ha
- Dates
- 13 Feb 2020 – 21 Feb 2020
- Name
- Mueang Phetchabun
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/mueang-phetchabun-2020-02-5?v=2026-10-26A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire mueang-phetchabun-2020-02-5.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020-02-13 | 1 | 1 | 31.9 | 20.2 | 46 | 12.7 | 31 | 0 | 26.2 | alto | 1 |
| 2020-02-14 | 7 | 15 | 31.7 | 19.8 | 43 | 16.5 | 39.2 | 0.3 | 29.1 | alto | 1 |
| 2020-02-15 | 25 | 57 | 32.2 | 18.8 | 33 | 11.2 | 28.4 | 0 | 27.4 | alto | 1 |
| 2020-02-16 | 5 | 11 | 33.5 | 16.2 | 30 | 9.9 | 20.5 | 0 | 28.8 | alto | 1 |
| 2020-02-17 | 0 | 0 | 30.8 | 17 | 42 | 11.9 | 33.1 | 0 | 28.1 | alto | 1 |
| 2020-02-18 | 0 | 0 | 28.4 | 17.4 | 42 | 13 | 32.4 | 0 | 27.8 | alto | 1 |
| 2020-02-19 | 0 | 0 | 30.4 | 16.2 | 40 | 8.9 | 25.2 | 0 | 25.3 | alto | 1 |
| 2020-02-20 | 1 | 1 | 31.1 | 15.3 | 36 | 11 | 29.9 | 0 | 26.9 | alto | 1 |
| 2020-02-21 | 0 | 0 | 30.2 | 16.5 | 35 | 16.1 | 38.5 | 0 | 30.8 | alto | 1 |
| 2020-02-22 | 0 | 0 | 30.3 | 17.1 | 35 | 17.1 | 41.4 | 0 | 31.9 | alto | 0 |
| 2020-02-23 | 0 | 0 | 30.9 | 17 | 36 | 12.3 | 31.7 | 0 | 28.5 | alto | 0 |
| 2020-02-24 | 0 | 0 | 31.9 | 15.5 | 33 | 6.9 | 22.7 | 0 | 25.6 | alto | 0 |
| 2020-02-25 | 0 | 0 | 33.5 | 14.5 | 29 | 6.2 | 16.2 | 0 | 27.6 | alto | 0 |
| 2020-02-26 | 0 | 0 | 33.4 | 16.9 | 31 | 7 | 16.9 | 0 | 28.4 | alto | 0 |
| 2020-02-27 | 0 | 0 | 31.9 | 15.9 | 32 | 7.6 | 20.9 | 0 | 29.1 | alto | 0 |
| 2020-02-28 | 0 | 0 | 32.5 | 16.4 | 33 | 7.6 | 20.9 | 0 | 29.3 | alto | 0 |
| 2020-02-29 | 0 | 0 | 32.3 | 18.8 | 42 | 7.2 | 22.7 | 0 | 26.8 | alto | 0 |
| 2020-03-01 | 0 | 0 | 32.1 | 21 | 48 | 5.2 | 17.6 | 0 | 23.1 | alto | 0 |
| 2020-03-02 | 0 | 0 | 32.1 | 21.6 | 52 | 7.4 | 23 | 1.1 | 14.3 | moderado | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 1,489ha
- GWIS perimeter (Copernicus)
- Duration
- 9days
- 13 Feb 2020 – 21 Feb 2020
- Municipalities hit
- 2
- districts
- Started on
- 13 Feb
- 2020
- Heat detections
- 39
- in a single hotspot: 7 MW
- Danger at start
- 26
- High · FWI index
- Average daily power
- 17MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
13 Feb21 Feb
20 Feb 2020
How it evolved, day by day
13 Feb
14 Feb
15 Feb
16 Feb
20 Feb
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
34°high
39km/h · peak gust
30%lowest humidity
It had gone 18 days without rain (1 mm or more) when it started. Rain came after the fire: 1.1 mm on 2 Mar.
This area had burned before
70% of the perimeter overlaps earlier fires recorded since 2016: 159 ha in 2016, 536 ha in 2017, 456 ha in 2018, 588 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 1,046 ha that had burned before.
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
-
Lom Sak หล่มสัก1,115 ha reached on 14 Feb0.8 %
-
382 ha reached on 13 Feb0.2 %
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 2020Built-up area0.34 ha
Residents≈ 20
Inside the perimeter there were about 0.34 hectares of built-up land and about 20 residents (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) |
|---|---|---|---|---|---|
| 13 Feb | 31.9 °C | 46 % | 31 km/h | 0.0 mm | High 26 |
| 14 Feb | 31.7 °C | 43 % | 39 km/h | 0.3 mm | High 29 |
| 15 Feb | 32.2 °C | 33 % | 28 km/h | 0.0 mm | High 27 |
| 16 Feb | 33.5 °C | 30 % | 20 km/h | 0.0 mm | High 29 |
| 17 Feb | 30.8 °C | 42 % | 33 km/h | 0.0 mm | High 28 |
| 18 Feb | 28.4 °C | 42 % | 32 km/h | 0.0 mm | High 28 |
| 19 Feb | 30.4 °C | 40 % | 25 km/h | 0.0 mm | High 25 |
| 20 Feb | 31.1 °C | 36 % | 30 km/h | 0.0 mm | High 27 |
| 21 Feb | 30.2 °C | 35 % | 38 km/h | 0.0 mm | High 31 |
| 22 Feb after | 30.3 °C | 35 % | 41 km/h | 0.0 mm | High 32 |
| 23 Feb after | 30.9 °C | 36 % | 32 km/h | 0.0 mm | High 28 |
| 24 Feb after | 31.9 °C | 33 % | 23 km/h | 0.0 mm | High 26 |
| 25 Feb after | 33.5 °C | 29 % | 16 km/h | 0.0 mm | High 28 |
| 26 Feb after | 33.4 °C | 31 % | 17 km/h | 0.0 mm | High 28 |
| 27 Feb after | 31.9 °C | 32 % | 21 km/h | 0.0 mm | High 29 |
| 28 Feb after | 32.5 °C | 33 % | 21 km/h | 0.0 mm | High 29 |
| 29 Feb after | 32.3 °C | 42 % | 23 km/h | 0.0 mm | High 27 |
| 1 Mar after | 32.1 °C | 48 % | 18 km/h | 0.0 mm | High 23 |
| 2 Mar after | 32.1 °C | 52 % | 23 km/h | 1.1 mm | Moderate 14 |
Its twins: fires that started in the same weather
It started with an FWI of 26.2, a minimum humidity of 46% and 18 days without rain. Fires in the area that started in weather like this since 2016: 34.
FWI at the start
26.2
Minimum humidity
46 %
Days without rain
18
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Mueang Phetchabun fire, 13 February 2020
1,489 ha
9 days
FWI 26.2
Min. humidity 46 %
Thong Saen Khan fire, April 2024
2,661 ha
13 days
FWI 25.4
Min. humidity 46 %
130 km away, in 2024
First rain (1 mm or more) after it ended: 3.4 mm on 7 May.
Nong Bua Daeng fire, February 2023
1,150 ha
9 days
FWI 28.4
Min. humidity 45 %
81 km away, in 2023
First rain (1 mm or more) after it ended: none in the following ten days.
Mueang Phetchabun fire, April 2024
1,620 ha
7 days
FWI 25.3
Min. humidity 42 %
16 km away, in 2024
First rain (1 mm or more) after it ended: 6.2 mm on 7 May.
Phu Luang fire, March 2023
3,117 ha
8 days
FWI 25.8
Min. humidity 45 %
70 km away, in 2023
First rain (1 mm or more) after it ended: 3.9 mm on 9 Apr.
Nong Bua Daeng fire, February 2021
1,568 ha
11 days
FWI 27.9
Min. humidity 45 %
45 km away, in 2021
First rain (1 mm or more) after it ended: 5.4 mm on 3 Mar.
What happened to them
- 8 days
- median duration
- 1,453 ha
- median area
- 100 %
- went past 1,000 ha
- 3.4 mm
- rain at the end (median; 18 of 34 had it)
It burned an area similar to its twins (1,489 ha against a median of 1,453 ha) and lasted 9 days, against 8 days.
In 16 of 34, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.4 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
1.1 mmfirst rain
2 Mar10 days after it ended
39km/h · max. gust
It was considered over on 21 Feb, and on 2 Mar 1.1 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 18 of 34, with a median of 3.4 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 6 Feb 2020
After · 28 Feb 2020
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 39Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV
Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Mueang Phetchabun fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 13 February 2020 to 21 February 2020 (9 days). The perimeter dates it from 13 February 2020 to 16 February 2020.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,489 hectares (14.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Lom Sak (1,115 ha, 0.8 %); Mueang Phetchabun (382 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 33.5 °C, humidity dropped to 30 % and gusts hit 39 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.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 34. Their median duration was 8 days and their median area 1,453 ha; 100 % went past 1,000 ha. In 16 of 34, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 3.4 mm.
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: 16 February 2020 → 21 February 2020.
RSS Changes to this page With cross-checks and a citable version
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 13 February 2020 to 16 February 2020. 39 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.