20010809021889I

Incident · Minor damage

FAA incident report · Cessna 172N · Atlantic City, NJ · August 9, 2001

Date
August 9, 2001 · 09:50 local
Place
Atlantic City, NJ
Airport
Atlantic City Municipal-Bader Field
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N5215E
Reported as
Cessna 172N
Reported engine
Lycoming O320*
People aboard
2
Fatal injuries
0
Pilot’s flight hours
334 total150 in this make and model62 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.

(-23) On August 10, 2001, 0950 hours eastern daylight savings time, a Cessna 172N, N5215E, ran off runway 4 at Bader field, Atlantic City, NJ (aiy). The botched landing was made to a runway, which was restricted as being closed to landing traffic. The airplane sustained minor damage to the propeller when it veered off to the right approximately 2100 feet down the 2700 foot runway coming to rest at the edge of the bay. The pilot and passenger were not injured during the mishap. Montgomery aviation, a fixed base operator at gaithersburg, MD operated the aircraft, which was rented by the pilot, under the provisions of 14 CFR part 91. The personal flight departed montgomery county airpark at approximately 0845 with full fuel under an IFR flight plan to Atlantic City Municipal-Bader Field (aiy). The pilot requested a visual approach with ATC and cancelled IFR upon arrival at aiy. While in the traffic pattern, the pilot stated that he had planned to land on runway 11, but after listening to the field UNICOM that landings were being made to runway 4. The pilot also stated that the transmissions were very poor with much static. Subsequent review of the UNICOM pre-recorded advisory which was current at the time of incident revealed that runway 4 was closed to landing traffic and runway 22 was closed for takeoff. The pilot stated that he broke off the approach to runway 11 and circled to land runway 4 after hearing the UNICOM advisory and made a normal approach using full flaps at an indicated airspeed of 60 KTS. The pilot also stated that he had landed on the first third of the runway and did not have full breaking until he raised the flaps. The skid marks at the incident site began at the intersection of runways 11-29 and 4-22 and veered off to the right of runway 4. The aircraft role was interrupted by a large boulder along the Beech embankment preventing the aircraft from being submerged in the bay. The pilot had secured the engine, fuel and electric power prior to the aircraft coming to rest. Atlantic City arf responded and there was no post-crash fire. There was no visible damage to the aircraft structure and only one of the propeller blade had been damaged.

As the FAA filed it

(-23) ON AUGUST 10, 2001, 0950 HOURS EASTERN DAYLIGHT SAVINGS TIME, A CESSNA 172N, N5215E, RAN OFF RUNWAY 4 AT BADER FIELD, ATLANTIC CITY, NJ (AIY). THE BOTCHED LANDING WAS MADE TO A RUNWAY, WHICH WAS RESTRICTED AS BEING CLOSED TO LANDING TRAFFIC. THE AIRPLANE SUSTAINED MINOR DAMAGE TO THE PROPELLER WHEN IT VEERED OFF TO THE RIGHT APPROXIMATELY 2100 FEET DOWN THE 2700 FOOT RUNWAY COMING TO REST AT THE EDGE OF THE BAY. THE PILOT AND PASSENGER WERE NOT INJURED DURING THE MISHAP. MONTGOMERY AVIATION, A FIXED BASE OPERATOR AT GAITHERSBURG, MD OPERATED THE AIRCRAFT, WHICH WAS RENTED BY THE PILOT, UNDER THE PROVISIONS OF 14 CFR PART 91. THE PERSONAL FLIGHT DEPARTED MONTGOMERY COUNTY AIRPARK AT APPROXIMATELY 0845 WITH FULL FUEL UNDER AN IFR FLIGHT PLAN TO ATLANTIC CITY MUNICIPAL-BADER FIELD (AIY). THE PILOT REQUESTED A VISUAL APPROACH WITH ATC AND CANCELLED IFR UPON ARRIVAL AT AIY. WHILE IN THE TRAFFIC PATTERN, THE PILOT STATED THAT HE HAD PLANNED TO LAND ON RUNWAY 11, BUT AFTER LISTENING TO THE FIELD UNICOM THAT LANDINGS WERE BEING MADE TO RUNWAY 4. THE PILOT ALSO STATED THAT THE TRANSMISSIONS WERE VERY POOR WITH MUCH STATIC. SUBSEQUENT REVIEW OF THE UNICOM PRE-RECORDED ADVISORY WHICH WAS CURRENT AT THE TIME OF INCIDENT REVEALED THAT RUNWAY 4 WAS CLOSED TO LANDING TRAFFIC AND RUNWAY 22 WAS CLOSED FOR TAKEOFF. THE PILOT STATED THAT HE BROKE OFF THE APPROACH TO RUNWAY 11 AND CIRCLED TO LAND RUNWAY 4 AFTER HEARING THE UNICOM ADVISORY AND MADE A NORMAL APPROACH USING FULL FLAPS AT AN INDICATED AIRSPEED OF 60 KTS. THE PILOT ALSO STATED THAT HE HAD LANDED ON THE FIRST THIRD OF THE RUNWAY AND DID NOT HAVE FULL BREAKING UNTIL HE RAISED THE FLAPS. THE SKID MARKS AT THE INCIDENT SITE BEGAN AT THE INTERSECTION OF RUNWAYS 11-29 AND 4-22 AND VEERED OFF TO THE RIGHT OF RUNWAY 4. THE AIRCRAFT ROLE WAS INTERRUPTED BY A LARGE BOULDER ALONG THE BEECH EMBANKMENT PREVENTING THE AIRCRAFT FROM BEING SUBMERGED IN THE BAY. THE PILOT HAD SECURED THE ENGINE, FUEL AND ELECTRIC POWER PRIOR TO THE AIRCRAFT COMING TO REST. ATLANTIC CITY ARF RESPONDED AND THERE WAS NO POST-CRASH FIRE. THERE WAS NO VISIBLE DAMAGE TO THE AIRCRAFT STRUCTURE AND ONLY ONE OF THE PROPELLER BLADE HAD BEEN DAMAGED.

Other reports on N5215E · 2

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