# Accident 20151115022962A: Cessna 172L, Greeley, CO, November 15, 2015

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 15, 2015, 15:45 local time
- Place: Greeley, CO
- Damage: Substantial damage
- Collision: Collision on the ground
- Phase of flight: Taxi
- Operating rules: General operating rules (Part 91)
- Location: 40.4375° N, 104.6333° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.4375&lon=-104.6333&mi=10
- Aircraft: N4256Q, registered now (https://openairdocs.org/aircraft/N4256Q) (OpenAirDocs)
- Registry model: Cessna 172L (registry code 2072432, https://openairdocs.org/model/cessna-172l) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172L
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- NTSB investigation: [NTSB GAA16CA058](https://openairdocs.org/ntsb/GAA16CA058) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20151115022962A

## Narrative

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

PIC WAS HOLDING POSITION SHORT OF THE RUNWAY WHEN AN AIRCRAFT TAXIED INTO THE RUDDER.

SEE REPORT NUMBER A-NM-03-16-011

## Other aircraft in the event

- N70522, Piper J3C-65: [Accident 20151115021872A](https://openairdocs.org/incident/20151115021872A)

## 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 GAA16CA058](https://openairdocs.org/ntsb/GAA16CA058), Nov 15, 2015: Cessna 172 (N4256Q), Greeley, CO, substantial damage. Probable cause: The pilot of the following airplane failed to maintain adequate spacing during the taxi to the runway, resulting in a collision with the lead airplane.

## Other reports on N4256Q (1)

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

- [Incident 20070920824069I](https://openairdocs.org/incident/20070920824069I), Sep 20, 2007: Cessna 172L (N4256Q), Beaver Falls, PA, No damage. (-23) Upon takeoff the aircraft engine stopped at approx. 200' AGL. The pilot performed a 90 degree left turn while declaring an emergency with the tower and…

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.