# Accident 20050618034189A: Cessna 172M, Rochester, MN, June 18, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 18, 2005, 17:25 local time
- Place: Rochester, MN
- Airport: Rochester Municipal
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 43.9072° N, 92.4989° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=43.9072&lon=-92.4989&mi=10
- Aircraft: N73328, a cancelled registration (https://openairdocs.org/deregistered/N73328-2012-02-21) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYC O320E2D
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 950 total, 874 in this make and model, 1 in the last 90 days
- NTSB investigation: [NTSB CHI05CA152](https://openairdocs.org/ntsb/CHI05CA152) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050618034189A

## Narrative

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

(-23) AIRCRAFT WAS LANDING ON RUNWAY 20 AT ROCHESTER, MN. DURING LANDING AIRCRAFT BOUNCED, PILOT ADDED POWER AND NOSEWHEEL STRUCK THE RUNWAY HARD. NOSE TIRE BLEW OUT, PROPELLER STRUCK RUNWAY. AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE TO 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 CHI05CA152](https://openairdocs.org/ntsb/CHI05CA152), Jun 18, 2005: Cessna 172M (N73328), Rochester, MN, substantial damage. Probable cause: The pilot flared improperly and failed to recover from a bounced landing.

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.