NTSB investigations: Boeing B75N1

6 cases on aircraft the registry lists as Boeing B75N1, where the first occurrence was “In flight collision with object”. 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

19832026
NTSB investigations: Boeing B75N1 per year, 1983–2026: 6 cases
19831
19871
19901
19921
19951
20051

Latest 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 ('1380144')
      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\" = 220))
  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.

NTSB SEA06LA006Accident · No injuriesLimited investigationFinal reportBoeing B75N1 · Burlington, WAThe pilot's failure to maintain clearance from a utility pole during a precautionary landing. The utility pole was a factor.Oct 15, 2005 · N5158N · Substantial damageNTSB LAX96LA066Accident · No injuriesLimited investigationFinal reportBoeing B75-N1 · Chino, CAthe pilot's failure to see and avoid light poles. A poorly planned approach was a factor.Nov 29, 1995 · N5114N · Substantial damageNTSB CHI92LA288Accident · No injuriesLimited investigationFinal reportBoeing B75N1 · Belvidere, ILThe pilot's failure to maintain adequate clearance from obstacles during the aborted landing. Related factors are the failure to maintain directional control, and the pilot's lack of total experience in the type of operation.Sep 23, 1992 · N1943H · Substantial damageNTSB CHI90LA256Accident · Serious injuriesLimited investigationFinal reportBoeing B75N1 · Marseilles, ILThe pilot-in-command's failure to maintain adequate visual outlook to avoid collision with a wire while conducting intentional low level flight.Sep 5, 1990 · N62438 · Substantial damageNTSB FTW87DPJ03Accident · Minor injuriesFinal reportBoeing B75N1 · Fairmont, OKDuring the pull up at end of swath run pilot misjudged power line clearance. Top line caught on aircraft and caused uncontrolled descent to ground.Mar 8, 1987 · N5102N · Substantial damageNTSB FTW83FA332Accident · Serious injuriesField investigationFinal reportBoeing B75N1 · Webb, TXThe pilot stated that before flying under wires a bird struck and broke a plastic fuel gauge mounted under the center section of the upper wing. Fuel reportedly sprayed onto the windscreen and the pilots face restricting his forward visibility. In an effort…Jul 12, 1983 · N59085 · Destroyed