# Accident 19980925033239A: Cessna 152, Danbury, CT, September 25, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 25, 1998, 10:51 local time
- Place: Danbury, CT
- Airport: Danbury Municipal
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 41.3715° N, 73.4822° W: Placed by OpenAirDocs at DANBURY MUNI (DXR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.3715&lon=-73.4822&mi=10
- Aircraft: N94784, a cancelled registration (https://openairdocs.org/deregistered/N94784-2007-01-23) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYC O235L2C
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 33 total, 33 in this make and model, 8 in the last 90 days
- NTSB investigation: [NTSB IAD98LA111](https://openairdocs.org/ntsb/IAD98LA111) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980925033239A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

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.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB IAD98LA111](https://openairdocs.org/ntsb/IAD98LA111), Sep 25, 1998: Cessna 152 (N94784), Danbury, CT, substantial damage. Probable cause: The pilot's improper flare and improper recovery from a bounced landing.

## Other reports on N94784 (1)

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

- [Incident 19870716083482I](https://openairdocs.org/incident/19870716083482I), Jul 16, 1987: Cessna 152 (N94784), Burlington, CT, Minor damage. The aircraft was hit from behind during run up by N68215. Aircraft were lined up one behind the other.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.