DEN66D0322

NTSB accident investigation · Cessna 172 · Elroy, AZ · April 24, 1966

Accident · No injuriesClosed
Date
April 24, 1966
Place
Elroy, AZ · ELROY, AZ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N4170FCessna 172
Status
Completed · report June 30, 1966
Report
Brief approved by the director
Case key
172233

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

NTSB brief

NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.

----------------------------------------------------------------------------------------------------------------------------
 FILE    DATE          LOCATION          AIRCRAFT DATA       INJURIES       FLIGHT                        PILOT DATA
                                                               F  S M/N     PURPOSE
----------------------------------------------------------------------------------------------------------------------------
3-1098  66/4/24    ELROY ARIZ          CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 36, 39 TOTAL
        TIME - 1230                    N4170F              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - AL-DON AIRSTRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               TAXI: FROM LANDING
           COLLIDED WITH: PARKED AIRCRAFT                           TAXI: FROM LANDING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        REMARKS- PARKED ACFT.PIPER N66612 MINOR DAMAGE.N4170F PIVOTED AROUND POLE INTO N66612.

Aircraft

Registration
N4170F
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Al-Don Airstrip

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.