# NTSB SEA06LA012: Cessna 172, N6000A, Gleneden Beach, OR, October 21, 2005

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: October 20, 2005, 20:00 local (Oct 21, 2005, 03:00 UTC)
- Place: Gleneden Beach, OR
- Coordinates: 44.866664, -124.01667
- Nearby events: https://openairdocs.org/map.md?lat=44.8667&lon=-124.0167&mi=10
- Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report March 28, 2006
- Report: Approved by Office Director
- Parties: FAA-FSDO
- NTSB case key (mKey): 62729
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA06LA012
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/62729/pdf
- Page: https://openairdocs.org/ntsb/SEA06LA012

## Probable cause

The pilot's failure to maintain clearance from objects while maneuvering over the airport environment.  Dark night conditions, trees, and ground fog were factors.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- In flight collision with object, maneuvering
  - object - tree(s) (contributing factor)
  - clearance - not maintained, pilot in command (cause)
  - weather condition - fog (contributing factor)
  - light condition - dark night (contributing factor)

## Analysis

The pilot reported that he was in-flight maneuvering over the airstrip to determine runway conditions.  There was ground fog present and the lighting conditions were "very dark."  The pilot circled the airstrip three or four times and he had the rotating beacon and runway lights in sight, however, he lost sight of the runway lights and when he passed by the rotating beacon he pulled up and heard something hit the right wing.  The pilot believed that he was near the southwest end of the airport environment when this happened.  The pilot stated that he was unsure if he hit a tree or a bird, but decided not to land and diverted to another airport 42 nautical miles to the northeast, where a landing was made without further incident.  Inspection of the aircraft revealed that the right wing tip, to include the outboard rib and about half of the right side aileron had been torn away.

## Factual narrative

On October 20, about 2000 Pacific daylight time, a Cessna 172, N6000A, registered to and operated by the pilot as a 14 CFR Part 91 personal flight, collided with a tree while maneuvering near the Siletz Bay State Airport, Gleneden Beach, Oregon.  Visual meteorological conditions prevailed at the time and no flight plan was filed.  The aircraft was substantially damaged and the private pilot and passenger were not injured.  The flight departed from Hillsboro, Oregon, about 30 minutes prior to the accident with the intended destination of Siletz Bay State.

During a telephone interview, the pilot reported that he was maneuvering around the airstrip to determine runway conditions.  There was ground fog present and the lighting conditions were "very dark."  The pilot circled the airstrip three or four times and he had the rotating beacon and runway lights in sight, however, he lost sight of the runway lights and when he passed by the rotating beacon he pulled up and heard something hit the right wing.  The pilot believed that he was near the southwest end of the airport environment when this happened.  The pilot stated that he was unsure if he hit a tree or a bird, but decided not to land and diverted to McMinnville, Oregon, a distance of 42 nautical miles to the northeast, where a landing was made without further incident.

Inspection of the aircraft revealed that the right wing tip, to include the outboard rib and about half of the right side aileron had been torn away.

## Aircraft

- Registration: [N6000A](https://openairdocs.org/aircraft/N6000A), registered now, S/N 28600, built 1956 (OpenAirDocs)
- Reported make and model: Cessna 172
- Registry model: [Cessna 172](https://openairdocs.org/model/cessna-172) (registry code 2072402) (OpenAirDocs)
- Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 28600
- Airframe hours: 5135
- Engines: Continental O-200 145 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: John M. Richards
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, December 1, 2004
- Departed: HIO, Hillsboro, OR
- Destination: S45, Gleneden Beach, OR
- Airport: S45, Siletz Bay State

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 55; injuries: none; private; airplane ratings: single-engine land; medical: class 3; last flight review October 1, 2004; seat: left; flight hours: 789 total, 600 in this make and model, 18 in the last 90 days, 4 in the last 30 days

## Weather

- Conditions: Visual (VMC), Night/dark
- Wind: calm
- Visibility: 2 statute miles
- Lowest ceiling: 100 ft broken
- Temperature: 52 °F, dew point 50 °F
- Altimeter: 30.20 inHg
- Observed at: ONP, 18 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20051020024739A](https://openairdocs.org/incident/20051020024739A), Oct 20, 2005: Cessna 172, Glenedon, OR, Substantial damage. (-23) The pilot [privacy data omitted] allowed his aircraft (N6000A) to descend to an unsafe altitude in the vicinity of the glenenden beach airport where he…

## Other investigations on N6000A (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 CHI67F0465](https://openairdocs.org/ntsb/CHI67F0465), Feb 3, 1967: Cessna 172 (N6000A), Roselle, IL, substantial damage

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.

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