FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW07FA055 · Cessna 310

10 Jan 2007 · Jackson, MS, United States

Cessna 310 · Accident: loss of control in flight en route

From Hawkins Field (HKS) to Ocean Springs Airport (5R2)

Report a problem

Event

NTSB case
DFW07FA055
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
1 · 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

Cessna 310

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
N2625H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hawkins Field (HKS), Jackson, MSTo Ocean Springs Airport (5R2), Ocean Springs, MS
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 · 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
Loss of control in flight
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

  • Reason for occurrence undetermined

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

NTSB narrative

A 3,800-hour commercial pilot departed on a personal cross-country flight in a light piston powered, twin-engine airplane. Shortly after take-off, the pilot reported to the controller that "[he] found a problem and that he wanted to check it out on the ground". The pilot stated that, he was heading back to the departure airport. The air traffic controller offered the pilot, a straight-in approach to the airport. The pilot declined, and stated that he would do a [normal] downwind to the runway. During the conversation with the controller, the pilot did not disclose the nature of the problem. The airplane crashed approximately 4 miles prior to reaching the airport, in a vacant lot. Radar data revealed the airplane departed the airport and flew the runway heading. When the airplane was approximately 5 miles from the airfield and approximately 5,000 feet mean sea level (msl), altitude, the airplane initiated a turn to the right. The airplane continued with a 180-degree turn and then proceeded in a straight line. During the return flight back to the airfield, radar showed the airplane gradually descending while at a ground speed of 170 knots. The last radar hit showed the airplane at 2,700 feet, at a ground speed of 160 knots. The wreckage of the airplane was examined at the accident site on January 11-12, 2007. A post-impact fire consumed part of the airframe cabin. All major components of the airplane were accounted for at the scene. The airplane was found to have impacted the ground in a near nose-down (vertical) attitude. The airframe was extensively crushed by the impact, in an "accordion" style-crushing nose to tail. The wings remained attached to the airplane and perpendicular to the fuselage; both engines were driven several feet into the ground. Control continuity to all flight controls was established. The landing gear was in the retracted position. The flap drive mechanism was located and corresponded to a flap setting of approximately 30 degrees. Post examinations of the engines and propellers were conducted. The left engine sustained heavy impact damage to the front of the engine, and included a crack in the engine's crankcase. Both magnetos separated from the engine during the accident sequence; the magneto's had heavy impact damage and would not produce a spark. Sparkplugs in the left engine were removed and examined. When compared to the Champion Aviation Check-a-Plug Comparison card, the sparkplugs were worn out normal. The top sparkplugs had light gray deposits and the bottom sparkplugs were oily in the electrode areas. No anomalies were noted with the fuel pump or oil pump. The engine was disassembled, and no pre-impact abnormalities with the engine, cylinder assemblies, or engine components were found. The right engine also sustained heavy impact damage. Both magnetos, which separated from the engine during the crash, produced spark. The sparkplugs had similar appearances to the ones installed in the left engine. During the disassembly of the right engine, no pre-impact abnormalities with the engine, cylinder assemblies, or engine components were found. During the accident sequence both propellers remained attached to their respective engine. The propeller blades on both engines were "wrapped" aft to the engines. Examination of the propellers revealed that neither propeller was feathered at the time of impact. Three of the four propeller blades had extensive nicks and gouges along the leading edge.

Probable cause

The pilot's loss of control for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW07FA055
Event ID
20070116X00058
Case number
DFW07FA055
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, coordinates. 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: cc6a4e4bd39278bf4ff589daebd3ba71e90e78fa65d3c622e2e4f332ef0254eb; retrieved 2026-09-20T16:54:44.763Z.