WPR24FA252 · Textron Aviation Inc T206H
Dyncorp International Textron Aviation Inc T206H · Accident: abnormal runway contact during landing
From McClellan Airfield (MCC) to an unrecorded destination
Event
- NTSB case
- WPR24FA252
- 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
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
Textron Aviation Inc T206H
- Aircraft type
- Cessna 206
- 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
- N460DC
- Operator
- Dyncorp International
- Onboard fatalities
- Unknown
- Route
- From McClellan Airfield (MCC), Sacramento, CATo not recorded
- Aircraft age
- About 3 years (built 2021)
- 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
- Landing
- Defining eventThe 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was transporting a mechanic and parts to an airport on a plateau surrounded by rolling peaks and valleys. The pilot approached the runway from the southeast and performed a go-around. It is unknown if it was the pilot’s intention to complete an initial pass by overflying the runway. Flight data suggests that the pilot’s second approach was unstabilized as he overshot the runway centerline before realigning with the runway and then descending rapidly in a short distance to reach the runway threshold. Witness statements and ground signatures indicated that during this second pass the airplane touched down hard about midfield, bounced, and landed hard again towards the end of the runway. The tie-down ring separated and the airplane deviated to the left of the runway centerline. The left wing collided with some branches off the left side of the runway before the airplane rolled off the runway and impacted trees and then the ground about 700 ft from the departure end of the runway. A postacrash fire consumed the wreckage. Postaccident examination of the wreckage did not reveal any preimpact mechanical anomalies with the airframe or engine that would have precluded normal operation. The flight track data, accident site signatures, and witness observations showed that the pilot attempted to touch down about halfway down the runway during a second pass and immediately lost directional control of the airplane. He then added power to perform a go-around about 150 ft from the end of the runway and never regained control. The pilot’s loss of control during the landing attempt and subsequent delayed decision to initiate a go-around resulted in a runway overrun and impact with trees and terrain. The pilot’s flight logbook showed he had only recently started with the company and had logged about 88 hours of total flight experience in the airplane make and model at the time of the accident. While his records suggest he likely had limited experience flying into the accident airport, his relative experience flying into airports with similar topographical challenges could not be determined with the available evidence.
Probable cause
The pilot’s delayed decision to perform a go-around after an unstabilized approach, which resulted in a loss of control, runway overrun, and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA252
- Event ID
- 20240723194756
- Case number
- WPR24FA252
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: b0a55b9769c0f1851120c4bd9193bb413e6d5cde3f01da2b433c2eaa1567ea36; retrieved 2026-09-15T08:25:15.205Z.