# NTSB investigations: Aero Commander S2R: In flight collision with terrain/water

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 CHI07LA162](https://openairdocs.org/ntsb/CHI07LA162.md): Aero Commander S2R · Watford City, ND · Accident · 1 fatal · Limited investigation · Final report · Jun 5, 2007 · N8835Q · Destroyed
  > The agricultural pilot's failure to maintain clearance from the terrain while maneuvering to avoid power lines. The power lines were a contributing factor in the accident.
- [NTSB LAX95LA261](https://openairdocs.org/ntsb/LAX95LA261.md): Aero Commander S2R · Huron, CA · Accident · Minor injuries · Limited investigation · Final report · Jul 21, 1995 · N5609X · Substantial damage
  > Failure of the pilot to maintain sufficient altitude above the ground after diverting his attention to read a map. Factors relating to the accident were: darkness, which reduced the pilot's visual cues concerning outside references while reading the map; and…
- [NTSB SEA89LA048](https://openairdocs.org/ntsb/SEA89LA048.md): Aero Commander S2R · Cottonwood, ID · Accident · No injuries · Limited investigation · Final report · Feb 8, 1989 · N5620X · Substantial damage
  > The pilot misjudging his altitude due to the white out conditions. Contributing to the accident was the pilots lack of experience in this aircraft and this type of operation.
- [NTSB FTW83LA446](https://openairdocs.org/ntsb/FTW83LA446.md): Aero Commander S2R · Napoleonville, LA · Accident · No injuries · Limited investigation · Final report · Sep 29, 1983 · N8890Q · Substantial damage
  > The acft dragged a wing in the sugarcane crop during a start of a swath run. According to the operator the plt was looking at a map as he approached the run. After the wing dragged the acft yawed 90 degrees and settled into the crop. The engine and right main…

## 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 ('0143022')
    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" = 230))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?model=0143022&occurrence=230

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