# Accident 20040829022299A: Cessna 172S, Erie, CO, August 29, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 29, 2004, 09:00 local time
- Place: Erie, CO
- Airport: Tri-County Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 40.0100° N, 105.0483° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.0100&lon=-105.0483&mi=10
- Aircraft: N2099J, a cancelled registration (https://openairdocs.org/deregistered/N2099J-2023-02-04) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 200 total, 165 in this make and model, 16 in the last 90 days
- NTSB investigation: [NTSB DEN04CA137](https://openairdocs.org/ntsb/DEN04CA137) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040829022299A

## Narrative

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

(-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.

## 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 DEN04CA137](https://openairdocs.org/ntsb/DEN04CA137), Aug 29, 2004: Cessna 172S (N2099J), Erie, CO, substantial damage. Probable cause: the 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.

## Other reports on N2099J (2)

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

- [Accident 20210910012829A](https://openairdocs.org/incident/20210910012829A), Sep 10, 2021: Cessna 172S (N2099J), Lasalle, CO, Substantial damage. The 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…
- [Incident 20150316002489I](https://openairdocs.org/incident/20150316002489I), Mar 16, 2015: Cessna 172S (N2099J), Broomfield, CO, Minor damage. Cessna 172S registration N2099J began take off roll on runway 29L and departed runway striking a runway landing light before coming to a rest.

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.