MKC73FCG23

NTSB accident investigation · Cessna 177 · Olathe, KS · November 18, 1972

Accident · No injuriesClosed
Date
November 18, 1972
Place
Olathe, KS · OLATHE, KS
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N3452TCessna 177
Status
Completed · report March 1, 1973
Report
Brief approved by the director
Case key
168896

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-3261  72/11/18   OLATHE,KAN          CESSNA 177          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 45, 107
        TIME - 1326                    N3452T              PX-  0  0  0  TRAINING                  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - JOHNSON COUNTY
        DEPARTURE POINT             INTENDED DESTINATION
          OLATHE,KAN                  LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - PREMATURE LIFT-OFF
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N3452T
Reported as
Cessna 177
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Johnson 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.