4 Aug 2013: CESSNA 182P

4 Aug 2013: CESSNA 182P (N58437) — Unknown operator

No fatalities • Stanwood, WA, United States

Probable cause

The pilot’s unstabilized approach and his subsequent failure to maintain airspeed during the aborted landing, which resulted in a stall and the airplane bouncing hard on the runway.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn August 04, 2013, about 1130 Pacific daylight time, a Cessna 182P, N58437, collided with terrain shortly after the pilot aborted the landing at Camano Island Airfield, Stanwood, Washington. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot and passenger sustained serious injuries; the airplane sustained substantial damage. The local personal flight departed from Boeing Field/King County International Airport, Seattle, Washington about 1100 with a planned destination of Stanwood. Visual meteorological conditions prevailed and the pilot had filed a visual flight rules (VFR) flight plan.

Several witnesses observed the accident sequence. They stated that the airplane was landing on runway 16, which slopes upward at the first section. The airplane touched down hard after the mid-field area and bounced. The pilot then appeared to add full engine power in an attempt to abort the landing. The airplane climbed about 40 to 50 feet and stalled, descending into terrain.

The pilot stated that as he approached the vicinity of the airport, he observed the windsock indicating a light crosswind for runway 16. He maneuvered the airplane in a standard right-traffic pattern and when on final approach, he extended the flaps fully down while reducing the engine power. In an effort to ensure adequate clearance from trees located at the north end of the runway, he temporarily added power. While descending to the runway, the stall warning would intermittently sound and then there was a continuous stall horn. The airplane stalled and bounced hard on the runway surface. The pilot opted to abort the landing and applied full power. The engine hesitated and he began to retract the flaps. Subsequently the airplane lurched airborne as the engine power increased and the pilot was not able to maneuver the nose down before the airplane again stalled. The airplane bounced hard and rolled onto its side.

In the section titled "RECOMMENDATION" in the NTSB Pilot/Operator Report, form 6120.1/2, the pilot stated that the accident could have been prevented if he had executed a better short-field landing procedure to eliminate the airplane bouncing upon touchdown. He thought that because the airplane was loaded with a forward center of gravity, that a short-field landing was inadvisable because of the increased chance of a power-on stall during a go-around. He noted that he hadn't practiced short-field landings in over 10 months and should have considered a different destination. PERSONNEL INFORMATIONThe pilot was certified to operate the accident airplane in accordance with existing Federal Aviation Regulations (FARs). A review of the Federal Aviation Administration (FAA) Airman and Medical Records database disclosed that the pilot held a private pilot certificate, with ratings for airplane single-engine land and instrument flight. The pilot's third-class medical certificate was issued in April 2009, with no limitations.

The pilot's self-reported flight time indicated he had amassed 270 hours total flight experience, with 100 hours accumulated in Cessna 182 airplanes. The pilot reported that during the preceding 90 days, 30 days, and 24 hours, he had flown in the capacity of pilot-in-command approximately 46, 15, and 0 hours, respectively.

The pilot stated that he had purchased the airplane about one year before the accident. He recalled that he had been to the airport on past flights.

Contributing factors

  • cause Related operating info
  • cause Incorrect use/operation
  • cause Angle of attack — Not attained/maintained
  • cause Pilot

Conditions

Weather
VMC, wind 270/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.