OAK68D0202

NTSB accident investigation · Piper PA-23 · Redding, CA · August 23, 1967

Accident · No injuriesClosed
Date
August 23, 1967
Place
Redding, CA · REDDING, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5286YPiper PA-23
Status
Completed · report December 27, 1967
Report
Brief approved by the director
Case key
113809

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-3551  67/8/23    REDDING,CALIF       PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 58, 2677
        TIME - 1745                    N5286Y              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 1697 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - BENTON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - CHECKLIST-FAILED TO USE

Aircraft

Registration
N5286Y
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Benton

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.