Accident Socata TB20 Trinidad N28070,
ASN logo
ASN Wikibase Occurrence # 194903
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 17 April 2017
Time:16:10
Type:Silhouette image of generic TB20 model; specific model in this crash may look slightly different    
Socata TB20 Trinidad
Owner/operator:Private
Registration: N28070
MSN: 1082
Year of manufacture:1990
Total airframe hrs:3131 hours
Engine model:Lycoming IO-540 SER
Fatalities:Fatalities: 2 / Occupants: 2
Aircraft damage: Destroyed
Category:Accident
Location:NW of Truckee, CA -   United States of America
Phase: En route
Nature:Private
Departure airport:Truckee, CA (TRK)
Destination airport:Petaluma, CA (O69)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The noninstrument-rated private pilot was making a visual flight rules (VFR) cross-country flight in the airplane over mountainous terrain. Radar data revealed that the airplane initially flew in a northerly direction after takeoff and then turned west toward the destination; this route was consistent with a route the pilot had followed on previous flights. About 17 minutes after takeoff, the airplane was about 19 nautical miles (nm) northwest of the departure airport. The last radar return, which occurred about 18 minutes after takeoff, showed that the airplane was about 20 nautical miles (nm) northwest of the departure airport and about 0.47 nm southeast of the accident site on a southwesterly heading at an altitude of 8,869 ft mean sea level (msl). Shortly thereafter, the airplane impacted remote, snow-covered, mountainous terrain on a northerly heading at an elevation of 7,697 ft msl. The changes in heading and altitude between the last radar return and the impact suggest that the pilot began maneuvering the airplane after radar contact was lost. A survey of the accident site revealed a linear debris path and damage to the airplane that were consistent with controlled flight into terrain. Examination of the airframe and engine did not reveal evidence of any mechanical anomalies that would have precluded normal operation.

Review of weather information strongly suggests that clouds, light rain, snow, or mixed precipitation was falling and instrument meteorological conditions (IMC) likely existed in the accident area. It is likely that the pilot encountered IMC conditions and was maneuvering in an attempt to return to VFR flight when the airplane collided with terrain.

Probable Cause: The pilot's decision to continue visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into mountainous terrain.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR17FA105
Status: Investigation completed
Duration: 1 year and 6 months
Download report: Final report

Sources:

NTSB

Location

Images:


Photo: NTSB

Revision history:

Date/timeContributorUpdates
19-Apr-2017 03:27 Geno Added
19-Apr-2017 06:52 gerard57 Updated [Total fatalities]
26-Apr-2017 14:32 Anon. Updated [Source, Narrative]
28-Apr-2017 17:42 Aerossurance Updated [Operator, Location, Nature, Source, Narrative]
20-May-2017 01:20 Geno Updated [Total fatalities, Source, Damage, Narrative]
10-Mar-2018 08:05 TB Updated [Aircraft type, Operator, Location]
15-Oct-2018 17:05 ASN Update Bot Updated [Time, Operator, Departure airport, Destination airport, Source, Narrative, Accident report, ]
15-Oct-2018 17:17 harro Updated [Narrative, Photo]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org