NTSB investigations: Beech 35
11 cases on aircraft the registry lists as Beech 35, where the first occurrence was “Airframe/component/system failure/malfunction”. 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 |
|---|---|
| 1988 | 1 |
| 1991 | 2 |
| 1992 | 1 |
| 1994 | 2 |
| 1996 | 3 |
| 1997 | 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.aircraft_model_code IN ('1151502')
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\" = 130))
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 ('1151502')
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" = 130))
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 CHI97IA122Incident · No injuriesIncident investigationFinal reportBeech 35 · Spokane, WAthe vibration of the fuselage was due to flutter.NTSB ATL97LA027Accident · No injuriesLimited investigationFinal reportBeech 35 · Lafayette, GAfailure of maintenance personnel to balance the ruddervator assemblies after they had been reskinned and painted, which resulted in flutter and subsequent damage to the empennage.NTSB CHI96LA274Accident · No injuriesLimited investigationFinal reportBeech 35 · Yankton, SDan improper in-flight decision by the pilot when he shut the engine off as the airplane approached the landing runway. Factors associated with this accident were an inadequate maintenance inspection by the mechanic when the actuating arm fracture was not…NTSB SEA96LA181Accident · No injuriesLimited investigationFinal reportBeech 35 · Spokane, WAfailure (cracking) of the aft fuselage bulkhead for undetermined reason(s).NTSB CHI94FA212Accident · 3 fatalField investigationFinal reportBeech A35 · Lakeville, MNThe jamming of the elevator control which resulted in the pilot's inability to control the pitch attitude of the airplane. The airplane encountered a stall-spin and impacted level terrain in an uncontrolled descent.NTSB FTW94LA189Accident · No injuriesLimited investigationFinal reportBeech 35 · Mckinney, TXThe ailerons being locked by a foreign object.NTSB DEN92FA028Accident · No injuriesField investigationFinal reportBeech 35 · Nucla, COImproper static balance of the ruddervators following rebuilding/repainting, which resulted in empennage flutter.NTSB SEA92LA027Accident · Serious injuriesLimited investigationFinal reportBeech 35 · Klamath Falls, ORPilot factor in that he failed to follow IFR procedures. Factors to the accident were generator failure, operation with known deficiencies with equipment, and poor inflight planning.NTSB SEA91FA261Accident · No injuriesField investigationFinal reportBeech 35 · Walla Walla, WAImproper static balance of the ruddervators following rebuilding/repainting, which resulted in empennage flutter. Improper installation of the trim tabs and an encounter with turbulence were related factors.NTSB NYC88LA130Accident · No injuriesLimited investigationFinal reportBeech 35 · New Haven, CTDuring engine start the throttle jammed in the full forward position and could not be pulled back to the idle position to retard the power. The aircraft started rolling and collided with an unoccupied parked aircraft. Examination of the throttle control…NTSB FTW83LA169Accident · Minor injuriesLimited investigationFinal reportBeech 35 · El Paso, TXOn a flt after an annual inspn, the plt could not retract the gear, using the normal electrical sys. It remained extended with the green safe light on & the gear pointer indicating down. He tried to assist the normal sys with the manual handcrank, although…