Tilin fire, 23 February 2017 Gangaw, Matupi, Tilin
The fire started on 23 February 2017 in Tilin, Myanmar, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,544 hectares from heat detections, spread across 3 municipalities.
It is the 75th largest in Magway since 2016 (of 190 with a page). Number 44 in Myanmar in 2017, of 145.
The power measured by the satellite is low (28.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: Gangaw · 2016Gangaw · 2016Hakha · 2026Gangaw · 2023
- Burnt area
- 3,544ha
- GWIS perimeter (Copernicus)
- Duration
- 5days
- 23 Feb 2017 – 27 Feb 2017
- Municipalities hit
- 3
- municipalities
- Started on
- 23 Feb
- 2017
- Heat detections
- 140
- in a single hotspot: 29 MW
- Danger at start
- 21
- Moderate · FWI index
- Average daily power
- 77MW
- 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 48 days without rain (1 mm or more) when it started.
This area had burned before
56% of the perimeter overlaps earlier fires recorded since 2016: 2,094 ha in 2016.
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
-
1,462 ha0.6 %
-
1,374 ha0.2 %
-
Tilin where it started726 ha0.5 %
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 2015Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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) |
|---|---|---|---|---|---|
| 23 Feb | 34.8 °C | 33 % | 22 km/h | 0.0 mm | Moderate 21 |
| 24 Feb | 32.5 °C | 26 % | 22 km/h | 0.0 mm | High 23 |
| 25 Feb | 32.0 °C | 30 % | 23 km/h | 0.0 mm | High 24 |
| 26 Feb | 30.6 °C | 22 % | 26 km/h | 0.0 mm | High 25 |
| 27 Feb | 31.7 °C | 29 % | 24 km/h | 0.0 mm | High 25 |
| 28 Feb after | 30.8 °C | 39 % | 29 km/h | 0.0 mm | High 22 |
| 1 Mar after | 31.4 °C | 41 % | 29 km/h | 0.0 mm | High 22 |
| 2 Mar after | 32.6 °C | 35 % | 26 km/h | 0.0 mm | Moderate 21 |
| 3 Mar after | 34.8 °C | 26 % | 24 km/h | 0.0 mm | High 26 |
| 4 Mar after | 34.5 °C | 28 % | 23 km/h | 0.0 mm | High 27 |
| 5 Mar after | 33.0 °C | 17 % | 23 km/h | 0.0 mm | High 31 |
| 6 Mar after | 32.5 °C | 28 % | 23 km/h | 0.0 mm | High 30 |
| 7 Mar after | 32.2 °C | 29 % | 24 km/h | 0.5 mm | High 29 |
| 8 Mar after | 28.9 °C | 48 % | 25 km/h | 0.0 mm | Moderate 20 |
| 9 Mar after | 30.1 °C | 47 % | 26 km/h | 0.3 mm | Moderate 20 |
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 · 140Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 9,334 haHakha5 February 2026 · 20 days · 10 km away
- 13,643 haGangawJanuary 2023 · 15 days · 11 km away
- 13,183 haTilinFebruary 2024 · 16 days · 13 km away
- 11,583 haTilinFebruary 2019 · 11 days · 13 km away
- 12,588 haHakha22 February 2021 · 12 days · 21 km away
- 11,026 haHakha21 February 2026 · 11 days · 29 km away
Frequently asked questions
- How long did the Tilin fire last?
- GWIS (Copernicus) dates it between 23 February 2017 and 27 February 2017: 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,544 hectares (35.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Gangaw (1,462 ha, 0.6 %); Matupi (1,374 ha, 0.2 %); Tilin (726 ha, 0.5 %).
- What was the weather like?
- During the fire the temperature reached 34.8 °C, humidity dropped to 22 % and gusts hit 26 km/h. The fire danger index (FWI) reached 25, 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 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. 140 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 2015, 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.