Skip to content
worldfires
MY · Malaysia · →

Tongod fire, 27 March 2016 Tongod

Out · last detection 31 Mar 2016, 05:17 UTC

The fire started on 27 March 2016 in Tongod, Malaysia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 689 hectares from heat detections, spread across a single municipality.

It is the 48th largest in Sabah since 2016 (of 106 with a page). Number 67 in Malaysia in 2016, of 104.

The power measured by the satellite is low (25.2 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
689ha
GWIS perimeter (Copernicus)
Duration
4days
27 Mar 2016 – 30 Mar 2016
Municipalities hit
1
districts
Started on
27 Mar
2016
Heat detections
26
in a single hotspot: 25 MW
Danger at start
20
Moderate · FWI index
Average daily power
53MW
detected power per day, on average

Where it burned

31 Mar 2016
HOTSPOTS BY DAY 27 Mar30 Mar

How it evolved, day by day

27 Mar 2016 · 106 MW · 20 28 Mar 2016 · 2 MW · 1 30 Mar 2016 · 101 MW · 4 31 Mar 2016 · 4 MW · 1
27 Mar 28 Mar 30 Mar 31 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

37°high
38km/h · peak gust
25%lowest humidity

It had gone 0 days without rain (1 mm or more) when it started. Rain came after the fire: 1.4 mm on 31 Mar.

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 0.4% of the area of London (6.9 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. Tongod where it started
    693 ha
    0.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)
27 Mar 36.8 °C 25 % 31 km/h 0.0 mm Moderate 20
28 Mar 35.3 °C 38 % 38 km/h 0.0 mm High 22
29 Mar 35.7 °C 40 % 36 km/h 0.9 mm Moderate 17
30 Mar 34.3 °C 48 % 35 km/h 2.1 mm Low 8
31 Mar after 35.8 °C 40 % 31 km/h 1.4 mm Moderate 12

Before and after, from space

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

Before · 20 Mar 2016
After · 6 Apr 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 · 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 Malaysia ›

Frequently asked questions

How long did the Tongod fire last?
GWIS (Copernicus) dates it between 27 March 2016 and 30 March 2016: 4 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 689 hectares (6.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Tongod (693 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 36.8 °C, humidity dropped to 25 % and gusts hit 38 km/h. The fire danger index (FWI) reached 22, class High.
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
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 999.

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. 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.

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 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.