DEN66F0232

NTSB accident investigation · Beechcraft 33 · Woods Cross, UT · March 2, 1966

Accident · No injuriesClosed
Date
March 2, 1966
Place
Woods Cross, UT · WOODS CROSS, UT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N8502MBeechcraft 33
Status
Completed · report March 31, 1966
Report
Brief approved by the director
Case key
173867

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-0319   66/3/2    WOODS CROSS UT      BEECHCRAFT 33       CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 492
        TIME - 1615                    N8502M              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 65 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BOUNTIFUL SKY HVN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: ICE/SLUSH ON RUNWAY

Aircraft

Registration
N8502M
Reported as
Beechcraft 33
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Bountiful Sky Hvn

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.