Cessna 172 and Piper J3C accident near Greeley, Colorado, November 15, 2015
On November 15, 2015 at about 5:00 pm local time, 2 aircraft, Cessna 172 (N4256Q) and Piper J3C (N70522), were involved in the same accident near Greeley, Colorado (Greeley-Weld County airport). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 15, 2015 · about 5:00 pm local time
- Place
- Greeley, Colorado · Greeley-Weld County · map
- Type
- Accident · collision on the ground
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Cessna 172 L, built 1971 · all 172s on the register
- Registration
- N4256Q · registry record · serial 17260156
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
- Aircraft 2
- Piper J3C 65, built 1946 · all J3Cs on the register
- Registration
- N70522 · registry record · serial 17528
- Damage
- Minor damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Cessna 172 final · quoted from the NTSB record
According to the pilot of tandem cockpit, tailwheel-equipped Piper airplane, which he was operating from the rear seat, while taxiing to the runway his forward visibility was diminished by his airplane's nose, requiring the use of "S" turns in order to clear the area in front of the airplane. He reported that a Cessna airplane was in front of his airplane, and taxiing to the runway as well. He remarked that he and the Cessna were holding on the taxiway momentarily in order to monitor and give way to arriving and departing traffic. He reported that the Cessna moved forward, and he followed, but while entering the "S" turn, he lost sight of the Cessna. He remarked that he abruptly applied the right brake in order to avoid a collision, and his left wing impacted the Cessna's rudder. The pilot of the Cessna reported that during his taxi to the runway, his airplane was struck from behind by the Piper airplane. Both pilots shut down their airplanes, assessed the damage and exchanged information. The Cessna sustained substantial damage to the rudder, while the Piper sustained minor damage to the left wing. Both pilots reported that there were no mechanical failures or anomalies prior to or during the flight that would have prevented normal operation.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Piper J3C final · quoted from the NTSB record
According to the pilot of tandem cockpit, tailwheel-equipped Piper airplane, which he was operating from the rear seat, while taxiing to the runway his forward visibility was diminished by his airplane's nose, requiring the use of "S" turns in order to clear the area in front of the airplane. He reported that a Cessna airplane was in front of his airplane, and taxiing to the runway as well. He remarked that he and the Cessna were holding on the taxiway momentarily in order to monitor and give way to arriving and departing traffic. He reported that the Cessna moved forward, and he followed, but while entering the "S" turn, he lost sight of the Cessna. He remarked that he abruptly applied the right brake in order to avoid a collision, and his left wing impacted the Cessna's rudder. The pilot of the Cessna reported that during his taxi to the runway, his airplane was struck from behind by the Piper airplane. Both pilots shut down their airplanes, assessed the damage and exchanged information. The Cessna sustained substantial damage to the rudder, while the Piper sustained minor damage to the left wing. Both pilots reported that there were no mechanical failures or anomalies prior to or during the flight that would have prevented normal operation.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Cessna 172 from the NTSB's investigation tables, in plain English
What happened, in order
- Ground collision during taxi (to runway) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot of other aircraft
- cause Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot of other aircraft
Dual student
- Certificate: flight instructor, commercial pilot, private
- Ratings: single-engine land; instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
- Flight time: 1,208 hours in all; 63 in this make and model; 1,114 as pilot in command
- Last flight review: April 18, 2014
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,988.2 hours
- Last inspection: 100-hour inspection, October 24, 2015
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-E2D (piston); 5,763 hours total
The flight
- Departed from: GXY Greeley CO at 5:00 pm
- Destination: GXY Greeley CO
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 39°F (4°C), dew point 27°F (-3°C)
- Altimeter: 29.87 inHg
- Observation at 4:55 pm from KGXY
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
The factual record for the Piper J3C from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of visual reference during taxi (to runway) defining event
- Attempted remediation/recovery during taxi (to runway)
- Ground collision during taxi (to runway)
The NTSB's findings
- cause Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Physical environment › Object/animal/substance › Aircraft › Ability to respond/compensate
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine sea
- Flight time: 2,510 hours in all; 577 in this make and model; 20 in the last 90 days; 10 in the last 30 days; 2,450 as pilot in command
- Last flight review: March 2, 2009
- Medical certificate: Sport Pilot
- Seat: rear
- Injury: no injuries
The aircraft
- Airframe total time: 2,813 hours
- Last inspection: annual inspection, March 2, 2015
- Maximum gross weight: 1,220 lb
- Seats: 2
- Landing gear: fixed
- Engine: Cont Motor C75-8F (piston); 2,813 hours total
The flight
- Departed from: GXY Greeley CO
- Destination: GXY Greeley CO
- Flight plan: none
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.