# Accident 20000809011739A: Cessna 172N, Glenedon, OR, August 9, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 9, 2000, 15:00 local time
- Place: Glenedon, OR
- Airport: Siletz Bay State Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 44.8803° N, 124.0301° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=44.8803&lon=-124.0301&mi=10
- Aircraft: N737CM, a cancelled registration (https://openairdocs.org/deregistered/N737CM-2013-02-21) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Fatal injuries: 0
- NTSB investigation: [NTSB SEA00LA155](https://openairdocs.org/ntsb/SEA00LA155) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000809011739A

## Narrative

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

(-23) A/C RECEIVED PRE-FLIGHT AND CONTROL GUST LOCK WAS NOT REMOVED PRIOR TO FLIGHT. OPERATOR STATED THAT GUST LOCK WAS NOT NORMALLY INSTALLED SO IT WAS OVERLOOKED DURING PRE-FLIGHT. AFTER SUCCESSIVE PRE-TAKEOFF RUNUP, THE A/C WAS POSITIONED IN THE ACTIVE RUNWAY. DURING GROUND ROLL THE PILOT DISCOVERED THAT THE CONTROLS WERE NOT REACTING TO COMMANDS. HE FURTHER DISCOVERED THAT THE GUST LOCK WAS INSTALLED. THE OPERATED ATTMPTED TO STOP THE A/C BUT WAS UNSUCCESSFUL. THE A/C RAN OFF THE END OF THE RUNWAY AND CAME TO REST IN A GULLY WITH SUBSTANTIAL DAMAGE TO A/C. MINOR INJURIES SUSTAINED BY THE OPERATOR. THE NEWPORT, OREGON POLICE AND EMERGENCY RESCUE GROUPS RESPONDED TO THE SCENE. NO FIRE OR GROUND PERSONNEL INJURIES.

## 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 SEA00LA155](https://openairdocs.org/ntsb/SEA00LA155), Aug 9, 2000: Cessna 172N (N737CM), Gleneden Beach, OR, substantial damage. Probable cause: The pilot's failure to remove the control lock during his preflight inspection. Factors contributing to the accident were the pilot's failure to follow the BEFORE TAKEOFF checklist, trees beyond the…

## Other reports on N737CM (1)

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

- [Accident 19790210005769A](https://openairdocs.org/incident/19790210005769A), Feb 10, 1979: Cessna 172 (N737CM), Sedona, AZ, Substantial damage. Student pilot made hard landing on nose wheel. Nose wheel tire blew out. Pilot lost directional control.

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.