UNK65X0125

NTSB accident investigation · Piper PA22 · Fresno, CA · October 3, 1964

Accident · No injuriesClosed
Date
October 3, 1964
Place
Fresno, CA · FRESNO, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N3730PPiper PA22
Status
Completed · report November 19, 1964
Report
Brief approved by the director
Case key
181374

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-3101   64/10/3   FRESNO CALIF        PIPER PA22          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 41, 311
        TIME - 1918                    N3730P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 300 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FRESNO AIR TMNL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    TAXI: FROM LANDING
           GEAR COLLAPSED                                           TAXI: FROM LANDING
        PROBABLE CAUSE(S)
          PILOT-TAXIED ONTO CONSTRUCTION AREA
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3730P
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fresno Air Tmnl

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.