Burned area
satellite only1,860ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 5 Mar 2019 – 11 Mar 2019
+− cross-check
No official record is matched to this page to compare it with.
TH · Thailand · –
Nam Yuen fire, 5 March 2019 น้ำยืน · Nam Yuen
Out · last detection 11 Mar 2019, 18:36 UTC
The fire started on 5 March 2019 in Nam Yuen, Thailand, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,860 hectares from heat detections, spread across a single municipality.
Number 123 in Thailand in 2019, of 385.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-27matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only7days
5 Mar 2019 to 11 Mar 2019: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 11 Mar 2019, 18:36 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only5 Mar 2019
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 5 Mar 2019
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
The worst day
satellite only81MW
Total radiative power on 7 March 2019; hotspots that day: 20.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 7 Mar 2019
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model22.2FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 60.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 5 Mar 2019, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model33.3°C · 36% RH
High of 33.3 °C and minimum humidity of 36% on 7 March 2019; gusts of 31 km/h on 9 March 2019.
- Source
- weather model at the fire’s grid cell
- Date
- 5 Mar 2019 – 11 Mar 2019
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
logStart date: 27 February 2019 → 5 March 2019.
-
logStart date: 5 March 2019 → 27 February 2019.
-
· reconstructed GHSLPopulation and built-up area computed
Area logged each night
Move the slider to see which area the page published each day.
Versioned permanent link
https://worldfires.org/en/fire/nam-yuen-2019-03-2?v=2026-10-27A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire nam-yuen-2019-03-2.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2019-03-05 | 6 | 12 | 31.1 | 20.4 | 50 | 8.2 | 24.5 | 0 | 22.2 | alto | 1 |
| 2019-03-06 | 18 | 35 | 31.9 | 19.8 | 44 | 9 | 25.9 | 0 | 22.9 | alto | 1 |
| 2019-03-07 | 20 | 81 | 33.3 | 20.2 | 36 | 8 | 19.8 | 0 | 24.7 | alto | 1 |
| 2019-03-08 | 2 | 4 | 31.8 | 20.8 | 42 | 9.8 | 27.7 | 0 | 26.1 | alto | 1 |
| 2019-03-09 | 0 | 0 | 32.2 | 21.3 | 44 | 11.2 | 31.3 | 0 | 27.3 | alto | 1 |
| 2019-03-10 | 4 | 19 | 30.9 | 21.1 | 47 | 9.4 | 27 | 0 | 24.7 | alto | 1 |
| 2019-03-11 | 12 | 19 | 33 | 20.7 | 42 | 7.2 | 19.1 | 0 | 23.6 | alto | 1 |
| 2019-03-12 | 0 | 0 | 32.6 | 20.2 | 39 | 8.7 | 23 | 0 | 24.7 | alto | 0 |
| 2019-03-13 | 0 | 0 | 31.3 | 19.8 | 45 | 9.2 | 27 | 0 | 25.2 | alto | 0 |
| 2019-03-14 | 0 | 0 | 31 | 21.2 | 57 | 8 | 26.6 | 0.3 | 20.6 | moderado | 0 |
| 2019-03-15 | 0 | 0 | 31.4 | 22.3 | 49 | 7.8 | 21.6 | 0.2 | 20.6 | moderado | 0 |
| 2019-03-16 | 0 | 0 | 32.4 | 21.9 | 45 | 13.5 | 31 | 0.1 | 24.9 | alto | 0 |
| 2019-03-17 | 0 | 0 | 33 | 21.9 | 42 | 11.5 | 31 | 0 | 25.2 | alto | 0 |
| 2019-03-18 | 0 | 0 | 33.4 | 22.3 | 37 | 12.5 | 33.1 | 0 | 28.4 | alto | 0 |
| 2019-03-19 | 0 | 0 | 32.7 | 21.9 | 39 | 12 | 30.6 | 0 | 28.2 | alto | 0 |
| 2019-03-20 | 0 | 0 | 31.6 | 21 | 49 | 11 | 27.7 | 0 | 25.9 | alto | 0 |
| 2019-03-21 | 0 | 0 | 33 | 21.1 | 45 | 7.8 | 23.4 | 0.2 | 24 | alto | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 1,860ha
- GWIS perimeter (Copernicus)
- Duration
- 7days
- 5 Mar 2019 – 11 Mar 2019
- Municipalities hit
- 1
- districts
- Started on
- 5 Mar
- 2019
- Heat detections
- 62
- in a single hotspot: 0 MW
- Danger at start
- 22
- High · FWI index
- Average daily power
- 28MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
5 Mar11 Mar
11 Mar 2019
How it evolved, day by day
5 Mar
7 Mar
10 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
33°high
31km/h · peak gust
36%lowest humidity
It had gone more than two months without rain (1 mm or more) when it started.
This area had burned before
45% of the perimeter overlaps earlier fires recorded since 2016: 945 ha in 2016. Part of it burned more than once, so the yearly figures add up to more than the 846 ha that had burned before.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Bangkok boundary: geoBoundaries · OpenStreetMap, Wambacher · © OpenStreetMap contributors (ODbL 1.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).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
1,870 ha1.7 %
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 2020Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (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)
Started with 60 days without rain: 15 % of the area in Thailand
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 5 Mar | 31.1 °C | 50 % | 24 km/h | 0.0 mm | High 22 |
| 6 Mar | 31.9 °C | 44 % | 26 km/h | 0.0 mm | High 23 |
| 7 Mar | 33.3 °C | 36 % | 20 km/h | 0.0 mm | High 25 |
| 8 Mar | 31.8 °C | 42 % | 28 km/h | 0.0 mm | High 26 |
| 9 Mar | 32.2 °C | 44 % | 31 km/h | 0.0 mm | High 27 |
| 10 Mar | 30.9 °C | 47 % | 27 km/h | 0.0 mm | High 25 |
| 11 Mar | 33.0 °C | 42 % | 19 km/h | 0.0 mm | High 24 |
| 12 Mar after | 32.6 °C | 39 % | 23 km/h | 0.0 mm | High 25 |
| 13 Mar after | 31.3 °C | 45 % | 27 km/h | 0.0 mm | High 25 |
| 14 Mar after | 31.0 °C | 57 % | 27 km/h | 0.3 mm | Moderate 21 |
| 15 Mar after | 31.4 °C | 49 % | 22 km/h | 0.2 mm | Moderate 21 |
| 16 Mar after | 32.4 °C | 45 % | 31 km/h | 0.1 mm | High 25 |
| 17 Mar after | 33.0 °C | 42 % | 31 km/h | 0.0 mm | High 25 |
| 18 Mar after | 33.4 °C | 37 % | 33 km/h | 0.0 mm | High 28 |
| 19 Mar after | 32.7 °C | 39 % | 31 km/h | 0.0 mm | High 28 |
| 20 Mar after | 31.6 °C | 49 % | 28 km/h | 0.0 mm | High 26 |
| 21 Mar after | 33.0 °C | 45 % | 23 km/h | 0.2 mm | High 24 |
Its twins: fires that started in the same weather
It started with an FWI of 22.2, a minimum humidity of 50% and more than two months without rain. Fires in the area that started in weather like this since 2016: 24.
FWI at the start
22.2
Minimum humidity
50 %
Days without rain
60+
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Nam Yuen fire, 5 March 2019
1,860 ha
7 days
FWI 22.2
Min. humidity 50 %
Chey Saen fire, January 2020
2,324 ha
17 days
FWI 22.1
Min. humidity 49 %
86 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Thala Barivat fire, January 2020
4,915 ha
21 days
FWI 23.9
Min. humidity 50 %
94 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Choam Ksant fire, January 2020
2,254 ha
11 days
FWI 20.4
Min. humidity 51 %
17 km away, in 2020
First rain (1 mm or more) after it ended: none in the following ten days.
Thala Barivat fire, February 2024
5,228 ha
21 days
FWI 24.4
Min. humidity 50 %
83 km away, in 2024
First rain (1 mm or more) after it ended: none in the following ten days.
Trapeang Prasat fire, April 2016
7,677 ha
25 days
FWI 20.5
Min. humidity 49 %
107 km away, in 2016
First rain (1 mm or more) after it ended: 1.8 mm on 28 Apr.
What happened to them
- 21 days
- median duration
- 2,540 ha
- median area
- 100 %
- went past 1,000 ha
- 2.0 mm
- rain at the end (median; 3 of 24 had it)
It burned an area similar to its twins (1,860 ha against a median of 2,540 ha) and lasted 7 days, against 21 days.
In 21 of 24, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.0 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
—first rain
—no rain in ten days
31km/h · max. gust
It was considered over on 11 Mar, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 3 of 24, with a median of 2.0 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 26 Feb 2019
After · 18 Mar 2019
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 0Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Nam Yuen fire last?
- GWIS (Copernicus) dates it between 5 March 2019 and 11 March 2019: 7 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 1,860 hectares (18.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Nam Yuen (1,870 ha, 1.7 %).
- What was the weather like?
- During the fire the temperature reached 33.3 °C, humidity dropped to 36 % and gusts hit 31 km/h. The fire danger index (FWI) reached 27, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Thailand (geoBoundaries). It is not an official report.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 24. Their median duration was 21 days and their median area 2,540 ha; 100 % went past 1,000 ha. In 21 of 24, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.0 mm.
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.
Emergency number: 199 · 191 · Emergency number and official warnings
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.
- Start date: 27 February 2019 → 5 March 2019.
- Start date: 5 March 2019 → 27 February 2019.
RSS Changes to this page With cross-checks and a citable version
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. No 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.