Blackbird Mountain Guides Responds to Cal/OSHA Avalanche Fines
The guide service has answered allegations behind $151,300 in proposed fines over avalanche-terrain travel.
3 reports on this incident · first at Aug 21, 2026, 6:22 p.m. ET
Earlier reports
Aug 21, 2026, 6:23 p.m. ET
Cal/OSHA Seeks $151,300 in Fines Against Blackbird Mountain Guides in Avalanche Case
Cal/OSHA has proposed $151,300 in fines against Blackbird Mountain Guides, according to NBC Bay Area. The fines stem from seven alleged violations, including failing to correct the imminent hazard posed by traveling in avalanche terrain when the avalanche danger was rated high.
The administrative proceeding is at the charging stage, and the allegations have not been decided. The case is being handled by Cal/OSHA, which issued the proposed fines. The matter remains open and unresolved.
Aug 21, 2026, 6:22 p.m. ETFirst report
Cal/OSHA Fines Blackbird Mountain Guides $151,300 in Avalanche Case
Cal/OSHA has issued $151,300 in fines against Blackbird Mountain Guides, according to a report from NBC Bay Area. The administrative proceeding alleges seven violations, including failing to correct the imminent hazard posed by traveling in avalanche terrain when the avalanche danger was rated high.
The case is at the charging stage, and the allegations have not been decided. The company has not yet responded publicly.
Was this report accurate and useful?
Sources
Revision history
- Version 121 Aug 2026, 22:52current
First published.
- Version 121 Aug 2026, 22:22current
First published.
- Version 121 Aug 2026, 22:23current
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.