MKC67D0253

NTSB accident investigation · Mooney M20C · Dexter, KS · October 24, 1966

Accident · No injuriesClosed
Date
October 24, 1966
Place
Dexter, KS · DEXTER, KS
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N5543QMooney M20C
Status
Completed · report February 2, 1967
Report
Brief approved by the director
Case key
120376

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-3741  66/10/24 NR.DEXTER,KANS        MOONEY M20C         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 178
        TIME - 1120                    N5543Q              PX-  0  0  2  BUSINESS                  TOTAL HOURS, 125 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           PILOT IN COMMAND - MISJUDGED DISTANCE
        FACTOR(S)
           TERRAIN - HIGH OBSTRUCTIONS
        REMARKS- UNABLE TO CLEAR WIRES,FLEW UNDER THEM.WINGTIP STRUCK TELEPHONE POLE.LANDED WITHOUT FURTHER DAMAGE.

Aircraft

Registration
N5543Q
Reported as
Mooney M20C
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.