# NTSB WPR10LA082: EADS Socata TBM 700, N850MT, Truckee, CA, December 14, 2009

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Limited investigation · Final report
- Date: December 13, 2009, 17:38 local (Dec 14, 2009, 01:38 UTC)
- Place: Truckee, CA
- Coordinates: 39.319999, -120.139442 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=39.3200&lon=-120.1394&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470)
- Highest injury: Minor injuries
- Injuries: 2 minor
- Status: Completed, report March 16, 2011
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 75166
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA082
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75166/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75166
- Page: https://openairdocs.org/ntsb/WPR10LA082

## Probable cause

The pilot’s failure to maintain an adequate airspeed and clearance from terrain during an attempted go-around. Contributing to the accident was the pilot's decision to land on a partially obscured runway.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [EADS Socata TBM 700, 1 case](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=8682004), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md)
- [Attention/monitoring: monitoring environment](https://openairdocs.org/ntsb-findings/02021545): Personnel issues › Psychological · Pilot (probable cause); cases with it: [EADS Socata TBM 700, 1 case](https://openairdocs.org/ntsb-findings/02021545/cases.md?model=8682004), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [EADS Socata TBM 700, 1 case](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=8682004), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md)
- [Terrain: mountainous/hilly terrain](https://openairdocs.org/ntsb-findings/03021010): Environmental issues › Physical environment · Response/compensation; cases with it: [EADS Socata TBM 700, 1 case](https://openairdocs.org/ntsb-findings/03021010/cases.md?model=8682004), [All aircraft, 329 cases](https://openairdocs.org/ntsb-findings/03021010/cases.md)
- [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [EADS Socata TBM 700, 1 case](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=8682004), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR go-around: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470) (defining event); cases with it: [EADS Socata TBM 700, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=8682004), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

During the flight, the instrument-rated private pilot was monitoring the weather at his intended destination. He noted the weather and runway conditions and decided to conduct a global-positioning-system instrument approach to a known closed runway with the intention of circling to a different runway. As the airplane neared the missed approach point, the pilot established visual contact with the airport's runway environment and canceled his instrument flight rules clearance. As he entered the left downwind leg of the traffic pattern for his intended runway, the pilot noticed that the first part of the runway was covered in fog and that the visibility was 0.75 of a mile with light snow. With at least 5,000 feet of clear runway, he opted to land just beyond the fog. Prior to touchdown, the pilot concluded that there was not enough runway length left to make a landing and performed a go-around by applying power, pitching up, and retracting the landing gear. During the go-around, the pilot focused outside the airplane cockpit but had no horizon reference in the dark night conditions. He heard the stall warning and realized that the aircraft was not climbing. The pilot pitched the nose down and observed only snow and trees ahead. Not being able to climb over the trees, the airplane subsequently impacted trees and terrain, coming to rest upright in a wooded, snow-covered field. The pilot stated that there were no anomalies with the engine or airframe that would have precluded normal operation of the airplane.

## Factual narrative

On December 13, 2009, about 1738 Pacific standard time, an EADS Socata TBM-700 airplane, N850MT, was substantially damaged when it impacted terrain following an aborted landing near the Truckee-Tahoe Airport (TRK), Truckee, California. The airplane was registered to Tahoe Investments, Los Altos Hills, California, and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The instrument-rated private pilot and his passenger received minor injuries. Instrument meteorological conditions prevailed and an instrument flight rules (IFR) flight plan was filed for the personal flight. The cross-country flight originated from the San Carlos Airport (SQL), San Carlos, California, at 1630, with an intended destination of TRK. In a written statement, the pilot reported that prior to the flight he obtained a weather briefing for the intended route of flight and destination. He also continuously checked the TRK weather prior to departure. He recalled that prior to departure the TRK weather indicated visibility greater than 7 miles, overcast clouds at 2,000 feet, wind calm, and that runway 19 was closed. During the flight, he monitored the weather conditions at TRK and decided to conduct the Global Positioning System (GPS) Runway 19 instrument approach with the intention of circling to a different runway. The pilot reported that the passenger saw the airport as they passed over it, but he could not see it and continued IFR flight. As the pilot initiated the instrument approach, he continued to monitor the weather conditions at the airport and noted that the visibility had decreased to 7 miles. The pilot stated that during the approach he activated all of the airplane’s deicing equipment, as the airplane had “picked up some light rime ice.” The pilot was unsure at what altitude the airplane broke out of the clouds because the ground was visible throughout the approach. As the airplane approached the published missed approach point (MAP), the pilot established visual contact with the runway lighting for runway 28 and subsequently canceled his IFR clearance. As the pilot entered a left downwind for runway 28, he noticed “the first part of [runway] 28 was covered in fog.” The pilot checked the reported weather conditions via the Automated Surface Observing System (ASOS) located at TRK and noted that the visibility was three-quarters of a mile with light snow. The pilot reported that there was at least 5,000 feet of clear runway and he decided to make a mid-field landing, just beyond the fog. Prior to touchdown the pilot decided that there was not enough runway to land, as the airplane was “too high and fast.” The pilot initiated a go-around by applying power, pitching up, and retracting the landing gear. During the go-around the pilot reported that he “was totally focused outside the plane because of the clouds and mountains, but had no horizon reference in the dark.” He also stated that he heard an audible warning horn, whichhe thought was activated because he had failed to raise the landing flaps before retracting the gear. As the audible horn warning continued, the pilot observed that the airplane was not climbing; he then realized that the sound was the stall warning horn. The pilot stated that when he pitched the nose down, he immediately saw only snow and trees ahead. Not being able to climb over the trees, the airplane subsequently impacted trees and terrain about 0.5 miles northwest from the departure end of runway 28. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the airplane came to rest upright within a wooded snow covered field. The left and right wings were structurally damaged. The propeller assembly was separated from the engine and located adjacent to the main wreckage. A strong odor of jet fuel was also present at the accident site. The pilot reported that there were no pre-existing mechanical problems with the engine or airframe.

## Aircraft

- Registration: [N850MT](https://openairdocs.org/deregistered/N850MT-2014-11-18), registration cancelled 2014-11-18, S/N 489 (OpenAirDocs)
- Reported make and model: EADS SOCATA TBM 700
- Registry model: [EADS Socata TBM 700](https://openairdocs.org/model/eads-socata-tbm-700) (registry code 8682004) (OpenAirDocs)
- Category: Airplane
- Serial number: 489
- Airframe hours: 196
- Engines: Pratt & Whitney PT6A-66D 850 horsepower turbo prop
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Tahoe Investments Inc
- Registered owner: Tahoe Investments Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, December 11, 2009, 4 hours before
- Departed: SQL, San Carlos, CA
- Destination: TRK, Truckee, CA
- Flight plan: IFR
- Airport: TRK, Truckee-Tahoe Airport, runway 28, 7,000 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 61; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review November 4, 2009; seat: left; flight hours: 1,738 total, 1,098 in this make and model, 1,547 as pilot in command, 41 in the last 90 days, 7 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Instrument (IMC), Dusk
- Wind: 90° at 4 knots
- Visibility: 1 statute miles
- Lowest ceiling: 1,500 ft broken
- Temperature: 28 °F, dew point 27 °F
- Altimeter: 29.92 inHg
- Observed at: TRK, 1 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20091213022449A](https://openairdocs.org/incident/20091213022449A), Dec 13, 2009: Socata TBM700, Truckee, CA, Substantial damage. The pilot reported that he was conducting the GPS 19 instrument approach. During the approach, he was "in and out of clouds". Upon breaking out of the clouds,…

## Docket (3 files)

The files NTSB released with the investigation on October 29, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75166. 501 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 342 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40338344&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Record of Conversation - Pilot (item 2, .PDF, 30 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40338345&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Pilot-Master.PDF
- Release of Aircraft Wreckage, NTSB Form 6120.15 (item 3, .PDF, 129 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40338346&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.