UNK64X2919

NTSB accident investigation · Cessna 195 · Tinley Park, IL · July 19, 1964

Accident · No injuriesClosed
Date
July 19, 1964
Place
Tinley Park, IL · TINLEY PARK, IL
Injuries
1 uninjured
Damage
Destroyed
Phase of flight
Approach
Aircraft
N3433VCessna 195
Status
Completed · report October 15, 1964
Report
Brief approved by the director
Case key
183120

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-2137  64/7/19    TINLEY PARK ILL     CESSNA 195          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 50, 323
        TIME - 1730                    N3433V              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PROSPERI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           FIRE OR EXPLOSION: IN FLIGHT                             LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - FIRE IN CABIN,COCKPIT,BAGGAGE COMPARTMENT
           MISCELLANEOUS ACTS,CONDITIONS - *ERROR-INVALID CODE*
        EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT.

Aircraft

Registration
N3433V
Reported as
Cessna 195
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Prosperi

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.