Cessna 172N N737QQ
7 September 2017 · Bolinas, California, United States · Fatal
Summary
On 7 September 2017 at about 21:00 local time, a Cessna 172N registered N737QQ was involved in an accident near Bolinas, California, United States. One person was on board and one died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 21:00
- Classification
- Accident
- Location
- Bolinas, California, United States
- Coordinates
- 37.9369, -122.7264
- Aircraft
- Cessna 172N
- Registration
- N737QQ
- Category
- Airplane
- Year built
- 1977
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Santa Ynez → Santa Rosa
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR17FA196
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 1 Mar 2017 | Cessna 172S | St Petersburg, Florida, United States | - | No injuries | - |
| 9 Nov 2017 | Cessna 172 | Trenton, New Jersey, United States | Christiansen Aviation Inc | No injuries | - |
| 19 Nov 2017 | Cessna 172M | Chico, California, United States | Northgate Aviation Inc | Minor injuries | - |
| 19 Nov 2017 | Cessna 172P | San Jose, California, United States | Squadron 2 | Serious injuries | - |
| 24 Jun 2017 | Cessna 172 | Fulton, Missouri, United States | - | Minor injuries | - |
| 16 Nov 2017 | Cessna 172RG | Opa Locka, Florida, United States | - | No injuries | - |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 1 Mar 2017 | Bell 206B | Firebaugh, California, United States | West Valley Aviation Inc | No injuries | - |
| 1 Aug 2017 | Rockwell S 2R | Brawley, California, United States | - | No injuries | - |
| 15 Sep 2017 | Cessna T210N | Watsonville, California, United States | Singh Amandeep | No injuries | - |
| 17 Nov 2017 | Piper PA 28R-201T | Nipton, California, United States | - | No injuries | - |
| 1 Mar 2017 | Maule MX7 | Live Oak, California, United States | - | Minor injuries | - |
| 5 May 2017 | Robinson R44 | Santa Barbara, California, United States | Santa Barbara Helicopter Tours | Serious injuries | - |