# Accident 19990527005889A: Cessna 172N, Kent, WA, May 27, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 27, 1999, 15:30 local time
- Place: Kent, WA
- Airport: Crest Airpark Airport
- Damage: Substantial damage
- Operating rules: General operating rules (Part 91)
- Location: 47.3594° N, 122.1004° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=47.3594&lon=-122.1004&mi=10
- Aircraft: N5120D, a cancelled registration (https://openairdocs.org/deregistered/N5120D-2001-05-07) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Fatal injuries: 0
- Pilot certificates: Student
- NTSB investigation: [NTSB SEA99LA077](https://openairdocs.org/ntsb/SEA99LA077) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990527005889A

## Narrative

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

ACFT CRASHED UNDER UNKNOWN CIRCUMSTANCES. (-23) STUDENT PILOT WAS ON A SOLO FLIGHT. HE HAD FLOWN IN THE PAST AND HAD RECENTLY BEGUN FLIGHT TRAINING TO OBTAIN A PRIVATE PILOTS CERTIFICATE. STUDENT PILOT PLANNED A FULL STOP LANDING ON RUNWAY 33, BUT LANDED LONG AND INITIATED A GO AROUND. THE A/C DID NOT CLIMB AND STRUCK TREES OFF THE END OF THE RUNWAY.

## 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 SEA99LA077](https://openairdocs.org/ntsb/SEA99LA077), May 27, 1999: Cessna 172N (N5120D), Covington, WA, substantial damage. Probable cause: The student pilot's inadequate recovery from a bounced landing, and his subsequent improper execution of the go-around procedure, resulting in collision with trees off the departure end of the…

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.