Mae Wang fire, February 2024 แม่วาง · Mae Wang
The fire started on 28 February 2024 in Mae Wang, Thailand, and satellites saw it burning for 10 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,162 hectares from heat detections, spread across a single municipality.
It is the 42th largest in Chiang Mai Province since 2016 (of 399 with a page). Number 31 in Thailand in 2024, of 277.
The power measured by the satellite is low (21.5 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
- 4,162ha
- GWIS perimeter (Copernicus)
- Duration
- 10days
- 28 Feb 2024 – 8 Mar 2024
- Municipalities hit
- 1
- districts
- Started on
- 28 Feb
- 2024
- Heat detections
- 137
- in a single hotspot: 22 MW
- Danger at start
- 22
- High · FWI index
- Average daily power
- 32MW
- 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 9 days without rain (1 mm or more) when it started.
This area had burned before
88% of the perimeter overlaps earlier fires recorded since 2016: 672 ha in 2016, 2,179 ha in 2017, 1,605 ha in 2018, 1,302 ha in 2019, 1,691 ha in 2020, 1,577 ha in 2021, 311 ha in 2022, 1,574 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 3,643 ha that had burned before.
- 1,514 ha Mae Wang fire, March 2017 2,512 ha in total; the hectares shown are those it shares with this fire
- 910 ha Mae Wang fire, February 2021 1,791 ha in total; the hectares shown are those it shares with this fire
- 724 ha Mae Wang fire, March 2018 1,273 ha in total; the hectares shown are those it shares with this fire
- 518 ha Mae Wang fire, March 2023 3,576 ha in total; the hectares shown are those it shares with this fire
- 23 ha Mae Wang fire, March 2017 1,185 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
-
4,184 ha6.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 2025Inside the perimeter there were about 1.3 hectares of built-up land and about 100 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) |
|---|---|---|---|---|---|
| 21 Feb | 30.3 °C | 33 % | 26 km/h | 0.0 mm | High 22 |
| 22 Feb | 30.4 °C | 34 % | 28 km/h | 0.0 mm | High 22 |
| 23 Feb | 32.0 °C | 29 % | 27 km/h | 0.0 mm | High 23 |
| 24 Feb | 32.3 °C | 30 % | 27 km/h | 0.0 mm | High 24 |
| 25 Feb | 33.6 °C | 27 % | 27 km/h | 0.0 mm | High 24 |
| 26 Feb | 32.5 °C | 44 % | 27 km/h | 0.0 mm | High 21 |
| 27 Feb | 31.4 °C | 53 % | 32 km/h | 0.0 mm | Moderate 19 |
| 28 Feb | 34.2 °C | 35 % | 27 km/h | 0.0 mm | Moderate 21 |
| 29 Feb | 33.5 °C | 31 % | 28 km/h | 0.0 mm | High 23 |
| 1 Mar | 33.3 °C | 33 % | 26 km/h | 0.0 mm | High 23 |
| 2 Mar | 34.0 °C | 31 % | 31 km/h | 0.0 mm | High 25 |
| 3 Mar | 33.8 °C | 34 % | 29 km/h | 0.0 mm | High 26 |
| 4 Mar | 34.2 °C | 31 % | 26 km/h | 0.0 mm | High 25 |
| 5 Mar | 34.0 °C | 31 % | 22 km/h | 0.0 mm | High 26 |
| 6 Mar | 33.7 °C | 32 % | 30 km/h | 0.0 mm | High 27 |
| 7 Mar | 32.4 °C | 36 % | 31 km/h | 0.0 mm | High 28 |
| 8 Mar | 34.2 °C | 38 % | 33 km/h | 0.0 mm | High 28 |
| 9 Mar after | 35.4 °C | 26 % | 30 km/h | 0.0 mm | High 30 |
| 10 Mar after | 33.7 °C | 37 % | 30 km/h | 0.0 mm | High 29 |
| 11 Mar after | 33.3 °C | 32 % | 32 km/h | 0.0 mm | High 29 |
| 12 Mar after | 34.5 °C | 29 % | 34 km/h | 0.0 mm | High 32 |
| 13 Mar after | 34.5 °C | 25 % | 28 km/h | 0.0 mm | High 31 |
| 14 Mar after | 32.5 °C | 32 % | 31 km/h | 0.0 mm | High 31 |
| 15 Mar after | 32.5 °C | 32 % | 32 km/h | 0.0 mm | High 32 |
| 16 Mar after | 33.1 °C | 36 % | 36 km/h | 0.0 mm | High 32 |
| 17 Mar after | 32.6 °C | 39 % | 33 km/h | 0.0 mm | High 29 |
| 18 Mar after | 34.2 °C | 37 % | 29 km/h | 0.0 mm | High 28 |
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 7 March 2024 the air beside the fire reached 58 µg/m³ of PM2.5. That day averaged 41: 2.7 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 · 137Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 9,276 haSamoeng สะเมิง22 March 2020 · 14 days · 20 km away
- 48,637 haSamoeng สะเมิง21 March 2026 · 31 days · 22 km away
- 12,979 haHang Dong หางดงMarch 2016 · 17 days · 30 km away
- 9,213 haSamoeng สะเมิง20 March 2020 · 20 days · 30 km away
- 8,068 haMae Chaem แม่แจ่ม27 March 2020 · 13 days · 36 km away
- 7,439 haMae Chaem แม่แจ่ม23 March 2026 · 20 days · 38 km away
Frequently asked questions
- How long did the Mae Wang fire last?
- GWIS (Copernicus) dates it between 28 February 2024 and 8 March 2024: 10 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 4,162 hectares (41.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mae Wang (4,184 ha, 6.2 %).
- What was the weather like?
- During the fire the temperature reached 34.2 °C, humidity dropped to 27 % and gusts hit 33 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 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. 137 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.