FTW68F0327

NTSB accident investigation · Cessna 140 · Dallas, TX · November 4, 1967

Accident · No injuriesClosed
Date
November 4, 1967
Place
Dallas, TX · DALLAS, TX
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N2242VCessna 140
Status
Completed · report January 5, 1968
Report
Brief approved by the director
Case key
113315

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-3819   67/11/4   DALLAS,TEX          CESSNA 140          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 19, 187
        TIME - 1350                    N2242V              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 2 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - DALLAS GARLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2242V
Reported as
Cessna 140
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.