Second Flat (OR) — Incident File

Fireline Report · Incident File · Northwest

Second Flat (OR)

Persistent incident record · Updated 2026-10-14T02:04:55.750Z

105,854
Acres
99%
Contained
Moderate
Assessment confidence
Incident location

Regional orientation

Second Flat (OR) near OR. This map provides regional context; the detailed perimeter map follows when available.

Regional map locating Second Flat (OR)

Marker uses the reported incident location. Base map: Esri World Topographic Map.

Bottom Line

The Second Flat fire, reported 6 miles NE of Riley, OR, is listed at 105,854 acres and 99% contained in the WFIGS current perimeters feed (last update 2026-10-14). The incident remains active but is nearly contained; official operational details (personnel, structure impacts, evacuations, fire behavior) have not been publicly released.

Current Situation

Perimeter/registry snapshot: 105,854 acres; 99% contained; status Active; discovery 2026-07-24; location ~6 miles NE of Riley, OR (lat 43.608667, lon -119.439167). Last authoritative update in this packet: 2026-10-14T02:04:55.750Z (WFIGS Current Perimeters). No incident command or agency situation report was included. The perimeter data indicate the fire is largely controlled but remains an active incident in official feeds.

Significant Changes

  • Authoritative perimeter feed reports containment at 99% (2026-10-14) — indicates near-complete containment status in the official perimeter dataset.
  • No official operational updates (IMT briefings, ICS-209) were included in the packet to confirm resource posture, structure impacts, or evacuation status since the perimeter update.

Operational Concerns

  • Remaining 1% uncontained perimeter: potential for isolated hotspots or holdover smoldering that could lead to localized spread if not fully secured; status of mop-up/patrol operations not published.
  • Lack of publicly available resource and staffing information prevents assessment of suppression capacity for final containment and patrol.
  • No published information on structure exposure, damage, or critical infrastructure impacts in the packet — risk to communities cannot be assessed from available data.
  • No official fire-behavior or weather briefing was provided; inability to evaluate short-term risk of flare-ups or re-growth along the perimeter.

Operational Outlook

Observed: Perimeter feed shows near-complete containment; operational activity is likely focused on mop-up, patrol, and securing the remaining perimeter, but this is an assessment, not a confirmed operational order. Forecast/expected conditions: no official weather or suppression outlook was included in the packet. Without IMT or agency briefings, duration until full containment and transition to patrol/stabilization is unknown.

Public Safety

Evacuations and closures: No evacuation orders, warnings, or road/area closures were published in the provided package. Evacuation status cannot be verified from available sources.

Structure exposure: No confirmed reports of structures threatened, damaged, or destroyed are present in the packet. Structure impact status is unknown.

Fire Behavior and Weather

The packet contains no official description of current fire behavior. The 'Active' status and 99% containment suggest limited ongoing activity, but specific behavior (smoke, creeping, spotting, rate of spread) is not reported.

No weather information or forecasts were included in the packet. Potential weather-driven risks (wind events, humidity changes, lightning) are not addressed by available sources.

Resources

Current personnel and equipment assignments have not been publicly released.

Intelligence Gaps

  • No Incident Management Team (IMT) or ICS-209 style situational reports included — missing tactical objectives, priorities, and resource assignments.
  • No published personnel/equipment rosters or resource orders — cannot assess suppression capacity or readiness.
  • No official documentation of evacuations, road closures, or community impacts.
  • No confirmed structure damage reports or assessments of critical infrastructure impacts.
  • No recent fire behavior or weather briefings to evaluate short-term escalation risk.
  • Perimeter metadata field 'perimeter_source_updated_at' is empty in the packet; mapping currency beyond the summary timestamp is unclear.

Sources

  • WFIGS Current Perimeters (ArcGIS) — Source of authoritative perimeter data: reported 105,854 acres, 99% contained, Active status, discovery date 2026-07-24, location ~6 miles NE of Riley, OR; last update in packet 2026-10-14T02:04:55.750Z.
    Open source ↗

This page is a continuously updated incident file. Values reflect the most recent verified information available to Fireline Report and may change as agencies publish new data.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *