OpenAirDocs.org

20140913016819A

Accident · Substantial damage
Open the Markdown

FAA accident report · Cessna T210N · Gaithersburg, MD · September 13, 2014

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
September 13, 2014 · 13:40 local
Place
Gaithersburg, MD
Airport
Montgomery County
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N5132C
NTSB investigation
NTSBERA14TA435
Reported as
Cessna T210N
Reported engine
Continental TSIO-520 series
People aboard
3
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Commercial pilot
Pilot’s flight hours
6,000 total4,020 in this make and model
N5132CRegistration cancelled Dec 21, 2023 · Cessna T210NS/N 21063708Airframe modelCessna T210NEngine modelContinental TSIO-520 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

On September 13, 2014, privacy data omitted piloted aircraft N5132C, a Cessna 210 from millville, n.j. enroute to Gaithersburg airpark, Gaithersburg, Maryland under VFR conditions. During the flight ATC advised privacy data omitted of the weather conditions at gai. He was told that a falcon had to abort because of poor conditions there. privacy data omitted Then requested and was granted an IFR clearance. He was offered fdk as an alternate, but insisted on going to gai. privacy data omitted Was cleared for the runway 14 GPS approach and broke out at approximately 550 feet. After breaking out he was too FAR to the left of the runway, so he corrected back to the right in order to line up with the runway. As he continued his descent to a landing the aircraft touched down about midway down the runway. He said that his ground speed was approximately 78 KTS. The runway was wet from rain. He landed and could not get the airplane stopped. The airplane ran off the end of the runway into the grass, struck a mound and flipped over.

As the FAA filed it

ON SEPTEMBER 13, 2014, ^PRIVACY DATA OMITTED^ PILOTED AIRCRAFT N5132C, A CESSNA 210 FROM MILLVILLE, N.J. ENROUTE TO GAITHERSBURG AIRPARK, GAITHERSBURG, MARYLAND UNDER VFR CONDITIONS. DURING THE FLIGHT ATC ADVISED ^PRIVACY DATA OMITTED^ OF THE WEATHER CONDITIONS AT GAI. HE WAS TOLD THAT A FALCON HAD TO ABORT BECAUSE OF POOR CONDITIONS THERE. ^PRIVACY DATA OMITTED^ THEN REQUESTED AND WAS GRANTED AN IFR CLEARANCE. HE WAS OFFERED FDK AS AN ALTERNATE, BUT INSISTED ON GOING TO GAI. ^PRIVACY DATA OMITTED^ WAS CLEARED FOR THE RUNWAY 14 GPS APPROACH AND BROKE OUT AT APPROXIMATELY 550 FEET. AFTER BREAKING OUT HE WAS TOO FAR TO THE LEFT OF THE RUNWAY, SO HE CORRECTED BACK TO THE RIGHT IN ORDER TO LINE UP WITH THE RUNWAY. AS HE CONTINUED HIS DESCENT TO A LANDING THE AIRCRAFT TOUCHED DOWN ABOUT MIDWAY DOWN THE RUNWAY. HE SAID THAT HIS GROUND SPEED WAS APPROXIMATELY 78 KTS. THE RUNWAY WAS WET FROM RAIN. HE LANDED AND COULD NOT GET THE AIRPLANE STOPPED. THE AIRPLANE RAN OFF THE END OF THE RUNWAY INTO THE GRASS, STRUCK A MOUND AND FLIPPED OVER.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB ERA14TA435Accident · No injuriesFinal reportGaithersburg, MDThe pilot’s failure to execute a missed approach after recognizing that the airplane was not aligned with the wet runway, which resulted in a long landing with a tailwind and a subsequent runway overrun.Sep 13, 2014 · Substantial damage

Other reports on N5132C · 5

Matched to the same aircraft by N-number and date.

Accident 20220825015439ALanding: Touchdown · Georgetown, DEAirman returned to airport after having communication issues prior to turning on final approach. Airman then landed the aircraft with the gear up and while skidding it wore though fuselage skin and longerons until it came to a stop on the runway.Aug 25, 2022 · Substantial damageIncident 20180830012599IGround/Ramp/Ma · Avoca, PAThe pilot did not set the hand brake. The aircraft began to roll and it was not immediately noticed by the pilot, who at the time was reviewing a checklist. Upon noticing the movement, the pilot applied brakes. The aircraft contacted a parked vehicle,…Aug 30, 2018 · Minor damageIncident 20020330013359ILevel Off Touchdown · Gaithersburg, MD(-23) Nose gear collapse upon landing. Inspection of parts found old crack in nose gear collar where unit failed. Crack could not be seen until parts were removed and inspected. Area is not easily acceptable to inspection. There was a previous nose gear…Mar 30, 2002 · Minor damageIncident 19951111045479IGo Round (Aborted VFR) · Gaithersburg, MDNarrative: this pilot was conducting an IFR flight from charlottesville, VA to Gaithersburg, MD. Before departure the pilot received a wx briefing that indicated gusty winds and possible tsm in area. He was cleared through cassanova VOR to fdk VOR with the…Nov 11, 1995 · Minor damageIncident 19810815067479ILevel Off Touchdown · Saranac Lake, NYPilot changed approach patterns. Damaged propeller on touchdown because of hard landing.Aug 15, 1981 · Minor damage