NTSB investigations: Continental 0-300 series, 2001

28 cases on aircraft whose registry engine model is Continental 0-300 series. 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: Continental 0-300 series, 2001 per year, 1964–2026: 3,125 cases
1964183
1965197
1966237
1967250
1968163
1969112
1970114
1971113
197296
197387
197453
197551
197661
197768
197865
197949
198037
198148
198231
198331
198434
198531
198638
198739
198835
198927
199028
199123
199229
199330
199422
199532
199629
199718
199831
199928
200027
200128
200230
200337
200428
200532
200627
200728
200823
200918
201022
201117
201220
201321
201412
201522
201617
201720
201822
201923
202013
202130
202217
202319
202417
202525
202610

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\") = 2001
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022'))
  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 LAX02FA040Accident · No injuriesField investigationFinal reportCessna 172C · Corona, CAa loss of engine power due to the pilot's improper use of the carburetor heat controls while in weather conditions conducive to serious carburetor icing.Dec 5, 2001 · N1834Y · Substantial damageNTSB NYC02LA024Accident · No injuriesLimited investigationFinal reportCessna 172D · Argyle, NYThe pilot's failure to maintain aircraft control while maneuvering.Nov 2, 2001 · N36SK · Substantial damageNTSB NYC02FA012Accident · 3 fatalField investigationFinal reportCessna 172 · South Hero, VTThe pilot's failure to maintain aircraft control during the takeoff. Factors in this accident were wind gusts and the airplane's high gross weight condition.Oct 18, 2001 · N8255B · DestroyedNTSB MIA02LA006Accident · No injuriesLimited investigationFinal reportCessna 170 · Bennettsville, SCThe blockage of the fuel vent and also the collapsed fuel supply line resulting in the total loss of engine power due to fuel starvation.Oct 5, 2001 · N4180V · Substantial damageNTSB IAD02LA001Accident · Serious injuriesLimited investigationFinal reportCessna 172B · Phillips, MELoss of engine power due to a blockage of the left fuel tank vent line with mud, and the subsequent inadvertent stall.Oct 4, 2001 · N7591X · Substantial damageNTSB SEA02LA001Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Lindsay, MTThe pilot's failure to maintain an altitude clear of terrain. A factor was intentional low altitude flight.Oct 1, 2001 · N3910F · DestroyedNTSB NYC01LA227Accident · No injuriesLimited investigationFinal reportCessna 170B · Wildwood, NJthe pilot's inadequate compensation for wind conditions. Factors were the crosswind and the gusts.Sep 28, 2001 · N3465D · Substantial damageNTSB LAX01LA295Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Skull Valley, AZthe loss of engine power during takeoff for undetermined reasons. A contributing factor was the lack of suitable terrain for the ensuing emergency landing.Sep 22, 2001 · N5792A · Substantial damageNTSB FTW01LA190Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Odom, ARthe pilot's failure to follow the proper procedures for hand-propping an airplane.Aug 23, 2001 · N9154B · Substantial damageNTSB LAX01LA282Accident · Minor injuriesLimited investigationFinal reportCessna 172-A · Groveland, CAa loss of engine power due to water contamination forced the pilot to land in an unsuitable area resulting in collision with a tree.Aug 18, 2001 · N7198T · Substantial damageNTSB ATL01LA101Accident · No injuriesLimited investigationFinal reportCessna 172 · Mobile, ALThe pilot's improper landing flare that resulted in a hard landing. A factor was the pilot induced porpoise.Aug 2, 2001 · N7006A · Substantial damageNTSB CHI01LA219Accident · No injuriesLimited investigationFinal reportCessna 172C · Grand Island, NEThe procedures for using carburetor heat not followed by the student pilot and the unsuitable terrain encountered during the forced landing. Additional factors included the carburetor icing conditions, the carburetor icing, the student pilot's lack of…Jul 18, 2001 · N1860Y · Substantial damageNTSB NYC01FA147Accident · 1 fatalField investigationFinal reportCessna 172 · Newfane, VTThe pilot's failure to maintain aircraft control during takeoff. A factor was the pilot's impairment due to a narcotic painkiller and antihistamine.Jun 16, 2001 · N7106T · Substantial damageNTSB LAX01LA209Accident · No injuriesLimited investigationFinal reportCessna 170B · Payson, AZThe pilot's failure to maintain directional control and improper corrective action while landing in a quartering tailwind condition. A contributing factor was his lack of experience in the type of operation.Jun 15, 2001 · N4338B · Substantial damageNTSB NYC01LA142Accident · Minor injuriesLimited investigationFinal reportCessna 170A · South Charlesto, WVThe pilot's failure to maintain directional control while landing.Jun 11, 2001 · N9509A · Substantial damageNTSB ANC01LA061Accident · No injuriesLimited investigationFinal reportCessna 172 · Wasilla, AKAn undershoot due to the pilot's failure to maintain a proper glide path during a VFR final approach to landing. A factor in the accident was a downdraft.May 31, 2001 · N8054X · DestroyedNTSB SEA01LA098Accident · No injuriesLimited investigationFinal reportCessna 172 · Rogersburg, WAThe pilot's failure to maintain aircraft control while on final approach for landing. A tailwind was a factor.May 19, 2001 · N4053F · Substantial damageNTSB MIA01LA139Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Pierce, FLa loss of engine power due to fuel exhaustion which resulted in a forced landing, and subsequent impact with a sign and a ditch.May 6, 2001 · N8664U · Substantial damageNTSB ANC01LA054Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Soldotna, AKThe pilot's failure to refuel the airplane, and subsequent fuel exhaustion. A factor in the accident was an inadvertent stall during an emergency descent/landing.May 5, 2001 · N5530T · Substantial damageNTSB FTW01LA106Accident · No injuriesLimited investigationFinal reportCessna 172G · N. Little Rock, ARthe pilot's delayed go-around on landing.Apr 26, 2001 · N3860L · Substantial damageNTSB LAX01LA149Accident · Serious injuriesLimited investigationFinal reportCessna 172B · Lancaster, CAThe pilot's delay reversing course while flying toward rising terrain in a box canyon. Factors in the accident included a downdraft on the lee side of a ridge forming the box canyon, high density altitude, and the pilot's improper use of flaps.Apr 18, 2001 · N4672L · Substantial damageNTSB FTW01FA098Accident · 1 fatalField investigationFinal reportCessna 172E · Bay City, TXthe pilot's delay in taking remedial action (contacting ATC) after he became lost/disoriented during a night cross country flight, which resulted in a forced landing due to fuel exhaustion. Contributing factors to the accident were the pilot's failure to…Apr 13, 2001 · N5638T · DestroyedNTSB LAX01LA132Accident · No injuriesLimited investigationFinal reportCessna 170B · Lincoln, CAThe certified flight instructor's inadequate supervision of his dual student who used excessive braking on landing resulting in the airplane's nose over.Mar 31, 2001 · N4315B · Substantial damageNTSB FTW01LA075Accident · No injuriesLimited investigationFinal reportCessna 172F · Clovis, NMthe pilot's failure to maintain directional control during take off roll resulting in a ground loop. A contributing factor was the crosswind.Mar 6, 2001 · N5175F · Substantial damageNTSB DEN01LA055Accident · No injuriesLimited investigationFinal reportCessna 172F · Larkspur, COthe flight instructor inadvertently stalling the airplane during a forced landing. Contributing factors were fuel exhaustion due to inadvertent opening of the fuel drain, lack of familiarity with the airplane, inadequate supervision of the flight, and the…Feb 26, 2001 · N8389U · Substantial damageNTSB DEN01LA051Accident · No injuriesLimited investigationFinal reportCessna 172 · Grand Junction, COFailure by the pilot to maintain directional control of the aircraft during landing roll. A factor was lack of total pilot experience in aircraft make and model.Jan 31, 2001 · N6830A · Substantial damageNTSB LAX01FA070Accident · 2 fatalField investigationFinal reportCessna 172F · San Luis Obispo, CAThe pilot's failure to maintain a proper climb rate to VFR conditions on-top.Jan 7, 2001 · N383CA · DestroyedNTSB FTW01LA064Accident · No injuriesLimited investigationFinal reportCessna 172 · Pine Bluff, ARthe pilot's failure to maintain directional control during the forced landing on a gravel road. Contributing factors were the pilot's delay in using carburetor heat and the loose gravel.Jan 6, 2001 · N8984B · Substantial damage