Skip to content
worldfires
MM · Myanmar · →

Bawlake fire, 6 March 2019 Bawlake

Out · last detection 22 Mar 2019, 07:39 UTC

The fire started on 6 March 2019 in Bawlake, Myanmar, and satellites saw it burning for 18 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,443 hectares from heat detections, spread across a single municipality.

It is the 85th largest in Kayah since 2016 (of 209 with a page). Number 50 in Myanmar in 2019, of 177.

Compare with…
Burnt area
3,443ha
GWIS perimeter (Copernicus)
Duration
18days
6 Mar 2019 – 23 Mar 2019
Municipalities hit
1
municipalities
Started on
6 Mar
2019
Heat detections
130
in a single hotspot: 112 MW
Danger at start
35
High · FWI index
Average daily power
70MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 6 Mar23 Mar
22 Mar 2019

How it evolved, day by day

7 Mar 2019 · 3 MW · 1 9 Mar 2019 · 5 MW · 2 10 Mar 2019 · 23 MW · 2 12 Mar 2019 · 3 MW · 3 13 Mar 2019 · 32 MW · 8 14 Mar 2019 · 47 MW · 14 15 Mar 2019 · 55 MW · 25 16 Mar 2019 · 98 MW · 38 17 Mar 2019 · 248 MW · 25 18 Mar 2019 · 69 MW · 6 21 Mar 2019 · 18 MW · 3 22 Mar 2019 · 239 MW · 3
7 Mar 10 Mar 13 Mar 15 Mar 17 Mar 21 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

39°high
32km/h · peak gust
24%lowest humidity

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

This area had burned before

83% of the perimeter overlaps earlier fires recorded since 2016: 1,706 ha in 2016, 1,535 ha in 2017, 982 ha in 2018. Part of it burned more than once, so the yearly figures add up to more than the 2,869 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 2.2% of the area of London (34 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. Bawlake where it started
    3,461 ha reached on 7 Mar
    1.8 %

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 area0.21 ha
Residents≈ 40

Inside the perimeter there were about 0.21 hectares of built-up land and about 40 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)
13 Mar 38.1 °C 25 % 21 km/h 0.0 mm High 35
14 Mar 38.2 °C 24 % 22 km/h 0.0 mm High 36
15 Mar 37.8 °C 32 % 22 km/h 0.0 mm High 34
16 Mar 38.9 °C 29 % 24 km/h 0.0 mm High 34
17 Mar 39.0 °C 24 % 24 km/h 0.0 mm High 34
18 Mar 39.0 °C 29 % 32 km/h 0.0 mm High 38
19 Mar 38.7 °C 24 % 33 km/h 0.0 mm High 38
20 Mar 38.8 °C 24 % 36 km/h 0.0 mm Very high 39
21 Mar 38.7 °C 21 % 28 km/h 0.0 mm High 38
22 Mar 38.6 °C 26 % 22 km/h 0.0 mm Very high 39
23 Mar 39.0 °C 24 % 26 km/h 0.0 mm High 37
24 Mar after 39.7 °C 23 % 27 km/h 0.0 mm Very high 38
25 Mar after 39.6 °C 26 % 29 km/h 0.0 mm Very high 40
26 Mar after 40.5 °C 25 % 26 km/h 0.0 mm Very high 40
27 Mar after 37.8 °C 34 % 36 km/h 0.0 mm Very high 39
28 Mar after 38.1 °C 26 % 33 km/h 0.0 mm High 38

Before and after, from space

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

Before · 27 Feb 2019
After · 30 Mar 2019

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 · 130Every 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 Myanmar ›

Frequently asked questions

How long did the Bawlake fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 6 March 2019 to 23 March 2019 (18 days). The perimeter dates it from 13 March 2019 to 18 March 2019.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 3,443 hectares (34.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Bawlake (3,461 ha, 1.8 %).
What was the weather like?
During the fire the temperature reached 39.0 °C, humidity dropped to 24 % and gusts hit 32 km/h. The fire danger index (FWI) reached 38, 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

History of this page · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Last day with fire: 18 March 2019 → 23 March 2019.
  2. Start date: 13 March 2019 → 6 March 2019.

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.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 13 March 2019 to 18 March 2019. 130 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 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.