Kanpetlet fire, 20 March 2020 Kanpetlet, Sidoktaya, Saw
The fire started on 20 March 2020 in Kanpetlet, Myanmar, and satellites saw it burning for 30 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 24,764 hectares from heat detections, spread across 3 municipalities.
It is the 6th largest in Chin since 2016 (of 242 with a page). Number 4 in Myanmar in 2020, of 232.
Compare with…
- Burnt area
- 24,764ha
- GWIS perimeter (Copernicus)
- Duration
- 30days
- 20 Mar 2020 – 18 Apr 2020
- Municipalities hit
- 3
- municipalities
- Started on
- 20 Mar
- 2020
- Heat detections
- 980
- in a single hotspot: 340 MW
- Danger at start
- 31
- High · FWI index
- Average daily power
- 286MW
- 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 more than two months without rain (1 mm or more) when it started. Rain came after the fire: 2.6 mm on 19 Apr.
This area had burned before
79% of the perimeter overlaps earlier fires recorded since 2016: 12,634 ha in 2016, 10,752 ha in 2017, 4,720 ha in 2018, 15,635 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 19,571 ha that had burned before.
- 14,683 ha Sidoktaya fire, March 2019 29,536 ha in total; the hectares shown are those it shares with this fire
- 7,865 ha Sidoktaya fire, March 2017 16,167 ha in total; the hectares shown are those it shares with this fire
- 6,485 ha Kanpetlet fire, April 2016 7,201 ha in total; the hectares shown are those it shares with this fire
- 2,114 ha Kanpetlet fire, March 2018 2,258 ha in total; the hectares shown are those it shares with this fire
- 1,174 ha Kanpetlet fire, April 2016 3,642 ha in total; the hectares shown are those it shares with this fire
- 179 ha Sidoktaya fire, March 2016 2,754 ha in total; the hectares shown are those it shares with this fire
- 65 ha Kanpetlet fire, March 2018 2,138 ha in total; the hectares shown are those it shares with this fire
- 4 ha Sidoktaya fire, March 2016 3,245 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).
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).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Kanpetlet where it started20,361 ha reached on 20 Mar8.1 %
-
4,473 ha reached on 27 Mar1.6 %
-
66 ha reached on 20 Mar0.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 2020Inside the perimeter there were about 0.31 hectares of built-up land and about 600 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) |
|---|---|---|---|---|---|
| 20 Mar | 33.1 °C | 27 % | 44 km/h | 0.7 mm | High 31 |
| 21 Mar | 32.4 °C | 27 % | 34 km/h | 0.0 mm | High 31 |
| 22 Mar | 31.4 °C | 31 % | 37 km/h | 0.0 mm | High 31 |
| 23 Mar | 32.9 °C | 24 % | 43 km/h | 0.0 mm | High 34 |
| 24 Mar | 32.5 °C | 29 % | 33 km/h | 0.0 mm | High 32 |
| 25 Mar | 34.2 °C | 30 % | 32 km/h | 0.0 mm | High 32 |
| 26 Mar | 35.0 °C | 29 % | 34 km/h | 0.0 mm | High 32 |
| 27 Mar | 36.1 °C | 34 % | 31 km/h | 0.0 mm | High 32 |
| 28 Mar | 37.2 °C | 29 % | 36 km/h | 0.0 mm | High 33 |
| 29 Mar | 38.6 °C | 25 % | 37 km/h | 0.0 mm | High 36 |
| 30 Mar | 38.3 °C | 23 % | 34 km/h | 0.0 mm | High 37 |
| 31 Mar | 36.8 °C | 24 % | 32 km/h | 0.0 mm | High 36 |
| 1 Apr | 36.2 °C | 23 % | 36 km/h | 0.0 mm | High 37 |
| 2 Apr | 37.1 °C | 25 % | 31 km/h | 0.0 mm | High 37 |
| 3 Apr | 37.1 °C | 29 % | 30 km/h | 0.0 mm | High 37 |
| 4 Apr | 36.2 °C | 27 % | 40 km/h | 0.0 mm | High 37 |
| 5 Apr | 36.4 °C | 26 % | 39 km/h | 0.0 mm | High 37 |
| 6 Apr | 36.6 °C | 23 % | 38 km/h | 0.0 mm | High 38 |
| 7 Apr | 37.1 °C | 22 % | 28 km/h | 0.0 mm | Very high 38 |
| 8 Apr | 36.1 °C | 26 % | 29 km/h | 0.0 mm | High 38 |
| 9 Apr | 35.0 °C | 28 % | 34 km/h | 0.7 mm | High 31 |
| 10 Apr | 35.2 °C | 31 % | 36 km/h | 0.0 mm | High 31 |
| 11 Apr | 34.9 °C | 34 % | 29 km/h | 1.2 mm | High 23 |
| 12 Apr | 36.5 °C | 28 % | 40 km/h | 0.0 mm | High 32 |
| 13 Apr | 36.5 °C | 27 % | 28 km/h | 0.5 mm | High 32 |
| 14 Apr | 37.3 °C | 30 % | 34 km/h | 0.7 mm | High 30 |
| 15 Apr | 38.7 °C | 26 % | 39 km/h | 0.2 mm | High 37 |
| 16 Apr | 36.8 °C | 23 % | 49 km/h | 0.0 mm | Very high 40 |
| 17 Apr | 34.9 °C | 33 % | 48 km/h | 0.9 mm | High 30 |
| 18 Apr | 37.2 °C | 26 % | 42 km/h | 0.0 mm | High 37 |
| 19 Apr after | 36.7 °C | 30 % | 42 km/h | 2.6 mm | Moderate 19 |
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 · 980Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 19,378 haKanpetlet4 March 2021 · 24 days · 7 km away
- 19,991 haKanpetletMarch 2025 · 30 days · 9 km away
- 29,536 haSidoktaya9 March 2019 · 45 days · 10 km away
- 17,031 haKanpetletMarch 2024 · 23 days · 11 km away
- 17,092 haSaw21 February 2021 · 32 days · 16 km away
- 18,538 haKanpetlet9 March 2020 · 40 days · 20 km away
Frequently asked questions
- How long did the Kanpetlet fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 20 March 2020 to 18 April 2020 (30 days). The perimeter dates it from 27 March 2020 to 18 April 2020.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 24,764 hectares (247.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Kanpetlet (20,361 ha, 8.1 %); Sidoktaya (4,473 ha, 1.6 %); Saw (66 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 38.7 °C, humidity dropped to 22 % and gusts hit 49 km/h. The fire danger index (FWI) reached 40, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Myanmar (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.
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.
- Start date: 27 March 2020 → 20 March 2020.
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; 4 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 27 March 2020 to 18 April 2020. 980 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 ADM3 (Creative Commons Attribution 4.0 (CC BY 4.0)). 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.