Skip to content
worldfires
TH · Thailand · –

Nong Bua Daeng fire, 10 February 2017 หนองบัวแดง · Nong Bua Daeng

Out · last detection 15 Feb 2017, 19:13 UTC

The fire started on 10 February 2017 in Nong Bua Daeng, Thailand, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,111 hectares from heat detections, spread across a single municipality.

It is the 73th largest in Chaiyaphum Province since 2016 (of 90 with a page). Number 129 in Thailand in 2017, of 155.

The power measured by the satellite is low (11.9 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Burnt area
1,111ha
GWIS perimeter (Copernicus)
Duration
6days
10 Feb 2017 – 15 Feb 2017
Municipalities hit
1
districts
Started on
10 Feb
2017
Heat detections
26
in a single hotspot: 12 MW
Danger at start
17
Moderate · FWI index
Average daily power
12MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 10 Feb15 Feb
15 Feb 2017

How it evolved, day by day

10 Feb 2017 · 3 MW · 2 11 Feb 2017 · 5 MW · 8 12 Feb 2017 · 23 MW · 8 13 Feb 2017 · 31 MW · 6 14 Feb 2017 · 3 MW · 1 15 Feb 2017 · 3 MW · 1
10 Feb 13 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

29°high
43km/h · peak gust
42%lowest humidity

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

This area had burned before

56% of the perimeter overlaps earlier fires recorded since 2016: 627 ha in 2016.

How big is it?

10 km
It burned the equivalent of 0.7% of the area of London (11 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. Nong Bua Daeng หนองบัวแดง where it started
    1,117 ha reached on 10 Feb
    0.5 %

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 area0.22 ha
Residents< 20

Inside the perimeter there were about 0.22 hectares of 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)
10 Feb 29.0 °C 51 % 34 km/h 0.0 mm Moderate 17
11 Feb 28.1 °C 49 % 42 km/h 0.0 mm Moderate 19
12 Feb 26.6 °C 47 % 43 km/h 0.0 mm Moderate 20
13 Feb 27.0 °C 45 % 40 km/h 0.0 mm Moderate 20
14 Feb 27.6 °C 42 % 41 km/h 0.0 mm Moderate 21
15 Feb 28.4 °C 43 % 39 km/h 0.0 mm Moderate 21
16 Feb after 29.9 °C 41 % 30 km/h 0.0 mm Moderate 19
17 Feb after 31.1 °C 38 % 27 km/h 0.0 mm Moderate 19
18 Feb after 30.9 °C 36 % 34 km/h 0.0 mm High 22
19 Feb after 31.4 °C 38 % 17 km/h 0.0 mm Moderate 20
20 Feb after 32.0 °C 42 % 33 km/h 0.0 mm High 23
21 Feb after 32.6 °C 43 % 28 km/h 0.0 mm High 22
22 Feb after 33.0 °C 47 % 26 km/h 0.0 mm High 22
23 Feb after 34.1 °C 46 % 23 km/h 0.0 mm High 22
24 Feb after 33.3 °C 49 % 21 km/h 0.1 mm Moderate 20
25 Feb after 29.7 °C 64 % 28 km/h 0.3 mm Moderate 16

Its twins: fires that started in the same weather

It started with an FWI of 17.1, a minimum humidity of 51% and 27 days without rain. Fires in the area that started in weather like this since 2016: 16.

FWI at the start 17.1
Minimum humidity 51 %
Days without rain 27
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Mueang Phetchabun fire, March 2023
4,081 ha 12 days FWI 16.8 Min. humidity 50 % 39 km away, in 2023

First rain (1 mm or more) after it ended: none in the following ten days.

What happened to them

9 days
median duration
1,389 ha
median area
100 %
went past 1,000 ha
1.7 mm
rain at the end (median; 9 of 16 had it)

It burned an area similar to its twins (1,111 ha against a median of 1,389 ha) and lasted 6 days, against 9 days.

In 7 of 16, 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 1.7 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
43km/h · max. gust

It was considered over on 15 Feb, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 9 of 16, with a median of 1.7 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.

How we calculate it

Before and after, from space

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

Before · 3 Feb 2017
After · 22 Feb 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 · 26Every 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 Nong Bua Daeng fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 10 February 2017 to 15 February 2017 (6 days). The perimeter dates it from 10 February 2017 to 13 February 2017.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,111 hectares (11.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Nong Bua Daeng (1,117 ha, 0.5 %).
What was the weather like?
During the fire the temperature reached 29.0 °C, humidity dropped to 42 % and gusts hit 43 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.
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: 16. Their median duration was 9 days and their median area 1,389 ha; 100 % went past 1,000 ha. In 7 of 16, 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 1.7 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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Last day with fire: 13 February 2017 → 15 February 2017.

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
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 adjusted with the VIIRS detections inside the perimeter, which said 10 February 2017 to 13 February 2017. 26 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.