Burned area
satellite only1,063ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 29 Mar 2019 – 1 Apr 2019
+− cross-check
No official record is matched to this page to compare it with.
TH · Thailand · –
Ban Luang fire, March 2019 บ้านหลวง · Ban Luang
Out · last detection 1 Apr 2019, 18:41 UTC
The fire started on 29 March 2019 in Ban Luang, Thailand, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,063 hectares from heat detections, spread across a single municipality.
It is the 133th largest in Nan Province since 2016 (of 157 with a page). Number 339 in Thailand in 2019, of 385.
The power measured by the satellite is low (7.6 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches 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 only4days
29 Mar 2019 to 1 Apr 2019: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 1 Apr 2019, 18:41 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 only29 Mar 2019
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 29 Mar 2019
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only31
VIIRS detections at 375 m. Most intense hotspot: 8 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 29 Mar 2019 – 1 Apr 2019
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only33MW
Total radiative power on 30 March 2019; hotspots that day: 12.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 30 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
model34.0FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 36.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 29 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
model38.0°C · 27% RH
High of 38.0 °C and minimum humidity of 27% on 31 March 2019; gusts of 30 km/h on 1 April 2019.
- Source
- weather model at the fire’s grid cell
- Date
- 29 Mar 2019 – 1 Apr 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 GHSLPopulation and built-up area computed
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 1,063 ha
- Dates
- 29 Mar 2019 – 1 Apr 2019
- Name
- Ban Luang
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/ban-luang-2019-03?v=2026-10-24A 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 ban-luang-2019-03.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-25 | 0 | 0 | 36.2 | 22.2 | 38 | 11.9 | 35.6 | 0.2 | 34 | alto | 0 |
| 2019-03-26 | 0 | 0 | 36.2 | 22.9 | 38 | 9.6 | 31.7 | 0.7 | 26.1 | alto | 0 |
| 2019-03-27 | 0 | 0 | 35.2 | 24.2 | 40 | 10.8 | 35.3 | 2 | 15.6 | moderado | 0 |
| 2019-03-28 | 0 | 0 | 36.7 | 22.6 | 28 | 10.3 | 31 | 0 | 29.5 | alto | 0 |
| 2019-03-29 | 1 | 2 | 37.7 | 21.5 | 19 | 6.8 | 22.3 | 0 | 34.2 | alto | 1 |
| 2019-03-30 | 12 | 33 | 37.3 | 19.8 | 25 | 6.4 | 26.3 | 0 | 34.2 | alto | 1 |
| 2019-03-31 | 14 | 31 | 38 | 20.3 | 27 | 8.8 | 28.4 | 0 | 36.7 | alto | 1 |
| 2019-04-01 | 4 | 4 | 36.6 | 21.9 | 31 | 9.7 | 29.9 | 0 | 35.2 | alto | 1 |
| 2019-04-02 | 0 | 0 | 36.3 | 21.9 | 37 | 11 | 30.6 | 0.3 | 33 | alto | 0 |
| 2019-04-03 | 0 | 0 | 36.2 | 23.4 | 30 | 9.1 | 35.6 | 0 | 31.9 | alto | 0 |
| 2019-04-04 | 0 | 0 | 35 | 23.6 | 38 | 9.2 | 29.5 | 0.5 | 30.7 | alto | 0 |
| 2019-04-05 | 0 | 0 | 36.5 | 22.9 | 31 | 9.7 | 32.4 | 0.7 | 29.4 | alto | 0 |
| 2019-04-06 | 0 | 0 | 36.6 | 23.2 | 31 | 10.1 | 35.3 | 0 | 31.3 | alto | 0 |
| 2019-04-07 | 0 | 0 | 37.8 | 23 | 28 | 10.5 | 35.3 | 0 | 34.2 | alto | 0 |
| 2019-04-08 | 0 | 0 | 38.8 | 22.4 | 21 | 11.6 | 31.7 | 0 | 40.6 | muy_alto | 0 |
| 2019-04-09 | 0 | 0 | 39.2 | 22.1 | 24 | 8 | 27 | 0 | 37.6 | alto | 0 |
| 2019-04-10 | 0 | 0 | 39.2 | 23 | 25 | 10.2 | 31.7 | 0 | 40 | muy_alto | 0 |
| 2019-04-11 | 0 | 0 | 39.7 | 21.8 | 22 | 8.8 | 25.6 | 0 | 39 | muy_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,063ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 29 Mar 2019 – 1 Apr 2019
- Municipalities hit
- 1
- districts
- Started on
- 29 Mar
- 2019
- Heat detections
- 31
- in a single hotspot: 8 MW
- Danger at start
- 34
- High · FWI index
- Average daily power
- 18MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
29 Mar1 Apr
1 Apr 2019
How it evolved, day by day
29 Mar
30 Mar
31 Mar
1 Apr
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
38°high
36km/h · peak gust
19%lowest humidity
It had gone 36 days without rain (1 mm or more) when it started.
This area had burned before
24% of the perimeter overlaps earlier fires recorded since 2016: 263 ha in 2016. Part of it burned more than once, so the yearly figures add up to more than the 250 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,068 ha reached on 29 Mar2.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 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)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 25 Mar | 36.2 °C | 38 % | 36 km/h | 0.2 mm | High 34 |
| 26 Mar | 36.2 °C | 38 % | 32 km/h | 0.7 mm | High 26 |
| 27 Mar | 35.2 °C | 40 % | 35 km/h | 2.0 mm | Moderate 16 |
| 28 Mar | 36.7 °C | 28 % | 31 km/h | 0.0 mm | High 30 |
| 29 Mar | 37.7 °C | 19 % | 22 km/h | 0.0 mm | High 34 |
| 30 Mar | 37.3 °C | 25 % | 26 km/h | 0.0 mm | High 34 |
| 31 Mar | 38.0 °C | 27 % | 28 km/h | 0.0 mm | High 37 |
| 1 Apr | 36.6 °C | 31 % | 30 km/h | 0.0 mm | High 35 |
| 2 Apr after | 36.3 °C | 37 % | 31 km/h | 0.3 mm | High 33 |
| 3 Apr after | 36.2 °C | 30 % | 36 km/h | 0.0 mm | High 32 |
| 4 Apr after | 35.0 °C | 38 % | 30 km/h | 0.5 mm | High 31 |
| 5 Apr after | 36.5 °C | 31 % | 32 km/h | 0.7 mm | High 29 |
| 6 Apr after | 36.6 °C | 31 % | 35 km/h | 0.0 mm | High 31 |
| 7 Apr after | 37.8 °C | 28 % | 35 km/h | 0.0 mm | High 34 |
| 8 Apr after | 38.8 °C | 21 % | 32 km/h | 0.0 mm | Very high 41 |
| 9 Apr after | 39.2 °C | 24 % | 27 km/h | 0.0 mm | High 38 |
| 10 Apr after | 39.2 °C | 25 % | 32 km/h | 0.0 mm | Very high 40 |
| 11 Apr after | 39.7 °C | 22 % | 26 km/h | 0.0 mm | Very high 39 |
Its twins: fires that started in the same weather
It started with an FWI of 34.0, a minimum humidity of 19% and 36 days without rain. Fires in the area that started in weather like this since 2016: 34.
FWI at the start
34.0
Minimum humidity
19 %
Days without rain
36
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Ban Luang fire, March 2019
1,063 ha
4 days
FWI 34.0
Min. humidity 19 %
Tha Wang Pha fire, March 2024
1,286 ha
12 days
FWI 34.0
Min. humidity 24 %
47 km away, in 2024
First rain (1 mm or more) after it ended: 5.8 mm on 19 Mar.
Song fire, March 2024
1,662 ha
12 days
FWI 34.5
Min. humidity 24 %
35 km away, in 2024
First rain (1 mm or more) after it ended: 15.0 mm on 19 Mar.
Song fire, March 2024
1,122 ha
5 days
FWI 36.1
Min. humidity 23 %
34 km away, in 2024
First rain (1 mm or more) after it ended: 1.5 mm on 12 Mar.
Chun fire, February 2023
1,869 ha
7 days
FWI 35.0
Min. humidity 21 %
69 km away, in 2023
First rain (1 mm or more) after it ended: none in the following ten days.
Mueang Chiang Rai fire, April 2016
3,047 ha
19 days
FWI 34.6
Min. humidity 23 %
150 km away, in 2016
First rain (1 mm or more) after it ended: 1.4 mm on 29 Apr.
What happened to them
- 12 days
- median duration
- 1,938 ha
- median area
- 100 %
- went past 1,000 ha
- 2.0 mm
- rain at the end (median; 22 of 34 had it)
It stayed below its twins: 1,063 ha against a median of 1,938 ha. It lasted 4 days, against 12 days.
In 12 of 34, 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
36km/h · max. gust
It was considered over on 1 Apr, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 22 of 34, 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 · 22 Mar 2019
After · 8 Apr 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 · 31Every 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
- 19,938 haMueang Nan เมืองน่านMarch 2026 · 36 days · 19 km away
- 6,784 haMueang Nan เมืองน่าน23 March 2023 · 22 days · 23 km away
- 14,483 haPong ปง27 March 2026 · 26 days · 27 km away
- 4,696 haPong ปง22 March 2026 · 20 days · 34 km away
- 8,861 haSong สอง18 March 2026 · 33 days · 35 km away
- 5,304 haDok Khamtai ดอกคำใต้March 2023 · 22 days · 38 km away
Frequently asked questions
- How long did the Ban Luang fire last?
- GWIS (Copernicus) dates it between 29 March 2019 and 1 April 2019: 4 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,063 hectares (10.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Ban Luang (1,068 ha, 2.8 %).
- What was the weather like?
- During the fire the temperature reached 38.0 °C, humidity dropped to 19 % and gusts hit 36 km/h. The fire danger index (FWI) reached 37, 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: 34. Their median duration was 12 days and their median area 1,938 ha; 100 % went past 1,000 ha. In 12 of 34, 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 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
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. 31 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.