24 Dec 2019: Cessna 210 L

24 Dec 2019: Cessna 210 L (N30259) — Unknown operator

No fatalities • Concord, NC, United States

Probable cause

A malfunction of the left main landing gear brake during landing for undetermined reasons. Contributing was the pilot’s failure to attain a proper touchdown point and maintain an appropriate approach speed while landing on the wet turf runway.

— NTSB Determination

Accident narrative

On December 24, 2019, at 1600 eastern standard time, a Cessna 210L, N30259, was substantially damaged when it when it was involved in an accident at Spencer Airport (NC35), Concord, North Carolina. The pilot sustained minor injuries; the pilot-rated passenger and two other passengers were uninjured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91.

According to the pilot, while flying in the traffic pattern at NC35, he had performed one uneventful approach and then conducted a go-around to runway 21, a 2,180 ft long turf runway, which was wet from rainfall the previous day. The pilot stated that during the second approach his “sight picture looked normal, but he was hot and long.” After touching down about halfway down the runway, he tapped the brakes and the left brake “went to the floor” with little or no resistance. He pumped the brake in an attempt to get it to work but was unsuccessful. The airplane veered to the right, and he chose to ground loop the airplane into pine trees on the right side of the runway, to avoid a fence and drainage ditch off the end of the runway. The airplane struck trees, spun to the right, and came to rest.

According to the pilot, he had been having an intermittent problem with the left brake for nearly 2 years and had brought the airplane to two separate maintenance facilities to address the issue. The symptoms were very similar to the brake behavior on the day of the accident; however, he was always able to regain brake performance by pumping the brake pedal during previous events. A review of the airplane maintenance records revealed the master cylinder had been replaced twice, most recently 2 weeks before the accident, and previously in March 2019. It had also been overhauled in January 2019. Several other maintenance entries described replacement of o-rings, line plugs, the brake swivel and other brake hardware.

An examination of the wreckage at the accident site by a Federal Aviation Administration (FAA) inspector revealed substantial impact damage to the leading edge of both wings and buckling of the fuselage forward of the horizontal stabilizer and forward of the left door. The airplane impacted trees on the right side of the runway 21, near the end. A subsequent examination of the airplane at the salvage facility revealed that the left brake pedal had more travel than the right and did not offer as much resistance as the right brake pedal. No damage to the airplane was observed that would affect the operation of the pedal.

A set of marks in the turf runway consistent with a touchdown were found about halfway down the runway. Another set of asymmetrical skid marks on runway were found leading from the center of the runway toward the right side and ended at the impact location. The mark consistent with the right main landing gear was estimated to be about 500 feet long. The mark consistent with the left main landing was estimated to be about 75 feet long. Both marks were relatively continuous up to the impact location.

According to the pilot’s operating handbook, for landing at gross weight on a dry grass runway with zero wind, the required ground roll distance was 918 ft.

The Concord Regional Airport (JQF), Concord, North Carolina, located about 4 miles west of the accident site, was the nearest weather reporting station. At 1550, the reported weather included wind from 360° at 8 knots, visibility 10 miles, sky clear, temperature 18°C, dew point 8°C, and an altimeter setting of 30.04 inches of mercury. For a runway oriented on a heading of 210°, the tailwind component would be about 7 knots.

Contributing factors

  • Airspeed — Not attained/maintained
  • Pilot
  • Pilot
  • Malfunction
  • Contributed to outcome

Conditions

Weather
VMC, wind 360/08kt, 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.