Skip to content
worldfires
TH · Thailand · →

Dan Sai fire, 9 February 2020 ด่านซ้าย · Dan Sai

Out · last detection 14 Feb 2020, 06:29 UTC

The fire started on 9 February 2020 in Dan Sai, Thailand, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,577 hectares from heat detections, spread across a single municipality.

It is the 57th largest in Loei Province since 2016 (of 113 with a page). Number 224 in Thailand in 2020, of 457.

The power measured by the satellite is low (29.0 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…
Burnt area
1,577ha
GWIS perimeter (Copernicus)
Duration
5days
9 Feb 2020 – 13 Feb 2020
Municipalities hit
1
districts
Started on
9 Feb
2020
Heat detections
57
in a single hotspot: 29 MW
Danger at start
23
High · FWI index
Average daily power
84MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 9 Feb13 Feb
14 Feb 2020

How it evolved, day by day

9 Feb 2020 · 53 MW · 5 10 Feb 2020 · 43 MW · 6 11 Feb 2020 · 140 MW · 15 13 Feb 2020 · 168 MW · 16 14 Feb 2020 · 15 MW · 2
9 Feb 10 Feb 11 Feb 13 Feb 14 Feb

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

32°high
37km/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

99% of the perimeter overlaps earlier fires recorded since 2016: 1,262 ha in 2016, 1,009 ha in 2017, 1,370 ha in 2018, 1,438 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 1,560 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 1% of the area of London (16 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. Dan Sai ด่านซ้าย where it started
    1,585 ha
    1.2 %

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 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)
9 Feb 29.6 °C 43 % 37 km/h 0.0 mm High 23
10 Feb 29.4 °C 42 % 23 km/h 0.0 mm Moderate 20
11 Feb 32.5 °C 36 % 20 km/h 0.0 mm High 22
12 Feb 31.4 °C 49 % 37 km/h 0.0 mm High 25
13 Feb 32.3 °C 40 % 37 km/h 0.0 mm High 25
14 Feb after 31.2 °C 42 % 46 km/h 0.0 mm High 28
15 Feb after 32.4 °C 29 % 32 km/h 0.0 mm High 28
16 Feb after 33.9 °C 27 % 23 km/h 0.0 mm High 29
17 Feb after 29.8 °C 47 % 31 km/h 0.0 mm High 24
18 Feb after 27.7 °C 47 % 29 km/h 0.0 mm High 22
19 Feb after 30.0 °C 45 % 22 km/h 0.0 mm High 21
20 Feb after 30.2 °C 42 % 28 km/h 0.0 mm High 23
21 Feb after 29.5 °C 42 % 39 km/h 0.0 mm High 26
22 Feb after 29.2 °C 42 % 41 km/h 0.0 mm High 27
23 Feb after 29.9 °C 40 % 27 km/h 0.0 mm High 23

Before and after, from space

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

Before · 2 Feb 2020
After · 20 Feb 2020

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 · 57Every 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 Thailand ›

Frequently asked questions

How long did the Dan Sai fire last?
GWIS (Copernicus) dates it between 9 February 2020 and 13 February 2020: 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 1,577 hectares (15.8 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Dan Sai (1,585 ha, 1.2 %).
What was the weather like?
During the fire the temperature reached 32.5 °C, humidity dropped to 36 % and gusts hit 37 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 Thailand (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.

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

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. This is not an emergency service: if there is a fire now, call 199 · 191.

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. 57 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 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.