NTSB investigations: Continental IO-360 series, AL
10 cases on aircraft whose registry engine model is Continental IO-360 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
| 1966 | 1 |
|---|---|
| 1970 | 3 |
| 1980 | 1 |
| 1986 | 1 |
| 1991 | 1 |
| 2005 | 1 |
| 2012 | 1 |
| 2014 | 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\" = '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 ('17025', '17045'))
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 ('17025', '17045'))
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 ERA14TA326Accident · Serious injuriesFinal reportCessna 336 · Mobile, ALThe pilot’s inadequate preflight fuel planning during which he did not ensure that there was adequate fuel in the main tanks for the flight, which resulted in a loss of engine power.NTSB ERA12LA273Accident · No injuriesLimited investigationFinal reportCessna T337B · Dothan, ALThe failure of the landing gear to extend and lock, despite troubleshooting attempts using normal and emergency procedures. The reason for the failure could not be determined because the systems were unavailable for testing.NTSB ATL05CA162Accident · Serious injuriesData collectionFinal reportPiper PA-34-200 · Greenville, ALThe loss of left engine power due to fuel system contamination and the pilot's failure to follow procedures and his improper use of the throttle and flight controls during the forced landing.NTSB ATL92LA018Accident · Serious injuriesLimited investigationFinal reportGlobe GC-1D · Brewton, ALA blockage of the fuel vent system which prevented the pilot from topping off the fuel system. A factor in this accident was the inadequate design by the manufacturer of the fuel vent system.NTSB ATL86FA055Accident · 2 fatalField investigationFinal reportCessna T337B · Talladega, ALThe acft collided with trees during the final approach to landing. The light conditions were dark, skies were clear and winds were calm. Prior to the accident, the plt had landed and visited the FBO from where the acft was recently purchased to correct some…NTSB ATL80DKJ05Incident · No injuriesClosedGlobe GC-1B · Spring Hill, ALNTSB MIA71DKJ28Accident · No injuriesClosedMaule M4-210 · Gadsden, ALNTSB MIA71DKJ01Accident · No injuriesClosedCessna 337 · Alexander Cty, ALNTSB MIA70DKJ26Accident · No injuriesClosedCessna 337B · Birmingham, ALNTSB MIA67D0096Accident · No injuriesClosedCessna 337 · Mobile, AL