MIA80DLE01

NTSB accident investigation · Cessna 172 · Kissimmee, FL · September 15, 1980

Accident · No injuriesClosed
Date
September 15, 1980
Place
Kissimmee, FL · KISSIMMEE, FL
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N737MUCessna 172
Status
Completed · report January 9, 1981
Report
Brief approved by the director
Case key
127802

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-3127  80/9/15    KISSIMMEE,FL        CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 30, 214
        TIME - 1100                    N737MU              PX-  0  0  1  PRACTICE                  TOTAL HOURS, 97 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          KISSIMMEE,FL                ST.PETERSBURG,FL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           BIRD STRIKE                                              IN FLIGHT: CLIMB TO CRUISE
        PROBABLE CAUSE(S)
           MISCELLANEOUS - BIRD COLLISION
        REMARKS- LARGE BIRD STRUCK THE L WING STRUT & L HOR STABILIZER.ACFT WAS LNDD SAFELY.

Aircraft

Registration
N737MU
Reported as
Cessna 172
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.