Cessna 172A accident near Enumclaw, Washington, July 28, 2017
On July 28, 2017 at about 3:30 am local time, a 1959 Cessna 172A, registered N7243T, was substantially damaged in an accident during landing (flare/touchdown) near Enumclaw, Washington (Enumclaw airport). It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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 airport perimeter fence.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 28, 2017 · about 3:30 am local time
- Place
- Enumclaw, Washington · Enumclaw · map
- Type
- Accident
- Injuries
- 2 people were seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172A UNDESIGNAT, built 1959 · all 172As on the register
- Registration
- N7243T · no longer on the register · serial 46843
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot and a noncurrent private pilot were conducting a local, personal flight. The student reported that he did not remember the flight or any details surrounding the accident other than that the private pilot was operating the airplane at the time of the accident. The private pilot did not provide an account of the accident. A witness reported seeing the airplane making touch-and-go landings and noted that, during the last landing, the airplane landed near the departure end of the runway, attempted to stop, but the left main tire skidded, and with about 40 yards remaining, power was added for a takeoff attempt. The airplane then travelled off the runway end onto grass, impacted the top of the airport's barbed wire perimeter fence, and came to rest nose down. The fence's top rail and about 260 ft of wire were found separated from the fence, a large part of the wire was twined around the airplane, and the top rail was found on the path between the runway and the wreckage, indicating that the airplane became airborne after the pilot added power. Examination of the airframe and engine did not reveal evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. Given the evidence, it is likely that the pilot did not establish a proper approach for landing, which resulted in the airplane landing long, and that his subsequent delayed decision to go around with insufficient runway remaining led to the airplane impacting an airport perimeter fence.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Landing area overshoot during landing (flare/touchdown) defining event
- Collision with terrain or object (not controlled flight into terrain) during takeoff
- Nose over/nose down during takeoff
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- cause Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Effect on operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Medical certificate: None
- Seat: unk
- Injury: serious injuries
Dual student
- Certificate: student
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: unk
- Injury: serious injuries
Passenger
- Seat: rear
The aircraft
- Last inspection: annual inspection, June 18, 2017; 3 hours since
- Maximum gross weight: 2,299 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor O-300 SER (piston); 3,490 hours total
- Fire on the ground
The flight
- Departed from: WA77 Enumclaw WA
- Destination: WA77 Enumclaw WA
- Flight plan: none
- Runway 07, 1,800 ft by 25 ft
Weather at the time
- Light: night
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 64°F (18°C), dew point 57°F (14°C)
- Altimeter: 30.10 inHg
- Observation at 3:35 am from KPLU
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
10 documents, released by the NTSB on January 14, 2020. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Phone Conversation with Owner | PDF, 1 page | View Download |
| 3 | FAA Witness Statement | PDF, 1 page | View Download |
| 4 | Wreckage Location | PDF, 1 page | View Download |
| 5 | FAA Statement | PDF, 2 pages | View Download |
| 6 | Engine Examination | PDF, 16 pages | View Download |
| 7 | Airframe Examination | PDF, 4 pages | View Download |
| 8 | Flight Instructor Reference | PDF, 1 page | View Download |
| 9 | Statement of Party Representatives to NTSB Investigation | PDF, 3 pages | View Download |
| 10 | Photos | PDF, 14 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
