DEN66A0057

NTSB accident investigation · Lockheed PV-2 · Phoenix, AZ · February 3, 1966

Accident · FatalClosed
Date
February 3, 1966
Place
Phoenix, AZ · PHOENIX, AZ
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N7258CLockheed PV-2
Status
Completed · report July 25, 1966
Report
Brief approved by the director
Case key
174129

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-0143   66/2/3    PHOENIX ARIZ        LOCKHEED PV-2       CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 46, 7000
        TIME - 1504                    N7258C              PX-  1  0  0  BUSINESS                  TOTAL HOURS, 250 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SKY HARBOR
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           FIRE OR EXPLOSION: IN FLIGHT                             LANDING: TRAFFIC PATTERN-CIRCLING
           COLLIDED WITH: RESIDENCE(S)                              LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
          PWR PLT-FUEL FED ENG.NACELLE FIRE,CAUSE-UNDETERMIN
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND

Aircraft

Registration
N7258C
Reported as
Lockheed PV-2
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Sky Harbor

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.