7 Jun 2008: CESSNA 150M

7 Jun 2008: CESSNA 150M — Unknown operator

1 fatality • Forrest City, AR, United States

Probable cause

The failure of the pilot to maintain adequate airspeed while maneuvering in the traffic pattern, resulting in an inadvertent aerodynamic stall.

— NTSB Determination

Accident narrative

On June 7, 2008, at approximately 1145 central daylight time, a single-engine Cessna 150M, was substantially damaged after impacting terrain near Forrest City Municipal Airport (FCY), Forrest City, Arkansas. The private pilot was seriously injured and the passenger sustained fatal injuries. The airplane was co-owned and operated by the pilot. The flight originated from Walnut Ridge Municipal Airport (ARG), Walnut Ridge, Arkansas at an unknown time and was destined for FCY. No flight plan was filed and visual meteorological conditions prevailed for the 14 Code of Federal Regulations Part 91 personal flight.

Two people provided eyewitness testimony. One eyewitness reported observing the pilot take-off with the airplane in a "very steep climb" numerous times prior to the day of the accident. On the day of the accident, this eyewitness observed the airplane in a steep climbing turn to enter the traffic pattern for runway 18. He estimated that the turn to enter the pattern was executed prior to reaching the departure end of the airfield.

A second eyewitness observed the airplane as it departed the airfield and entered the pattern. The eyewitness recalled that the engine sounded "smooth." Upon completing the turn to head north, the airplane was observed to descend rapidly and the impact the terrain nose-first. The eyewitness called for emergency services.

The pilot experienced difficulty recalling the events that transpired, but did recall that the approach did not seem normal, so he elected to perform a go-around. No further details could be provided by the pilot. The pilot was not able to provide an NTSB Form 6120.

An inspector from the Federal Aviation Administration (FAA) Flight Standards District Office (FSDO) responded to the scene and conducted an examination of the wreckage with technical assistance provided by representatives from Cessna Aircraft and Teledyne Continental Motors. The initial point of impact and main wreckage were located along a 350 degree magnetic heading. Impact signatures were consistent with a left wing low, steep-nose down attitude. Furthermore, the artiificial horizon displayed a left wing low, 15 degree nose down attitude. The throttle was found near the idle position. The mixture was found in the full-rich position. The flaps were found down at approximately 5 degrees. Elevator trim was found at approximately 5 degrees tab up. The wings were modified with a Horton short take-off and landing (STOL) kit, including wing vortex generators, modified wing tips and modified leading edges. The vertical stabilizer was modified with vortex generators. The fuel selector was in the "on" position and both wing fuel tanks were approximately 2/3 full. Fuel in both wing fuel tanks tested negative for water contamination using a water detection paste. No pre-impact anomalies were discovered with the airframe.

The engine's crankshaft was rotated by hand and valve train continuity and thumb compression was verified to all four cylinders. The magnetos were activated by hand-rotation of the propeller and "spark" was obtained from all harness leads. The firewall fuel screen and carburetor fuel screen were found clear of debris. The oil filter was examined and found to be clear of debris. No pre-impact anomalies were discovered with the engine.

At 1135 an automated weather reporting facility at Tunica Regional Airport (UTA), located approximately 26 nautical miles southeast of the accident site, reported winds from 130 degrees variable to 190 degrees at 11 knots gusting to 16 knots, visibility 10 miles, scattered clouds at 3,600 feet, temperature 88 degrees Fahrenheit, dew point 70 degrees Fahrenheit, and a barometric pressure of 30.12 inches of Mercury.

Contributing factors

  • cause Airspeed — Not attained/maintained

Conditions

Weather
VMC, wind 160/11kt, 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.