# Accident 20170727007939A: Cessna 172A, Enumclaw, WA, July 27, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 27, 2017, 20:55 local time
- Place: Enumclaw, WA
- Airport: Enumclaw
- Damage: Substantial damage
- Phase of flight: Other, Specify
- Operating rules: General operating rules (Part 91)
- Location: 47.1964° N, 122.0147° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=47.1964&lon=-122.0147&mi=10
- Aircraft: N7243T, a cancelled registration (https://openairdocs.org/deregistered/N7243T-2017-12-15) (OpenAirDocs)
- Registry model: Cessna 172A (registry code 2072404, https://openairdocs.org/model/cessna-172a) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172A
- Reported engine: CONT MOTOR 0-300-D
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 3
- Pilot certificates: Private pilot
- NTSB investigation: [NTSB WPR17LA169](https://openairdocs.org/ntsb/WPR17LA169) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170727007939A

## Narrative

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

ABORTED EAST LDG. ATTEMPTED GO-AROUND. CLIPPED THE TOP OF PERIMETER FENCE TAKING BARBED WIRE WITH AIRCRAFT.  CRASHED IN PARK EAST OF 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 WPR17LA169](https://openairdocs.org/ntsb/WPR17LA169), Jul 28, 2017: Cessna 172A (N7243T), Enumclaw, WA, substantial damage. Probable cause: The pilot's improper approach for landing, which resulted in the airplane landing long, and his delayed decision to go around with insufficient runway remaining, which resulted in collision with an…

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.