UNK64X2045

NTSB accident investigation · Piper J3 · Bixby, OK · May 31, 1964

Accident · Serious injuriesClosed
Date
May 31, 1964
Place
Bixby, OK · BIXBY, OK
Injuries
1 serious, 1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N41308Piper J3
Status
Completed · report November 9, 1964
Report
Brief approved by the director
Case key
183675

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-0483  64/5/31  NR.BIXBY OKLA         PIPER J3            CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 35, 260
        TIME - 1015                    N41308              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 58 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: ABORTED
           GEAR COLLAPSED                                           TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
        FACTOR(S)
           TERRAIN - HIGH VEGETATION

Aircraft

Registration
N41308
Reported as
Piper J3
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.