SEA66F0249

NTSB accident investigation · Beech A23 · Eugene, OR · March 27, 1966

Accident · No injuriesClosed
Date
March 27, 1966
Place
Eugene, OR · EUGENE, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3558RBeech A23
Status
Completed · report June 16, 1966
Report
Brief approved by the director
Case key
172118

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-0973  66/3/27    EUGENE OREG         BEECH A23           CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 0015                    N3558R              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  AGE 34, 583 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            28 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - MAHLON-SWEET
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- NIGHT OPERATION, SAFE LANDING MADE ON LIGHTED RUUNWAY

Aircraft

Registration
N3558R
Reported as
Beech A23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mahlon-Sweet

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.