FTW6MF0154

NTSB accident investigation · Piper PA-22 · Dallas, TX · July 26, 1966

Accident · No injuriesClosed
Date
July 26, 1966
Place
Dallas, TX · DALLAS, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N4541ZPiper PA-22
Status
Completed · report October 6, 1966
Report
Brief approved by the director
Case key
122135

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-2098  66/7/26    DALLAS TEX          PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 36, 50 TOTAL
        TIME - 2000                    N4541Z              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 22 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - REDBIRD APT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            LANDING: FINAL APPROACH
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISMANAGEMENT OF FUEL
           MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION

Aircraft

Registration
N4541Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Redbird Apt

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.