# NTSB investigations: Flt management computing sys

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 DCA22LA133](https://openairdocs.org/ntsb/DCA22LA133.md): Boeing 737-9 · Pittsburgh, PA · Incident · No injuries · Class 3 · Limited · Final report · Jun 21, 2022 · N37513 · No damage
  > The flightcrew’s misidentification of the intended landing runway, which resulted in approach to and landing on the wrong runway. Contributing to the incident was the distraction caused by the dual reset of the flight management computer displays.
- [NTSB WPR16FA054](https://openairdocs.org/ntsb/WPR16FA054.md): Cessna 525 · Cedar Fort, UT · Accident · 2 fatal · Field investigation · Final report · Jan 18, 2016 · N711BX · Destroyed
  > The pilot's loss of control due to spatial disorientation while operating in instrument meteorological conditions, which resulted in an exceedance of the airplane's design stress limitations, and a subsequent in-flight breakup. Contributing to the accident…
- [NTSB DCA14MA081](https://openairdocs.org/ntsb/DCA14MA081.md): Airbus A320 - 214 · Philadelphia, PA · Accident · No injuries · Class 2 · Major · Final report · Mar 13, 2014 · N113UW · Substantial damage
  > the captain's decision to reject the takeoff after the airplane had rotated. Contributing to the accident was the flight crew's failure to follow standard operating procedures by not verifying that the airplane's flight management computer was properly…
- [NTSB DCA13MA133](https://openairdocs.org/ntsb/DCA13MA133.md): Airbus A300 - F4 622R · Birmingham, AL · Accident · 2 fatal · Class 1 · Major · Final report · Aug 14, 2013 · N155UP · Destroyed
  > the flight crew's continuation of an unstabilized approach and their failure to monitor the aircraft's altitude during the approach, which led to an inadvertent descent below the minimum approach altitude and subsequently into terrain. Contributing to the…

## 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 f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '01023460'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb-findings/01023460/cases

---
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.