Skip to content
worldfires
TH · Thailand · →

Khon San fire, February 2016 คอนสาร · Khon San

Out · last detection 2 Mar 2016, 18:37 UTC

The fire started on 24 February 2016 in Khon San, Thailand, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,727 hectares from heat detections, spread across a single municipality.

It is the 42th largest in Chaiyaphum Province since 2016 (of 123 with a page). Number 156 in Thailand in 2016, of 387.

The power measured by the satellite is low (17.6 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,727ha
GWIS perimeter (Copernicus)
Duration
8days
24 Feb 2016 – 2 Mar 2016
Municipalities hit
1
districts
Started on
24 Feb
2016
Heat detections
73
in a single hotspot: 18 MW
Danger at start
16
Moderate · FWI index
Average daily power
39MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 24 Feb2 Mar
2 Mar 2016

How it evolved, day by day

24 Feb 2016 · 5 MW · 2 25 Feb 2016 · 14 MW · 9 26 Feb 2016 · 12 MW · 8 27 Feb 2016 · 1 MW · 1 28 Feb 2016 · 6 MW · 1 29 Feb 2016 · 54 MW · 12 1 Mar 2016 · 197 MW · 34 2 Mar 2016 · 24 MW · 6
24 Feb 26 Feb 28 Feb 1 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

29°high
47km/h · peak gust
28%lowest humidity

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

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 1.1% of the area of London (17 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. Khon San คอนสาร where it started
    1,737 ha
    1.3 %

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 2015
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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)
24 Feb 29.3 °C 53 % 47 km/h 0.0 mm Moderate 16
25 Feb 25.8 °C 49 % 44 km/h 0.0 mm Moderate 15
26 Feb 26.4 °C 50 % 41 km/h 0.0 mm Moderate 15
27 Feb 27.2 °C 47 % 36 km/h 0.0 mm Moderate 15
28 Feb 28.2 °C 50 % 35 km/h 0.0 mm Moderate 15
29 Feb 28.1 °C 41 % 42 km/h 0.0 mm Moderate 17
1 Mar 28.0 °C 28 % 39 km/h 0.0 mm Moderate 21
2 Mar 29.2 °C 38 % 34 km/h 0.0 mm Moderate 20
3 Mar after 30.5 °C 45 % 29 km/h 0.0 mm Moderate 17
4 Mar after 32.5 °C 39 % 20 km/h 0.0 mm Moderate 15
5 Mar after 32.6 °C 45 % 19 km/h 0.0 mm Moderate 16
6 Mar after 32.7 °C 50 % 20 km/h 0.0 mm Moderate 15
7 Mar after 34.3 °C 47 % 25 km/h 0.0 mm Moderate 18
8 Mar after 34.4 °C 45 % 30 km/h 0.0 mm Moderate 19
9 Mar after 35.8 °C 39 % 25 km/h 0.0 mm Moderate 20
10 Mar after 36.8 °C 36 % 23 km/h 0.0 mm High 21
11 Mar after 31.3 °C 52 % 31 km/h 0.0 mm Moderate 18
12 Mar after 32.0 °C 51 % 29 km/h 0.3 mm Moderate 19

Before and after, from space

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

Before · 17 Feb 2016
After · 9 Mar 2016

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 · 73Every 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 Khon San fire last?
GWIS (Copernicus) dates it between 24 February 2016 and 2 March 2016: 8 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,727 hectares (17.3 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Khon San (1,737 ha, 1.3 %).
What was the weather like?
During the fire the temperature reached 29.3 °C, humidity dropped to 28 % and gusts hit 47 km/h. The fire danger index (FWI) reached 21, class Moderate.
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. 73 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 2015, 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.