Plane crash map Locate crash sites, wreckage and more

N2545H accident description

Washington map... Washington list
Crash location 48.160833°N, 122.160278°W
Nearest city Arlington, WA
48.198712°N, 122.125142°W
3.1 miles away
Tail number N2545H
Accident date 12 Jul 2003
Aircraft type Ercoupe 415-D
Additional details: None

NTSB Factual Report

On July 12, 2003, approximately 0940 Pacific daylight time, an Ercoupe 415-D single-engine airplane, N2545H, was substantially damaged following an overrun during the landing roll at the Arlington Municipal Airport (AWO), Arlington, Washington. The airplane was registered to and operated by a private individual. The private pilot sustained serious injuries, and his passenger was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the 14 CFR Part 91 personal flight which departed the Arlington Municipal Airport at 0815.

Consistent with on scene observations by the NTSB investigator-in-charge (IIC), and according to the Pilot/Operator Aircraft Accident Report (NTSB form 6120.1/2) submitted to the IIC by the pilot, the airport in use on the day of the accident was the site of an Experimental Aircraft Association (EAA) Flyin. In addition to runway 34 as being the active runway in use, a grass strip approximately 1,500 feet long and 200 feet wide, lying parallel to and east of runway 34, was being used to simultaneously accommodate the increase in air traffic. It was also noted by the IIC, and reported by the pilot, that a taxiway bordered and ran perpendicular to the grass strip on the north. The pilot reported that after being cleared to land he entered a right base leg for runway 34, but was then asked if he would "accept the grass." Seeing the long line of airplanes waiting [for runway 34], he decided to take the grass strip to help facilitate traffic taking off. The pilot stated that he "killed" [reduced] the power to idle and was over the threshold of the grass runway about 10 miles per hour faster the he liked. After touching down, he realized he had used up too much runway and decided to go around, but his speed was too slow to takeoff. The pilot related, "I had to decide if it was better to take off and risk a 'mush' back to the ground, or catch my wheels on the slope of the taxiway, or just steer for clear ground and hope for the best. I decided my chances to go around were all past, and so I headed up over the taxiway and down the other side. The airplane bounced a lot, and then headed down and flipped over on its back." The pilot further stated, "....my brakes did not seem to have any effect, as I felt like I was sliding on glass. I landed the evening before on this same grass strip without any problems." The pilot stated that he wasn't advised of the wind direction and speed before landing.

A certificated airframe and power plant mechanic, who examined the airplane, reported the fuselage was buckled, and that both rudders, horizontal stabilizers and the firewall had sustained substantial damage.

At 0955, the weather observation facility located at AWO reported wind 180 degrees at 7 knots.

NTSB Probable Cause

The pilot's failure to maintain proper approach speed and landing touch down point resulting in a runway overrun. A factor was the tailwind condition.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.