Skip to content
worldfires
MY · Malaysia · →

Segamat fire, February 2016 Segamat, Jempol

Out · last detection 2 Mar 2016, 18:40 UTC

The fire started on 27 February 2016 in Segamat, Malaysia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 701 hectares from heat detections, spread across 2 municipalities.

It is the 8th largest in Johor since 2016 (of 16 with a page). Number 64 in Malaysia in 2016, of 104.

The power measured by the satellite is low (11.1 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
701ha
GWIS perimeter (Copernicus)
Duration
5days
27 Feb 2016 – 2 Mar 2016
Municipalities hit
2
districts
Started on
27 Feb
2016
Heat detections
17
in a single hotspot: 11 MW
Danger at start
11
Moderate · FWI index
Energy released
61MW
sum of detected power

Where it burned

2 Mar 2016
HOTSPOTS BY DAY 27 Feb2 Mar

How it evolved, day by day

272912

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

The weather it burned in

35°high
50km/h · peak gust
43%lowest humidity

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

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Segamat where it started
    608 ha reached on 27 Feb
    0.2 %
  2. 97 ha reached on 29 Feb
    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 Feb 33.0 °C 52 % 43 km/h 0.6 mm Moderate 11
28 Feb 33.0 °C 54 % 46 km/h 0.1 mm Moderate 12
29 Feb 33.8 °C 51 % 50 km/h 0.4 mm Moderate 14
1 Mar 34.9 °C 43 % 45 km/h 0.0 mm Moderate 16
2 Mar 34.2 °C 45 % 45 km/h 0.1 mm Moderate 18
3 Mar after 34.9 °C 43 % 43 km/h 0.0 mm Moderate 18
4 Mar after 33.5 °C 52 % 40 km/h 0.0 mm Moderate 18
5 Mar after 32.7 °C 57 % 39 km/h 3.9 mm Very low 4

Before and after, from space

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

Before · 20 Feb 2016
After · 9 Mar 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 · 17Every 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

Frequently asked questions

How long did the Segamat fire last?
GWIS (Copernicus) dates it between 27 February 2016 and 2 March 2016: 5 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 701 hectares (7.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Segamat (608 ha, 0.2 %); Jempol (97 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 34.9 °C, humidity dropped to 43 % and gusts hit 50 km/h. The fire danger index (FWI) reached 18, class Moderate.
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.

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.