FTW69D0138

NTSB accident investigation · Piper PA-28 · Dixie, LA · August 3, 1968

Accident · No injuriesClosed
Date
August 3, 1968
Place
Dixie, LA · DIXIE, LA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N1857JPiper PA-28
Status
Completed · report October 14, 1968
Report
Brief approved by the director
Case key
108782

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-2677   68/8/3    DIXIE,LA            PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 33, 47 TOTAL
        TIME - 1220                    N1857J              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - DIXIE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N1857J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Dixie

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.