FTW68F0619

NTSB accident investigation · Piper PA-28 · Dallas, TX · June 12, 1968

Accident · No injuriesClosed
Date
June 12, 1968
Place
Dallas, TX · DALLAS, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1875JPiper PA-28
Status
Completed · report July 3, 1968
Report
Brief approved by the director
Case key
110129

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-1446  68/6/12    DALLAS,TEX          PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 16, 13 TOTAL
        TIME - 1915                    N1875J              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - DALLAS GARLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N1875J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Dallas Garland

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.