NTSB investigations: Continental IO-360 series, VA
14 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
| 1973 | 1 |
|---|---|
| 1979 | 1 |
| 1983 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1993 | 2 |
| 2000 | 1 |
| 2003 | 1 |
| 2006 | 1 |
| 2008 | 1 |
| 2011 | 1 |
| 2019 | 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\" = 'VA' 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" = 'VA' 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 CEN19LA258Accident · Minor injuriesClass 3 · LimitedFinal reportCessna R172 · North Garden, VAA total loss of engine power due to the failure of the oil pump drive gear.NTSB ERA12LA033Accident · No injuriesLimited investigationFinal reportCessna R172K · Williamsburg, VAA total loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.NTSB MIA08LA035Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Spotsylvania, VAThe pilot's failure to follow the checklist and failure to achieve the proper touchdown point during a forced landing. Contributing to the accident was a loss of engine power due to a cracked No. 4 top sparkplug insulator, resulting in pre-ignition/detonation…NTSB NYC06CA103Accident · No injuriesData collectionFinal reportMaule M-5-210C · Linville, VAThe pilot's improper decision to depart with a tailwind.NTSB IAD03LA036Accident · 1 fatalLimited investigationFinal reportCessna R172K · Richmond, VAThe passenger's failure to remain clear of the propeller. Factors included the passenger's recent use of marijuana, the pilot's inadequate pre-flight inspection, and the night lighting conditions.NTSB NYC00LA196Accident · No injuriesLimited investigationFinal reportCessna 337C · Chesapeake, VAThe pilot's failure to follow the published go-around procedure. Factors were the pilot's improper evaluation of the wind conditions, and a tailwind.NTSB BFO93FA178Accident · 1 fatalField investigationFinal reportMaule M-4-210C · Staunton, VAInadequate preflight by the pilot which resulted in inadequate altitude to clear the embankment during the initial climb. Factors in this accident were a tailwind on takeoff and rising terrain at the departure end of the grass airstrip.NTSB NYC93LA092Accident · No injuriesLimited investigationFinal reportCessna P337 · Holland, VAThe pilot's improper inflight planning during the approach for landing, resulting in a touchdown too FAR down the runway, and the subsequent collision with objects off the end of the runway.NTSB BFO88FA085Accident · 1 fatalField investigationFinal reportMaule M-5-210C · Clarksville, VAInflight loss of control as a result of pilot disorientation when the pilot tried to conduct VFR flight into IMC. Low clouds, poor visibility, fog and poor decision are contributing factors.NTSB BFO87LA051Accident · Minor injuriesLimited investigationFinal reportMaule M-4-210C · Burnt Chimney, VAThe plt attempted to land on a 1400 ft grass airstrip. The plt later stated that during the lndg roll the passg alerted him to the fact that they would not stop on the rwy. This caused the plt to start a go-around followed by a 2nd attempt to stop. The plt…NTSB BFO86FID05Accident · No injuriesFinal reportMaule M-4-210C · Saluda, VAWhile on final apch, the acft struck the top side of a van which was on a road off the apch end of the rwy. Both main landing gear were sheared off and the plt landed the acft in a grass area along the side of the rwy. The plt reported that a high sink rate…NTSB ATL83LA332Accident · Serious injuriesLimited investigationFinal reportStarduster II · Wakefield, VADuring flt, the eng lost power & the propeller stopped. The passenger recalled hearing a 'ticking' sound from the eng prior to the power loss. According to the plt & the passenger, the acft stalled & began to spin as the plt tried to turn into a bean field…NTSB IAD80DID02Accident · No injuriesClosedCessna T-41 · Richmond, VANTSB IAD74DID11Accident · No injuriesClosedCessna 172E · Fort Eustis, VA