Plane crash map Locate crash sites, wreckage and more

N761YN accident description

Mississippi map... Mississippi list
Crash location 34.008056°N, 89.865833°W
Nearest city Tillatoba, MS
33.984835°N, 89.896755°W
2.4 miles away
Tail number N761YN
Accident date 02 Sep 2012
Aircraft type Cessna T210M
Additional details: None

NTSB Factual Report

On September 2, 2012, at 2054 central daylight time, a Cessna T210M, N761YN, operated by a private individual, was substantially damaged when it impacted trees during a forced landing, following a total loss of engine power while in cruise flight near Tillatoba, Mississippi. The private pilot was seriously injured. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. Night visual meteorological conditions prevailed and no flight plan was filed for the flight that departed Suffolk Executive Airport (SFQ), Suffolk, Virginia, about 1526; destined for Olive Branch Airport (OLV), Olive Branch, Mississippi.

The pilot telephoned flight service at 1505 and received a weather briefing for the planned visual flight rules (VFR) flight from SFQ to OLV. The flight service specialist advised of thunderstorms along the planned route of flight due to the remnants of Hurricane Isaac and he did not recommend VFR flight. The pilot remarked about deviating south to avoid thunderstorms, rather than flying a direct route to his planned destination. He further indicated that he may delay the flight, or land at a closer airport if weather deteriorated, and he declined any further weather briefing information from the flight service specialist.

According to a fuel receipt, the airplane was completely fueled at SFQ about 1 hour prior to departure. Review of data recovered from a handheld global positioning system (GPS) receiver revealed that the airplane departed at 1526 and flew a course south of a direct route to OLV. Additionally, the airplane did not stop while enroute to OLV. The last GPS point was recorded near the accident site at 2054, indicating a GPS altitude of 469 feet and a groundspeed of 67 knots. The GPS data indicated that the accident flight was 5 hours 28 minutes long.

According to data from the Federal Aviation Administration (FAA), the airplane was in radio and radar contact with Memphis Center. At 1925, the controller advised the pilot of severe weather at OLV. The pilot acknowledged the information and added that he was seeing the same thing at OLV. At 1955, the pilot stated that he was still 45 minutes away from OLV due to deviations and that the severe weather may move out of the area by the time he arrived. At 2010, the Memphis Center controller telephoned a Memphis Approach controller to get more weather information pertaining to OLV. The Memphis Approach controller advised that the severe weather was moving to the southeast at only 12 knots and it would be a while before it was clear of the area. The Memphis Center controller relayed the information to the pilot, which he acknowledged. The pilot then advised that he planned to divert to University-Oxford Airport (UOX), Oxford, Mississippi, which the controller acknowledged.

At 2024, the pilot advised that he was diverting to Water Valley Municipal Airport (33M), Water Valley, Mississippi, as lighting was getting too close to UOX. The controller acknowledged the new destination, advised of no traffic between the airplane and 33M, and terminated radar services with an instruction to the pilot to enter a VFR transponder code. The pilot acknowledged the instruction and thanked the controller for his help. No further communications were received from the accident airplane. At that time, the airplane was about 10 miles south of 33M. It descended and circled over 33M at 2029, but then continued north until 2040, where it reversed course near Panola County Airport (PMU), Batesville, Mississippi. The airplane subsequently flew in a southerly direction until the end of the data, which was approximately 13 miles west-southwest of 33M.

A witness, who was driving his car near 33M about 2030, stated that he saw an airplane with its landing lights on and descending, as if it was going to land at 33M. At the time, the weather conditions were good at the airport with no ceiling, a slight breeze, and the runway lights were on. The airplane then flew northwest parallel to the runway and the witness thought that the pilot was setting up for an approach from the north; however, the airplane continued northwest out of sight. At the time, severe storms were present to the north and northeast.

Examination of the wreckage by an FAA inspector revealed that both wings separated during impact and no evidence of fuel was observed in the vicinity of the accident site. Additionally, the propeller blades exhibited little to no rotational damage. The engine was examined after the airplane was recovered to a hangar. The examination, which included a successful test-run of the engine, did not reveal any preimpact mechanical malfunctions.

The pilot held a private pilot certificate, with ratings for airplane single-engine land and instrument airplane. His most recent FAA third-class medical certificate was issued on August 26, 2010. At that time, the pilot reported a total flight experience of 2,525 hours. Due to his injuries, the pilot could not recall the accident sequence.

Review of an endurance chart, contained in a pilot's operating handbook for the same make and model airplane, revealed that at 70 percent power, the airplane had an endurance of approximately 5 hours 10 minutes, which did not account for fuel used for engine start, taxi, takeoff, and climb.

NTSB Probable Cause

The pilot's improper fuel management and his decision to continue flight in deteriorating weather conditions with low fuel, which resulted in a total loss of engine power due to fuel exhaustion.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.