GARDA FALLSPierce, Washington | 2026
Latest available agency record · Exact WFIGS/NIFC source record · More reports in Washington
At a glance
The latest available WFIGS/NIFC record for GARDA FALLS in Pierce, Washington reports 308 acres and 0% containment.
Containment does not tell you whether the fire is out.
Recent saved changes
- Added or returned to the observed source feedSaved observations: Nov 2, 2026, 1:15 PM ET → Nov 14, 2026, 7:04 PM ET
Latest agency update: Nov 12, 2026, 7:47 PM ET - Left the observed source feedSaved observations: Nov 2, 2026, 12:21 PM ET → Nov 2, 2026, 1:15 PM ET
Latest agency update: Oct 19, 2026, 1:28 PM ET
Observed source changes do not establish ignition or extinguishment. Reported acreage can be revised after mapping corrections. View saved report history →
GARDA FALLS map
The fire pin and blue ring mark this incident's reported point. They are not a fire boundary or evacuation zone.
About GARDA FALLS
The agency recorded discovery on Aug 24, 2026, 4:03 PM ET. The reported cause is listed as "Natural".
The agency describes the location or incident as: “null Miles null from null,”.
Jurisdiction is listed as NPS.
- Discovery
- Aug 24, 2026
- Reported cause
- Natural
- Agency
- NPS
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 GARDA FALLS
Saved WFIGS/NIFC observations show how the agency-reported area and containment have changed. WildfireSignal does not estimate values between reports.
Reference lookback: 24 hours. Nearest available earlier report; this is not an exact rolling-window measurement.
Saved observations: Nov 17, 2026, 9:06 AM ET → Nov 18, 2026, 9:17 AM ET
Reference lookback: 7 days. Nearest available earlier report; this is not an exact rolling-window measurement.
Saved observations: Nov 2, 2026, 1:15 PM ET → Nov 18, 2026, 9:17 AM ET
Since the previous saved report
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.
Recorded range: 308 to 308 acres. See the saved agency reports for exact observations.
Recorded range: 0 to 0%. See the saved agency reports for exact observations.
Seven-day report progression
One latest saved observation is shown for each day with history available.
| Date | Reported acres | Containment | Agency updated |
|---|---|---|---|
| Nov 18, 2026 ET | 308 | 0% | |
| Nov 17, 2026 ET | 308 | 0% | |
| Nov 16, 2026 ET | 308 | 0% | |
| Nov 15, 2026 ET | 308 | 0% | |
| Nov 14, 2026 ET | 308 | 0% |
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.
| Saved by WildfireSignal | Agency record updated | Reported acres | Containment | Feed presence |
|---|---|---|---|---|
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | Not in observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed | ||
| 308 | 0% | In observed feed |
Fire details
- Reported location
- Pierce, Washington
- Discovery
- Reported cause
- Natural
- Jurisdictional agency
- NPS
- Incident identifier
- 2026-WAMRP-000968
- Situation report date
- Reported coordinates
- 46.9220, -121.7198
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 GARDA FALLS
Where is GARDA FALLS?
The official incident record places it in Pierce, Washington. The map pin is a reported location, not the full fire boundary.
How large is GARDA FALLS?
The latest available record reports 308 acres (approximately 124.6 hectares). This is reported incident size, not a measurement of current flames, and agencies can revise it.
How contained is GARDA FALLS?
The latest available record reports 0% containment. Containment describes control work intended to stop spread. It is not the percentage extinguished or an all-clear for nearby communities.
When was GARDA FALLS discovered?
The reported discovery date is Aug 24, 2026, 4:03 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.
WFIGS / NIFC
Use this for the reported fire name, acreage, containment, incident location and agency update time shown on this page.
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.
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.