FirstAlerts
Plane CrashesVersion 2

One dead in Pipistrel Sinus 912 crash near Columbus, Mississippi

The accident record lists one person on board and one fatality; the National Transportation Safety Board is investigating and the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 10:03 a.m. ET
One person was killed when a light aircraft crashed near Columbus, Mississippi, on May 31, 2026, at about 5:36 p.m. local time, according to the accident record. The investigation is open and details may change. The accident record identifies the aircraft as a Pipistrel d.o.o. Sinus 912, registration , and lists it as destroyed. The record states there was one person on board and one fatality, and classifies the flight as a Part 91 general aviation flight. Geographic reference data places Columbus in Lowndes County, Mississippi, at a settlement elevation of 230 feet, and lists the city as 3.4 miles NW of Columbus Lowndes County Airport (KUBS), 8.8 miles SSW of Shockley Field Airport and 10.0 miles ENE of Golden Triangle Regional Airport (KGTR). That reference data locates the settlement only and says nothing about where the accident occurred or what happened. The National Transportation Safety Board is listed in the accident record as the investigating body. The cause has not been determined.

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.

Terrain elevation
230 ft
Nearest aerodrome
3.4 miles NW of Columbus Lowndes County Airport (KUBS/UBS)

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:03current

    Corrected the aerodrome bearings to match the geographic reference data as given and clarified that the elevation and distances describe the settlement, not the accident site.

  2. Version 15 Aug 2026, 15:45

    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.