MIA71AM017

NTSB accident investigation · Lockheed PV-1 · Opa Locka, FL · August 18, 1970

Accident · No injuriesClosed
Date
August 18, 1970
Place
Opa Locka, FL · OPA LOCKA, FL
Injuries
2 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N350QLockheed PV-1
Status
Completed · report November 12, 1970
Report
Brief approved by the director
Case key
116821

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-1365  70/8/18    OPA LOCKA,FLA       LOCKHEED PV-1       CR-  0  0  2  MISCELLANEOUS             COMMERCIAL, AGE 41, 7600
        TIME - 2018                    N350Q               PX-  0  0  0  FERRY                     TOTAL HOURS, 211 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - OPA LOCKA
        DEPARTURE POINT             INTENDED DESTINATION
          BROOKSVILLE,FLA             OPA LOCKA,FLA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR RETRACTED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
         FIRE AFTER IMPACT
        REMARKS- CREW STATED GR WAS LOWERED PRIOR TO T/D. GR HANDLE FOUND IN UP POSITION.

Aircraft

Registration
N350Q
Reported as
Lockheed PV-1
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Opa Locka

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.