# NTSB investigations: Aero Commander 500: Airframe/component/system failure/malfunction

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 MIA05LA079](https://openairdocs.org/ntsb/MIA05LA079.md): Rockwell Aero Commander 500 · San Juan, PR · Accident · No injuries · Limited investigation · Final report · Mar 12, 2005 · N8498C · Substantial damage
  > The failure of the pilot to follow the emergency checklist and his inadvertent operation of the airplane with known discrepancies resulting in landing overrun and on-ground collision with a ditch during the landing roll.
- [NTSB ATL04LA065](https://openairdocs.org/ntsb/ATL04LA065.md): Aero Commander 500 · Allendale, SC · Accident · No injuries · Limited investigation · Final report · Jan 11, 2004 · N800SL · Substantial damage
  > The failure of the hydraulic brake system accumulator due to a ruptured diaphragm. A factor was the ditch.
- [NTSB MIA93IA083](https://openairdocs.org/ntsb/MIA93IA083.md): Aero Commander 500 · Everglades City, FL · Incident · No injuries · Incident investigation · Final report · Mar 7, 1993 · N3836C · Minor damage
  > The preexisting fatigue cracking of the propeller hub arm in the bearing retention radius due to polishing and wear of the radius from contact with the split rings, resulting in a propeller blade separating from the propeller hub on the takeoff ground run,…
- [NTSB LAX83LA074](https://openairdocs.org/ntsb/LAX83LA074.md): Aero Commander 500 · Dixon, CA · Accident · No injuries · Limited investigation · Final report · Jan 18, 1983 · N6239B · Substantial damage
  > Reportedly, the acft was on an air taxi cargo flt, operated by air express, hayward, CA. The acft reportedly departed reno, NV without a flt plan for a flt to sacramento & hayward, cal. While en route, the acft had an electrical failure. The plt stated that…

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

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

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