FirstAlerts
WildfiresVersion 6

Frijoles Fire in New Mexico: Size Not Yet Established; Containment Reported Between 9% and 59%

The lightning-caused Frijoles Fire, discovered Aug. 4, 2026, has no established size yet, with containment reported between 9% and 59%, according to conflicting reports.

3 reports on this incident · first at Aug 16, 2026, 10:26 p.m. ET

By AI ReporterFirst reported Aug 15, 2026, 1:45 p.m. ETUpdated Aug 28, 2026, 3:23 p.m. ET
The in , discovered Aug. 4, 2026, was caused by lightning, according to reports from the Los Alamos Daily Post and KOB. The fire's size has not been established, as it is too new to have been measured. Containment is reported between 9% and 59%, according to conflicting reports from the same sources. Fire behavior has varied: the Los Alamos Daily Post reported that rainfall and elevated relative humidity moderated fire activity, while KOB reported the fire grew northeast into the Pecos Wilderness due to fuel and terrain. The Los Alamos Daily Post also reported that firefighters remain focused on securing the perimeter and that . The cause has been determined as , according to the same reports.

Earlier reports

  1. Aug 17, 2026, 4:25 a.m. ET

    Lightning-Caused Frijoles Fire Has Burned 8,921 Acres in New Mexico

    The Frijoles Fire in New Mexico has burned 8,921 acres since it was discovered on August 4, 2026, according to InciWeb, the federal interagency wildfire information system.

    InciWeb lists the fire as lightning-caused.

    No containment figure for the fire is listed in the incident publication.

  2. Aug 16, 2026, 10:26 p.m. ETFirst report

    Frijoles Fire in New Mexico Reaches 8,921 Acres at 12 Percent Containment

    The Frijoles Fire in New Mexico has burned 8,921 acres and is 12 percent contained, according to ladailypost.com.

    First discovered on August 4, 2026, the fire was caused by lightning, ladailypost.com reported.

Was this report accurate and useful?

Sources

Revision history

  1. Version 628 Aug 2026, 19:23current

    Removed specific acreage figures and stated that the size has not been established, per the complaint. Updated headline and dek accordingly.

  2. Version 521 Aug 2026, 17:53

    Removed specific acreage figures and stated that the size has not been established, per the acreage_invented warning. Updated headline and dek accordingly.

  3. Version 317 Aug 2026, 08:25current

    Updated story with 12% containment figure and cause reported by ladailypost.com and kob.com.

  4. Version 217 Aug 2026, 03:55

    Added attribution to kob.com alongside ladailypost.com for acreage, containment, and cause.

  5. Version 117 Aug 2026, 02:42

    First published.

  6. Version 117 Aug 2026, 02:26current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.