FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA196 · Cessna 172N N

7 Sept 2017 · Bolinas, CA, United States

Cessna 172N N · Accident: controlled flight into terrain/object (CFIT) en route

From Santa Ynez Airport (IZA) to Charles M. Schulz Sonoma County Airport (STS)

Report a problem

Event

NTSB case
WPR17FA196
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
1 · 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
Visual Meteorological Cond

Cessna 172N N

Aircraft type
Cessna 172
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
N737QQ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Ynez Airport (IZA), Santa Ynez, CATo Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, CA
Aircraft age
About 40 years (built 1977)
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 · cruise
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
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During a personal cross-country flight, the non-instrument-rated private pilot reported to air traffic control that the airplane would be descending below the marine layer clouds to fly along the coastline to the intended destination. Before the pilot's descent, he asked the controller about the cloud base altitude, but the controller did not have that information. The pilot stated that he would descend to 1,500 ft. The controller asked the pilot if he was going to follow the shoreline, and the pilot replied, "yes, at 2,100 [ft]." Shortly afterward, the controller advised the pilot to contact the next sector. About 13 minutes later, the pilot attempted to contact the next sector, but that sector controller was not able to understand the transmission. The controller instructed the pilot to contact approach control in 15 miles. No further communications from the pilot were received. The wreckage evidence indicated that the airplane impacted rising terrain.

Witnesses in the area did not see the accident airplane but heard a loud noise about the time of the accident. The witnesses reported a thick fog layer near the accident site. The airframe and engine examinations found no mechanical anomalies that would have precluded normal operation.

The accident site was in an area that had a low- to mid-level pressure troughs, which induced an onshore flow toward the mountainous terrain along the coastline. The persistent onshore flow was favorable for the development of a marine layer and mountain obscuration. An AIRMET that was valid for the time of the accident indicated mountain obscuration and instrument flight rules (IFR) conditions along the coastal water; the accident site was less than 1-mile northeast of the coastline.

The closest official weather observation site to the accident site, which was located 15 miles northeast of the accident site, reported an overcast ceiling at 2,600 above ground level (agl). An unofficial weather site that was 5 miles east-northeast of the accident site reported a temperature and dew point that were nearly equal and a relative humidity above 85%. These conditions increased the potential for instrument meteorological conditions (IMC) in the area. In addition, the cloud ceilings near the accident site were likely at 800 ft mean sea level according to the upper air sounding data.

A review of archived ForeFlight data and DUATS and Leidos records revealed that the pilot received several weather briefings in preparation for the flight, and that the briefings identified marginal VFR and IMC conditions along the intended route of flight. Thus, the pilot had sufficient weather forecast information to understand that IFR and mountain obscuration conditions would have existed northward along the coastline.

Probable cause

The non-instrument rated private pilot's improper decision to embark on a flight and continue to fly into forecasted instrument meteorological conditions and mountain obscuration while conducting a visual flight rules flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA196
Event ID
20170902X54656
Case number
WPR17FA196
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: d67fbefc81dadbe1370ca3b91d038f84d3336fe71535735e989b50e11fd18f2f; retrieved 2026-09-15T06:15:05.913Z.