Hot fire, 23 February 2024 ฮอด · Mae Chaem, Hot
The fire started on 23 February 2024 in Hot, Thailand, and satellites saw it burning for 18 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,733 hectares from heat detections, spread across 2 municipalities.
It is the 18th largest in Chiang Mai Province since 2016 (of 399 with a page). Number 11 in Thailand in 2024, of 277.
The power measured by the satellite is low (26.8 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
- 6,733ha
- GWIS perimeter (Copernicus)
- Duration
- 18days
- 23 Feb 2024 – 11 Mar 2024
- Municipalities hit
- 2
- districts
- Started on
- 23 Feb
- 2024
- Heat detections
- 282
- in a single hotspot: 27 MW
- Danger at start
- 25
- High · FWI index
- Average daily power
- 59MW
- 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 18 days without rain (1 mm or more) when it started. Rain came after the fire: 5.2 mm on 20 Mar.
This area had burned before
69% of the perimeter overlaps earlier fires recorded since 2016: 473 ha in 2016, 752 ha in 2017, 100 ha in 2018, 692 ha in 2019, 3,488 ha in 2020, 1,126 ha in 2021, 305 ha in 2022, 307 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 4,633 ha that had burned before.
- 350 ha Mae Chaem fire, March 2020 3,273 ha in total; the hectares shown are those it shares with this fire
- 302 ha Mae Chaem fire, February 2020 1,220 ha in total; the hectares shown are those it shares with this fire
- 134 ha Mae Chaem fire, January 2020 1,052 ha in total; the hectares shown are those it shares with this fire
- 2 ha Mae Chaem fire, April 2016 1,074 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
-
Mae Chaem แม่แจ่ม6,724 ha2.4 %
-
36 ha0.0 %
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.98 hectares of built-up land and about 200 residents (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) |
|---|---|---|---|---|---|
| 16 Feb | 34.9 °C | 31 % | 31 km/h | 0.0 mm | High 25 |
| 17 Feb | 33.1 °C | 38 % | 45 km/h | 0.0 mm | High 28 |
| 18 Feb | 33.3 °C | 27 % | 45 km/h | 0.0 mm | High 30 |
| 19 Feb | 33.2 °C | 32 % | 45 km/h | 0.0 mm | High 30 |
| 20 Feb | 32.5 °C | 27 % | 48 km/h | 0.0 mm | High 31 |
| 21 Feb | 32.4 °C | 30 % | 32 km/h | 0.0 mm | High 28 |
| 22 Feb | 33.8 °C | 25 % | 27 km/h | 0.0 mm | High 28 |
| 23 Feb | 34.2 °C | 27 % | 36 km/h | 0.0 mm | High 31 |
| 24 Feb | 35.5 °C | 26 % | 32 km/h | 0.0 mm | High 30 |
| 25 Feb | 36.7 °C | 24 % | 31 km/h | 0.0 mm | High 32 |
| 26 Feb | 36.1 °C | 32 % | 23 km/h | 0.0 mm | High 28 |
| 27 Feb | 35.0 °C | 40 % | 27 km/h | 0.5 mm | High 26 |
| 28 Feb | 35.4 °C | 36 % | 42 km/h | 0.0 mm | High 32 |
| 29 Feb | 35.8 °C | 25 % | 37 km/h | 0.0 mm | High 34 |
| 1 Mar | 35.4 °C | 30 % | 37 km/h | 0.0 mm | High 34 |
| 2 Mar | 36.2 °C | 26 % | 41 km/h | 0.0 mm | High 36 |
| 3 Mar | 34.3 °C | 37 % | 46 km/h | 0.0 mm | High 34 |
| 4 Mar | 34.9 °C | 28 % | 42 km/h | 0.0 mm | High 34 |
| 5 Mar | 35.8 °C | 29 % | 36 km/h | 0.0 mm | High 32 |
| 6 Mar | 36.2 °C | 31 % | 33 km/h | 0.0 mm | High 31 |
| 7 Mar | 35.6 °C | 34 % | 26 km/h | 0.0 mm | High 29 |
| 8 Mar | 36.4 °C | 34 % | 42 km/h | 0.0 mm | High 36 |
| 9 Mar | 35.8 °C | 27 % | 46 km/h | 0.0 mm | High 37 |
| 10 Mar | 35.6 °C | 34 % | 42 km/h | 0.0 mm | High 36 |
| 11 Mar | 36.2 °C | 27 % | 40 km/h | 0.0 mm | High 36 |
| 12 Mar after | 34.5 °C | 35 % | 50 km/h | 0.0 mm | Very high 38 |
| 13 Mar after | 34.6 °C | 24 % | 43 km/h | 0.0 mm | High 37 |
| 14 Mar after | 34.5 °C | 32 % | 36 km/h | 0.0 mm | High 36 |
| 15 Mar after | 35.5 °C | 33 % | 23 km/h | 0.0 mm | High 32 |
| 16 Mar after | 35.9 °C | 36 % | 32 km/h | 0.0 mm | High 34 |
| 17 Mar after | 34.5 °C | 39 % | 37 km/h | 0.0 mm | High 34 |
| 18 Mar after | 35.4 °C | 41 % | 35 km/h | 0.0 mm | High 32 |
| 19 Mar after | 36.2 °C | 37 % | 24 km/h | 0.1 mm | High 28 |
| 20 Mar after | 31.6 °C | 49 % | 29 km/h | 5.2 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.
The smoke
CAMS · CopernicusOn 14 March 2024 the air beside the fire reached 36 µg/m³ of PM2.5. That day averaged 29: 1.9 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 · 282Every 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 Hot fire last?
- GWIS (Copernicus) dates it between 23 February 2024 and 11 March 2024: 18 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 6,733 hectares (67.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Mae Chaem (6,724 ha, 2.4 %); Hot (36 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 36.7 °C, humidity dropped to 24 % and gusts hit 48 km/h. The fire danger index (FWI) reached 37, 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 from the perimeter: the VIIRS detections inside it did not change them. 282 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.