Skip to content
worldfires
TH · Thailand · →

Lan Sak fire, March 2017 Lan Sak

Out · last detection 8 Mar 2017, 06:48 UTC

The fire started on 7 March 2017 in Lan Sak, Thailand, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,143 hectares from heat detections, spread across a single municipality.

It is the 62th largest in Uthai Thani Province since 2016 (of 72 with a page). Number 188 in Thailand in 2017, of 240.

Burnt area
1,143ha
GWIS perimeter (Copernicus)
Duration
2days
7 Mar 2017 – 8 Mar 2017
Municipalities hit
1
districts
Started on
7 Mar
2017
Heat detections
27
in a single hotspot: 49 MW
Danger at start
21
Moderate · FWI index
Energy released
470MW
sum of detected power

Where it burned

8 Mar 2017
HOTSPOTS BY DAY 7 Mar8 Mar

How it evolved, day by day

78

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

The weather it burned in

35°high
24km/h · peak gust
39%lowest humidity

It had gone 7 days without rain (1 mm or more) when it started.

This area had burned before

96% of the perimeter overlaps earlier fires recorded since 2016: 1,094 ha in 2016.

What happened to each town

  1. Lan Sak where it started
    1,150 ha reached on 7 Mar
    0.8 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.

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)
7 Mar 35.0 °C 39 % 24 km/h 0.0 mm Moderate 21
8 Mar 34.4 °C 44 % 23 km/h 0.0 mm High 22
9 Mar after 34.2 °C 47 % 27 km/h 0.0 mm Moderate 21
10 Mar after 36.4 °C 36 % 20 km/h 0.0 mm High 22
11 Mar after 36.5 °C 37 % 26 km/h 0.0 mm High 23
12 Mar after 37.6 °C 31 % 25 km/h 0.0 mm High 27
13 Mar after 37.3 °C 32 % 24 km/h 0.0 mm High 27
14 Mar after 37.5 °C 30 % 23 km/h 0.0 mm High 28
15 Mar after 36.3 °C 35 % 34 km/h 0.0 mm High 30
16 Mar after 36.6 °C 36 % 26 km/h 0.0 mm High 28
17 Mar after 34.6 °C 41 % 28 km/h 0.0 mm High 26
18 Mar after 35.6 °C 43 % 26 km/h 0.3 mm High 25

Before and after, from space

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

Before · 28 Feb 2017
After · 15 Mar 2017

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 · 27Every 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 Lan Sak fire last?
GWIS (Copernicus) dates it between 7 March 2017 and 8 March 2017: 2 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,143 hectares (11.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Lan Sak (1,150 ha, 0.8 %).
What was the weather like?
During the fire the temperature reached 35.0 °C, humidity dropped to 39 % and gusts hit 24 km/h. The fire danger index (FWI) reached 22, 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

Satellite cross-check

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.

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.