UNK64X0507

NTSB accident investigation · Piper PA24 · Dallas, TX · February 9, 1964

Accident · FatalClosed
Date
February 9, 1964
Place
Dallas, TX · DALLAS, TX
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N5692PPiper PA24
Status
Completed · report January 7, 1965
Report
Brief approved by the director
Case key
123461

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
----------------------------------------------------------------------------------------------------------------------------
2-0097   64/2/9    DALLAS TEX          PIPER PA24          CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 46, 70 TOTAL
        TIME - 1900                    N5692P              PX-  0  0  0  BUSINESS                  HOURS, UNK/NR IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - REDBIRD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,ALTITUDE OR CLEARANCE
           MISCELLANEOUS ACTS,CONDITIONS - PILOT FATIGUE
         FIRE AFTER IMPACT

Aircraft

Registration
N5692P
Reported as
Piper PA24
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Redbird

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.