NTSB investigations: Continental TSIO-520 series, VA
11 cases on aircraft whose registry engine model is Continental TSIO-520 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
| 1982 | 1 |
|---|---|
| 1984 | 1 |
| 1988 | 1 |
| 2004 | 1 |
| 2006 | 1 |
| 2010 | 2 |
| 2012 | 1 |
| 2013 | 2 |
| 2016 | 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 ('17040'))
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 ('17040'))
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 GAA16CA235Accident · No injuriesData collectionFinal reportCessna 182P · Williamsburg, VAThe pilot's failure to maintain directional control during the landing in variable direction and gusting wind conditions, resulting in a landing off the side of the runway and impact with a drainage culvert.NTSB ERA14FA075Accident · 1 fatalField investigationFinal reportBeech A36TC · Chatlottesville, VAThe pilot’s failure to position the fuel selector handle in a fuel tank detent, which resulted in a total loss of engine power due to fuel starvation. Contributing to the pilot’s fatal injuries was the separation of his shoulder harness due to overload in an…NTSB ERA14LA006Accident · 4 fatalLimited investigationFinal reportCessna 340A · Hampton Roads, VAThe pilot’s failure to maintain airplane control due to spatial disorientation in low-visibility conditions while maneuvering during a missed approach. Contributing to the accident was the pilot’s ineffective use of the onboard GPS equipment.NTSB ERA12CA288Accident · No injuriesData collectionFinal reportCessna 180J · Abingdon, VAThe passenger’s inadvertent blockage of the rudder pedals, which resulted in the pilot’s inability to maintain directional control during the landing roll.NTSB ERA10FA195Accident · 1 fatalField investigationFinal reportPiper PA46 · Roanoke, VAA malfunction of the flight controls for undetermined reasons.NTSB ERA10FA161Accident · 1 fatalField investigationFinal reportCessna T303 · Louisa, VAThe pilot's failure to maintain aircraft control and secure the right engine during a loss of engine power after takeoff. Contributing to the accident was the loss of engine power on the right engine for undetermined reasons.NTSB NYC06FA145Accident · 2 fatalField investigationFinal reportRaytheon B36TC · North Garden, VAThe pilot's failure to maintain airspeed while turning onto the final approach, which resulted in an inadvertent stall/spin and subsequent impact with terrain.NTSB IAD05LA022Accident · No injuriesLimited investigationFinal reportCessna 414 · Petersburg, VAThe partial loss of engine power for undetermined reasons, and the pilot's failure to maintain adequate airspeed (Vmc).NTSB BFO88FA014Accident · No injuriesField investigationFinal reportCessna T210N · Sterling, VAAbt 2.7 hrs after takeoff, the student plt & instructor (CFI) were practicing instrument apchs when the eng lost pwr. The CFI took control of the acft & made a forced lndg, but the acft was damaged on rough terrain. An exam of the acft revealed the right &…NTSB ATL85FA011Accident · 1 fatalField investigationFinal reportBeech QU-22A 1074 · Fancy Gap, VAAt about the 2,800 ft level the acft flew into the mountainous terrain which was obscured by clouds. Witnesses observed 2 previous attempts to fly over the rising terrain under the cloud layer. Departure and dest arpt, plt identity, and acft owner are all…NTSB ATL82FID06Accident · No injuriesFinal reportCessna 402B · Newport News, VAThe pilot stated that during his first ILS approach, the localizer needle fluctuated to the left. He made corrective turns to the left. When he broke out of the clouds at the decision height (dh), he observed the runway to the right and made a missed…