Skip to content
worldfires
PH · Philippines · →

Sablayan fire, January 2026 Sablayan

Out · last detection 23 Jan 2026, 17:39 UTC

The fire started on 23 January 2026 in Sablayan, Philippines, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,028 hectares from heat detections, spread across a single municipality.

It is the 16th largest in Mimaropa since 2016 (of 19 with a page). Number 46 in Philippines in 2026, of 52.

The power measured by the satellite is low (16.8 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
1,028ha
GWIS perimeter (Copernicus)
Duration
2days
23 Jan 2026 – 24 Jan 2026
Municipalities hit
1
municipalities
Started on
23 Jan
2026
Heat detections
16
in a single hotspot: 17 MW
Danger at start
2
Very low · FWI index
Average daily power
87MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 23 Jan24 Jan

How it evolved, day by day

23 Jan 2026 · 87 MW · 16

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

The weather it burned in

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

It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 11.4 mm on 26 Jan.

This area had burned before

52% of the perimeter overlaps earlier fires recorded since 2016: 180 ha in 2018, 13 ha in 2019, 18 ha in 2020, 182 ha in 2021, 37 ha in 2023, 105 ha in 2024.

How big is it?

10 km
It burned the equivalent of 0.6% of the area of London (10 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. Sablayan where it started
    1,034 ha reached on 23 Jan
    0.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.

People and buildings inside the perimeter

GHSL 2025
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.

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)

Day High Min. humidity Peak gust Rain Danger (FWI)
23 Jan 24.9 °C 53 % 38 km/h 0.0 mm Very low 2
24 Jan 25.1 °C 57 % 32 km/h 0.1 mm Very low 2
25 Jan after 25.4 °C 55 % 32 km/h 0.0 mm Very low 3
26 Jan after 24.4 °C 73 % 30 km/h 11.4 mm Very low 0

Before and after, from space

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

Before · 16 Jan 2026
After · 31 Jan 2026

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

The smoke

CAMS · Copernicus

On 24 January 2026 the air beside the fire reached 11 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak11 µg/m³
Days over the guideline0 days
PM1014 µg/m³
Optical depth0.23
21222324252627
Good Fair Moderate Poor Very poor Extremely poor

Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.

Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)

Detections table · 16Every 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 Philippines ›

Frequently asked questions

How long did the Sablayan fire last?
GWIS (Copernicus) dates it between 23 January 2026 and 24 January 2026: 2 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 1,028 hectares (10.3 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Sablayan (1,034 ha, 0.5 %).
What was the weather like?
During the fire the temperature reached 25.1 °C, humidity dropped to 53 % and gusts hit 38 km/h. The fire danger index (FWI) reached 2, class Very low.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Philippines (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: 911 · 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.

RSS Changes to this page

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

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. 16 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 2025, 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 ADM3 (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.