# NTSB investigations: Raytheon 400A: Runway excursion

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB ERA21LA036](https://openairdocs.org/ntsb/ERA21LA036.md): Raytheon 400A · Fernandina Beach, FL · Accident · Minor injuries · Class 3 · Limited · Final report · Nov 1, 2020 · N456FL · Substantial damage
  > The flight crew's improper decision to land with a tailwind on a wet runway, which resulted in a runway overrun. Contributing to the accident was the copilot’s early retraction of the speed brakes and the pilot’s decision to turn off the anti-skid system.
- [NTSB CEN19LA090](https://openairdocs.org/ntsb/CEN19LA090.md): Beech 400 · Richmond, IN · Accident · No injuries · Class 2 · Limited · Final report · Feb 11, 2019 · N750TA · Substantial damage
  > The flight crew's decision to continue an unstable approach under conditions that exceeded the airplane's landing performance capabilities, which resulted in a runway overrun and impact with terrain.
- [NTSB CEN18LA094](https://openairdocs.org/ntsb/CEN18LA094.md): Raytheon 400A · Cleveland, OH · Accident · No injuries · Limited investigation · Final report · Feb 5, 2018 · N570TM · Substantial damage
  > The airplane's reduced braking performance due to an ice-covered runway, which resulted in a runway excursion. Contributing to the accident was the crew's selection of a runway with a tailwind.
- [NTSB ERA16LA131](https://openairdocs.org/ntsb/ERA16LA131.md): Raytheon 400A · Rome, GA · Accident · Minor injuries · Class 3 · Limited · Final report · Mar 14, 2016 · N465FL · Substantial damage
  > The pilots’ failure to use available sources of wind information before landing and recognize cues indicating the presence of the tailwind and conduct a go-around, which resulted in their landing with a significant tailwind and a subsequent runway overrun.

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
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 ('7150010')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '300' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb-events/300/sequence?model=7150010

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.