DEN69F0004

NTSB accident investigation · Piper PA-28 · Salt Lake City, UT · June 17, 1968

Accident · Serious injuriesClosed
Date
June 17, 1968
Place
Salt Lake City, UT · SALT LAKE CITY, UT
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N9513WPiper PA-28
Status
Completed · report July 16, 1968
Report
Brief approved by the director
Case key
110192

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-1543  68/6/17    SALT LAKE CITY,UT   PIPER PA-28         CR-  0  1  0  INSTRUCTIONAL             STUDENT, AGE 26, 14 TOTAL
        TIME - 1606                    N9513W              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SALT LAKE CITY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- 1ST SOLO-BUSY ARPT.

Aircraft

Registration
N9513W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Salt Lake City

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.