DEN65F0111

NTSB accident investigation · Cessna 172 · Albuquerque, NM · May 29, 1965

Accident · No injuriesClosed
Date
May 29, 1965
Place
Albuquerque, NM · ALBUQUERQUE, NM
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6668ACessna 172
Status
Completed · report July 19, 1965
Report
Brief approved by the director
Case key
177846

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-1166  65/5/29    ALBUQUERQUE N MEX   CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 70 TOTAL
        TIME - 1400                    N6668A              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  HOURS, 20 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CORONADO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: PARKED AIRCRAFT                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER COMPENSATION FOR WIND CONDITIONS
        REMARKS- PARKED AIRCRAFT 4 SUBSTANTIALLY DAMAGED

Aircraft

Registration
N6668A
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Coronado

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.