OAK72AP008

NTSB accident investigation · Cessna 172K · Sparks, NV · September 7, 1971

Accident · FatalClosed
Date
September 7, 1971
Place
Sparks, NV · SPARKS, NV
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N7408GCessna 172K
Status
Completed · report July 28, 1972
Report
Brief approved by the director
Case key
163329

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-4293   71/9/7    SPARKS,NEV          CESSNA 172K         CR-  1  0  0  INSTRUCTIONAL             STUDENT, AGE 44, 51 TOTAL
        TIME - 1200                    N7408G              PX-  0  0  0  SOLO                      HOURS, 4 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          RENO,NEV                    LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - PHYSICAL IMPAIRMENT
           MISCELLANEOUS ACTS,CONDITIONS - ALCOHOLIC IMPAIRMENT OF EFFICIENCY AND JUDGMENT
        REMARKS- BLOOD ALCOHOL LVL .121 PCT.

Aircraft

Registration
N7408G
Reported as
Cessna 172K
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.