UNK65X0214

NTSB accident investigation · Cessna 182 · Redding, CA · October 9, 1964

Accident · Serious injuriesClosed
Date
October 9, 1964
Place
Redding, CA · REDDING, CA
Injuries
1 serious, 1 minor, 2 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N4066DCessna 182
Status
Completed · report November 25, 1964
Report
Brief approved by the director
Case key
186005

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
----------------------------------------------------------------------------------------------------------------------------
2-0563   64/10/9   REDDING CALIF       CESSNA 182          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 31, 109
        TIME - 1905                    N4066D              PX-  0  0  3  BUSINESS                  TOTAL HOURS, 19 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BENTON FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: WIRES/POLES                               LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,AND ALTITUDE
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N4066D
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Benton Field

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.