# NTSB LAX99LA297: Cessna 205, N1854Z, Gualala, CA, September 5, 1999

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: September 5, 1999, 14:08 local (21:08 UTC)
- Place: Gualala, CA
- Coordinates: 38.82096, -123.509727 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=38.8210&lon=-123.5097&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report May 17, 2001
- Report: Approved by Office Director
- NTSB case key (mKey): 47310
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX99LA297
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/47310/pdf
- Page: https://openairdocs.org/ntsb/LAX99LA297

## Probable cause

The pilot's failure to attain a proper touchdown point due to his misjudgment of the aircraft's speed, altitude, and distance to the runway.  The pilot's failure to initiate a go-around is also causal.

## Sequence of events

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

- Overrun, landing - roll
  - airport facilities,runway/landing area condition - short runway/landing area
  - distance/speed - misjudged, pilot in command (cause)
  - proper touchdown point - not attained, pilot in command (cause)
  - go-around - not performed, pilot in command (cause)
- On ground/water collision with object, landing - roll
  - object - tree(s)

## Analysis

Approaching the airport, the pilot observed the windsock and noted it indicated calm wind conditions.  He chose to land on runway 13.  The airport manager observed the airplane land and opined that its approach had been too high.  The pilot reported that he had never been to the airport and acknowledged that his approach was high and he touched down long.  With insufficient runway to decelerate, the airplane skidded 150 feet off the runway's departure end and impacted trees.  The FAA's Airport Facility Directory indicated that runway 13 is 2,500 feet long and has a 400-foot displaced threshold due to the presence of trees.  During calm wind conditions, runway 31 should be used.

## Factual narrative

On September 5, 1999, about 1408 hours Pacific daylight time, a Cessna 205, N1854Z, owned and operated by the pilot, overran the departure end of runway 13 and collided with trees during landing rollout at the uncontrolled Ocean Ridge Airport, Gualala, California.  Visual meteorological conditions prevailed at the time, and no flight plan was filed.  The airplane was substantially damaged, and the private pilot was not injured.  The flight was performed under the provisions of 14 CFR Part 91, and originated from Watsonville, California, about 1241.

The Gualala Airport manager reported to the National Transportation Safety Board investigator that he observed the accident airplane during its approach and landing.  At the time, the wind was calm.  The airplane's approach path appeared to be too high, and the pilot touched down beyond midfield.  Thereafter, the airplane skidded off the departure end of the runway, veered left, and impacted trees about 150 feet beyond the runway's end.

The pilot reported to the Safety Board investigator that, prior to the accident, he had never landed at the Ocean Ridge Airport.  Upon arriving over the field he noted the windsock, and the wind was calm.  He stated that his approach was too high, he touched down long, and there was insufficient remaining runway to stop.  No mechanical failures or malfunctions were experienced with the airplane.

According to the "Airport Facility Directory," runway 13 is 2,500 feet long, and it has a 400-foot displaced threshold due to the presence of trees.  During calm wind conditions, runway 31 should be used.

## Aircraft

- Registration: [N1854Z](https://openairdocs.org/aircraft/N1854Z), registered now, S/N 2050054 (OpenAirDocs)
- Reported make and model: Cessna 205
- Registry model: [Cessna 210-5(205)](https://openairdocs.org/model/cessna-210-5-205) (registry code 2073202) (OpenAirDocs)
- Registry engine: [Continental I0-470 series](https://openairdocs.org/engine/continental-i0-470-series) (registry code 17027, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 0054
- Airframe hours: 2564
- Engines: Continental IO-470S 260 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: George E. Malby
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, August 1, 1999, 19 hours before
- Departed: WVI, WATSONVILLE, CA
- Destination: Q69
- Airport: Q69, Ocean Ridge, runway 13, 2,500 × 50 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 60; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 955 total, 435 in this make and model, 26 in the last 90 days, 22 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 91 °F, dew point 46 °F
- Altimeter: 29.00 inHg
- Observed at: UKI, 25 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 19990905044039A](https://openairdocs.org/incident/19990905044039A), Sep 5, 1999: Cessna 2105, Gualala, CA, No damage. (-23) Pilot stated that his approach was too high. He touched down long and there was insufficient remaining runway to stop. No mechanical failures or…

## Other investigations on N1854Z (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 NYC68D0358](https://openairdocs.org/ntsb/NYC68D0358), Jan 21, 1968: Cessna 210 (N1854Z), Hartford, CT, 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.
