Skip to content
worldfires
US · United States · →

Babylon Fire, June 2026 San Juan

Out · last detection 27 Jun 2026, 20:24 UTC

The fire started on 26 June 2026 in San Juan, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 43,378 hectares, spread across a single county.

It is the 4th largest in Utah since 2016 (of 165 with a page). Number 10 in United States in 2026, of 423.

Burnt area
43,378ha
official perimeter (MTBS / NIFC)
Duration
1day
26 Jun 2026 – 26 Jun 2026
Municipalities hit
1
counties
Started on
26 Jun
2026
Heat detections
3,746
in a single hotspot: 1,683 MW
Energy released
100MW
sum of detected power

Where it burned

HOTSPOTS BY DAY 26 Jun26 Jun

How it evolved, day by day

27

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

This area had burned before

0% of the perimeter overlaps earlier fires recorded since 2016: 154 ha in 2019.

What happened to each town

  1. San Juan where it started
    44,459 ha reached on 27 Jun
    2.2 %

Burnt area inside each county, from crossing the official perimeter with administrative boundaries. The distance is from the town centre 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)
8 Jul after 28.9 °C 16 % 28 km/h 0.0 mm Moderate 16
9 Jul after 29.0 °C 9 % 29 km/h 0.0 mm High 23
10 Jul after 28.1 °C 9 % 23 km/h 0.0 mm High 23
11 Jul after 30.8 °C 10 % 26 km/h 0.0 mm High 28
12 Jul after 30.2 °C 13 % 38 km/h 0.0 mm Very high 41
13 Jul after 30.1 °C 19 % 32 km/h 1.5 mm High 26

Before and after, from space

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

Before · 19 Jun 2026
After · 3 Jul 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 3 July 2026 the air beside the fire reached 290 µg/m³ of PM2.5. That day averaged 118: 7.9 times the WHO daily guideline (15).

PM2.5 peak290 µg/m³
Days over the guideline8 days
PM10290 µg/m³
Optical depth1.48
24252627282930123456
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 · 3,746Every 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 Babylon fire last?
It burned between 26 June 2026 and 26 June 2026: 1 day, according to the start date recorded by United States agencies (MTBS / NIFC) and the heat detections seen by satellite.
How much area did it burn?
The official perimeter published by United States agencies (MTBS / NIFC) is 43,378 hectares (433.8 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered San Juan (44,459 ha, 2.2 %).
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

Satellite cross-check

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.

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.