Satellites first detected fire on 15 October 2026 in San Diego, United States. It was active for 2 days, with 34 heat detections and an area with fire of about 448 hectares rebuilt from them, spread across a single county.
matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Burned area
satellite only
≈ 448ha
Estimated from hotspots: no perimeter has been published yet.
Source
NASA FIRMS · VIIRS
Date
15 Oct 2026 – 16 Oct 2026
+− cross-check
This is an estimate from the VIIRS pixels that saw fire. It will change when the perimeter is published.
Duration by satellite
satellite only
2days
15 Oct 2026 to 16 Oct 2026: first and last day with fire on the page.
Source
NASA FIRMS · VIIRS
Date
15 Oct 2026 – 16 Oct 2026
+− cross-check
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.
Start
satellite only
15 Oct 2026
First day with fire seen by the satellites or the perimeter.
Source
NASA FIRMS · VIIRS
Date
15 Oct 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only
34
VIIRS detections at 375 m. Most intense hotspot: 102 MW.
Source
NASA FIRMS · VIIRS (Suomi NPP)
Date
15 Oct 2026 – 16 Oct 2026
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
Danger at the start
model
28.5FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 2.
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings ›
Weather during the fire
model
33.6°C · 19% RH
High of 33.6 °C and minimum humidity of 19% on 16 October 2026; gusts of 50 km/h on 16 October 2026.
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
ⓘThis page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
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.
Area with fire
≈ 448ha
rebuilt from hotspots, no official perimeter yet
Duration
2days
15 Oct 2026 – 16 Oct 2026
Counties hit
1
counties
Started on
15 Oct
2026
Heat detections
34
in a single hotspot: 102 MW
Danger at start
28
High · FWI index
Where it burned
HOTSPOTS BY DAY
15 Oct16 Oct
The weather it burned in
34°high
50km/h · peak gust
19%lowest humidity
It had gone 2 days without rain (1 mm or more) when it started. Rain came after the fire: 8.3 mm on 21 Oct.
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) · Copernicus Climate Change Service (ERA5)
Day
High
Min. humidity
Peak gust
Rain
Danger (FWI)
15 Oct
30.8 °C
20 %
37 km/h
0.0 mm
High 28
16 Oct
33.6 °C
19 %
50 km/h
0.0 mm
Very high 43
17 Oct after
30.1 °C
19 %
34 km/h
0.0 mm
High 37
18 Oct after
28.3 °C
25 %
23 km/h
0.0 mm
High 30
19 Oct after
27.6 °C
38 %
26 km/h
0.0 mm
High 26
20 Oct after
25.7 °C
51 %
28 km/h
0.0 mm
Moderate 20
21 Oct after
24.7 °C
51 %
42 km/h
8.3 mm
Moderate 21
Its twins: fires that started in the same weather
It started with an FWI of 28.5, a minimum humidity of 20% and 2 days without rain. Fires in the area that started in weather like this since 2016: 9.
FWI at the start28.5
Minimum humidity20 %
Days without rain2
this firechosen twinsrest of the area
Almost identicalSimilar
Outlines of the closest twins
Playas de Rosarito fire, October 2017
4,247 ha5 daysFWI 31.4Min. humidity 21 %125 km away, in 2017
First rain (1 mm or more) after it ended: none in the following ten days.
Fires in the area that started in similar weather: 9. With fewer than 15 we give no figures: they would be more noise than signal.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
8.3 mmfirst rain
21 Oct5 days after it ended
50km/h · max. gust
It was considered over on 16 Oct, and on 21 Oct 8.3 mm fell. We do not know whether the rain or the firefighters put it out.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
Same area: fires that have already ended, less than 250 km from this one, since 2016.
Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
They are sorted by similarity, and the outlines of the first five are drawn.
Drag the line to compare the same ground before the fire and after it.
↔
Before · 8 Oct 2026
After · 23 Oct 2026
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 16 October 2026 the air beside the fire reached 25 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
PM2.5 peak25µg/m³
Days over the guideline0days
PM1054µg/m³
Optical depth0.20
WHO 15
13141516
GoodFairModeratePoorVery poorExtremely 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· 34Every satellite heat detection, one by one, with time, satellite, power and coordinates.›
⬇ Download CSVTimes in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
According to the heat detections seen by satellite, it burned from 15 October 2026 to 16 October 2026 (2 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 448 hectares with fire (4.5 km²).
Which counties burned?
The fire only entered San Diego (420 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 33.6 °C, humidity dropped to 19 % and gusts hit 50 km/h. The fire danger index (FWI) reached 43, class Very 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.
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 errorHow we know this›
No perimeter yet: the area (≈ 448 ha) is estimated by counting VIIRS pixels with fire, about 14 ha each.
Dates of the first and last VIIRS detection of the cluster. 34 Suomi-NPP VIIRS detections on those dates.
Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
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.