NTSB investigations: Continental 0-300 series, CA

14 cases on aircraft whose registry engine model is Continental 0-300 series, where the first occurrence was “Loss of engine power(total) - nonmechanical”. 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

19822026
NTSB investigations: Continental 0-300 series, CA per year, 1982–2026: 14 cases
19821
19832
19841
19862
19891
19901
19921
19931
19941
19961
19971
19981

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\" = 'CA' AND c.\"eventCountry\" = 'USA'
    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')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 353))
  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 LAX98LA183Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Mariposa, CAFuel exhaustion due to the pilot's inadequate preflight planning, and improper in-flight decision not to make a precautionary landing for additional fuel.Jun 5, 1998 · N2573L · Substantial damageNTSB LAX97LA103Accident · Minor injuriesLimited investigationFinal reportCessna 172F · San Pablo Bay, CAtotal loss of engine power due to carburetor icing and the pilot's failure to use carburetor heat.Feb 14, 1997 · N3757F · Substantial damageNTSB LAX96LA143Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Upland, CAfuel system contamination and the pilot's intentional operation of a known unairworthy aircraft.Mar 23, 1996 · N7044T · Substantial damageNTSB LAX94LA359Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Corona, CAThe pilot's poor preflight planning/preparation and fuel consumption calculations. Fuel exhaustion and the rough terrain were factors in this accident.Sep 11, 1994 · N4328L · Substantial damageNTSB LAX93LA268Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Danville, CAThe pilot's poor fuel consumption calculations. Contributing to this accident was the downsloping terrain.Jun 27, 1993 · N2791U · Substantial damageNTSB LAX92LA084Accident · No injuriesLimited investigationFinal reportCessna 172H · Arcata, CACarburetor icing and the failure of the pilot to use carburetor heat.Jan 8, 1992 · N1608F · Substantial damageNTSB LAX90LA196Accident · Serious injuriesLimited investigationFinal reportCessna 172E · Brentwood, CAThe pilot improperly calculated the fuel consumption causing the airplane to sustain a total loss of power due to fuel exhaustion.May 25, 1990 · N5714T · Substantial damageNTSB LAX89LA235Accident · No injuriesLimited investigationFinal reportCessna 172E · Mariposa, CAStudent pilot's miscalculation of the fuel supply which led to a loss of engine power due to fuel exhaustion.Jun 26, 1989 · N7744U · Substantial damageNTSB LAX87LA021Accident · Serious injuriesLimited investigationFinal reportCessna 172C · Michigan Bar, CADuring a pleasure cross-country flight, the aircraft experienced an enging failure. Examination of the fuel tanks revealed that both tanks were empty of fuel. The carburetor was removed from the engine and found to contain approximately 1 tablespoon of fuel.…Oct 19, 1986 · N8449X · Substantial damageNTSB LAX86LA095Accident · No injuriesLimited investigationFinal reportCessna 172 · Woodland, CAThe pilot reported that he experienced a loss of power shortly after leveling off at about 1,000 MSL. The power loss was smooth and rapid. During the subsequent forced landing roll-out, the acft nosed over onto its back. Post accident investigation disclosed…Jan 19, 1986 · N6421E · Substantial damageNTSB LAX84LA127Accident · No injuriesLimited investigationFinal reportCessna 172E · Selma, CAThe plt stated he was practicing landings when after takeoff following a full stop landing, the 'motor stopped then started again momentarily.' He landed in a vineyard. Responding officers from the sherriff's department observed no fuelin the aircraft tanks.Jan 2, 1984 · N5314T · Substantial damageNTSB LAX84LA001Accident · No injuriesLimited investigationFinal reportCessna 172 · Salinas, CAThe acft nosed over during a forced landing after the engine quit on an inital approach to land. The pilot had taken offfrom monterey CA at 1100 hours PDT to fly to Salinas CA with an estimated 4-5 gallons of fuel on board the acft. At 1150PDT the acft landed…Oct 1, 1983 · N8426X · Substantial damageNTSB LAX83LA110Accident · No injuriesLimited investigationFinal reportCessna 172G · Antioch, CAAccording to the left seat pilot the engine sputtered at 2200 RPM and quit. There were wires obstructing the field selected for landing. The acft went under most of them but clipped one service electric line. The acft landed & rolled about 75 feet before…Feb 19, 1983 · N4611L · Substantial damageNTSB LAX82DA220Accident · No injuriesFinal reportCessna 172 · Lancaster, CADuring flight, the pilot landed at an airport to refuel. However, the fuel trucks were locked up and no one was at the UNICOM office, even though, the airport directory indicated the field was attended and fuel should have been available. The pilot…Jun 14, 1982 · N1580Y · Substantial damage