NTSB investigations: Continental GO-300 series, AL
10 cases on aircraft whose registry engine model is Continental GO-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
| 1964 | 1 |
|---|---|
| 1965 | 3 |
| 1967 | 1 |
| 1983 | 1 |
| 1984 | 1 |
| 2001 | 1 |
| 2008 | 1 |
| 2023 | 1 |
Where
Open the mapLatest 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\" = 'AL' 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 ('17024'))
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" = 'AL' 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 ('17024'))
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 ERA23LA331Accident · No injuriesClass 3 · LimitedFinal reportCessna 175 · Wetumpka, ALA total loss of engine power due to the separation of the No. 3 connecting rod from the crankshaft.NTSB ERA09LA026Accident · Serious injuriesLimited investigationFinal reportCessna 175A · Foley, ALThe pilot’s failure to maintain adequate airspeed during initial climb, resulting in a stall and collision with terrain. Contributing to the accident was the pilot’s lack of recent experience.NTSB MIA02LA035Accident · No injuriesLimited investigationFinal reportCessna 175A · Fairhope, ALThe pilot's failure to check wind conditions prior to landing resulting in a landing with a tailwind, on a wet runway, and damage to the airplane during a ground loop in an attempt to stop the airplane before over running the runway.NTSB ATL84LA228Accident · No injuriesLimited investigationFinal reportCessna 175 · Enterprise, ALA witness observed the airplane slipping on final apch. The aircraft lost too much altitude and hit the terrain short of the runway. The airplane damage indicated that the pilot failed to correct the slip condition in time to arrest the descent.NTSB ATL83LA148Accident · No injuriesLimited investigationFinal reportCessna 175 · Tuscaloosa, ALThe aircraft landed off the runway in soft terrain during a forced landing and nosed down. According to the pilot the engine began to run rough at 400 AGL on takeoff. He turned back toward the field and the engine quit. The pilot could not complete the turn…NTSB MIA67F0402Accident · No injuriesClosedCessna 175 · Lanett, ALNTSB MIA66D0035Accident · No injuriesClosedCessna 175B · Wadley, ALNTSB MIA66F0103Accident · No injuriesClosedCessna 175 · Guntersville, ALNTSB MIA65D0082Accident · No injuriesClosedCessna 175 · Tishabee, ALNTSB UNK64X1405Accident · No injuriesClosedCessna 175 · Montgomery, AL