Beech B36TC
FAA incident reports · 103
Matched to the registry by N-number and event date, newest first.
Query with SQL
duckdb -csv -c "SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('1151609')
ORDER BY event_date DESC, report_number 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 report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('1151609')
ORDER BY event_date DESC, report_number 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.
Incident 19840107009419IBeech B36TC · Payson, AZHard landing. Started to porpoise nose gear collapsed. Ran off runway.Incident 19831110070789IBeech B36TC · Gaithersburg, MDLanded long and fast on wet runway unable to stop, slid off end of runway down an incline.Accident 19830530072029ABeech B36TC · Farmingdale, NYVeered off ILS and became too low after marker inbound. Struck a powerline static cable. Weather below minimums.
Back to Beech B36TC