# Accident 20170610010909A: Piper PA-28-161, Carpinteria, CA, June 10, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 10, 2017, 14:17 local time
- Place: Carpinteria, CA
- Damage: Substantial damage
- Phase of flight: Descent
- Operating rules: General operating rules (Part 91)
- Location: 34.4472° N, 119.4492° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=34.4472&lon=-119.4492&mi=10
- Aircraft: N2171D, a cancelled registration (https://openairdocs.org/deregistered/N2171D-2019-05-06) (OpenAirDocs)
- Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28-161
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot, unknown or foreign certificate
- Pilot flight hours: 280 total, 40 in this make and model, 106 in the last 90 days
- NTSB investigation: [NTSB WPR17LA124](https://openairdocs.org/ntsb/WPR17LA124) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170610010909A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

^MR. CHAEWON KO, ^PILOT OF N2171D, STATED HE DEPARTED MONTGOMERY-GIBBS EXECUTIVE AIRPORT(KMFY), SAN DIEGO, CA, ENROUTE TO SANTA YNEZ AIRPORT (KIZA), SANTA YNEZ, CALIFORNIA, TO LAND AND REFUEL. PILOT STATED HE DID RECEIVE A WEATHER BRIEFING PRIOR TO DEPARTURE FROM KMFY. HE STATED HE USED AN 'APP' ON HIS IPHONE FOR THE BRIEFING. PILOT STATED HE WAS AWARE OF CLOUDS ALONG THE ROUTE, BUT THOUGHT THEY WOULD CLEAR BY THE TIME HE APPROACHED KIZA. PILOT STATED HE WAS FLYING VFR WITH FLIGHT FOLLOWING BY ATC AT 10,500' MSL.

PILOT STATED HE LISTENED TO THE SANTA BARBARA AIRPORT (KSBA), SANTA BARBARA, CALIFORNA ATIS REPORT, AND HEARD THE CLOUDS WERE AT 2,200'. PILOT STATED HE BEGAN A DESCENT, AND ENTERED CLOUDS AT 5,500' MSL. PILOT STATED HE WAS IN THE CLOUDS, AND WAS UNABLE TO SEE THE GROUND. PILOT STATED HE WAS UNAWARE OF APPROACHING, RISING TERRAIN. AT 2,100' MSL, ACCIDENT AIRCRAFT IMPACTED TERRAIN. PILOT SUSTAINED FRACTURES TO BOTH LEGS, FACIAL LACERATIONS, AND TEETH LOST. PILOT WAS AIRLIFTED FROM SCENE BY HELICOPTER.

## The NTSB's investigation of this event (1)

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.

- [NTSB WPR17LA124](https://openairdocs.org/ntsb/WPR17LA124), Jun 10, 2017: Piper PA28 (N2171D), Carpinteria, CA, substantial damage. Probable cause: The noninstrument-rated pilot's improper decision to continue visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain.

## Other reports on N2171D (3)

Matched to the same aircraft by N-number and date.

- [Incident 20040110000669I](https://openairdocs.org/incident/20040110000669I), Jan 10, 2004: Piper PA28161 (N2171D), San Diego, CA, Minor damage. (-23) On January 10, 2004, at approximately 1433 PST, N2171D, a Piper PA-28-161 sustained a left main gear separation prior to landing at Montgomery field San…
- [Incident 20020903022039I](https://openairdocs.org/incident/20020903022039I), Sep 3, 2002: Piper PA28161 (N2171D), San Diego, CA, Minor damage. (-23) On September 3, 2002, at approximately 1852PST, N2171D, a Piper PA-28-161, sustained a collapsed left main gear during landing at Montgomery field San…
- [Incident 19910507018889I](https://openairdocs.org/incident/19910507018889I), May 7, 1991: Piper PA28161 (N2171D), Ramona, CA, Minor damage. Engine fire after landing. Used fire extinguisher. Suspects alternator and associated wiring was source of fire.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.