Hot fire, 1 March 2017 ฮอด · Hot
The fire started on 1 March 2017 in Hot, Thailand, and satellites saw it burning for 10 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,222 hectares from heat detections, spread across a single municipality.
It is the 122th largest in Chiang Mai Province since 2016 (of 399 with a page). Number 32 in Thailand in 2017, of 155.
The power measured by the satellite is low (9.7 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…
Suggestions: Hot · 2026Hot · 2026Hot · 2026Chom Thong · 2026
- Burnt area
- 2,222ha
- GWIS perimeter (Copernicus)
- Duration
- 10days
- 1 Mar 2017 – 10 Mar 2017
- Municipalities hit
- 1
- districts
- Started on
- 1 Mar
- 2017
- Heat detections
- 90
- in a single hotspot: 10 MW
- Danger at start
- 31
- High · FWI index
- Average daily power
- 24MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 43 days without rain (1 mm or more) when it started.
This area had burned before
21% of the perimeter overlaps earlier fires recorded since 2016: 476 ha in 2016.
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
-
2,234 ha1.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.
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 Feb | 35.5 °C | 23 % | 38 km/h | 0.0 mm | High 31 |
| 26 Feb | 35.0 °C | 22 % | 32 km/h | 0.0 mm | High 30 |
| 27 Feb | 35.2 °C | 30 % | 25 km/h | 0.0 mm | High 28 |
| 28 Feb | 35.1 °C | 29 % | 19 km/h | 0.0 mm | High 27 |
| 1 Mar | 35.0 °C | 32 % | 18 km/h | 0.0 mm | High 27 |
| 2 Mar | 33.5 °C | 36 % | 27 km/h | 0.0 mm | High 25 |
| 3 Mar | 34.7 °C | 31 % | 26 km/h | 0.0 mm | High 25 |
| 4 Mar | 34.5 °C | 31 % | 28 km/h | 0.0 mm | High 27 |
| 5 Mar | 34.6 °C | 27 % | 27 km/h | 0.0 mm | High 28 |
| 6 Mar | 35.3 °C | 28 % | 25 km/h | 0.0 mm | High 28 |
| 7 Mar | 34.8 °C | 26 % | 28 km/h | 0.0 mm | High 30 |
| 8 Mar | 34.9 °C | 33 % | 28 km/h | 0.0 mm | High 30 |
| 9 Mar | 33.7 °C | 33 % | 43 km/h | 0.0 mm | High 34 |
| 10 Mar | 33.7 °C | 38 % | 40 km/h | 0.1 mm | High 31 |
| 11 Mar after | 34.7 °C | 37 % | 36 km/h | 0.0 mm | High 31 |
| 12 Mar after | 35.5 °C | 31 % | 45 km/h | 0.0 mm | High 34 |
| 13 Mar after | 35.3 °C | 27 % | 40 km/h | 0.0 mm | High 33 |
| 14 Mar after | 35.6 °C | 31 % | 32 km/h | 0.0 mm | High 32 |
| 15 Mar after | 35.8 °C | 21 % | 36 km/h | 0.0 mm | High 37 |
| 16 Mar after | 36.3 °C | 27 % | 41 km/h | 0.0 mm | Very high 40 |
| 17 Mar after | 35.1 °C | 30 % | 41 km/h | 0.0 mm | Very high 38 |
| 18 Mar after | 35.1 °C | 29 % | 40 km/h | 0.0 mm | Very high 39 |
| 19 Mar after | 35.2 °C | 27 % | 37 km/h | 0.0 mm | Very high 38 |
| 20 Mar after | 35.4 °C | 28 % | 35 km/h | 0.0 mm | Very high 38 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · 90Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,142 haHot ฮอด23 March 2026 · 19 days · 12 km away
- 4,715 haHot ฮอด27 March 2026 · 11 days · 14 km away
- 21,007 haHot ฮอด22 March 2026 · 23 days · 22 km away
- 5,960 haChom Thong จอมทอง22 March 2026 · 18 days · 26 km away
- 5,065 haChom Thong จอมทอง29 March 2024 · 10 days · 30 km away
- 6,733 haHot ฮอด23 February 2024 · 18 days · 34 km away
Frequently asked questions
- How long did the Hot fire last?
- GWIS (Copernicus) dates it between 1 March 2017 and 10 March 2017: 10 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 2,222 hectares (22.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Hot (2,234 ha, 1.5 %).
- What was the weather like?
- During the fire the temperature reached 35.5 °C, humidity dropped to 22 % and gusts hit 43 km/h. The fire danger index (FWI) reached 34, 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.
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. 90 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.
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.