MIA68D0143

NTSB accident investigation · Cessna 172 · Fyffe, AL · August 6, 1967

Accident · No injuriesClosed
Date
August 6, 1967
Place
Fyffe, AL · FYFFE, AL
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N7586TCessna 172
Status
Completed · report November 8, 1967
Report
Brief approved by the director
Case key
115236

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-2817   67/8/6    FYFFE, ALA          CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 33, 350
        TIME - 1700                    N7586T              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 45 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - DELAYED ACTION IN ABORTING TAKEOFF
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - HIGH VEGETATION
        REMARKS- TOOK OFF FROM SHORT FARM FIELD,GRASS 1 FT HIGH. UNABLE TO CLEAR TREES END OF FIELD. STRUCK HOG LOT

Aircraft

Registration
N7586T
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.