Skip to content
worldfires
US · United States · →

Pointe Coupee fire, 16 October 2026 Pointe Coupee, West Baton Rouge

Dying down · last detection 25 Oct 2026, 19:34 UTC

Satellites first detected fire on 16 October 2026 in Pointe Coupee, United States. It has been active for 10 days, with 44 heat detections and an area with fire of about 574 hectares rebuilt from them, spread across 2 counties.

Compare with…

Suggestions: Pointe Coupee · 2026

NIFC has not yet published the perimeter of this fire. For now the area is the one rebuilt from heat detections (about 14 hectares per pixel). When the perimeter arrives, this page picks it up on its own and keeps the same address.

Is it still active?

No detections since 25 Oct 2026, 19:34 UTC. That usually means no flame is visible from space any more, although hotspots may remain. Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.

Area with fire
≈ 574ha
rebuilt from hotspots, no official perimeter yet
Duration
10days
16 Oct 2026 – 25 Oct 2026
Counties hit
2
counties
Started on
16 Oct
2026
Heat detections
44
in a single hotspot: 68 MW
Danger at start
13
Moderate · FWI index
Average daily power
69MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 16 Oct25 Oct
25 Oct 2026

How it evolved, day by day

16 Oct 2026 · 15 MW · 2 18 Oct 2026 · 189 MW · 14 19 Oct 2026 · 36 MW · 7 20 Oct 2026 · 172 MW · 6 21 Oct 2026 · 55 MW · 2 22 Oct 2026 · 112 MW · 6 23 Oct 2026 · 13 MW · 3 24 Oct 2026 · 13 MW · 2 25 Oct 2026 · 15 MW · 3
16 Oct 18 Oct 19 Oct 21 Oct 23 Oct 25 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

31°high
56km/h · peak gust
20%lowest humidity

It had gone 10 days without rain (1 mm or more) when it started.

What happened to each county

  1. Pointe Coupee where it started
    392 ha reached on 16 Oct
    0.3 %
  2. 182 ha reached on 18 Oct
    0.3 %

Area with fire inside each county, rebuilt from heat detections (about 14 hectares per VIIRS pixel). An estimate until NIFC publishes the official perimeter. 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) · forecast models, provisional until the ERA5 reanalysis arrives

Day High Min. humidity Peak gust Rain Danger (FWI)
16 Oct 30.8 °C 39 % 56 km/h 2.7 mm Moderate 13
17 Oct 21.9 °C 36 % 50 km/h 0.0 mm Moderate 17
18 Oct 24.1 °C 35 % 30 km/h 0.0 mm Moderate 14
19 Oct 24.9 °C 22 % 29 km/h 0.0 mm Moderate 18
20 Oct 26.7 °C 34 % 29 km/h 0.0 mm Moderate 18
21 Oct 27.4 °C 23 % 25 km/h 0.0 mm Moderate 19
22 Oct 29.4 °C 22 % 23 km/h 0.0 mm Moderate 21
23 Oct 29.8 °C 20 % 26 km/h 0.0 mm High 22
24 Oct 28.3 °C 28 % 32 km/h 0.0 mm High 26
25 Oct 26.6 °C 33 % 29 km/h 0.0 mm High 22
26 Oct after 26.3 °C 37 % 26 km/h 0.0 mm Moderate 21

Before and after, from space

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

Before · 9 Oct 2026
After · 25 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 17 October 2026 the air beside the fire reached 16 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak16 µg/m³
Days over the guideline0 days
PM1019 µg/m³
Optical depth0.32
8910111213141516171819
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 · 44Every 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 United States ›

Frequently asked questions

How long did the Pointe Coupee fire last?
According to the heat detections seen by satellite, it burned from 16 October 2026 to 25 October 2026 (10 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 official perimeter yet: NIFC has not published it. Heat detections rebuild about 574 hectares with fire (5.7 km²).
Which counties burned?
The fire entered 2 counties: Pointe Coupee (392 ha, 0.3 %); West Baton Rouge (182 ha, 0.3 %).
Is the Pointe Coupee fire still active?
No fire detections since 25 Oct 2026, 19:34 UTC. A lack of detections is not an official extinction.
What was the weather like?
During the fire the temperature reached 30.8 °C, humidity dropped to 20 % and gusts hit 56 km/h. The fire danger index (FWI) reached 26, class High.
Where does this data come from?
From the official burnt perimeter of United States agencies (MTBS / NIFC, public domain), NASA FIRMS VIIRS hotspots and the administrative boundaries of United States. 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 · 4 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Area: ≈ 546 → ≈ 574 ha.
  2. Start date: 15 October 2026 → 16 October 2026.
  3. Area: ≈ 560 → ≈ 546 ha.
  4. Start date: 14 October 2026 → 15 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
  • No perimeter yet: the area (≈ 574 ha) is estimated by counting VIIRS pixels with fire, about 14 ha each.
  • Dates of the first and last VIIRS detection of the cluster. 44 Suomi-NPP VIIRS detections on those dates.
  • Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives.

How we build fire pages: methodology ›

Where this data comes from

The perimeter is official and in the public domain. For past years it comes from MTBS (Monitoring Trends in Burn Severity), run by the U.S. Geological Survey and the USDA Forest Service, which map it on Landsat and Sentinel-2 imagery. For the current and last year it comes from WFIGS at the National Interagency Fire Center (NIFC): incident perimeters mapped by fire crews, aircraft and imagery. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. County boundaries come from geoBoundaries ADM2 (Public Domain). The area per county is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from official figures.