Skip to content
worldfires
PE · Peru · →

Coronel Portillo fire, 4 October 2026 Coronel Portillo, Ucayali, Padre Abad

Out · last detection 17 Oct 2026, 06:16 UTC

Satellites first detected fire on 4 October 2026 in Coronel Portillo, Peru. It was active for 14 days, with 344 heat detections and an area with fire of about 3,654 hectares rebuilt from them, spread across 3 municipalities.

Compare with…

GWIS (Copernicus) has not yet published the perimeter of this fire. It rebuilds it from hotspots, which can take several days, and it does not always arrive. For now the area is the one rebuilt from heat detections (about 14 hectares per pixel). If the perimeter arrives, this page picks it up on its own and keeps the same address.

Area with fire
≈ 3,654ha
rebuilt from hotspots, no official perimeter yet
Duration
14days
4 Oct 2026 – 17 Oct 2026
Municipalities hit
3
provinces
Started on
4 Oct
2026
Heat detections
344
in a single hotspot: 295 MW
Danger at start
6
Low · FWI index
Average daily power
479MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 4 Oct17 Oct
17 Oct 2026

How it evolved, day by day

10 Oct 2026 · 48 MW · 10 11 Oct 2026 · 178 MW · 19 12 Oct 2026 · 0 MW · 0 13 Oct 2026 · 759 MW · 20 14 Oct 2026 · 0 MW · 0 15 Oct 2026 · 643 MW · 50 16 Oct 2026 · 1,238 MW · 109 17 Oct 2026 · 6 MW · 7
10 Oct 12 Oct 14 Oct 16 Oct

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

The weather it burned in

36°high
32km/h · peak gust
39%lowest humidity

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

What happened to each town

  1. Coronel Portillo 135,161 inhabitants where it started
    3,038 ha reached on 4 Oct
    0.1 %
  2. Ucayali 7,742 inhabitants
    504 ha reached on 4 Oct
    0.0 %
  3. Padre Abad 4,510 inhabitants
    112 ha reached on 5 Oct
    0.0 %

Area with fire inside each municipality, rebuilt from heat detections (about 14 hectares per VIIRS pixel). An estimate until the official perimeter arrives. 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.

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)
4 Oct 33.6 °C 45 % 32 km/h 0.6 mm Low 6
5 Oct 34.5 °C 43 % 32 km/h 0.0 mm Low 8
6 Oct 34.4 °C 45 % 26 km/h 0.4 mm Low 8
7 Oct 34.6 °C 47 % 28 km/h 3.4 mm Very low 2
8 Oct 33.7 °C 49 % 27 km/h 12.0 mm Very low 0
9 Oct 32.7 °C 52 % 21 km/h 5.9 mm Very low 0
10 Oct 33.5 °C 48 % 17 km/h 0.9 mm Very low 2
11 Oct 33.2 °C 65 % 21 km/h 2.1 mm Very low 1
12 Oct 34.4 °C 45 % 23 km/h 1.8 mm Very low 2
13 Oct 33.9 °C 47 % 24 km/h 1.2 mm Very low 4
14 Oct 32.8 °C 55 % 28 km/h 3.3 mm Very low 1
15 Oct 34.9 °C 44 % 26 km/h 1.1 mm Very low 4
16 Oct 35.6 °C 39 % 20 km/h 0.1 mm Low 8
17 Oct 27.3 °C 83 % 25 km/h 29.2 mm Very low 0
18 Oct after 29.7 °C 63 % 18 km/h 1.0 mm Very low 0

Before and after, from space

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

Before · 27 Sept 2026
After · 24 Oct 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 18 October 2026 the air beside the fire reached 170 µg/m³ of PM2.5. That day averaged 88: 5.9 times the WHO daily guideline (15).

PM2.5 peak170 µg/m³
Days over the guideline9 days
PM10174 µg/m³
Optical depth1.10
23456789101112131415161718
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 · 344Every 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 Peru ›

Frequently asked questions

How long did the Coronel Portillo fire last?
According to the heat detections seen by satellite, it burned from 4 October 2026 to 17 October 2026 (14 days between the first and the last detection). There is no perimeter yet to date it.
How much area did it burn?
There is no perimeter yet. Heat detections rebuild about 3,654 hectares with fire (36.5 km²), a rough figure; GWIS will give its own when it publishes the perimeter, which can take several days.
Which municipalities burned?
The fire entered 3 municipalities: Coronel Portillo (3,038 ha, 0.1 %); Ucayali (504 ha, 0.0 %); Padre Abad (112 ha, 0.0 %).
Is the Coronel Portillo fire still active?
No fire detections since 17 Oct 2026, 06:16 UTC. A lack of detections is not an official extinction.
What was the weather like?
During the fire the temperature reached 35.6 °C, humidity dropped to 39 % and gusts hit 32 km/h. The fire danger index (FWI) reached 8, class Low.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Peru (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: 116 · 105 · 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 116 · 105.

How we know this
  • No perimeter yet: the area (≈ 3,654 ha) is estimated by counting VIIRS pixels with fire, about 14 ha each.
  • Dates of the first and last VIIRS detection of the cluster. 344 Suomi-NPP VIIRS detections on those dates.
  • 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 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.