LAX67D0393

NTSB accident investigation · Piper PA-24 · Corona, CA · April 26, 1967

Accident · No injuriesClosed
Date
April 26, 1967
Place
Corona, CA · CORONA, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N6437PPiper PA-24
Status
Completed · report September 6, 1967
Report
Brief approved by the director
Case key
117664

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-1286  67/4/26    CORONA,CALIF        PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 182
        TIME - 1200                    N6437P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CORONA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    TAXI: TO TAKEOFF
        PROBABLE CAUSE(S)
           PERSONNEL - AIRPORT SUPERVISORY PERSONNEL: FAILURE TO NOTIFY OF UNSAFE COND/AND OR FAILURE TO MARK OBSTRUCTION
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: HIDDEN HAZARD
        REMARKS- RT GEAR DROPPED INTO SOFT SPOT ON TAXIWAY.

Aircraft

Registration
N6437P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Corona

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.