Beluran fire, May 2016 Beluran
The fire started on 10 May 2016 in Beluran, Malaysia, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 742 hectares from heat detections, spread across a single municipality.
It is the 40th largest in Sabah since 2016 (of 106 with a page). Number 55 in Malaysia in 2016, of 104.
- Burnt area
- 742ha
- GWIS perimeter (Copernicus)
- Duration
- 8days
- 10 May 2016 – 17 May 2016
- Municipalities hit
- 1
- districts
- Started on
- 10 May
- 2016
- Heat detections
- 36
- in a single hotspot: 36 MW
- Danger at start
- 9
- Low · FWI index
- Energy released
- 328MW
- sum of detected power
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 2 days without rain (1 mm or more) when it started. Rain came after the fire: 4.9 mm on 18 May.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Beluran where it started747 ha reached on 10 May0.1 %
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) |
|---|---|---|---|---|---|
| 10 May | 33.0 °C | 57 % | 28 km/h | 0.0 mm | Low 9 |
| 11 May | 33.9 °C | 55 % | 35 km/h | 2.7 mm | Very low 5 |
| 12 May | 32.9 °C | 62 % | 26 km/h | 2.8 mm | Very low 2 |
| 13 May | 32.2 °C | 65 % | 32 km/h | 3.1 mm | Very low 2 |
| 14 May | 32.6 °C | 64 % | 31 km/h | 3.7 mm | Very low 1 |
| 15 May | 33.1 °C | 59 % | 32 km/h | 0.5 mm | Low 6 |
| 16 May | 31.3 °C | 70 % | 28 km/h | 4.5 mm | Very low 1 |
| 17 May | 30.9 °C | 69 % | 19 km/h | 2.0 mm | Very low 1 |
| 18 May after | 32.3 °C | 67 % | 31 km/h | 4.9 mm | Very low 1 |
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 · 36Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Beluran fire last?
- GWIS (Copernicus) dates it between 10 May 2016 and 17 May 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 742 hectares (7.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Beluran (747 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 33.9 °C, humidity dropped to 55 % and gusts hit 35 km/h. The fire danger index (FWI) reached 9, class Low.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Malaysia (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: 999
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
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 License). 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.