FTW67F0639

NTSB accident investigation · Cessna 175 · Mangum, OK · May 16, 1967

Accident · Serious injuriesClosed
Date
May 16, 1967
Place
Mangum, OK · MANGUM, OK
Injuries
3 serious
Damage
Destroyed
Phase of flight
Approach
Aircraft
N7399MCessna 175
Status
Completed · report September 13, 1967
Report
Brief approved by the director
Case key
116825

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
----------------------------------------------------------------------------------------------------------------------------
2-0368  67/5/16    MANGUM OKLA         CESSNA 175          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 33, 98 TOTAL
        TIME - 1710                    N7399M              PX-  0  2  0  BUSINESS                  HOURS, 1 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PONDER FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND
        REMARKS- WIND 360 DEGREES 20-25 KNOTS.

Aircraft

Registration
N7399M
Reported as
Cessna 175
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Ponder Field

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.