NYC68D0118

NTSB accident investigation · Cessna 172 · New Hope, PA · August 19, 1967

Accident · No injuriesClosed
Date
August 19, 1967
Place
New Hope, PA · NEW HOPE, PA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N7393TCessna 172
Status
Completed · report November 20, 1967
Report
Brief approved by the director
Case key
114056

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-2966  67/8/19    NEW HOPE,PA         CESSNA 172          CR-  0  0  1  COMMERCIAL                COMMERCIAL, FL.INSTR.,
        TIME - 1600                    N7393T              PX-  0  0  1  POWER/PIPELINE            AGE 42, 19000 TOTAL
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            HOURS, 2500 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           PILOT IN COMMAND - FAILED TO ABORT TAKEOFF
        REMARKS- UP HILL GRADIENT ON GRASS FIELD.WIND CALM.

Aircraft

Registration
N7393T
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.