# Accident 19990609043209A: Cessna 172N, Weaverville, CA, June 9, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 9, 1999, 12:30 local time
- Place: Weaverville, CA
- Airport: Lonnie Pool Field/Weaverville
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.7399° N, 122.9292° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.7399&lon=-122.9292&mi=10
- Aircraft: N5577E, a cancelled registration (https://openairdocs.org/deregistered/N5577E-2009-01-14) (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 LAX99LA213](https://openairdocs.org/ntsb/LAX99LA213) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990609043209A

## Narrative

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

(-23) PILOT ATTEMPTED A LOW PASS OVER RUNWAY 36 AT THE WEAVERVILLE AIRPORT, HE DID NOT INTEND TO LAND AND CAME WITHIN 15 FEET ABOVE THE RUNWAY. THE A/C SUDDENLY STRUCK THE GROUND APPROX. 1/3 TO 1/2 DOWN THE RUNWAY. PILOT BEGAN A GO AROUND AND DUE TO RAPIDLY RISING TERRAIN STRUCK TREES AT THE END OF THE RUNWAY. THE A/C FLIPPED OVER AND CRASHED.

## 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 LAX99LA213](https://openairdocs.org/ntsb/LAX99LA213), Jun 10, 1999: Cessna 172 (N5577E), Weaverville, CA, substantial damage. Probable cause: the pilot's failure to follow prescribed procedures and directives for the particular airport.

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.