OAK68D0045

NTSB accident investigation · Piper PA-28 · Fresno, CA · June 30, 1967

Accident · No injuriesClosed
Date
June 30, 1967
Place
Fresno, CA · FRESNO, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N7730WPiper PA-28
Status
Completed · report October 9, 1967
Report
Brief approved by the director
Case key
116310

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-2262  67/6/30    FRESNO,CALIF        PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 136
        TIME - 1200                    N7730W              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 2 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FRESNO AIR TERM
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- ACFT TOUCHED DOWN 50 FT SHORT OF RNWY.

Aircraft

Registration
N7730W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fresno Air Term

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.