NTSB investigations: Cessna 150J, MS
8 cases on aircraft the registry lists as Cessna 150J. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1970 | 1 |
|---|---|
| 1971 | 1 |
| 1984 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1995 | 1 |
| 2016 | 1 |
| 2025 | 1 |
Where
Latest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"eventStateOrRegion\" = 'MS' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2071820'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."eventStateOrRegion" = 'MS' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2071820'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB CEN25LA121Accident · No injuriesClass 4 · LimitedFinal reportCessna 150J · Greenville, MSThe pilots’ inadequate fuel planning and failure to monitor the fuel consumption which resulted in a total loss of engine power due to fuel exhaustion and a subsequent forced landing into wooded terrain. Contributing to the accident was the flight…NTSB GAA16CA414Accident · No injuriesData collectionFinal reportCessna 150 · New Albany, MSThe pilot's failure to maintain an appropriate pitch attitude during landing, which resulted in an initial nose wheel contact, followed by a nose gear collapse, and the airplane came to rest in a nose down position.NTSB MIA96LA023Accident · No injuriesLimited investigationFinal reportCessna 150 · Saltillo, MSThe failure of the pilot-in-command to perform fuel comsumption calculations before and during the flight.NTSB MIA89LA135Accident · Serious injuriesLimited investigationFinal reportCessna 150M · Olive Branch, MSFuel exhaustion caused by the pilot exceeding the fuel endurance of the airplane.NTSB MIA88LA190Accident · No injuriesLimited investigationFinal reportCessna 150J · Carthage, MSWhile on a personal flt, during the upwind leg after completion of the second touch-and-go landing, the plt reported that the eng sputtered. He then turned crosswind & attempted to land on a section of road under construction. Shortly before touchdown a…NTSB ATL85LA009Accident · Minor injuriesLimited investigationFinal reportCessna 150J · Brookhaven, MSA total power loss occurred due to fuel exhaustion. During a forced landing, the plt stalled the acft while clearing over power lines, then the acft collided with trees as it descended out of control. A successful test run of the eng was performed.…NTSB MIA72FKQ13Accident · No injuriesClosedCessna 150J · Brookhaven, MSNTSB MIA70FKQ01Accident · No injuriesClosedCessna 150J · Southaven, MS