Skip to content
worldfires
US · United States · →

Ascension fire, October 2026 Assumption, Ascension, Iberville

Burning · last detection 25 Oct 2026, 08:35 UTC

Satellites first detected fire on 15 October 2026 in Ascension, United States. It has been active for 11 days, with 66 heat detections and an area with fire of about 868 hectares rebuilt from them, spread across 3 counties.

Compare with…

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?

Satellites detected fire on 25 Oct 2026, 08:35 UTC. Everything suggests it is still burning. 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
≈ 868ha
rebuilt from hotspots, no official perimeter yet
Duration
11days
15 Oct 2026 – 25 Oct 2026
Counties hit
3
counties
Started on
15 Oct
2026
Heat detections
66
in a single hotspot: 175 MW
Danger at start
10
Low · FWI index
Average daily power
104MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 15 Oct25 Oct
25 Oct 2026

How it evolved, day by day

15 Oct 2026 · 53 MW · 5 16 Oct 2026 · 20 MW · 5 17 Oct 2026 · 14 MW · 5 18 Oct 2026 · 3 MW · 3 19 Oct 2026 · 275 MW · 7 20 Oct 2026 · 304 MW · 10 21 Oct 2026 · 91 MW · 10 22 Oct 2026 · 131 MW · 8 23 Oct 2026 · 9 MW · 5 24 Oct 2026 · 238 MW · 11 25 Oct 2026 · 1 MW · 1
15 Oct 17 Oct 19 Oct 20 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
55km/h · peak gust
25%lowest humidity

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

What happened to each county

  1. Assumption where it started
    392 ha reached on 15 Oct
    0.4 %
  2. 280 ha reached on 15 Oct
    0.4 %
  3. 196 ha reached on 17 Oct
    0.1 %

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)
15 Oct 30.6 °C 43 % 23 km/h 0.0 mm Low 10
16 Oct 30.7 °C 43 % 55 km/h 0.3 mm Moderate 18
17 Oct 21.6 °C 37 % 50 km/h 0.0 mm Moderate 17
18 Oct 23.5 °C 45 % 34 km/h 0.0 mm Moderate 12
19 Oct 24.4 °C 34 % 28 km/h 0.0 mm Moderate 12
20 Oct 25.7 °C 41 % 30 km/h 0.0 mm Moderate 12
21 Oct 26.1 °C 28 % 24 km/h 0.0 mm Moderate 13
22 Oct 28.1 °C 27 % 23 km/h 0.0 mm Moderate 15
23 Oct 28.0 °C 25 % 21 km/h 0.0 mm Moderate 16
24 Oct 27.1 °C 31 % 35 km/h 0.0 mm Moderate 20
25 Oct 24.8 °C 46 % 35 km/h 0.0 mm Moderate 16

Before and after, from space

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

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

PM2.5 peak18 µg/m³
Days over the guideline0 days
PM1019 µg/m³
Optical depth0.23
45678910
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 · 66Every 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 Ascension fire last?
According to the heat detections seen by satellite, it burned from 15 October 2026 to 25 October 2026 (11 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 868 hectares with fire (8.7 km²).
Which counties burned?
The fire entered 3 counties: Assumption (392 ha, 0.4 %); Ascension (280 ha, 0.4 %); Iberville (196 ha, 0.1 %).
Is the Ascension fire still active?
Yes: satellites detected fire on 25 Oct 2026, 08:35 UTC. Check the emergency service for the official status.
What was the weather like?
During the fire the temperature reached 30.7 °C, humidity dropped to 25 % and gusts hit 55 km/h. The fire danger index (FWI) reached 20, class Moderate.
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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Area: ≈ 686 → ≈ 854 ha.
  2. 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 (≈ 868 ha) is estimated by counting VIIRS pixels with fire, about 14 ha each.
  • Dates of the first and last VIIRS detection of the cluster. 66 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.