FTW67D0325

NTSB accident investigation · Cessna 182 · El Paso, TX · August 5, 1966

Accident · No injuriesClosed
Date
August 5, 1966
Place
El Paso, TX · EL PASO, TX
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3495SCessna 182
Status
Completed · report February 27, 1967
Report
Brief approved by the director
Case key
121294

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-3718   66/8/5    EL PASO TEX         CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 43, 74 TOTAL
        TIME - 1045                    N3495S              PX-  0  0  3  BUSINESS                  HOURS, 26 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - EL PASO INTL.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING
           MISCELLANEOUS ACTS,CONDITIONS - INTERFERENCE WITH FLIGHT CONTROLS
        REMARKS- PASSENGER PUSHED ELEVATOR CONTROL FORWARD AFTER AIRCRAFT BOUNCED ON LANDING.

Aircraft

Registration
N3495S
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
El Paso Intl.

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.