# Accident 20000407012019A: Cessna 172P, Fort Collins, CO, April 7, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 7, 2000, 21:30 local time
- Place: Fort Collins, CO
- Airport: Fort Collins-Loveland Municipal Arp
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 40.5197° N, 105.1407° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.5197&lon=-105.1407&mi=10
- Aircraft: N65312, a cancelled registration (https://openairdocs.org/deregistered/N65312-2018-08-10) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- NTSB investigation: [NTSB DEN00LA070](https://openairdocs.org/ntsb/DEN00LA070) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000407012019A

## Narrative

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

(-23) THE PILOT STATED HE WAS ON A NIGHT CROSS COUNTRY FLIGHT FROM LIMON, CO. TO FT COLLINS, CO. HE STATED THAT HE HAD APPLIED THE BRAKES AFTER TAKEOFF FROM LIMON TO STOP TIRE ROTATION, PER HIS CHECKLIST. HE LISTENED TO THE AWOS REPORT AS HE APPROACHED THE FNL AIRPORT AND NOTED THE WINDS AT 030/10. LANDING WAS MADE ON RW33. HE SAID THAT UPON LANDING, THE A/C PULLED SUBSTANTIALLY TO THE RIGHT. HE STATED HE APPLIED LEFT RUDDER TO NO AVAIL. THE A/C DEPARTED THE RUNWAY AND STRUCK A RUNWAY TRAFFIC SIGN, SHEARING THE RIGHT MAIN GEAR OFF.

## 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 DEN00LA070](https://openairdocs.org/ntsb/DEN00LA070), Apr 8, 2000: Cessna 172P (N65312), Fort Collins, CO, substantial damage. Probable cause: On ground loss of control resulting in collision with airport markings due to inadequate compensation for wind conditions during landing roll. Factors were inaccurate in flight planning by landing…

## Other reports on N65312 (2)

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

- [Accident 20021006028679A](https://openairdocs.org/incident/20021006028679A), Oct 6, 2002: Cessna 172P (N65312), Denver, CO, Substantial damage. (-23) After landing at bjc, the pilot taxied to transient parking area southeast of main terminal. Finding this ramp full she then repositioned to another…
- [Incident 19900207009692I](https://openairdocs.org/incident/19900207009692I), Feb 7, 1990: Cessna 172P (N65312), Denver, CO, Minor damage. Was struck by another while taxiing on ramp. A mechanic was pilot of NR65312. Taxi was not intended for flight.

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.