NTSB investigations: Cessna 150M, 2003

9 cases on aircraft the registry lists as Cessna 150M. 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

19642026
NTSB investigations: Cessna 150M, 2003 per year, 1964–2026: 1,284 cases
19641
19651
19681
19691
19701
19746
197543
197672
1977123
1978104
197984
198057
198148
198253
198340
198440
198528
198631
198738
198832
198939
199034
199127
199226
199330
199432
199527
199626
199716
199822
199931
200017
200110
20027
20039
20049
200512
20069
200712
20089
20092
20106
20115
20127
20131
20144
201511
20163
20173
20186
20195
20204
20213
20221
20233
20246
20254
20262

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 year(c.\"eventDate\") = 2003
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2071830'))
  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.

NTSB LAX04LA247Accident · No injuriesLimited investigationFinal reportCessna 150M · Tucson, AZthe pilot's misjudged flare and improper recovery from a bounced landing, which resulted in a pilot induced porpoise/oscillation.Dec 10, 2003 · N63149 · Substantial damageNTSB NYC04LA030Accident · No injuriesLimited investigationFinal reportCessna 150M · Wooster, OHThe inadequate visual lookout of the student pilot of the Cessna 150M, which resulted in an on-ground collision with a Cessna 150K that was taking off.Nov 9, 2003 · N66748 · 2 aircraft · Minor damageNTSB NYC04LA011Accident · 2 fatalLimited investigationFinal reportCessna 150M · Wax, KYThe pilot's failure to maintain obstacle clearance. Low altitude flight is a contributing factor.Oct 16, 2003 · N3807V · Substantial damageNTSB NYC03CA193Accident · No injuriesData collectionFinal reportCessna 150M · Jetersville, VAThe pilot's delayed decision to abort the takeoff, which resulted in an overrun. A factor was the dew on the grass.Sep 7, 2003 · N63600 · Substantial damageNTSB NYC03LA121Accident · Serious injuriesLimited investigationFinal reportCessna 150M · Londonderry, VTThe pilots inadvertent flight into instrument meteorological conditions and his failure to maintain a safe altitude above the rising terrain. Factors related to the accident were the low ceilings and rising terrain.Jun 5, 2003 · N704TG · Substantial damageNTSB CHI03LA129Accident · Minor injuriesLimited investigationFinal reportCessna 150M · Freeport, ILThe pilot's misjudgment of distance and altitude, and his failure to maintain obstacle clearance.May 18, 2003 · N2842V · Substantial damageNTSB FTW03LA119Accident · No injuriesLimited investigationFinal reportCessna 150 · Pearland, TXThe pilot's failure to maintain runway alignment. Contributing factors were the pilot's diverted attention to the banner staging area, and the ditch.Mar 8, 2003 · N8994U · Substantial damageNTSB DEN03LA044Accident · No injuriesLimited investigationFinal reportCessna 150M · Gateway, COthe pilot's failure to maintain aircraft control. Contributing factors were the snow-covered runway.Mar 3, 2003 · N714NF · Substantial damageNTSB CHI03LA054Accident · No injuriesLimited investigationFinal reportCessna 150M · Charleston, MOthe inadequate flare by the pilot. Factors were the loose trim tab cable for undetermined reasons.Jan 12, 2003 · N66507 · Substantial damage