Fatal NTSB investigations: U/A Canada PT6A-27-28
13 cases on aircraft whose registry engine model is U/A Canada PT6A-27-28. 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
| 1986 | 1 |
|---|---|
| 1987 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2007 | 2 |
| 2012 | 2 |
| 2016 | 1 |
| 2019 | 1 |
| 2022 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('61504'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('61504'))
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 ERA23FA024Accident · 2 fatalClass 3 · FieldFinal reportBeech E-90 · Marietta, OHStructural icing on the tailplane that resulted in a tailplane stall and subsequent loss of control.NTSB CEN20MA044Accident · 5 fatalClass 2 · MajorFinal reportPiper PA 31T · Lafayette, LAThe pilot’s loss of airplane control due to spatial disorientation during the initial climb in instrument meteorological conditions.NTSB CEN17WA049Accident · 4 fatalForeign investigationBeech E 90 · Toledo, SpainNTSB CEN13FA105Accident · 2 fatalField investigationFinal reportBeech E-90 · Amarillo, TXThe pilot’s loss of control of the airplane after encountering icing conditions and heavy to extreme turbulence and the subsequent exceedance of the airplane’s design limit, which led to an in-flight breakup.NTSB CEN12FA421Accident · 1 fatalField investigationFinal reportBeech E90 · Karnack, TXThe pilot's inadvertent flight into thunderstorm activity, which resulted in the loss of airplane control and the subsequent exceedance of the airplane's design limits and in-flight breakup. Contributing to the accident was the failure of air traffic control…NTSB LAX08FA026Accident · 2 fatalField investigationFinal reportBeech A100 · Chino, CAThe pilot's failure to maintain a positive climb rate during an instrument takeoff. Contributing to the accident was the low visibility.NTSB LAX07FA200Accident · 2 fatalField investigationFinal reportBeech E90 · Carlsbad, CAThe pilot's failure to maintain clearance from wires during an instrument takeoff attempt. Contributing to the accident were fog, reduced visibility, and the low ceiling.NTSB CHI02FA199Accident · 2 fatalField investigationFinal reportBeech E-90 · Bloomington, ILThe cause of the accident is undetermined.NTSB NYC00FA067Accident · 4 fatalField investigationFinal reportBeech C-90 · Somerset, KYthe failure of the pilot to follow his approach clearance, and subsequent descent into unprotected airspace which resulted in a collision with the guy wire. Factors were the failure of the air traffic controller to verify the approach he cleared the pilot to…NTSB NYC90FA199Accident · 3 fatalField investigationFinal reportPiper PA-31T2 · Mattapan, MAThe pilot's improper in-flight planning/decision, which resulted in his failure to maintain control of the aircraft. Factors related to the accident were: failure of the left fuel control unit, and the adverse weather conditions.NTSB MKC89FA027Accident · 6 fatalField investigationFinal reportBeech E-90 · Locust Grove, ARThe pilot's failure to maintain obstacle clearance altitude and exceeding the minimum descent altitude published in the approach procedure.NTSB ATL88MA048Accident · 2 fatalMajor investigationFinal reportBeech C90 · Beaufort, SCAt 0938, while clbg thru 9000', the plt was clrd to clb to FL 210. Aprx 10 min later, the ATC ctlr noted the acft's mode c rtrn wasn't being displayed on his scope. He tried to adz the plt, but couldn't establish radio contact. The acftbroke up in flt & the…NTSB MIA86MA057Accident · 2 fatalMajor investigationFinal reportPiper PA-31T · Jacksonville, FLWhile being vectored for an ILS rwy 7 apch, the plt was told to maint 3000' & advised he was flwg a Boeing 727. The min apch alt bfr intercepting the ILS glide slope (g/s) at the final apch fix/outer marker (om) was 1900'. As the acft was apchg the om, the…