FirstAlerts
Plane CrashesVersion 2

NTSB Investigating Fatal Cirrus SR22T Crash Near Lincoln, Montana

The accident record lists one person aboard and one fatality in the October 25 crash; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 10:53 a.m. ET
A single-engine Cirrus SR22T was destroyed in a crash near Lincoln, Montana, at about 3:15 a.m. local time on October 25, 2025, according to the accident record. The record lists one person aboard and one fatality. The investigation is open, and this account reflects only what has been recorded so far. The accident record identifies the aircraft as a , registration , and lists the operator as . The record classifies the flight as a Part 91 general aviation flight. The National Transportation Safety Board is investigating. The cause has not been determined. Aircraft registry records describe as a single-engine piston landplane with a Continental Motors TSIO-550-K engine, serial number 8601, built in 2022 and three years old at the time of the crash. The registry lists the registered owner as T And S Dvbe Inc; the owner of record is not necessarily the operator of the flight, the pilot, or otherwise connected to it. Public business records and the company's own website describe T AND S DVBE, INC. as a California construction-services firm founded in 2010 and based in Redding, California, supplying road construction materials, traffic control, trucking and related services, with a federal SAM registration and USDOT motor carrier number 2643704; those sources do not describe any aviation operating business. SBA and SAM records list Taren Forde as president and Steven Forde as vice president; the investigation has made no finding connecting them to this accident. Geographic reference data, geocoded from the place name rather than from the accident site, places Lincoln County, Montana, at a settlement elevation of 4,816 feet, about 20 miles east-northeast of Troy Airport (K57S), 21 miles north of Libby Airport (KS59) and 31 miles west-southwest of Crystal Lakes Resort Airport (01MT). That describes the place only and says nothing about what happened. As a matter of record, the NTSB database, which begins in 2008, contains 33 other cases involving the , of which 8 involved a fatality. That is a count of cases, not a safety rate, and it says nothing about the cause of this accident. The NTSB investigation remains open.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Registration
N740TS
Type
Cirrus Design Corp SR22T — single-engine piston landplane
Engines
CONT MOTOR TSIO-550-K
Built
2022-01-01 (3 years old)
Registered owner
T And S Dvbe IncThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
4,816 ft
Nearest aerodrome
20 miles ENE of Troy Airport (K57S)

Sources

Revision history

  1. Version 27 Aug 2026, 14:53current

    Clarified that the elevation and aerodrome distances are geocoded from the place name and not the accident site, corrected the aerodrome identifiers to match the reference data, and added that no investigative finding connects the named company officers to the accident.

  2. Version 15 Aug 2026, 19:40

    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.