28 Mar 2009: CESSNA 182Q — Cody W. Greaves

28 Mar 2009: CESSNA 182Q (N97467) — Cody W. Greaves

No fatalities • Sedona, AZ, United States

Probable cause

The pilot's failure to achieve the proper touchdown point during a full-stop landing attempt. Contributing to the accident were the pilot's failure to ensure that the aircraft was properly configured for landing, his not initiating a go-around, and a malfunction in one of the main landing gear braking systems.

— NTSB Determination

Accident narrative

On March 27, 2009, about 1715 mountain standard time, a Cessna 182Q, N97467, hit a fence and nosed over after departing the end of the runway during a landing at Sedona Airport, Sedona, Arizona. The airline transport pilot, who was the sole occupant, was not injured, but the airplane, which was registered to Linear Management Corporation, sustained substantial damage. The 14 Code of Federal Regulations Part 91 cross-country positioning flight, which departed Cable Airport, Upland, California, about 1430 Pacific daylight time, was being operated in visual meteorological conditions. No flight plan had been filed.

During the investigation the NTSB Investigator-In-Charge (IIC) and the Federal Aviation Administration (FAA) Inspector who assisted with the investigation both conducted follow-up interviews with the pilot in order to clarify the sequence of events that he provided on the day of the accident and in the narrative of the NTSB Form 6120.1 that he submitted. According to the information derived from these interviews, when the pilot entered the downwind for runway 21 at Sedona, he selected a flap position of ten degrees, but because he was distracted by nearby hilly terrain and the presence of thermal turbulence, he did not visually confirm the position of the flaps. According to the pilot, when he turned onto final, he selected a flap position of 30 degrees, but once again did not visually check their position because of the distraction created by the turbulence. He further stated that although he did not visually check their position, he assumed the flaps were at 30 degrees on final, and at that point in time did not suspect any anomaly associated with the flap system. As he continued his final approach, the pilot realized that he was coming in too high, fast, and long, so he decided to execute a go-around. At the beginning of the go-around he repositioned the flaps to the 20 degree position, but reportedly did not feel the sinking sensation that he normally associated with a partial retraction of the flaps.

According to the pilot, because of the profile of his final approach, and since he did not feel the sinking sensation that he expected on the go-around, he thought that it was possible that the flaps might not be operating properly. Based upon that possibility, and because he had not visually confirmed their position at any time since entering the pattern, the pilot decided to leave the flaps where they were for the second approach.

During the second approach, the pilot proceeded as if he were making a no-flap landing, establishing an airspeed on final around 70 to 75 knots. Reportedly, his flare during this approach was near the halfway point of the runway, and he eventually touched down at the 4,000 foot point of the 5,183 foot long runway. He then attempted to apply maximum braking, but the brake pedal on the left brake rotated forward to its fully applied position with almost no resistance, and no braking action occurred at the left wheel. The pilot then tried to stop the airplane with only the one functional brake, but was unable to do so before the airplane exited the end of the runway. After the airplane departed the runway, it impacted a perimeter fence and nosed over onto its back.

An on-scene inspection found the flaps at 10 degrees.

After the accident, when the pilot was advised by the FAA that they were going to go inspect the airplane, he stated that they would find the flap handle in the 10 degree position, and that he thought the flaps were probably at 10 degrees during the second approach. In a further interview with the NTSB IIC, the pilot stated that the flaps were most likely functioning properly during both of his approaches, but that the turbulence may have masked that fact. During a post-accident function test performed by the airplane's owner, the flaps operated normally in all selector switch positions. In addition, the pilot reported that since he had not flown this airplane before this flight, prior to departure he performed a functionality check on all the airplane's systems, and no anomalies had been found.

As part of the investigation, an FAA Inspector inspected the left brake system, and it was determined that the left pedal master cylinder was low on fluid. It was also determined that very little braking or pedal resistance was present when the brake pedal was pushed toward its applied position, and according to the Inspector there was likely very little, if any, left wheel braking action during the pilot's attempt to stop the airplane after landing long.

Contributing factors

  • factor Malfunction
  • factor Pilot
  • cause Descent/approach/glide path — Not attained/maintained
  • cause Pilot
  • Incorrect use/operation
  • cause Pilot

Conditions

Weather
VMC, wind 000/04kt, 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.