5 Sep 2013: CESSNA 210J — OLIN DAVID G

5 Sep 2013: CESSNA 210J (N210WS) — OLIN DAVID G

No fatalities • Fort Myers, FL, United States

Probable cause

The failure of the landing gear hydraulic power pack system to provide sufficient pressure to lock the main landing gear in the down position. Contributing to the accident was the improper maintenance and inspection of the landing gear system, the pilot’s continued operation of the airplane with a known mechanical problem with the landing gear system, and the pilot’s failure to visually verify that the landing gear were down.

— NTSB Determination

Accident narrative

On September 5, 2013, about 1130 eastern daylight time, a Cessna 210J, N210WS, owned and operated by a private individual, was substantially damaged during landing at Page Field Airport, (FMY) Fort Myers, Florida. The private pilot was not injured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight that departed Opa-Locka Executive Airport (OPF) Miami, Florida about 1100.

The pilot stated that after takeoff from OPF, the landing gear would not lock into place on the first attempt to retract, the amber light did not illuminate on the landing gear console, and that he had to recycle the landing gear handle to get the landing gear to retract and lock. The pilot stated that the remainder of the flight was "uneventful" to FMY.

While on final approach for runway 5 at FMY, the pilot configured the airplane for landing with a "notch" of flaps and by placing the landing gear handle in the "DOWN" position. He stated that he felt the associated "clunk" of the landing gear locking into place, set the elevator trim for landing, and adjusted for a right crosswind. For further confirmation, the pilot stated that he looked out the window and at the mirror mounted on the right wing and confirmed that the landing gear were down. The pilot also stated that the green landing gear "LOCKED" light "appeared" to be illuminated.

The pilot stated that upon touchdown at FMY, the plane "took flight again." As this transpired, the pilot leveled his attitude and "held steady." The stall warning horn sounded, the tail lowered and the airplane "took flight again." The airplane then settled to the tarmac and exited the left side of the runway.

A witness to the accident stated that he observed the airplane during landing, and that the main landing gear was trailing aft upon landing. He added that the nose landing gear was down and locked and that the airplane was "being cushioned by the partially extended main landing gear tires". He watched the airplane slide down the runway until it exited into the dirt. The witness asked the pilot if he looked out his left window to visually inspect the left main landing gear and the pilot stated that no one had ever showed him that.

Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed substantial damage to the right wing, aileron, horizontal stabilizer; and elevator. The left main landing gear hydraulic down lock was not in the locked position.

The pilot, age 41, held a private pilot certificate with a rating for single-engine land that was issued on August 31, 2004. According to pilot logbooks, the pilot had accrued 772 total flight hours of which 301 hours were in the same make and model as the accident airplane. FAA records indicate that the pilot's third-class medical was issued on April 3, 2013, with no restrictions.

The 1142 recorded weather observation at FMY included wind 120 degrees at 7 knots, visibility 10 statute miles, few clouds at 1,900 feet mean sea level, temperature 28 degrees C, dew point 26 degrees C, and an altimeter setting of 30.08 inches of mercury.

The 6 seat, high-wing, retractable gear airplane, serial number 21059135, was manufactured in 1969. According to airplane maintenance records, the most recent annual inspection was completed on April 1, 2013 at a recorded airframe total time of 6066.4 hours. At the time of the accident, the airplane hour meter read 6,081 hours. The airplane was powered by a Continental IO-520-F, 290-hp engine. Engine maintenance records showed that the engine had accrued 3,583 total hours, 1,249 hours since overhaul, and 11 hours since its most recent recorded inspection. The engine was equipped with a McCauley, model number E-01, three-bladed, controllable pitch propeller. Propeller maintenance logs showed that the last annual inspection was completed on April 1, 2013 at that time had 546.7 hours total time in service since new.

According to maintenance records, during the airplane's most recent annual inspection, hydraulic fluid was added, a hydraulic filter, and a hydraulic hose fitting was replaced. A landing gear inspection with normal and emergency extension operations was also completed by the maintenance facility, in Orlando, Florida.

According to a written statement by the pilot, the airplane was experiencing landing gear problems prior to the most recent annual inspection in April 2013, and perceived that the landing gear problems had ceased after that inspection and maintenance.

Further examination of the landing gear system by an FAA inspector at a maintenance facility revealed that the hydraulic level was normal but needed about one pint to completely service the fluid quantity. The down locks and main landing gear linkages were void of any lubrication, would not move freely, and covered with rust. The maintenance facility stated that the landing gear would only fully extend and lock two or three times out of 10 attempts, and the green down and locked light would illuminate with the gear unlocked. The mechanic's list of discrepancies is located in the public docket.

Contributing factors

  • cause Malfunction
  • factor Incorrect service/maintenance
  • factor Inadequate inspection
  • factor Maintenance personnel
  • factor Pilot
  • factor Pilot

Conditions

Weather
VMC, wind 120/07kt, 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, 40,000+ 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.