Piper PA-18 accident near Enumclaw, Washington, July 2, 2011
On July 2, 2011 at about 11:00 pm local time, a Piper PA-18, registered N23TT, was destroyed in an accident during landing near Enumclaw, Washington (Ranger Station airport). It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain an adequate airspeed during an encounter with a mountain wave and downdraft landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 2, 2011 · about 11:00 pm local time · cases in 2011
- Place
- Enumclaw, Washington · Ranger Station · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-18 · all PA-18s on the register
- Registration
- N23TT · registry record · serial 18-6684
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that he was making an approach to an airstrip for a brief stop. He overflew the field and determined the wind was variable from the north and started his approach. On final approach he noticed an above average loss of altitude and speed due to a large mountain wave coming over the foothills to the west. He added power to compensate for the downdraft and continued on his landing approach. Once clear of some trees at the approach end of the runway he reduced the power to idle and was again pushed down by another downdraft. The pilot then added full power to arrest the airplane's descent but he did not have enough speed at that time to avoid a hard landing. The airplane slid off the runway and into a guard railing. The fuselage tubular frame sustained substantial damage. The pilot reported no mechanical problems that would have precluded normal operation.
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
- Windshear or thunderstorm during landing defining event
- Hard landing during landing (flare/touchdown)
- Runway excursion during landing (flare/touchdown)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Environmental issues › Conditions/weather/phenomena › Wind › Windshear › Response/compensation
- cause Environmental issues › Conditions/weather/phenomena › Wind › Downdraft › Response/compensation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 174 hours in all; 85 in this make and model; 3 in the last 90 days; 174 as pilot in command
- Last flight review: October 6, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 4,420 hours
- Last inspection: annual inspection, January 21, 2011; 10 hours since
- Maximum gross weight: 1,750 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320-A2B (piston); 0 hours total
The flight
- Departed from: 21W Enumclaw WA
- Destination: 21W Enumclaw WA
- Flight plan: not recorded
- Runway 33, 2,875 ft by 30 ft
Weather at the time
- Light: daylight
- Wind: at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 43°F (6°C)
- Altimeter: 29.88 inHg
- Observation at 11:35 pm from RNT, 40 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on July 22, 2011. 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 | Photo 1 - Skid Marks. Photo from FAA | PDF, 1 page | View Download |
| 3 | Photo 2 - Aircraft Damage. Photo from FAA | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N23TT the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N23TT on the register today · the tail number may have moved to another aircraft since
- Piper PA-18 Super Cub 3,620 registered today · the model family and its accident history
- Piper 44,844 aircraft on the register
- Engine: Lycoming O-320-A2B 179 aircraft carry this series today · as the NTSB recorded it
- Ranger Creek Airport · nearest airport
- Accidents and incidents in Washington 2,713 since 1982 · 361 in the last ten years
- Washington 10,661 aircraft registered
- Other NTSB records under N23TT 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/WPR11CA308.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
