Plane crash map Locate crash sites, wreckage and more

N814ER accident description

North Carolina map... North Carolina list
Crash location 35.870000°N, 82.347222°W
Reported location is a long distance from the NTSB's reported nearest city. This often means that the location has a typo, or is incorrect.
Nearest city Burnsville, NC
35.112373°N, 80.244506°W
129.4 miles away
Tail number N814ER
Accident date 01 Feb 2006
Aircraft type Cessna 500
Additional details: None

NTSB Factual Report

HISTORY OF FLIGHT

On February 1, 2006, at 1145 eastern standard time, a Cessna CE-500, N814ER, registered to and operated by Flite Services, Inc., touched down short of the runway while performing a touch-and-go landing at Mountain Air Airport, Burnsville, North Carolina. The corporate flight was operated under the provisions of Title 14 CFR Part 91. Visual meteorological conditions prevailed and an Instrument Flight Rules flight plan was filed. The pilot, co-pilot and two passengers were not injured, and the airplane sustained substantial damage. The flight originated from Asheville, North Carolina, on February 1, 2006, at 1130.

According to the flight crew, the departure from Asheville, was normal. The flight proceeded to Mountain Air Airport, Burnsville, North Carolina, where they performed a "touch-and-go." Following the touch-and-go, at about 1145, and upon raising the landing gear, they got an "unsafe gear" light. The crew cycled the gear back down and got a "three green" normal indication. They cycled the gear back up and again got the "gear unsafe" light. They cycled the gear three more times with the same results. The crew decided to return to Asheville, and upon extending the gear for a visual landing at Asheville, the right main landing gear green light did not illuminate. The crew stated that they performed all of the checklist procedures and asked the control tower personnel to visually look to see if the gear was down and that tower personnel reported that it was. The crew asked the tower personnel if the landing light was on, and tower personnel replied that is was not. According to the flight crew, they went through the emergency procedures again, but they had no luck in getting the landing gear to lock down. They said that there was no landing light and that they got the gear horn with the gear down and full flaps with the throttles at idle. The crew stated they were sure that the gear was out of the uplocks but not down and locked.

The crew stated that, after talking with maintenance personnel on the ground at Asheville, they decided to divert to Greensboro, North Carolina, where there were better facilities to handle the situation. One of the passengers had noticed that after the crew had recycled the gear the last time, a panel on the right wing was pushed up. The flight continued to Greensboro, at 150 knots with the gear down. Greensboro tower personnel cleared the flight for a visual approach. According to the crew, the landing was normal for the first 2,000 feet of roll out, then the right main landing gear collapsed. The crew said that, when the gear collapsed, they shut down both engines and the airplane veered off the right side of the runway into the grass. Both crewmembers and passengers exited the airplane through the main door with no injuries. The pilot stated that, he examined the right main landing gear after the airplane had been moved to the hangar, and it appeared to him that the landing gear failed due to metal fatigue. He said that, "where the gear was broken, there was evidence of old cracks with fresh breaks."

According to an FAA inspector the flight crew had attempted a landing at the Mountain Air Airport soon after their departure from Asheville. According to statements made to the FAA Inspector by the pilot and co-pilot, they performed only a low pass over the airport and did not touch down, and that no other landings or takeoffs were attempted prior to the landing at Greensboro. However, according to witnesses at the Mountain Air Airport, after seeing the airplane on the evening news, the owner of the private airport called the Greensboro FAA Flight Standards District Office (FSDO) and reported that the airplane crew talked with him on the airport's common traffic advisory frequency (CTAF) the afternoon of the accident and that the airplane was observed attempting to land on the northwest runway, but it aborted the landing at the last moment. Later that afternoon, airplane landing gear parts were discovered on the runway.

PERSONNEL INFORMATION

A review of information on file with the FAA Airman's Certification Division, Oklahoma City, Oklahoma, revealed the pilot was issued a commercial pilot certificate on December 24, 2003, with ratings for airplane multi-engine land and instrument airplane, and he held a private pilot certificate for airplane single-engine land. In addition, the pilot held a type rating for the CE-500. The pilot held a first-class medical issued on March 23, 2005, with a restriction that he must have available glasses for near vision. The pilot reported that he had accumulated 2,500 total flight hours, of which 700 hours were in the Cessna CE-500. The pilot's last flight review was conducted on April 10, 2005.

A review of information on file with the FAA Airman's Certification Division, Oklahoma City, Oklahoma, revealed that the co-pilot was issued an airline transport pilot certificate on October 16, 2003, with ratings for airplane multi-engine land, and he held a commercial pilot certificate for airplane single-engine land and helicopter. In addition, the co-pilot held type ratings for CE-500, HS-125, IA-Jet, and LR-Jet. The co-pilot held a second-class medical certificate issued on March 23, 2005, with a restriction that he must have available glasses for near vision. The co-pilot reported that he had accumulated 13,000 total flight hours of which 1,000 hours were in the Cessna CE-500. The co-pilot's last flight review was conducted on August 25, 2005.

AIRCRAFT INFORMATION

A review of information provided by the pilot revealed that the last continuous airworthiness inspection was conducted on November 30, 2005. The airframe total time at the time of the accident was 12,008.3 hours.

METEOROLOGICAL INFORMATION

The 1317 surface weather observation at Piedmont Triad International Airport was wind 220-degrees at 6 knots, visibility 10 statute miles, sky clear, temperature 9 degrees Celsius, dew point temperature 3 degrees Celsius, and altimeter 30.02.

FLIGHT RECORDERS

The CVR was not retained for readout by NTSB due to the elapsed time from the accident to the final landing.

WRECKAGE AND IMPACT INFORMATION

Examination of the airplane by an FAA Inspector following the landing at Greensboro revealed several of the landing gear components were missing. Following a conversation with the owner of the Mountain Air Airport, the FAA inspector went to the airport, and retrieved the landing gear parts found on their runway. He stated that he took one of the large parts, about half of the right main landing gear trunnion, to the hangar where the accident airplane was stored, and positively identified the part as coming from the accident airplane. The broken trunnion fit exactly with the other half of the broken trunnion still attached to the airplane and that the trunnion had bent 30-degrees before breaking. While at Mountain Air, the inspector observed that the airplane had touched down short of the runway and below the airport grade on the side of the mountain.

ADDITIONAL INFORMATION

Examination of photographs of the failed landing gear component fracture surfaces by the NTSB Materials Laboratory found no indication of fatigue. The angle brace fracture on the landing gear trunnion showed deformation consistent with overstress compression buckling. The upper support showed twisting deformation consistent with the direction of the bend in the angle brace and downward bending consistent with the wheel moving aft relative to the upper support, all consistent with the overstress fracture.

NTSB Probable Cause

The pilot's misjudged distance/altitude that led to an undershoot and the pilot's failure to attain the proper touchdown point.

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