# Accident 20050202002039A: Cessna 172N, Fort Collins, CO, February 2, 2005

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 2, 2005
- Place: Fort Collins, CO
- Airport: Fort Collins-Loveland Municipal Arp
- Damage: Substantial damage
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 40.4517° N, 105.0117° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.4517&lon=-105.0117&mi=10
- Aircraft: N618MN, registered now (https://openairdocs.org/aircraft/N618MN) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,180 total, 700 in this make and model, 110 in the last 90 days
- NTSB investigation: [NTSB DEN05LA055](https://openairdocs.org/ntsb/DEN05LA055) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050202002039A

## Narrative

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

(-23) AIRCRAFT WAS TOUCHING DOWN ON RUNWAY 15 WHEN AIRCRAFT BOUNCED BACK INTO THE AIR. FLIGHT INSTRUCTOR CALLED FOR A GO-AROUND, STUDENT PILOT APPLIED POWER AND PUSHED CONTROL YOKE FORWARD AND AIRCRAFT IMPACTED THE RUNWAY HARD. THE FLIGHT INSTRUCTOR TOOK CONTROL OF THE AIRCRAFT AT THAT TIME, BUT THE NOSE GEAR STRUT HAD BEEN DISLOCATED FROM THE FIREWALL ATTACH POINT AND NO STEERING WAS AVAILABLE TO THE PILOTS. THE AIRCRAFT BEGAN TO TURN LEFT AND EXITED THE RUNWAY AND CAME TO REST 20-30 FEET FROM THE RUNWAY IN THE MUD AND GRASS.

## 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 DEN05LA055](https://openairdocs.org/ntsb/DEN05LA055), Feb 2, 2005: Cessna 172N (N618MN), Loveland, CO, substantial damage. Probable cause: The dual student's improper flare and the flight instructor's inadequate supervision.. A contributing factor was the inadequate communication between the flight instructor and the dual student,

## Other reports on N618MN (3)

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

- [Incident 20040902021349I](https://openairdocs.org/incident/20040902021349I), Sep 2, 2004: Cessna 172N (N618MN), Fort Collins, CO. (-23) On September 2, 2004 N618MN, Cessna 172N made an off field landing 7 miles nw of 3V5, Fort Collins (weld county road 104 & 15) due to partial loss of…
- [Accident 19800427010519A](https://openairdocs.org/incident/19800427010519A), Apr 27, 1980: Cessna 172 (N618MN), Boulder, CO, Substantial damage. Landed long. Ran off end of runway. Runway end lights not lighted.
- [Incident 19800312033459I](https://openairdocs.org/incident/19800312033459I), Mar 12, 1980: Cessna 172N (N618MN), Ft Collins, CO, Minor damage. During training flight runup, instructor attempted to turn aircraft. A wind gust tipped the plane up on its nose.

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.