NTSB investigations: Beech A36TC
11 cases on aircraft the registry lists as Beech A36TC, where the first occurrence was “In flight encounter with weather”. 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 | 2 |
|---|---|
| 1984 | 1 |
| 1986 | 2 |
| 1992 | 1 |
| 1993 | 1 |
| 2000 | 1 |
| 2003 | 1 |
| 2007 | 2 |
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.aircraft_model_code IN ('1151603', '1151613')
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\" = 240))
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.aircraft_model_code IN ('1151603', '1151613')
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" = 240))
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 SEA08FA045Accident · 3 fatalField investigationFinal reportBeech A36TC · Minersville, UTThe flying pilot's continued flight into instrument meteorological conditions and failure to maintain adequate terrain clearance during cruise. Contributing to the accident were low clouds, reduced visibility and mountainous terrain.NTSB CHI07FA176Accident · 1 fatalField investigationFinal reportBeech A36TC · Cannon Falls, MNThe pilot's continued flight into instrument meteorological conditions, which resulted in spatial disorientaton and loss of control.NTSB LAX03FA182Accident · 5 fatalField investigationFinal reportBeech A36TC · Los Angeles, CAthe pilot's in-flight loss of control due to spatial disorientation, and failure to maintain airspeed, which resulted in a stall/spin. Also causal was the pilot's disregard of the weather information provided and his attempt to continue VFR flight into IMC. A…NTSB LAX01FA001Accident · 4 fatalField investigationFinal reportBeech A36TC · San Juan Batist, CAthe pilot's in-flight decision to continue flight into instrument weather conditions at an altitude that did not maintain an adequate terrain clearance, which resulted in a collision with terrain. Factors were a dark night, clouds, fog, mountainous terrain,…NTSB LAX94LA045Accident · Serious injuriesLimited investigationFinal reportBeech A-36 · Florence, AZthe pilot's poor inflight planning and decision making by continuing the flight into adverse weather conditions. Factors contributing to this accident were: not obtaining a preflight weather briefing, not following the airplane flight manuals, and exceeding…NTSB SEA92FA140Accident · 1 fatalField investigationFinal reportBeech A36TC · Ballantine, MTThe pilot-in-command's physical impairment and his continued VFR flight into instrument meteorological conditions. Factors relating to the accident were: the weather conditions and the hilly terrain.NTSB DEN86FA150Accident · 2 fatalField investigationFinal reportBeech A36TC · Marietta, OKThe plt obtained a wx briefing and was advised of scattered thunderstorm activity along his route of flt. The plt then filed an IFR flt plan from wiley post airport, Oklahoma city, OK, to houston intercontinental airport, TX. The plt and his wife took off at…NTSB LAX86FA140Accident · 3 fatalField investigationFinal reportBeech A36TC · Woodfords, CAThe wx deteriorated while the acft was cruising in IMC at 17,000 ft. moderate turbulence & icing conditions in the layered clouds were reported by other nearby flying acft. The plt informed ARTCC that he 'lost the autopilot,' & the acft's course began…NTSB MKC84FA106Accident · 2 fatalField investigationFinal reportBeech B36 · Webb City, MOThe plt was advised by springfield tower that icing conditions existed along his proposed route of flt. However, he elected to takeoff, & about 4 min later, the plt advised that he had encountered rime ice. He continued the flt to joplin, picking up more ice…NTSB LAX83FA166Accident · 3 fatalField investigationFinal reportBeech A36TC · Sedona, AZDuring preflt briefings, the plt was briefed to expect deteriorating wx conditions with associated flt precautions for mountain obscurement, icing & moderate turbulence. The wx briefings were complete, except due to an inoperative circuit, the 0654 prescott &…NTSB FTW83FA108Accident · 1 fatalField investigationFinal reportBeech A36TC · Addison, TXThe non-instrument rated, student plt used another person's name while filing an instrument flt plan. When he contacted ground control for departure, he was advised that the arpt had just become IFR. After some confusion concerning canceling & filing flt…