# Accident 20191110017009A: Cessna U206C, Mexico, MO, November 10, 2019

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 10, 2019, 16:01 local time
- Place: Mexico, MO
- Airport: Flying Shamrock
- Damage: Substantial damage
- Phase of flight: Ground/Ramp/Ma
- Operating rules: General operating rules (Part 91)
- Location: 39.0378° N, 91.7256° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.0378&lon=-91.7256&mi=10
- Aircraft: N29173, registered now (https://openairdocs.org/aircraft/N29173) (OpenAirDocs)
- Registry model: Cessna U206C (registry code 2073332, https://openairdocs.org/model/cessna-u206c) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: CESSNA U206C
- Reported engine: PRATT & WHITNEY CANADA PT-6A
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- Pilot flight hours: 8,524 total, 315 in this make and model, 15 in the last 90 days
- NTSB investigation: [NTSB GAA20CA072](https://openairdocs.org/ntsb/GAA20CA072) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20191110017009A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

AFTER AIRCRAFT ENGINE START, THE PILOT EXITED THE AIRCRAFT TO DISCONNECT THE EXTERNAL POWER UNIT AND PULL THE CHOCKS. WHEN THE CHOCKS WERE REMOVED, THE AIRCRAFT BEGAN ROLLING DOWN A SLIGHT INCLINE WITHOUT ANYONE IN THE PILOT'S SEAT. THE PILOT RE-ENTERED THE AIRCRAFT, BUT WAS UNABLE TO REGAIN CONTROL BEFORE THE AIRPLANE CAME TO REST IN A GROVE OF TREES.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB GAA20CA072](https://openairdocs.org/ntsb/GAA20CA072), Nov 10, 2019: Cessna U206 (N29173), Mexico, MO, substantial damage. Probable cause: The pilot's failure to properly set the parking brake before exiting an operating airplane, which resulted in a runaway airplane and subsequent impact with trees.

## Other reports on N29173 (6)

Matched to the same aircraft by N-number and date.

- [Accident 20240525005589A](https://openairdocs.org/incident/20240525005589A), May 25, 2024: Cessna U206C (N29173), Butler, MO, Destroyed. During a parachute jump run at 14,000FT, the first jumper's reserve parachute was accidentally deployed pulling the jumper out of the aircraft. The jumper…
- [Incident 19931020045869I](https://openairdocs.org/incident/19931020045869I), Oct 20, 1993: Cessna U206C (N29173), California City, CA, 1 fatal. Chutist mismanaged both main chute and reserve chute while making a free fall jump. Impacted the ground.
- [Incident 19910811054859I](https://openairdocs.org/incident/19910811054859I), Aug 11, 1991: Cessna U206C (N29173), California City, CA, 1 fatal. Main chute only partially deployed. First jump. Opened reserve chute too late to fully deploy. Fatally injured.
- [Incident 19840819055359I](https://openairdocs.org/incident/19840819055359I), Aug 19, 1984: Cessna U206C (N29173), California City, CA, 1 fatal. Deployed both chutes while falling on his back. Lines from both chutes tangled around victim and failed to open.
- [Incident 19830114076099I](https://openairdocs.org/incident/19830114076099I), Jan 14, 1983: Cessna U206 (N29173), California City, CA, 1 fatal. Parachutist failed to open either parachute after free fall maneuvering for photographer.
- [Incident 19810315024709I](https://openairdocs.org/incident/19810315024709I), Mar 15, 1981: Cessna 206CESSNA (N29173), California City, CA, 1 fatal. Zx main parachute deployed then streamed. Jumper broke away from main and reserved opened at 250 ft but not in time

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

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