Accident Details
Probable Cause and Findings
the pilot's spatial disorientation, which led to his failure to maintain aircraft control. A contributing factor was the pilot's decision to intentionally fly into known adverse weather that consisted of low ceilings, obscuration, and ice fog.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHT
On March 26, 2001, at 0719 mountain standard time, a Socata TBM 700, N300WC, owned and operated by Technical Leasing, Inc., of Cincinnati, Ohio, was destroyed when it impacted terrain following a loss of control on takeoff at Centennial Airport, Englewood, Colorado. The instrument rated private pilot, the sole occupant aboard, was fatally injured. Instrument meteorological conditions prevailed, and an IFR (instrument flight rules) flight plan had been filed for the business flight being conducted under Title 14 CFR (Code of Federal Regulations) Part 91. The flight originated from Centennial Airport at 0718.
The pilot landed at Centennial Airport on the afternoon before the accident (data downloaded from the Garmin GPSMAP 295 that was on board the airplane indicates the arrival was some time after 1341). He instructed Jet Center officials to refuel the airplane to capacity. This was done at 1430 and required 136 gallons of Jet-A fuel. The pilot was met by friends, who took him to dinner and a movie that evening. They said the pilot retired approximately 2300.
According to these friends, the pilot did not eat breakfast the next morning. He telephoned the FBO about 0515 and asked that the airplane be brought inside a hanger and preheated (it had been parked outdoors on the ramp overnight). This was done and the airplane was in the heated hangar approximately 45 to 60 minutes. According to FAA documents, the pilot telephoned the Denver Automated Flight Service Station (AFSS) at 0608 and obtained a standard weather briefing. He then filed an IFR flight plan to Santa Monica Airport in California. The pilot's host said he dropped the pilot off at the airport approximately 0615. He said it was snowing at the time, and visibility was poor. Jet Center linemen said the pilot did not perform a preflight inspection, but boarded the airplane, started the engine, and did a 20 minute engine run at "high rpm" on the ramp.
At 0647, the pilot received his IFR clearance, and at 0708 he was cleared to taxi. Because the wind was calm, the pilot was given his choice of runways. "Which one would you recommend," the pilot asked. "One seven will take me down to Blue Mesa, won't it?" When he was told it would, the pilot taxied to runway 17L and advised the control tower that he had ATIS (Automatic Terminal Information Service) Zulu and would need to do an engine runup. At 0712, he asked if there were any pilot reports, and was told that one pilot reported encountering no ice during climbout and that the cloud tops were at 7,200 feet. At 0717, the pilot was cleared for takeoff, but reduced visibility prevented control tower personnel from observing the airplane.
At 0719:27, the pilot said, "Whiskey Charlie, lookin' for higher." (According to the tower controller's statement, he had been watching the BRITE radar for the airplane's data tag to appear and when the pilot asked for a higher altitude, he observed a primary target, then a limited data tag, northbound and east of runway 17L). The controller asked the pilot for his heading, and he replied, "Whiskey Charlie, apologi . . ." He was then instructed to fly a heading of 170 degrees and to contact departure control. The pilot never responded. When it was determined that radio and radar contact had been lost with the airplane, the runway was closed and departures were temporarily suspended. The tower controller told the radar controller, "[Visibility is a] quarter mile. We cannot see the runway . . .we heard a noise . . . we heard the airplane." Another controller said she "heard a noise and felt a movement or 'thud' in the tower." At 0736, an airport maintenance vehicle reported he was investigating a report of smoke south of the airport. At 0740, the airport maintenance vehicle confirmed the airplane was down approximately 1/4-mile south of runways 10-28.
PERSONNEL INFORMATION
The pilot, age 49, held a private pilot certificate with airplane single-engine land and instrument ratings. He also held a first class airman medical certificate, dated March 11, 1999, with no limitations or restrictions. His logbook, which was recovered from the wreckage, contained entries from August 23, 1995, (when the pilot took his first instructional flight), to January 21, 2001 (the last recorded entry). According to the logbook, the pilot received his private pilot license and instrument rating on August 14, 1998. The airplane's flight time logbook was also recovered from the wreckage. Combining those entries made after January 21, 2001, with the entries made in the pilot's logbook, the following flight times were derived:
Total time: 1,024 hrs.
Airplane single-engine, land: 1,019.5 hrs.
Pilot-in-command: 719.4 hrs.
Instruction received: 412.3 hrs.
Cross-country: 987.8 hrs.
Night: 85.7 hrs.
Actual instruments: 94.3 hrs.
Simulated instruments: 9.7 hrs.
By make/model: Cessna 150: 2.8 hrs.
Cessna 172: 8.5 hrs.
Piper PA-28-161: 3.2 hrs.
Piper PA-28R-201RT: 6.3 hrs.
Piper PA-46-350: 488.4 hrs.
Beech A36TC: 376.7 hrs.
Socata TBM-700: 136.3 hrs.
The pilot's logbook also contained the following instrument proficiency checks, biennial flight reviews, and pilot proficiency endorsements:
November 7, 1998*#
(given by an individual flight instructor)
November 22, 1998#
Recurrent Training Center, Inc.
June 26, 1999+
(given by an individual flight instructor)
March 20, 2000*#
(given by an individual flight instructor)
August 25, 2000#+
SIMCOM Training Center
* Biennial Flight Review, BFR [FAR 61.56(a)(1)(2)].
# Instrument proficiency check (FAR 61.57).
+ Pilot Proficiency Award Program (AC61-91H).
AIRCRAFT INFORMATION
N300WC (s/n 82), a model TBM-700, was manufactured by Socata Aircraft Company and was given an FAA standard airworthiness certificate, normal category, on February 15, 1993. It was equipped with a Pratt & Whitney PT6A-64 engine (s/n PS 111074), rated at 700 shaft horsepower, and a Hartzell 4-blade composite, constant speed, full feathering propeller (m/n HC-E4N-3).
According to the aircraft maintenance records, the last annual inspection was completed on February 9, 2001, at a Hobbs meter time (airframe and propeller) of 5,098.7 hours (engine total time 4,885.7 hours). The last static system, automatic pressure altitude reporting and transponder system checks were made on October 20, 2000, at a Hobbs meter time of 4,978.3 hours. At the accident site, the Hobbs meter read 5,139.0 hours.
METEOROLOGICAL INFORMATION
METAR (Aviation Routine Weather Report) observations recorded at Centennial Airport before and after the accident were as follows:
0653: Wind, calm; visibility, 1/4 statute mile; freezing fog; vertical visibility, 100 feet; temperature, -1 degree C.; dew point, -1 degree C.; altimeter setting, 30.02 in.; sea level pressure, 1019.5 mb.
0730: Wind, calm; visibility, 1/8 statute mile; freezing fog; vertical visibility, 100 feet; temperature, -1 degree C.; dew point, -1 degree C.; altimeter setting, 30.02 in.
0753: Wind, calm; visibility, 1/4 statute mile; freezing fog; vertical visibility, 100 feet; temperature, -1 degree C.; dew point, -1 degree C.; altimeter setting, 30.03 in.; sea level pressure, 1019.7 mb.
AERODROME INFORMATION
Centennial Airport (APA) is situated at an elevation of 5,883 feet msl (above mean sea level). The departure runway, 17L, is of asphalt construction, 10,002 feet long and 100 feet wide, and grooved. The runway is equipped with medium intensity runway lights (MIRL). They were operating at the time of takeoff. The airport also has a control tower, Automatic Terminal Information Service (ATIS), and an Automated Flight Service Station (AFSS) that is operational 24 hours a day. At the time of departure, the rotating beacon was operating. The airport has several instrument approaches, including GPS (Global Positioning System), ILS (Instrument Landing System), NDB (Non-Directional Beacon), and VOR/DME RNAV (Very high frequency Omnidirectional Radio range/Distance Measuring Equipment aRea NAVigation). All of the instrument approaches were operational at the time of the accident. IFR arrivals and departures were being handled by Denver TRACON (terminal radar approach control).
WRECKAGE AND IMPACT INFORMATION
The on-scene investigation commenced and concluded on March 26, 2001.
The airplane first struck a newly planted pine tree (N39 degrees, 33.992', W104 degrees, 50.486'). Red lens fragments were found embedded in the bark approximately 5 feet above the ground. There was a faint ground scar from the tree leading up to the top of an embankment. There, 14 slashes were noted on the ground (N39 degrees, 33.993", W104 degrees, 50.476"). The distance between the first slash mark and second slash mark was 2 feet, 3 inches. Just beyond these marks was a small crater, aligned on a magnetic heading of 109 degrees, containing pieces identified as portions of the left wing tip fairing and the socket for a navigation light. At a point 6 feet beyond this crater was a large ground scar, containing a propeller blade tip (N39 degrees, 34.008', W104 degrees, 50.424'). This ground scar curved to the left from a magnetic heading of 082 degrees to 047 degrees. Indications of a flash fire encompassed approximately the last third of the first ground scar and extended through the first half of the second ground scar. Forty-eight feet from the beginning of this second ground scar was the right wing. At the 210 foot mark, where the ground scar curved to a magnetic heading of 055 degrees, was the right aileron. The vertical stabilizer (N39 degrees, 34.019', W104 degrees, 50.400') and right main landing gear (N39 degrees, 34.023', W104 degrees, 50.397') were found near the end of the fire area. The ground scar then curved to a magnetic heading of 047 degrees and terminated at a large dirt embankment at the 489 foot mark. The top o...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# DEN01FA075