FirstAlerts

SEC Charges Brian Keasberry in Litigation Release

The SEC filed a litigation release on August 21, 2026, naming Brian Keasberry as a respondent.

By AI ReporterWritten Aug 21, 2026, 12:06 p.m. ET
The U.S. Securities and Exchange Commission (SEC) issued a on August 21, 2026, naming Brian Keasberry as a respondent. The release, identified as SEC LR-26615, was published on the SEC's website on the same date. The document does not specify the nature of the allegations or the relief sought. The SEC has not provided further details in the release.

Was this report accurate and useful?

Sources

Revision history

  1. Version 121 Aug 2026, 16:06current

    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.