CHI00FA265 · Cessna 340A
Cessna 340A · Accident: in flight collision with terrain/water en route
From 0V6 to Rapid City Regional Airport (RAP)
Event
- NTSB case
- CHI00FA265
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 3 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 340A
- Aircraft type
- Cessna 340
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N34DD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 0V6To Rapid City Regional Airport (RAP), Rapid City, SD
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · climb to cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The corporate airplane was destroyed on impact with rolling terrain and fire 1.3 nm northeast of the Mission Sioux Airport (0V6), Mission, South Dakota. The flight was en route to the Rapid City Regional Airport, Rapid City, South Dakota, which was located 114 nm on a magnetic bearing 284 degrees from 0V6. The 290 foot long wreckage path was oriented on a magnetic heading of 290 degrees. Night meteorological conditions prevailed at the time of the accident. A witness and communications with the airplane/pilot indicate that the pilot had a continuous duty time of approximately 21 hours that began at least at 0414 mountain daylight time on the day prior to the date of the accident. The wreckage was distributed along 230 feet with propeller slash marks at the beginning of the wreckage path. Both propellers displayed twisting. Postaccident component examination revealed a preexisting crack in the right turbocharger's exhaust but no indication of melting of the fuel lines in the adjacent area. No other system anomalies were noted.
Probable cause
the aircraft control not maintained by the pilot. A contributing factor was pilot fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI00FA265
- Event ID
- 20001212X21659
- Case number
- CHI00FA265
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 2ab8ffa82e42839a92f6ce46c847e0c484d19b2ee40632c866ca31437c4d6b58; retrieved 2026-09-20T20:54:45.260Z.