20030629012989A

Accident · Substantial damage

FAA accident report · Cessna 172K · White Marsh, MD · June 29, 2003

Date: June 29, 2003 · 12:17 local
Place: White Marsh, MD
Phase of flight: Forced Landing
Operating rules: General operating rules (Part 91)
Damage: Substantial damage
Aircraft: N5138G
NTSB investigation: NTSBNYC03LA139
Reported as: Cessna 172K
Fatal injuries: 0
Pilot’s flight hours: 75 total60 in this make and model5 in the last 90 days

N5138GRegistration cancelled Jul 10, 2006 · Cessna 172KS/N 17259068 · Built 1970 Airframe modelCessna 172K Engine modelLycoming 0-320 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.

(-23) Aircraft left mtn for hgr approx 8 am. Went from hgr to fdk. On the way back from fdk pilot was told by potomac center to hold because they could not find his flight plan. Potomac had pilot circle for over an over as stated by the pilot. Pilot told potomac that he needed to land soon. He says that he may have said something about a fuel problem. Pilot was finally told to contact mtn. Pilot was cleared to land 15 at mtn and told to report over White Marsh. Pilot reported over White Marsh and was cleared again to runway 15. After this last contact the engine started to miss and the pilot declared and emergency. The pilot looked around for a place to land and did a 180 degree turn back to a field that he just passed over. After he made the turn he realized that he was not going to make the field and set the aircraft up to land in the trees. The pilot and both passengers were able to walk away from the airplane after it came down to ground level.

As the FAA filed it

(-23) AIRCRAFT LEFT MTN FOR HGR APPROX 8 AM. WENT FROM HGR TO FDK. ON THE WAY BACK FROM FDK PILOT WAS TOLD BY POTOMAC CENTER TO HOLD BECAUSE THEY COULD NOT FIND HIS FLIGHT PLAN. POTOMAC HAD PILOT CIRCLE FOR OVER AN OVER AS STATED BY THE PILOT. PILOT TOLD POTOMAC THAT HE NEEDED TO LAND SOON. HE SAYS THAT HE MAY HAVE SAID SOMETHING ABOUT A FUEL PROBLEM. PILOT WAS FINALLY TOLD TO CONTACT MTN. PILOT WAS CLEARED TO LAND 15 AT MTN AND TOLD TO REPORT OVER WHITE MARSH. PILOT REPORTED OVER WHITE MARSH AND WAS CLEARED AGAIN TO RUNWAY 15. AFTER THIS LAST CONTACT THE ENGINE STARTED TO MISS AND THE PILOT DECLARED AND EMERGENCY. THE PILOT LOOKED AROUND FOR A PLACE TO LAND AND DID A 180 DEGREE TURN BACK TO A FIELD THAT HE JUST PASSED OVER. AFTER HE MADE THE TURN HE REALIZED THAT HE WAS NOT GOING TO MAKE THE FIELD AND SET THE AIRCRAFT UP TO LAND IN THE TREES. THE PILOT AND BOTH PASSENGERS WERE ABLE TO WALK AWAY FROM THE AIRPLANE AFTER IT CAME DOWN TO GROUND LEVEL.

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 NYC03LA139Accident · Minor injuriesLimited investigationFinal reportWhite Marsh, MDThe pilot's in-flight decision to not land and refuel, which resulted in fuel exhaustion. A factor in the accident was the pilot's inadequate communications.Jun 29, 2003 · Substantial damage