Accident Details
Probable Cause and Findings
The pilot's failure to fly a stabilized, published instrument approach procedure, and his failure to maintain adequate airspeed which led to an aerodynamic stall.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHT
On March 1, 2003, about 1445 eastern standard time, a Socata TBM-700, N700PP, was substantially damaged when it collided with trees, during an instrument approach to Leesburg Executive Airport (JYO), Leesburg, Virginia. The certificated airline transport pilot, the private pilot, and the passenger were fatally injured. The airplane was owned and operated by High Performance Technologies, Incorporated, Arlington, Virginia. An instrument flight rules (IFR) flight plan was filed for the flight that originated at Greenville-Spartanburg International Airport (GSP), Greer, South Carolina, about 1230. Instrument meteorological conditions prevailed for the business flight conducted under 14 Code of Federal Regulations Part 91.
Several witnesses observed and heard the airplane. According to one witness, a private pilot and an airplane owner based at Leesburg, he was in his truck approaching a stop sign when he first saw and heard the airplane. He said the airplane "appeared" out of the fog about 300-400 feet above the ground, directly in front of where he was located. The airplane was in a "slight left bank" (10-15 degrees), with the nose pointed "slightly down" (about 20-25 degrees), and traveling fast. The airplane was in a left turn, moving south to east, and toward the north.
The witness then observed the airplane to "simultaneously and suddenly level out," pitch up (20-25 degrees), and increase power. The change in engine sound was similar to when an airplane applied power for take-off. The witness thought that the pilot realized he was low and was trying to "get out of there."
The airplane continued to descend in the nose-high attitude toward the trees. The witness estimated the descent angle of the airplane to be 65 degrees, before he lost sight of it as it descended behind trees.
The witness described the attitude of the airplane. He said, "It looked as if he got on the backside of the power curve... If he had had more altitude, he may have recovered. But, even if he did recover, there was still a ridge directly in front of his position that he would have had to clear, and I am not sure if he would have been able to do that." The witness also noted that the engine was operating normally, and the weather was foggy with low visibility.
A second witness stated that she was on her back porch about 1/8 mile from the accident site, when she heard an airplane engine getting "louder and louder." She then stepped off her porch and went out into her backyard. When she looked up, the airplane flew directly overhead going east bound, and it was about five stories above the ground. The belly of the airplane was parallel to the ground and was colored blue. The landing gear was not extended. The engine sounded "loud and constant" the entire time.
The airplane then made a sharp left bank and started to turn toward the north. It continued to increase the left bank, when the nose dropped down into the trees, and the witness lost sight of it.
The witness also described the weather as a gray overcast, but not foggy.
A third witness was in his yard, which he stated was about 1/4 mile from the accident site. He first heard an airplane flying low overhead. When he looked up, he saw it exiting the clouds, about four stories above the ground, in a level attitude, headed east. The airplane then made a sharp left bank and started to turn towards the north. The nose of the airplane "was being pulled up" while in the turn. It then dropped, and pointed down toward the ground. The witness did not see the airplane hit the ground, but noted that the engine sounded as if it was "cutting in-and-out" before impact. The witness also noted that the weather was "very foggy."
A fourth witness was in her backyard, located across the street from the accident site. She heard the sound of an airplane engine "revving up and down." The witness then looked up and saw the airplane on its side, descending through the trees. It was "teetering" back and forth as it descended, and the top of it was facing her direction. The witness also described the weather as foggy.
A fifth witness said that he heard an airplane that sounded really low, but could not see it. The engine sounded "normal", then faded for about 10 seconds, then began to "surge" or "race". Two to 3 seconds later, he heard a crashing sound. The witness also stated that the weather was extremely cloudy and foggy.
A sixth witness was in his home, which was located "very nearly under" the localizer approach and about 3 miles from runway 17 at Leesburg Executive Airport. He first heard the sound of the engine, which he described to be in "approach" mode or idle RPM. The witness thought the airplane was at the same altitude as his home, about 250 above ground level. The witness moved to the front of his home and looked outside in an attempt to see the airplane, but the visibility was less than 100 feet. Based on what he heard, and where he residence was located, the witness stated, " the airplane had descended considerably below the minimum descent altitude far short of the runway."
A review of air traffic control communications revealed that the pilot received radar vectors to intercept the localizer course for the LOC RWY 17 approach.
At 1429, an approach controller provided the current altimeter setting and asked the pilot if had the current weather conditions. The pilot acknowledged the altimeter setting and reported that he had the current weather information.
At 1440, the approach controller instructed the pilot to intercept the localizer course, and the pilot acknowledged. About 1 minute later, the approach controller advised the pilot that he was located 3 miles north of WARDE intersection (final approach fix), to maintain 3,000 feet until established, and that he was cleared for the LOC RWY 17 approach. The pilot acknowledged.
At 1442, the approach controller advised the pilot to cancel IFR services with Leesburg Flight Service Station (FSS) once on the ground, and approved a change in radio frequency for airport advisories. The pilot acknowledged, and there were no further communications from the pilot.
A review of radar data revealed an instrument flight rules (IFR) target approaching the Leesburg Airport from the north west. Examination of the last 4 minutes of radar data revealed the target turned toward the south about 9 miles from the end of runway 17. At that time the target was at an altitude of 3,100 feet msl and at a ground speed of 180 knots.
As the target continued to maneuver toward the south, it made a series of left and right hand turns along the localizer course. When the target was about 5 miles north of the runway, it was at an altitude of 1,700 feet msl and at an airspeed of 130 knots.
As the airplane continued to proceed toward the airport, it continued to make left and right hand turns along the course.
As the airplane crossed over the final approach fix, about 4 miles north of the airport, it was at an altitude of 1,700 feet msl, at a ground speed of 91 knots.
When the target was approximately 3 miles north of the airport, it was at an altitude of 800 feet msl, at a ground speed of 80 knots.
Eighteen seconds later, the target began a left turn to the east before the data ended at 1445:29. The last radar target was located at 38 degrees, 57 minutes north latitude, and 77 degrees, 27 minutes west longitude, at an altitude of 700 feet msl, and at a ground speed of 68 knots.
The accident occurred during the hours of daylight approximately 39 degrees, 07 minutes north latitude, and 77 degrees, 34 minutes west longitude.
PERSONNEL INFORMATION
The pilot in the left seat held a private pilot certificate with ratings for single engine land and instrument airplane. His most recent Federal Aviation Administration (FAA) second class medical certificate was issued on August 09, 2002. At that time, he reported 730 hours of flight experience.
Several requests were made to the family to obtain the pilot's personal logbooks. However, they were not made available for review.
SECOND PERSONNEL INFORMATION
The pilot in the right seat held an airline transport pilot certificate for airplane multi-engine land, with ratings for the ATR-42, ATR-72, B-737, and DHC-7. He also held a commercial pilot certificate for airplane single engine land, a certified flight instructor certificate for airplane single engine land, airplane multi-engine land, and instrument airplane. His most recent FAA second class medical certificate was issued on November 18, 2002. At that time, he reported 8,375 hours of flight experience.
According to the pilot's wife, he carried a logbook with him during trips, in a jacket pocket. However, the jacket and logbook were never located.
Both pilots completed TBM-700 ground and simulator/flight proficiency training at SIMCOM International, Inc. Pilot Training Center, Orlando, Florida, in December 2002. A review of training records revealed that both pilots practiced IFR procedures, which included a LOC approach.
According to a representative of the owner's insurance company, the pilot's insurance policy required a second pilot to be in the cockpit anytime the pilot was flying the airplane.
AIRCRAFT INFORMATION
The Socata TBM 700 was a single-engine turboprop, 6-7 seat, high-performance, pressurized, fixed-wing airplane. Examination of maintenance records revealed that the airplane and the Pratt and Whitney Canada PT6A-64 (750 SHP) engine underwent an annual inspection on May 24, 2002, at a total time of 1,049.1 hours each.
At the time of the accident, the engine and airplane had each accrued a total of 1,175 hours.
METEOROLOGICAL INFORMATION
Weather reported at the airport, at 1400, included winds from 150 degrees at 5 knots, temperature 37 degrees F, dewpoint 35 degrees F, and altimeter setting 30.14 inches Hg. The visibility was 1 statute mile and ...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# IAD03FA035