19971004030069A

Accident · Destroyed

FAA accident report · Piper PA-32-260 · College Park, MD · October 4, 1997

Date
October 4, 1997 · 08:40 local
Place
College Park, MD
Airport
College Park Airport
Phase of flight
Go Round (Aborted VFR)
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N7730J
NTSB investigation
NTSBIAD98FA001
Reported as
Piper PA32260
Reported engine
Lycoming O540E4B5
People aboard
1
Fatal injuries
0
Pilot’s flight hours
200 total6 in this make and model1 in the last 90 days

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.

Porpoised down the runway after landing, struck metro tracks at the end of the runway. (.4) the pilot remarked that all systems on the airplane were fully operational and the flight to his destination went uneventfully. He descended to 1,500 feet MSL and entered the traffic pattern on the downwind leg. He selected 10 degrees of flaps on base leg, and while crossing the 194 foot displaced threshold for the 2,610 foot runway, noticed that the airspeed was slow. During the flair for landing, the pilot closed the throttle, and remembered rolling out on the grass next to the runway. While attempting to remain parallel to the runway, the pilot aborted the landing. The airplane accelerated after raising the flaps, and once airborne, the pilot recalled `the airplane did not seem to climb, and the engine sounded correct for full power.' The airplane was seen in a nose high attitude, wings rocking as it impacted a 20 foot high embankment at the departure end of runway. No mechanical anomalies were found with the airframe or engine.

As the FAA filed it

PORPOISED DOWN THE RUNWAY AFTER LANDING, STRUCK METRO TRACKS AT THE END OF THE RUNWAY. (.4) THE PILOT REMARKED THAT ALL SYSTEMS ON THE AIRPLANE WERE FULLY OPERATIONAL AND THE FLIGHT TO HIS DESTINATION WENT UNEVENTFULLY. HE DESCENDED TO 1,500 FEET MSL AND ENTERED THE TRAFFIC PATTERN ON THE DOWNWIND LEG. HE SELECTED 10 DEGREES OF FLAPS ON BASE LEG, AND WHILE CROSSING THE 194 FOOT DISPLACED THRESHOLD FOR THE 2,610 FOOT RUNWAY, NOTICED THAT THE AIRSPEED WAS SLOW. DURING THE FLAIR FOR LANDING, THE PILOT CLOSED THE THROTTLE, AND REMEMBERED ROLLING OUT ON THE GRASS NEXT TO THE RUNWAY. WHILE ATTEMPTING TO REMAIN PARALLEL TO THE RUNWAY, THE PILOT ABORTED THE LANDING. THE AIRPLANE ACCELERATED AFTER RAISING THE FLAPS, AND ONCE AIRBORNE, THE PILOT RECALLED `THE AIRPLANE DID NOT SEEM TO CLIMB, AND THE ENGINE SOUNDED CORRECT FOR FULL POWER.' THE AIRPLANE WAS SEEN IN A NOSE HIGH ATTITUDE, WINGS ROCKING AS IT IMPACTED A 20 FOOT HIGH EMBANKMENT AT THE DEPARTURE END OF RUNWAY. NO MECHANICAL ANOMALIES WERE FOUND WITH THE AIRFRAME OR ENGINE.

NTSB investigation

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