25 Jan 2015: CESSNA 150 L

25 Jan 2015: CESSNA 150 L (N10616) — Unknown operator

No fatalities • Fernandina Beach, FL, United States

Probable cause

The pilot’s physical impairment due to intense pain, which resulted in his failure to maintain airplane control.

— NTSB Determination

Accident narrative

On January 25, 2015, about 1430 eastern standard time, a Cessna 150L, N10616, was substantially damaged when it impacted terrain while on approach to Fernandina Beach Municipal Airport (FHB), Fernandina Beach, Florida. The commercial pilot sustained serious injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight, which departed Lakeland Linder Regional Airport (LAL), Lakeland, Florida, at an unknown time, destined for FHB. The flight was conducted under the provisions of 14 Code of Federal Regulations Part 91.During a postaccident interview, the pilot reported that, as was his usual procedure, he flew along the west boundary of the Jacksonville Class B airspace until he was due west of his home airport. At which time he turned the airplane east, flew along the north boundary of the Class B airspace, directly to his home base airport. The distance between the departure and destination airports was about 160 nautical miles. Shortly after making the turn to the east, he experienced a "pain" in his right shoulder, which he experienced before when on a "long" car ride. After adjusting his seating position, he reported that the pain was tolerable. About 20 miles from his home base airport an "intense pain" began in his left shoulder, which was something he had not experienced previously. He contacted air traffic control, declared an emergency, and requested that an ambulance wait for him at the airport due to the intense pain. He attempted to line up for runway 9; however, he stated that he was unable to do so. He could not recall any details after that time.

According to a Federal Aviation Administration (FAA) inspector that responded to the accident location, the airplane impacted a berm on the east edge of a retention pond, about 1/2 mile from the approach end of runway 13. The airplane left a ground scar about 200 ft in length; subsequently, the nose landing gear separated and the airplane nosed over coming to rest inverted on the top of the berm. Photographs provided by the FAA inspector revealed that the fuselage was buckled, the outboard approximate 4 ft of the left wing was impact damaged, the top of the rudder was damaged, and forward of the firewall was bent. The propeller blades exhibited blade tip curling beginning about mid-span of the blades. There were no preimpact malfunctions or abnormalities noted with the airplane, that would have precluded normal operation.

Aircraft recovery personnel reported that about 15 gallons of fuel was removed from the fuel tanks and that the fuel tanks were unbreached.

Aircraft maintenance records provided by the mechanic indicated that the airplane's most recent annual inspection was recorded on January 22, 2014. At the time of the inspection the airplane had 8,891.2 total hours time in service. The airplane was powered by a Continental O-200-A engine.

According to the FAA, the 90-year-old pilot's most recent medical certification examination occurred on May 15, 2014, and included the limitation for corrective lenses for both near and distant vision. The certificate was also marked "not valid for any class after May 31, 2015." He had received a special issuance medical certificate due to diabetes since 2003. At the time of the medical examination, the pilot reported 25,265.5 total hours of flight experience.

Hospital records indicated that the pilot extricated himself from the airplane after the accident. He had been admitted to the hospital for about 3 weeks, due to injuries sustained during the accident. However, postaccident hospital evaluation found no definitive reason for the reported intense pain.

Contributing factors

  • cause Pilot
  • cause Pilot
  • cause Performance/control parameters — Not attained/maintained
  • Contributed to outcome

Conditions

Weather
VMC, wind 220/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, 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.