Mongton fire, 20 March 2026 Mongton
The fire started on 20 March 2026 in Mongton, Myanmar, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 8,164 hectares from heat detections, spread across a single municipality.
It is the 62th largest in Shan since 2016 (of 806 with a page). Number 67 in Myanmar in 2026, of 480.
Compare with…
- Burnt area
- 8,164ha
- GWIS perimeter (Copernicus)
- Duration
- 12days
- 20 Mar 2026 – 31 Mar 2026
- Municipalities hit
- 1
- municipalities
- Started on
- 20 Mar
- 2026
- Heat detections
- 193
- in a single hotspot: 123 MW
- Danger at start
- 14
- Moderate · FWI index
- Average daily power
- 231MW
- 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 5 days without rain (1 mm or more) when it started.
This area had burned before
25% of the perimeter overlaps earlier fires recorded since 2016: 220 ha in 2017, 413 ha in 2018, 956 ha in 2019, 1,330 ha in 2020, 43 ha in 2022, 1,230 ha in 2024, 31 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 2,031 ha that had burned before.
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
-
Mongton where it started8,199 ha1.6 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
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 | 31.7 °C | 34 % | 21 km/h | 0.0 mm | Moderate 14 |
| 21 Mar | 33.0 °C | 39 % | 33 km/h | 0.4 mm | Moderate 16 |
| 22 Mar | 32.8 °C | 34 % | 48 km/h | 0.6 mm | Moderate 17 |
| 23 Mar | 33.6 °C | 28 % | 39 km/h | 0.0 mm | Moderate 19 |
| 24 Mar | 34.1 °C | 27 % | 31 km/h | 0.0 mm | Moderate 19 |
| 25 Mar | 34.3 °C | 26 % | 34 km/h | 0.0 mm | Moderate 21 |
| 26 Mar | 34.5 °C | 29 % | 32 km/h | 0.0 mm | High 21 |
| 27 Mar | 34.9 °C | 29 % | 39 km/h | 0.0 mm | High 23 |
| 28 Mar | 36.0 °C | 22 % | 46 km/h | 0.0 mm | High 28 |
| 29 Mar | 34.8 °C | 24 % | 53 km/h | 0.0 mm | High 30 |
| 30 Mar | 35.2 °C | 27 % | 43 km/h | 0.0 mm | High 28 |
| 31 Mar | 36.0 °C | 27 % | 37 km/h | 0.0 mm | High 28 |
| 1 Apr after | 35.9 °C | 31 % | 33 km/h | 0.0 mm | High 27 |
| 2 Apr after | 36.1 °C | 28 % | 41 km/h | 0.0 mm | High 30 |
| 3 Apr after | 37.3 °C | 25 % | 37 km/h | 0.0 mm | High 30 |
| 4 Apr after | 36.2 °C | 30 % | 36 km/h | 0.0 mm | High 30 |
| 5 Apr after | 36.4 °C | 33 % | 37 km/h | 0.2 mm | High 30 |
| 6 Apr after | 34.8 °C | 37 % | 28 km/h | 0.1 mm | High 26 |
| 7 Apr after | 34.4 °C | 40 % | 37 km/h | 0.6 mm | High 23 |
| 8 Apr after | 35.6 °C | 34 % | 38 km/h | 0.0 mm | High 26 |
| 9 Apr after | 34.0 °C | 34 % | 40 km/h | 0.0 mm | High 27 |
| 10 Apr after | 33.8 °C | 33 % | 52 km/h | 0.0 mm | High 30 |
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 27 March 2026 the air beside the fire reached 98 µg/m³ of PM2.5. That day averaged 74: 4.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 · 193Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 8,518 haMongton22 March 2026 · 13 days · 17 km away
- 20,047 haMongton22 March 2026 · 23 days · 23 km away
- 16,091 haMongton20 March 2026 · 16 days · 33 km away
- 20,728 haMongpanMarch 2019 · 18 days · 34 km away
- 28,680 haMongton21 March 2026 · 17 days · 38 km away
- 8,206 haMongton12 March 2020 · 15 days · 40 km away
Frequently asked questions
- How long did the Mongton fire last?
- GWIS (Copernicus) dates it between 20 March 2026 and 31 March 2026: 12 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 8,164 hectares (81.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mongton (8,199 ha, 1.6 %).
- What was the weather like?
- During the fire the temperature reached 36.0 °C, humidity dropped to 22 % and gusts hit 53 km/h. The fire danger index (FWI) reached 30, class 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
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. 193 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.
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.