FTW66F0036

NTSB accident investigation · Cessna 172 · Poth, TX · May 8, 1965

Accident · Minor injuriesClosed
Date
May 8, 1965
Place
Poth, TX · POTH, TX
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7724XCessna 172
Status
Completed · report July 29, 1965
Report
Brief approved by the director
Case key
181704

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-1280   65/5/8    POTH TEX            CESSNA 172          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 22, 26 TOTAL
        TIME - 1140                    N7724X              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - BECAME LOST/DISORIENTED
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT
                                  LOW ON FUEL

Aircraft

Registration
N7724X
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.