WPR17FA105 · SOCATA TB 20 TRINIDAD
SOCATA TB 20 TRINIDAD · Accident: VFR encounter with IMC en route
From Truckee Tahoe Airport (TRK) to Petaluma Municipal Airport (O69)
Event
- NTSB case
- WPR17FA105
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Unknown
SOCATA TB 20 TRINIDAD
- Aircraft type
- Socata TB-20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N28070
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Truckee Tahoe Airport (TRK), Truckee, CATo Petaluma Municipal Airport (O69), Petaluma, CA
- Aircraft age
- About 27 years (built 1990)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- VFR encounter with IMC
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR17FA105
- Event ID
- 20170419X25815
- Case number
- WPR17FA105
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: aabac55c39ef600dd8250297913456e98c93dd02fee2ea53e1bd93b4d926e85b; retrieved 2026-09-15T06:01:17.468Z.