FTW70F0251

NTSB accident investigation · Cessna 172H · Fort Worth, TX · October 10, 1969

Accident · Serious injuriesClosed
Date
October 10, 1969
Place
Fort Worth, TX · FORT WORTH, TX
Injuries
1 serious, 3 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N2879LCessna 172H
Status
Completed · report May 15, 1970
Report
Brief approved by the director
Case key
152290

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-4161  69/10/10   FORT WORTH,TEX      CESSNA 172H         CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 22, 68 TOTAL
        TIME - 1915                    N2879L              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  HOURS, 7 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - OAK GROVE
        DEPARTURE POINT             INTENDED DESTINATION
          HOUSTON,TEX                 FORT WORTH,TEX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
           TERRAIN - HIGH OBSTRUCTIONS

Aircraft

Registration
N2879L
Reported as
Cessna 172H
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Oak Grove

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.