FTW68D0466

NTSB accident investigation · Piper PA-28 · Okla.City, OK · February 23, 1968

Accident · No injuriesClosed
Date
February 23, 1968
Place
Okla.City, OK · OKLA.CITY, OK
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4234JPiper PA-28
Status
Completed · report April 3, 1968
Report
Brief approved by the director
Case key
111941

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-0426  68/2/23    OKLA.CITY,OKLA      PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 54, 39 TOTAL
        TIME - 1550                    N4234J              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - EXPRESSWAY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N4234J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Expressway

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.