LAX69D0223

NTSB accident investigation · Cessna 310H · Perkinsville, AZ · November 29, 1968

Accident · No injuriesClosed
Date
November 29, 1968
Place
Perkinsville, AZ · PERKINSVILLE, AZ
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1070QCessna 310H
Status
Completed · report February 17, 1969
Report
Brief approved by the director
Case key
191813

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-4415  68/11/29   UNKNOWN/NOT REPORTEDCESSNA 310H         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 2000
        TIME - 1145                    N1070Q              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 1700 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           AIRFRAME - LANDING GEAR: WHEELS,TIRES,AXLES
           MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE
        REMARKS- PLT LANDED ON DIRT ROAD.BOTH TIRES FOUND DEFLATED.

Aircraft

Registration
N1070Q
Reported as
Cessna 310H
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.