FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW07FA036 · Cessna 310Q

10 Dec 2006 · Waco, TX, United States

Cessna 310Q · Accident: loss of control in flight on approach

From Natchez–Adams County Airport / Hardy-Anders Field (KHEZ) to Waco Regional Airport (KACT)

Report a problem

Event

NTSB case
DFW07FA036
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
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
Instrument Meteorological Cond

Cessna 310Q

Aircraft type
Cessna 310
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
N69677
Onboard fatalities
Unknown
Route
From Natchez–Adams County Airport / Hardy-Anders Field (KHEZ), Natchez, MSTo Waco Regional Airport (KACT), Waco, TX
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
Approach · IFR final approach
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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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 › Airspeed(vs), not maintained
  • Pilot in command › Impairment(drugs)

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The instrument rated commercial pilot was on the ILS RWY 19 instrument approach in actual instrument meteorological conditions at night, when, according to radar data, the airplane decelerated, lost altitude, and descended about 1.5 miles from the airport. The airplane collided with terrain in an attitude consistent with a loss of control and a stall, and came to rest upright in a plowed field. Radar data revealed that the airplane approached from the north, and was never stabilized during the approach. When it was about 7 miles from the airport, its altitude was 1,800 feet mean sea level (msl), at a ground speed of 76 knots. Approximately two minutes later, when the airplane crossed over the final approach fix, about 4.5 miles north of the airport, it was at an altitude of 2,100 feet msl, at a ground speed of 78 knots. When it was approximately 2.3 miles north of the airport, it was at an altitude of 900 feet msl, and at a ground speed of 81 knots. At this point, the airplane momentarily ascended to 1,100 feet msl, and maintained a ground speed of 81 knots. Over the next 30 seconds, the airplane's altitude descended to 600 feet msl, and the ground speed decelerated to 59 knots before the data ended. The published minimal approach speed for this airplane is 89 knots. A witness, who was driving on a road located south of the accident site, said that he first saw the airplane out the right side window of his vehicle. He said the lights of the airplane appeared hazy, and were not as bright as he was used to seeing on other aircraft that flew into the airport. Shortly after he saw the airplane's lights, he saw an explosion behind a tree line between him and the airplane. The witness also stated that the weather was a low overcast, fog, rain sprinkles, and mist. He said the cloud layer was above the height of the trees, the visibility was approximately .5 to 1 mile, and it was very dark. The weather reported at the airport was two-miles visibility with a 200-foot overcast ceiling and fog. Examination of the airplane and engine revealed no mechanical deficiencies. A review of the pilot's logbook revealed that he was not current for flight into instrument meteorological conditions. In addition, the privileges of his FAA medical certificate had expired approximately eight months prior to the accident. A postaccident toxicological examination was consistent with recent use of marijuana, phentermine (a prescription stimulant), and promethazine (a prescription antihistamine).

Probable cause

The pilot's failure to maintain sufficient airspeed to avoid a stall during the instrument landing approach, which resulted in an inadvertent stall and collision with terrain. Also causal was the pilot's impairment due to prohibited drugs. Factors associated with the accident are an inadvertent stall, a low ceiling, dark night, and the pilot's lack of currency in instrument flight rules.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW07FA036
Event ID
20061218X01801
Case number
DFW07FA036
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2006-12-11.
  • API snapshot SHA-256: b944fcb79d1f38c510e776e4829b4385c0da215dfa5c8745a518578ffb6ac1e4; retrieved 2026-09-20T16:57:55.993Z.