MIA73FLD11

NTSB accident investigation · Cessna 140 · Tampa, FL · August 20, 1972

Accident · No injuriesClosed
Date
August 20, 1972
Place
Tampa, FL · TAMPA, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2652NCessna 140
Status
Completed · report March 15, 1973
Report
Brief approved by the director
Case key
168455

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-3168  72/8/20    TAMPA,FLA           CESSNA 140          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 53, 13700
        TIME - 1040                    N2652N              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 100 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PETER O KNIGHT
        DEPARTURE POINT             INTENDED DESTINATION
          OCALA,FLA                   TAMPA,FLA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N2652N
Reported as
Cessna 140
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Peter O Knight

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.

Other investigations on N2652N · 2

Matched to the same aircraft by N-number and date.