LAX81DVG63

NTSB accident investigation · Cessna R172K · Chiles Valley, CA · August 30, 1981

Accident · No injuriesClosed
Date
August 30, 1981
Place
Chiles Valley, CA · CHILES VALLEY, CA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N1580VCessna R172K
Status
Completed · report November 9, 1981
Report
Brief approved by the director
FAA report
19810830052839A
Case key
123915

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-2317  81/8/30    CHILES VALLEY,CA    CESSNA R172K        CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 22, 732
        TIME - 1800                    N1580V              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 52 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GILSON RANCH
        DEPARTURE POINT             INTENDED DESTINATION
          CHILES VALLEY,CA            SAN JOSE, CA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N1580V
Reported as
Cessna R172K
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Gilson Ranch

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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.