LAX74FUQ12

NTSB accident investigation · Bellanca 17-30A · Ridgecrest, CA · August 16, 1973

Accident · Serious injuriesClosed
Date
August 16, 1973
Place
Ridgecrest, CA · RIDGECREST, CA
Injuries
1 serious, 2 minor
Damage
Destroyed
Phase of flight
Approach
Aircraft
N8832VBellanca 17-30A
Status
Completed · report October 3, 1973
Report
Brief approved by the director
FAA report
19730816024019A
Case key
189334

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-2280  73/8/16    RIDGECREST,CALIF    BELLANCA 17-30A     CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 1071
        TIME - 1953                    N8832V              PX-  0  1  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CHINA LAKE NAS
        DEPARTURE POINT             INTENDED DESTINATION
          VAN NUYS,CALIF              BAKERSFIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    LANDING: TRAFFIC PATTERN-CIRCLING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N8832V
Reported as
Bellanca 17-30A
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
China Lake Nas

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.