Fire near Washington (US)

48.78°N, 121.14°W · first detected on 22 September at 23:01

What the satellites measured

This fire was tracked from 22 September at 23:01 to 23 September at 22:44, through 42 satellite detections. The detected extent reaches 665 ha.

Detected extent
665 ha
Cumulative power
391 MW
Peak power, one pixel
67 MW
VIIRS and MODIS detections
42

These four figures cover the polar orbits alone, the ones that measure an area. The pass table below also counts geostationary detections, more frequent but too coarse for geometry, and its power column sums a whole pass where the peak above is that of a single pixel.

“Detected extent” is not “burned area”: it is the union of the ground footprints of the satellite pixels, and a pixel counts in full (375 m for VIIRS, 1 km for MODIS) even when only a forest edge is burning. Compared with press figures it is in practice one and a half to three times the area reported. Detections taken at the edge of the scan swath, too coarse to measure anything at all, are excluded. These figures come from thermal detection and are not an official assessment: only the emergency services and the competent authorities are authoritative.

Replay how the fire spread

The map is framed on this fire's footprint and loads only its detections. The timeline below covers the period in which satellites saw it, from the first to the last detection, with twelve hours before and twenty-four after; the ticks on the bar mark the emergency services' announcements that fall within it. The cursor opens on the most powerful pass, and playback replays the whole fire in about thirty seconds. “1 h” shows what is burning within an hour of the chosen moment : the map then follows the power curve below and empties when it falls. “24 h” stacks twenty-four hours : a fire stays visible between two satellite passes, which come two to four times a day. Both are true, but they say different things.

How the radiative power evolved

One point per satellite pass: the sum of the fire radiative power measured over the fire. This is the curve that says whether the fire eased off or picked up again, which no cumulative figure shows. The window covers 3 days; beyond that, clustering would merge two successive fires in the same place.

Fire dynamics

Loading history…

Satellite passes in detail

PassPower summed over the passDetectionsSensor
23 September at 22:4318 MW2N21
23 September at 12:564 MW1N21
23 September at 12:1113 MW14N20
23 September at 05:34145 MW3Terra
22 September at 23:5731 MW6N20
22 September at 23:38165 MW22N
22 September at 23:01218 MW20N21
22 September at 22:1715 MW2N20
22 September at 21:57101 MW12N
22 September at 21:21524 MW14N21
22 September at 13:5116 MW5N
22 September at 13:1661 MW26N21
22 September at 12:3199 MW30N20
22 September at 12:12291 MW58N
22 September at 11:34311 MW44N21
22 September at 06:32915 MW10Terra
22 September at 00:50415 MW5Aqua
22 September at 00:171,698 MW18N20
21 September at 23:57409 MW13N
21 September at 23:22563 MW16N21

6 other fires near Washington (US)

Separate fires, apart in time or in space, not pieces of this one. A single municipality can have several over one summer, and a forest massif often covers more than a hundred square kilometres.

Follow live

The map shows active fires in 3D, with smoke plumes, forecast wind, drop zones and the live position of water bombers tracked by ADS-B, anywhere in the world.

Open the fire map

Take the data of this fire with you

A ready-to-use archive, paid once, no subscription. It contains:

From €20.00 excl. VAT, six formats to choose from, link valid for 30 days.

Download the data

Pro subscribers: included. €49 excl. VAT a month, no commitment. The public map stays free. Discover GISFire Pro

© 2026 SARO · Gistin. All rights reserved. The interface, its presentation and the contents of GISFire are protected; reproducing or imitating them requires written permission. The source data remain the property of their respective producers, see the credits.

Legal notice · Privacy policy ·  · GISFire v2.4.2