19980925033239A

Accident · Substantial damage

FAA accident report · Cessna 152 · Danbury, CT · September 25, 1998

Date
September 25, 1998 · 10:51 local
Place
Danbury, CT
Airport
Danbury Municipal
Phase of flight
Level Off Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N94784
NTSB investigation
NTSBIAD98LA111
Reported as
Cessna 152
Reported engine
Lycoming O235L2C
People aboard
1
Fatal injuries
0
Pilot’s flight hours
33 total33 in this make and model8 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.

On September 25, 1998, at 1051 eastern daylight time, a Cessna 152, N94784, was substantially damaged during a hard landing at the Danbury Municipal Airport, Danbury, Connecticut. The student pilot was not injured. Visual meteorological conditions prevailed and a flight plan was not filed. The local, solo, instructional flight originated at Danbury, Connecticut, and was conducted under 14 CFR 91. The pilot reported that during touchdown on runway 17, he did not flare soon enough, and the airplane hit hard on all three wheels causing a bounce. He said he tried to recover from the bounce, but the airplane hit the ground again, and then the nose contacted the runway. According to a federal aviation administration (FAA) inspector, this was a supervised solo flight. The inspector reported that there was no mechanical malfunction with the airplane or the engine. The reported winds at the time of the accident were variable at 6 knots. (.4) the pilot reported that during touchdown on runway 17, he did not flare soon enough, and the airplane hit hard on all three wheels causing a bounce. He said he tried to recover from the bounce, but the airplane hit the ground again, and then the nose c ontacted the runway. The pilot reported that there was no mechanical malfunction with the airplane or the engine. The reported winds at the time of the accident was variable at 6 knots. (-23) did not flare soon enough and hit hard on all three wheels causing a bounce. Tried to recover but hit the ground again nose wheel first, causing the nose landing gear to break. (.19) on September 25, 1998, at 1051 eastern daylight time, a Cessna 152, N94784, was substantially damaged during a hard landing at the Danbury Municipal Airport, Danbury, Connecticut. The student pilot was not injured. Visual meteorological conditions prevailed and a flight plan was not filed. The local, solo, instructional flight originated at Danbury, Connecticut, and was conducted under 14 CFR 91. The pilot reported that during touchdown on runway 17, he did not flare soon enough, and the airplane hit hard on all three wheels causing a bounce. He said he tried to recover from the bounce, but the airplane hit the ground again, and then the nose contacted the runway. According to a federal aviation administration (FAA) inspector, this was a supervised solo flight. The inspector reported that there was no mechanical malfunction with the airplane or the engine. The reported winds at the time of the accident were variable at 6 knots.

As the FAA filed it

ON SEPTEMBER 25, 1998, AT 1051 EASTERN DAYLIGHT TIME, A CESSNA 152, N94784, WAS SUBSTANTIALLY DAMAGED DURING A HARD LANDING AT THE DANBURY MUNICIPAL AIRPORT, DANBURY, CONNECTICUT. THE STUDENT PILOT WAS NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND A FLIGHT PLAN WAS NOT FILED. THE LOCAL, SOLO, INSTRUCTIONAL FLIGHT ORIGINATED AT DANBURY, CONNECTICUT, AND WAS CONDUCTED UNDER 14 CFR 91. THE PILOT REPORTED THAT DURING TOUCHDOWN ON RUNWAY 17, HE DID NOT FLARE SOON ENOUGH, AND THE AIRPLANE HIT HARD ON ALL THREE WHEELS CAUSING A BOUNCE. HE SAID HE TRIED TO RECOVER FROM THE BOUNCE, BUT THE AIRPLANE HIT THE GROUND AGAIN, AND THEN THE NOSE CONTACTED THE RUNWAY. ACCORDING TO A FEDERAL AVIATION ADMINISTRATION (FAA) INSPECTOR, THIS WAS A SUPERVISED SOLO FLIGHT. THE INSPECTOR REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION WITH THE AIRPLANE OR THE ENGINE. THE REPORTED WINDS AT THE TIME OF THE ACCIDENT WERE VARIABLE AT 6 KNOTS. (.4) THE PILOT REPORTED THAT DURING TOUCHDOWN ON RUNWAY 17, HE DID NOT FLARE SOON ENOUGH, AND THE AIRPLANE HIT HARD ON ALL THREE WHEELS CAUSING A BOUNCE. HE SAID HE TRIED TO RECOVER FROM THE BOUNCE, BUT THE AIRPLANE HIT THE GROUND AGAIN, AND THEN THE NOSE C ONTACTED THE RUNWAY. THE PILOT REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION WITH THE AIRPLANE OR THE ENGINE. THE REPORTED WINDS AT THE TIME OF THE ACCIDENT WAS VARIABLE AT 6 KNOTS. (-23) DID NOT FLARE SOON ENOUGH AND HIT HARD ON ALL THREE WHEELS CAUSING A BOUNCE. TRIED TO RECOVER BUT HIT THE GROUND AGAIN NOSE WHEEL FIRST, CAUSING THE NOSE LANDING GEAR TO BREAK. (.19) ON SEPTEMBER 25, 1998, AT 1051 EASTERN DAYLIGHT TIME, A CESSNA 152, N94784, WAS SUBSTANTIALLY DAMAGED DURING A HARD LANDING AT THE DANBURY MUNICIPAL AIRPORT, DANBURY, CONNECTICUT. THE STUDENT PILOT WAS NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AND A FLIGHT PLAN WAS NOT FILED. THE LOCAL, SOLO, INSTRUCTIONAL FLIGHT ORIGINATED AT DANBURY, CONNECTICUT, AND WAS CONDUCTED UNDER 14 CFR 91. THE PILOT REPORTED THAT DURING TOUCHDOWN ON RUNWAY 17, HE DID NOT FLARE SOON ENOUGH, AND THE AIRPLANE HIT HARD ON ALL THREE WHEELS CAUSING A BOUNCE. HE SAID HE TRIED TO RECOVER FROM THE BOUNCE, BUT THE AIRPLANE HIT THE GROUND AGAIN, AND THEN THE NOSE CONTACTED THE RUNWAY. ACCORDING TO A FEDERAL AVIATION ADMINISTRATION (FAA) INSPECTOR, THIS WAS A SUPERVISED SOLO FLIGHT. THE INSPECTOR REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION WITH THE AIRPLANE OR THE ENGINE. THE REPORTED WINDS AT THE TIME OF THE ACCIDENT WERE VARIABLE AT 6 KNOTS.

NTSB investigation

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

Other reports on N94784 · 1

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