Park Ou fire, 9 March 2020 Pak Xeng, Phonxay, Park Ou
The fire started on 9 March 2020 in Park Ou, Laos, and satellites saw it burning for 31 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 35,409 hectares from heat detections, spread across 4 municipalities.
It is the 3th largest in Luang Prabang since 2016 (of 295 with a page). The largest in Laos in 2020, of 188.
Compare with…
- Burnt area
- 35,409ha
- GWIS perimeter (Copernicus)
- Duration
- 31days
- 9 Mar 2020 – 8 Apr 2020
- Municipalities hit
- 4
- districts
- Started on
- 9 Mar
- 2020
- Heat detections
- 1,509
- in a single hotspot: 493 MW
- Danger at start
- 27
- High · FWI index
- Average daily power
- 1.7GW
- 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 3 days without rain (1 mm or more) when it started. Rain came after the fire: 1.3 mm on 9 Apr.
This area had burned before
59% of the perimeter overlaps earlier fires recorded since 2016: 7,240 ha in 2016, 10,337 ha in 2017, 8,779 ha in 2018, 7,114 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 20,832 ha that had burned before.
- 4,901 ha Park Ou fire, April 2017 8,864 ha in total; the hectares shown are those it shares with this fire
- 3,291 ha Phonxay fire, April 2018 10,652 ha in total; the hectares shown are those it shares with this fire
- 2,876 ha Pak Xeng fire, April 2018 6,404 ha in total; the hectares shown are those it shares with this fire
- 2,246 ha Phonxay fire, April 2017 3,063 ha in total; the hectares shown are those it shares with this fire
- 893 ha Park Ou fire, April 2017 3,801 ha in total; the hectares shown are those it shares with this fire
- 660 ha Phonxay fire, March 2016 4,563 ha in total; the hectares shown are those it shares with this fire
- 150 ha Phonxay fire, April 2017 2,670 ha in total; the hectares shown are those it shares with this fire
- 5 ha Pak Xeng fire, April 2017 2,340 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
-
12,707 ha reached on 15 Mar7.6 %
-
12,285 ha reached on 15 Mar4.7 %
-
Park Ou where it started10,561 ha reached on 9 Mar12 %
-
52 ha reached on 16 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 6.4 hectares of built-up land and about 2,800 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) |
|---|---|---|---|---|---|
| 9 Mar | 35.5 °C | 23 % | 33 km/h | 0.0 mm | High 27 |
| 10 Mar | 36.5 °C | 25 % | 29 km/h | 0.0 mm | High 27 |
| 11 Mar | 34.7 °C | 31 % | 36 km/h | 0.0 mm | High 28 |
| 12 Mar | 35.8 °C | 29 % | 45 km/h | 0.0 mm | High 30 |
| 13 Mar | 37.1 °C | 26 % | 31 km/h | 0.0 mm | High 28 |
| 14 Mar | 36.7 °C | 31 % | 22 km/h | 0.0 mm | High 28 |
| 15 Mar | 31.9 °C | 50 % | 26 km/h | 0.1 mm | Moderate 20 |
| 16 Mar | 33.6 °C | 44 % | 37 km/h | 0.0 mm | Moderate 21 |
| 17 Mar | 36.4 °C | 31 % | 42 km/h | 0.0 mm | High 28 |
| 18 Mar | 36.2 °C | 32 % | 45 km/h | 0.0 mm | High 28 |
| 19 Mar | 34.8 °C | 33 % | 42 km/h | 0.0 mm | High 27 |
| 20 Mar | 32.9 °C | 40 % | 40 km/h | 2.1 mm | Moderate 12 |
| 21 Mar | 35.2 °C | 24 % | 49 km/h | 0.8 mm | High 29 |
| 22 Mar | 34.9 °C | 30 % | 41 km/h | 1.2 mm | High 24 |
| 23 Mar | 31.3 °C | 42 % | 40 km/h | 4.2 mm | Low 6 |
| 24 Mar | 32.4 °C | 42 % | 38 km/h | 3.2 mm | Low 5 |
| 25 Mar | 33.6 °C | 32 % | 43 km/h | 2.1 mm | Moderate 12 |
| 26 Mar | 34.2 °C | 30 % | 46 km/h | 0.0 mm | High 23 |
| 27 Mar | 36.1 °C | 27 % | 42 km/h | 0.0 mm | High 27 |
| 28 Mar | 37.6 °C | 25 % | 34 km/h | 0.0 mm | High 28 |
| 29 Mar | 38.1 °C | 24 % | 45 km/h | 0.0 mm | High 32 |
| 30 Mar | 38.2 °C | 25 % | 40 km/h | 0.0 mm | High 32 |
| 31 Mar | 38.2 °C | 26 % | 36 km/h | 0.0 mm | High 31 |
| 1 Apr | 37.8 °C | 26 % | 40 km/h | 0.0 mm | High 33 |
| 2 Apr | 35.8 °C | 29 % | 44 km/h | 0.0 mm | High 34 |
| 3 Apr | 37.3 °C | 28 % | 42 km/h | 0.0 mm | High 32 |
| 4 Apr | 37.5 °C | 30 % | 40 km/h | 0.5 mm | High 34 |
| 5 Apr | 32.4 °C | 51 % | 40 km/h | 5.8 mm | Very low 4 |
| 6 Apr | 31.9 °C | 51 % | 37 km/h | 7.5 mm | Very low 2 |
| 7 Apr | 31.0 °C | 54 % | 36 km/h | 7.2 mm | Very low 1 |
| 8 Apr | 32.4 °C | 53 % | 35 km/h | 2.5 mm | Very low 1 |
| 9 Apr after | 30.7 °C | 56 % | 33 km/h | 1.3 mm | Very low 2 |
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 · 1,509Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 14,236 haPark Ou26 March 2024 · 21 days · 8 km away
- 15,019 haNgoi1 April 2023 · 23 days · 11 km away
- 56,191 haPark Ou22 March 2026 · 32 days · 14 km away
- 30,865 haPak XengMarch 2023 · 26 days · 19 km away
- 40,796 haNga3 April 2018 · 12 days · 37 km away
- 19,543 haPak Xeng3 April 2023 · 27 days · 37 km away
Frequently asked questions
- How long did the Park Ou fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 9 March 2020 to 8 April 2020 (31 days). The perimeter dates it from 16 March 2020 to 4 April 2020.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 35,409 hectares (354.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 4 municipalities: Pak Xeng (12,707 ha, 7.6 %); Phonxay (12,285 ha, 4.7 %); Park Ou (10,561 ha, 12 %); Ngoi (52 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 38.2 °C, humidity dropped to 23 % and gusts hit 49 km/h. The fire danger index (FWI) reached 34, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Laos (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.
- Last day with fire: 6 April 2020 → 8 April 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; 6 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 16 March 2020 to 4 April 2020. 1,509 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 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.