MKC73DCG31

NTSB accident investigation · Cessna 172D · Queen City, MO · December 24, 1972

Accident · No injuriesClosed
Date
December 24, 1972
Place
Queen City, MO · QUEEN CITY, MO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N2817UCessna 172D
Status
Completed · report March 23, 1973
Report
Brief approved by the director
Case key
169368

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-3699  72/12/24   QUEEN CITY,MO       CESSNA 172D         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 62, 426
        TIME - 1500                    N2817U              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 17 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SCHUYLER COUNTY
        DEPARTURE POINT             INTENDED DESTINATION
          QUEEN CITY,MO               LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          TAXI: FROM LANDING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        REMARKS- TAIL SECTION HIT FENCE DRG TURN.

Aircraft

Registration
N2817U
Reported as
Cessna 172D
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Schuyler County

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.