Skip to content
worldfires
TH · Thailand · –

Sop Moei fire, April 2017 สบเมย · Sop Moei, Mae Sariang

Out · last detection 8 Apr 2017, 07:07 UTC

The fire started on 3 April 2017 in Sop Moei, Thailand, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,094 hectares from heat detections, spread across 2 municipalities.

It is the 126th largest in Mae Hong Son Province since 2016 (of 361 with a page). Number 36 in Thailand in 2017, of 155.

Burnt area
2,094ha
GWIS perimeter (Copernicus)
Duration
6days
3 Apr 2017 – 8 Apr 2017
Municipalities hit
2
districts
Started on
3 Apr
2017
Heat detections
44
in a single hotspot: 0 MW
Danger at start
25
High · FWI index
Average daily power
17MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 3 Apr8 Apr
8 Apr 2017

How it evolved, day by day

3 Apr 2017 · 4 MW · 4 4 Apr 2017 · 28 MW · 15 5 Apr 2017 · 55 MW · 20 6 Apr 2017 · 6 MW · 2 7 Apr 2017 · 6 MW · 2 8 Apr 2017 · 5 MW · 1
3 Apr 5 Apr 7 Apr

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

The weather it burned in

37°high
31km/h · peak gust
29%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started. Rain came after the fire: 1.1 mm on 12 Apr.

This area had burned before

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

How big is it?

10 km
It burned the equivalent of 1.3% of the area of London (21 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. Sop Moei สบเมย where it started
    2,099 ha
    1.5 %
  2. Mae Sariang แม่สะเรียง
    7 ha
    0.0 %

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)

Started with 60 days without rain: 15 % of the area in Thailand

Day High Min. humidity Peak gust Rain Danger (FWI)
3 Apr 34.3 °C 40 % 31 km/h 0.2 mm High 25
4 Apr 34.4 °C 29 % 31 km/h 0.0 mm High 30
5 Apr 35.1 °C 34 % 29 km/h 0.0 mm High 30
6 Apr 35.3 °C 32 % 27 km/h 0.0 mm High 30
7 Apr 35.9 °C 38 % 30 km/h 0.0 mm High 30
8 Apr 36.8 °C 37 % 31 km/h 0.0 mm High 31
9 Apr after 36.5 °C 39 % 31 km/h 0.0 mm High 32
10 Apr after 35.9 °C 44 % 37 km/h 0.0 mm High 30
11 Apr after 36.3 °C 35 % 34 km/h 0.0 mm High 30
12 Apr after 34.8 °C 47 % 37 km/h 1.1 mm Moderate 20

Its twins: fires that started in the same weather

It started with an FWI of 25.2, a minimum humidity of 40% and more than two months without rain. Fires in the area that started in weather like this since 2016: 16.

FWI at the start 25.2
Minimum humidity 40 %
Days without rain 60+
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Sop Moei fire, March 2020
6,560 ha 11 days FWI 27.1 Min. humidity 37 % 26 km away, in 2020

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

What happened to them

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

It burned an area similar to its twins (2,094 ha against a median of 2,729 ha) and lasted 6 days, against 9 days.

In 8 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 3.6 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

1.1 mmfirst rain
12 Apr4 days after it ended
31km/h · max. gust

It was considered over on 8 Apr, and on 12 Apr 1.1 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 8 of 16, with a median of 3.6 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 · 27 Mar 2017
After · 15 Apr 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 · 0Every 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 Sop Moei fire last?
GWIS (Copernicus) dates it between 3 April 2017 and 8 April 2017: 6 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,094 hectares (20.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Sop Moei (2,099 ha, 1.5 %); Mae Sariang (7 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 36.8 °C, humidity dropped to 29 % and gusts hit 31 km/h. The fire danger index (FWI) reached 31, 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.
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 2,729 ha; 100 % went past 1,000 ha. In 8 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 3.6 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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Start date: 30 March 2017 → 3 April 2017.
  2. Start date: 3 April 2017 → 30 March 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 from the perimeter: the VIIRS detections inside it did not change them. No 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.