LAX79IA082

NTSB incident investigation · Cessna 210 · Tucson, AZ · September 14, 1979

Incident · FatalClosed
Date
September 14, 1979
Place
Tucson, AZ · TUCSON, AZ
Injuries
1 fatal, 1 uninjured
Damage
No damage
Phase of flight
Enroute
Aircraft
N6125FCessna 210
Status
Completed · report October 4, 1979
Report
Brief approved by the director
Case key
132896

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.

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
----------------------------------------------------------------------------------------------------------------------------
5-0047  79/9/14    TUCSON,AZ           CESSNA 210          CR-  0  0  1  MISCELLANEOUS             PRIVATE, AGE 44, 980
        TIME - 1930                    N6125F              PX-  1  0  0  UNKNOWN/NOT REPORTED      TOTAL HOURS, UNK/NR IN
                                       DAMAGE-NONE         OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        CLASSIFIED AS INCIDENT
        DEPARTURE POINT             INTENDED DESTINATION
          TUCSON,AZ                  UNKNOWN/NOT REPORTED
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           MISCELLANEOUS                                            IN FLIGHT: CLIMB TO CRUISE
        PROBABLE CAUSE(S)
           PERSONNEL - MISCELLANEOUS-PERSONNEL: PASSENGER
        REMARKS- PASSENGER SUFFERED HEART ATTACK IN FLIGHT.DIED APPROX 2HRS LATER.

Aircraft

Registration
N6125F
Reported as
Cessna 210
Category
Airplane
Engine
reciprocating
Damage
No 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.