McCullyBaker City, Baker, Oregon | 2026

100% contained in report · Exact WFIGS/NIFC source record · More reports in Oregon

View fire map Official resources
Share & export
Export reports CSV
Share

At a glance

The latest available WFIGS/NIFC record for McCully in Baker City, Baker, Oregon reports 13,604 acres and 100% containment.

Reported area13,604acres / 5,505.3 hectares
Reported containment100%
Discovery dateAug 22, 2026Reported discovery, not verified ignition time
Reported locationBaker City, Baker, OregonAgency location record
100%

Containment does not tell you whether the fire is out.

Agency record updated
Retrieved by WildfireSignal

Recent saved changes

  1. Reported containment: 91% → 100%Saved observations: Nov 18, 2026, 2:02 PM ET → Nov 18, 2026, 4:58 PM ET
    Latest agency update: Nov 18, 2026, 2:58 PM ET

Observed source changes do not establish ignition or extinguishment. Reported acreage can be revised after mapping corrections. View saved report history →

McCully map

The fire pin and blue ring mark this incident's reported point. They are not a fire boundary or evacuation zone.

Oregon overview →
Filters
Time Window
Heat Intensity
Very strong>330 K
Strong300-330 K
Satellite heat Map layer loading…
Wildfire Overview
Current map view
Heat detections --
Very strong --
Last update --
Layers
Official fire Perimeter Strong heat Very strong
Reported incident locationSatellite heat, not attributed to this fireAgency perimeter when available via Layers

About McCully

The agency recorded discovery on Aug 22, 2026, 5:28 PM ET. The reported cause is listed as "Natural".

The agency describes the location or incident as: “22 Miles NW from Baker City, OR”.

The available agency report lists 1 personnel. Jurisdiction is listed as USFS. Reported fire behavior: Minimal.

Discovery
Aug 22, 2026
Reported cause
Natural
Personnel
1
Agency
USFS

Source: facts and saved reports from WFIGS/NIFC agency records. Check the report date for the timing of these details. How we use this data.

Saved report history for McCully

Saved WFIGS/NIFC observations show how the agency-reported area and containment have changed. WildfireSignal does not estimate values between reports.

Saved interval: 27h 42m
Reported areaNo reported change
Containment+9 pts

Reference lookback: 24 hours. Nearest available earlier report; this is not an exact rolling-window measurement.

Saved observations: Nov 18, 2026, 7:54 AM ET → Nov 19, 2026, 11:37 AM ET

Saved interval: 170h 25m
Reported areaNo reported change
Containment+9 pts

Reference lookback: 7 days. Nearest available earlier report; this is not an exact rolling-window measurement.

Saved observations: Nov 12, 2026, 9:11 AM ET → Nov 19, 2026, 11:37 AM ET

First saved by WildfireSignalNov 7, 2026, 12:27 PM ET
Latest meaningful saved changeNov 18, 2026, 4:58 PM ET

Since the previous saved report

Reported areaNo reported changeCompared with reports saved Nov 19, 5:22 AM ET and Nov 19, 11:37 AM ET
Reported containmentNo reported changeCompared with reports saved Nov 19, 5:22 AM ET and Nov 19, 11:37 AM ET

These figures compare agency reports saved at different times; they are not a measured spread rate. Acreage can change after mapping corrections, and unchanged values do not mean conditions on the ground are unchanged.

Seven-day report progression

One latest saved observation is shown for each day with history available.

Recent daily saved reports for McCully
DateReported acresContainmentAgency updated
Nov 19, 2026 ET13,604100%
Nov 18, 2026 ET13,604100%
Nov 17, 2026 ET13,60491%
Nov 16, 2026 ET13,60491%
Nov 15, 2026 ET13,60491%
Nov 14, 2026 ET13,60491%
Nov 13, 2026 ET13,60491%
View all saved agency reports (48)

WildfireSignal begins saving agency reports when it first observes a fire. Up to 48 recent observations are kept for 35 days. A compact incident identity and latest sourced summary are retained for up to five years so stable citations can outlast the detailed snapshot window; earlier detailed reports are not reconstructed.

Observed report snapshots for McCully
Saved by WildfireSignalAgency record updatedReported acresContainmentFeed presence
13,604100%In observed feed
13,604100%In observed feed
13,604100%In observed feed
13,604100%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed
13,60491%In observed feed

Fire details

Reported location
Baker City, Baker, Oregon
Discovery
Reported cause
Natural
Personnel reported
1
Primary fuel / fuel model
Timber (Litter and Understory)
Secondary fuel / fuel model
Short Grass (1 foot)
Reported fire behavior
Minimal
Behavior detail
Smoldering
Behavior detail
Smoldering
Behavior detail
Smoldering
Jurisdictional agency
USFS
Management organization
Type 4 IC
Incident complexity
Type 4 Incident
Incident identifier
2026-ORWWF-000531
Situation report date
Reported coordinates
44.8279, -118.2808

Optional facts appear only when present in the feed. Agency abbreviations and fuel-model labels are shown as reported, without guessing missing details.

Questions about McCully

Where is McCully?

The official incident record places it in Baker City, Baker, Oregon. The map pin is a reported location, not the full fire boundary.

How large is McCully?

The latest available record reports 13,604 acres (approximately 5,505.3 hectares). This is reported incident size, not a measurement of current flames, and agencies can revise it.

How contained is McCully?

The latest available record reports 100% containment. Containment describes control work intended to stop spread. It is not the percentage extinguished or an all-clear for nearby communities.

When was McCully discovered?

The reported discovery date is Aug 22, 2026, 5:28 PM ET. Discovery time may differ from ignition time; elapsed time does not establish continuous burning.

Where should I check evacuation orders and road closures?

Use local emergency management, the sheriff or other law enforcement, and official fire-agency updates. WildfireSignal does not verify evacuation zones, open roads, or safe travel routes. The official-information section provides starting points; it does not establish that orders are present or absent.

Why can the map and the incident report differ?

Agency records, mapped perimeters and NASA satellite detections are updated on different schedules. Satellite heat near a fire is not automatically attributed to that incident. Older or unavailable data does not establish that an area is safe.

Source details & methodologyHow this page uses agency, satellite and map data

This page combines agency incident reporting with separate satellite and map layers. They can update at different times and answer different questions.

Agency report

WFIGS / NIFC

Use this for the reported fire name, acreage, containment, incident location and agency update time shown on this page.

Satellite observations

NASA FIRMS

Heat detections can show recent thermal activity, but they are not an official acreage or containment figure and are not automatically attributed to this incident.

Boundary context

Agency perimeter layer

When a perimeter is available in the map layers, it may have a different timestamp from the incident report. The fire pin itself is only a reported location.