FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA122 · Cessna 175 A

8 Feb 2016 · Gold Beach, OR, United States

Cessna 175 A · Accident: landing area undershoot

From Jack Mc Namara Field Airport (CEC) to Gold Beach Municipal Airport (4S1)

Report a problem

Event

NTSB case
GAA16CA122
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
0 · 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 175 A

Aircraft type
Cessna 175
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
N6951E
Operator
Daniel R. Harrison · private individual
Onboard fatalities
Unknown
Route
From Jack Mc Namara Field Airport (CEC), Crescent City, CATo Gold Beach Municipal Airport (4S1), Gold Beach, OR
Aircraft age
About 56 years (built 1960)
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
Landing
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
Landing area undershoot
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
  • Personnel issues › Task performance

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

NTSB narrative

According to the pilot, during approach, the airplane encountered a wind gust and the landing gear struck the top of the airport's perimeter fence. The airplane flipped over and slid to a stop. According to the airport facility directory the fence was in excess of 200 feet from the approach end of the runway which was 3,237 feet in length. The airplane sustained substantial damage to both wings, the rudder and the vertical stabilizer.

The pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation.

There weren't any wind reporting facilities at the airport.

Probable cause

The pilot's failure to maintain an approach angle of descent to avoid obstacles, resulting in the airplane striking the airport perimeter fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA122
Event ID
20160208X65013
Case number
GAA16CA122
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: 67471d3660527630a69937556d6c702d4988373e871ac928c7c76f4f5fb88b9a; retrieved 2026-09-16T03:08:33.891Z.