LAX66F0225

NTSB accident investigation · Cessna 172 · Apple Valley, CA · January 31, 1966

Accident · Minor injuriesClosed
Date
January 31, 1966
Place
Apple Valley, CA · APPLE VALLEY, CA
Injuries
1 minor, 1 uninjured
Damage
Destroyed
Phase of flight
Approach
Aircraft
N8480XCessna 172
Status
Completed · report March 18, 1966
Report
Brief approved by the director
Case key
173773

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-0201  66/1/31    APPLE VALLEY CALI   CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 20, 88 TOTAL
        TIME - 1040                    N8480X              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 14 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - APPLE VALLEY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           PILOT IN COMMAND - MISUSED OR FAILED TO USE FLAPS
         FIRE AFTER IMPACT
        REMARKS- ATTEMPTED GO-AROUND WITH FLAPS EXTENDED

Aircraft

Registration
N8480X
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Apple Valley

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.