DEN67A0061

NTSB accident investigation · Cessna 337 · Huntington, UT · April 10, 1967

Accident · FatalClosed
Date
April 10, 1967
Place
Huntington, UT · HUNTINGTON, UT
Injuries
4 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N2214XCessna 337
Status
Completed · report July 20, 1967
Report
Brief approved by the director
Case key
117720

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-0142  67/4/10    HUNTINGTON,UT       CESSNA 337          CR-  1  0  0  COMMERCIAL                COMMERCIAL, FL.INSTR.,
        TIME - 1150                    N2214X              PX-  3  0  0  POWER/PIPELINE            AGE 51, 12000 TOTAL
                                       DAMAGE-DESTROYED    OT-  0  0  0                            HOURS, 705 IN TYPE,
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - HUNTINGTON MUNI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    IN FLIGHT: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- PIPELINE PATROL AT LOW ALTITUDE.

Aircraft

Registration
N2214X
Reported as
Cessna 337
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Huntington 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.