NTSB investigations: Raytheon 1900D
6 cases on aircraft the registry lists as Raytheon 1900D. 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
| 2000 | 1 |
|---|---|
| 2003 | 1 |
| 2005 | 1 |
| 2007 | 1 |
| 2008 | 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 ('7150005'))
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 ('7150005'))
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 SEA08IA096Incident · No injuriesIncident investigationFinal reportRaytheon 1900D · Page, AZThe flight crew’s unprofessional behavior and deviation from standard operating procedures which resulted in an in-flight emergency.NTSB SEA08LA082Accident · Serious injuriesLimited investigationFinal reportRaytheon 1900D · Kayenta, AZThe flight crew's failure to execute a missed approach, which resulted in a runway excursion after landing. Contributing to the accident were the inoperative lights, weather conditions below published approach minimums, and the slush contaminated runway.NTSB DEN07LA101Accident · No injuriesLimited investigationFinal reportBeech 1900D · Laramie, WYThe pilot's improper decision, his misjudgment of his speed and distance, and his failure to perform a go-around resulting in the airplane overrunning the runway and striking an electrical box. Factors contributing to the accident were the failure of the crew…NTSB DEN06IA019Incident · No injuriesIncident investigationFinal reportBeech 1900D · Telluride, COThe tug driver's failure to maintain adequate clearance from the airplane resulting in the baggage cart striking the airplane's stabilon. A factor contributing to the incident was the tug driver's failure to consider the extra height of the cart in relation…NTSB DEN04IA024Incident · No injuriesIncident investigationFinal reportBeech 1900D · Denver, COthe ground personnel’s failure to maintain aircraft clearance, resulting in the collision. Contributing factors include ground communications not coordinated by the ground personnel, the flight crew's inadequate visual outlook and the parked airplane.NTSB NYC00IA150Incident · No injuriesIncident investigationFinal reportBeech 1900D · Rochester, NYThe reversal of landing gear hydraulic lines by company maintenance personnel. Factors related to the incident were the manufacturers omission of maintenance procedures, and the failure of an electrical switch for undetermined reasons.