FTW66A0095

NTSB accident investigation · Lear Jet 23 · Clarendon, TX · April 23, 1966

Accident · FatalClosed
Date
April 23, 1966
Place
Clarendon, TX · CLARENDON, TX
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N235RLear Jet 23
Status
Completed · report August 21, 1967
Report
Brief approved by the director
Case key
172503

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
----------------------------------------------------------------------------------------------------------------------------
2-1179  66/4/23    CLARENDON TEX       LEAR JET 23         CR-  2  0  0  INSTRUCTIONAL             AIRLINE TRANSPORT, AGE
        TIME - 1238                    N235R               PX-  0  0  0  CHECK                     28, 2554 TOTAL HOURS, 380
                                       DAMAGE-DESTROYED    OT-  0  0  0                            IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - CLARENDON MUNI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
          PILOT-LOSS OF CTRL IN TURBLNT,INSTRMENT,CONDITIONS
        REMARKS- SUSPECT FAILURE BOTH GYRO HORIZONS

Aircraft

Registration
N235R
Reported as
Lear Jet 23
Category
Airplane
Engine
turbo jet
Damage
Destroyed
Airport
Clarendon Muni

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.