20040829022299A

Accident · Substantial damage

FAA accident report · Cessna 172S · Erie, CO · August 29, 2004

Date: August 29, 2004 · 09:00 local
Place: Erie, CO
Airport: Tri-County Airport
Phase of flight: Level Off Touchdown
Operating rules: General operating rules (Part 91)
Damage: Substantial damage
Aircraft: N2099J
NTSB investigation: NTSBDEN04CA137
Reported as: Cessna 172S
People aboard: 1
Fatal injuries: 0
Pilot’s flight hours: 200 total165 in this make and model16 in the last 90 days

N2099JRegistration cancelled Feb 4, 2023 · Cessna 172SS/N 172S9586 · Built 2004 Airframe modelCessna 172S Engine modelLycoming IO-360-L2AReciprocating

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) At approximately 16:00 gmt, at the Erie municipal airport, Erie, Colorado, the aircraft listed above was substantially damaged when the pilot made a hard landing on the nose of the aircraft. The pilot did not know that he had damaged the aircraft so he did not stop and continued to fly the aircraft back to jeffco airport. At jeffco airport the pilot inspected the aircraft and he discovered that the prop did strike the runway and that there was some damage to the fuselage and firewall.

As the FAA filed it

(-23) AT APPROXIMATELY 16:00 GMT, AT THE ERIE MUNICIPAL AIRPORT, ERIE, COLORADO, THE AIRCRAFT LISTED ABOVE WAS SUBSTANTIALLY DAMAGED WHEN THE PILOT MADE A HARD LANDING ON THE NOSE OF THE AIRCRAFT. THE PILOT DID NOT KNOW THAT HE HAD DAMAGED THE AIRCRAFT SO HE DID NOT STOP AND CONTINUED TO FLY THE AIRCRAFT BACK TO JEFFCO AIRPORT. AT JEFFCO AIRPORT THE PILOT INSPECTED THE AIRCRAFT AND HE DISCOVERED THAT THE PROP DID STRIKE THE RUNWAY AND THAT THERE WAS SOME DAMAGE TO THE FUSELAGE AND FIREWALL.

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 DEN04CA137Accident · No injuriesData collectionFinal reportErie, COthe pilot's failure to maintain aircraft control resulting in a hard landing. Factors contributing to the accident were the pilot induced oscillation and the high approach airspeed.Aug 29, 2004 · Substantial damage

Other reports on N2099J · 2

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

Accident 20210910012829AManeuver · Lasalle, COThe flight instructor (CFI) and student pilot (sp) departed rocky mountain metro (bjc) at approximately 10:20 a.m. on a pre-solo cross-country progress check flight destined for kimball muni (imb). The flight included several simulated in-flight…Sep 10, 2021 · Substantial damage Incident 20150316002489ITakeoff: Departure Roll · Broomfield, COCessna 172S registration N2099J began take off roll on runway 29L and departed runway striking a runway landing light before coming to a rest.Mar 16, 2015 · Minor damage