Skip to content
worldfires
TH · Thailand · →

Mae Chaem fire, 23 March 2020 แม่แจ่ม · Mae Chaem

Out · last detection 27 Mar 2020, 19:13 UTC

The fire started on 23 March 2020 in Mae Chaem, Thailand, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,273 hectares from heat detections, spread across a single municipality.

It is the 62th largest in Chiang Mai Province since 2016 (of 399 with a page). Number 73 in Thailand in 2020, of 457.

The power measured by the satellite is low (16.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…

Suggestions: Hot · 2024Mae Chaem · 2026

Burnt area
3,273ha
GWIS perimeter (Copernicus)
Duration
5days
23 Mar 2020 – 27 Mar 2020
Municipalities hit
1
districts
Started on
23 Mar
2020
Heat detections
94
in a single hotspot: 17 MW
Danger at start
37
High · FWI index
Average daily power
65MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 23 Mar27 Mar
27 Mar 2020

How it evolved, day by day

23 Mar 2020 · 40 MW · 20 24 Mar 2020 · 32 MW · 17 25 Mar 2020 · 77 MW · 14 26 Mar 2020 · 77 MW · 15 27 Mar 2020 · 99 MW · 28
23 Mar 24 Mar 25 Mar 26 Mar 27 Mar

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
52km/h · peak gust
27%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

17% of the perimeter overlaps earlier fires recorded since 2016: 221 ha in 2017, 136 ha in 2018, 361 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 546 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 2.1% of the area of London (33 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.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. Mae Chaem แม่แจ่ม where it started
    3,287 ha reached on 23 Mar
    1.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 2020
Built-up area< 0.1 ha
Residents< 20

Inside 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)
17 Mar 34.0 °C 28 % 40 km/h 0.0 mm High 37
18 Mar 33.7 °C 32 % 43 km/h 0.0 mm High 37
19 Mar 33.3 °C 31 % 34 km/h 0.0 mm High 34
20 Mar 32.9 °C 29 % 44 km/h 0.0 mm Very high 38
21 Mar 31.8 °C 34 % 49 km/h 0.3 mm High 36
22 Mar 32.0 °C 31 % 45 km/h 0.0 mm High 36
23 Mar 33.0 °C 28 % 45 km/h 0.0 mm High 36
24 Mar 32.5 °C 29 % 52 km/h 0.0 mm Very high 38
25 Mar 32.8 °C 27 % 52 km/h 0.0 mm Very high 39
26 Mar 32.7 °C 29 % 49 km/h 0.0 mm Very high 38
27 Mar 33.6 °C 29 % 40 km/h 0.0 mm High 36
28 Mar after 34.7 °C 33 % 34 km/h 0.0 mm High 35
29 Mar after 34.5 °C 23 % 39 km/h 0.0 mm Very high 38
30 Mar after 35.0 °C 33 % 38 km/h 0.0 mm High 37
31 Mar after 36.0 °C 29 % 37 km/h 0.0 mm High 37
1 Apr after 35.6 °C 25 % 43 km/h 0.0 mm Very high 39
2 Apr after 34.9 °C 26 % 49 km/h 0.0 mm Very high 41
3 Apr after 35.7 °C 21 % 44 km/h 0.0 mm Very high 42
4 Apr after 35.8 °C 23 % 38 km/h 0.0 mm Very high 40
5 Apr after 35.7 °C 23 % 43 km/h 0.0 mm Very high 43
6 Apr after 33.4 °C 39 % 45 km/h 0.0 mm High 36

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 16 Mar 2020
After · 3 Apr 2020

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 · 94Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Thailand ›

Frequently asked questions

How long did the Mae Chaem fire last?
GWIS (Copernicus) dates it between 23 March 2020 and 27 March 2020: 5 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 3,273 hectares (32.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Mae Chaem (3,287 ha, 1.2 %).
What was the weather like?
During the fire the temperature reached 34.0 °C, humidity dropped to 27 % and gusts hit 52 km/h. The fire danger index (FWI) reached 39, class Very 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.

RSS Changes to this page

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 199 · 191.

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. 94 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.

How we build fire pages: methodology ›

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.