NTSB investigations: Continental TSIO-360 series
17 cases on aircraft whose registry engine model is Continental TSIO-360 series, where the first occurrence was “Overrun”. 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
| 1983 | 1 |
|---|---|
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 1 |
| 1991 | 1 |
| 1993 | 3 |
| 1998 | 2 |
| 1999 | 1 |
| 2002 | 1 |
| 2005 | 1 |
| 2006 | 2 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17019', '17023')
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\" = 340))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17019', '17023')
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" = 340))
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 LAX07CA243Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Big Creek, IDThe pilot's misjudgment of distance and speed, which led to a long landing, and his delayed application of brakes that resulted in long landing and a runway overrun.NTSB NYC06CA206Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Lincoln Park, NJThe pilot's misjudged distance/speed which resulted in an overrun. A factor in the accident was the soft terrain.NTSB SEA06LA075Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Bullfrog Basin, UTA high airspeed at touchdown resulting in a high ground speed during the landing roll. Downhill sloping runway, a tailwind, the pilot's delayed remedial action and rough terrain off the end of the runway were factors.NTSB LAX05CA293Accident · No injuriesData collectionFinal reportPiper PA-28R-201T · Dunsmuir, CAthe pilot's delayed decision to abort the takeoff.NTSB CHI02LA257Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Kenmare, NDThe pilot's misjudgment of distance and speed. Factors associated with the accident were the sudden wind shift which resulted in a tailwind condition and the rough terrain encountered during the overrun landing.NTSB CHI99LA306Accident · No injuriesLimited investigationFinal reportPiper PA-34-220T · Salem, MOThe pilot in command misjudging the touchdown point.NTSB NYC98LA174Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Middlesboro, KYThe pilot's misjudgment of distance and speed, which resulted in runway overrun into a grass area where the gear collapsed. The tailwind was a contributing factor.NTSB CHI98LA077Accident · No injuriesLimited investigationFinal reportPiper PA-34-220T · Winterset, IAThe pilot misjudging his airspeed on final approach, resulting in a long touchdown and insufficient distance to stop on the remaining runway available.NTSB CHI93LA370Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · New Lenox, ILSelection of the wrong runway by the pilot after misreading the wind sock. The resultant tailwind was a related factor.NTSB BFO93LA072Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Simsbury, CTLack of braking action from the right brake. The pilot's failure to attain the proper touchdown point was a related factor.NTSB LAX93LA146Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Avalon, CAThe pilot's poorly planned approach, excessive airspeed, and failure to attain the proper touchdown point. The pilot's lack of familiarity with the airport is a factor in this accident.NTSB NYC91LA150Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201T · Tuckhannock, PAThe failure of the pilot to achieve a proper touchdown point. A factor related to the accident was the pilot's failure to make a go-around.NTSB ATL86LLT08Incident · No injuriesFinal reportPiper PA-34 · Smithville, TNThe acft ran off the departure end of the rwy during landing. The acft reportedly landed 1/2 way down the 3400 ft rwy. The plt stated in a post acc interview that he was 'too high too fast and too long.'NTSB LAX86LA067Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Glendale, AZAfter completing a LCL flight the plt returned to his home base arpt & proceeded to land on the 2400 ft long rwy. The plt reported that he was unable to stop at its end and collided with barricades and a fence. A witness reported that the acft skidded on the…NTSB LAX85LA404Accident · Minor injuriesLimited investigationFinal reportMooney M20K · Huntington Bch, CAThe plt acknowledged that on short final approach to the 2330 ft-long rwy, the acft's speed was 'a little hot', & during ldg flare the acft 'floated in ground effect'. After the acft bounced 3 times the plt decided to go around & he applied full pwr. The plt…NTSB ANC85FA023Accident · No injuriesField investigationFinal reportPiper PA-28RT-201T · Anchorage, AKThe acft crashed during the takeoff roll by running off the departure end of the rwy, gliding over a hwy & impacting trees. According to the plt, 'on takeoff, we accelerated to 90-95 KTS, but the acft did not respond to back pressure for lift off. We…NTSB NYC83LA213Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Rangeley, METhe pilot stated that a downdraft was encountered on the approach and in adding power to counteract, the airspeed increased over the threshold as the downdraft subsided. The acft floated 1/3 down the 2700 ft rwy and the remaining 1800FT was insufficient to…