MIA73DKT21

NTSB accident investigation · Cessna 175 · Miami, FL · October 22, 1972

Accident · Serious injuriesClosed
Date
October 22, 1972
Place
Miami, FL · MIAMI, FL
Injuries
1 serious, 1 minor, 1 uninjured
Damage
Minor damage
Phase of flight
Enroute
Aircraft
N7392MCessna 175
Status
Completed · report December 20, 1972
Report
Brief approved by the director
Case key
168629

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-0850  72/10/22   MIAMI,FLA           CESSNA 175          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 49, 800
        TIME - 1048                    N7392M              PX-  0  1  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 65 IN TYPE,
                                       DAMAGE-MINOR        OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NEW TAMIAMI
        DEPARTURE POINT             INTENDED DESTINATION
          BROOKSVILLE,FLA             MIAMI,FLA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           BIRD STRIKE                                              IN FLIGHT: DESCENDING
        PROBABLE CAUSE(S)
           MISCELLANEOUS - BIRD COLLISION
        REMARKS- COLLIDED WITH BUZZARD.LNDD WITHOUT FURTHER DMG.

Aircraft

Registration
N7392M
Reported as
Cessna 175
Category
Airplane
Engine
reciprocating
Damage
Minor damage
Airport
New Tamiami

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.