Lockheed PV-2
NTSB investigations · 21
Matched to the registry by N-number and event date, newest first.
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('5260106')
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('5260106')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB IAD97FA065Accident · 2 fatalField investigationFinal reportLockheed PV2 · Blandburg, PAPilot in command misjudged his maneuvering altitude. Factors to this accident were the mountainous terrain, windy conditions, turbulence in the area, and smoke.NTSB FTW94LA319Accident · No injuriesLimited investigationFinal reportLockheed PV-2 · Lafayette, LAThe pilot's inadvertent gear retraction.NTSB LAX90FA336Accident · 8 fatalField investigationFinal reportLockheed PV-2 · Lakeport, CAThe pilot-in-command's failure to maintain airspeed during a pull-up from a low pass. Factors which contributed to the accident were: the pilot's poor judgement in buzzing the seaplanes which resulted in insufficient altitude to recover from the stall, and…NTSB FTW90DRA10Accident · No injuriesFinal reportLockheed PV-2 · Conroe, TXThe engine starter remained engaged after engine start and the electrical system overheat.NTSB LAX85LA235Accident · No injuriesLimited investigationFinal reportLockheed PV-2 · Mesa, AZFollowing a dural engine chang, the plt test flew the acft. On initial climb, at about 500 ft AGL, both engines began backfiring violently & lost power. According to the plt, power sufficient for flt could not be obtained, & a forced ldg was made about 0.75…NTSB NYC80FGT11Accident · No injuriesClosedLockheed PV-2 · Philipsburg, PANTSB DEN79FA047Accident · No injuriesClosedLockheed PV-2 · Humble City, NMNTSB FTW75FPA25Accident · Serious injuriesClosedLockheed PV-2 · Addison, TXNTSB LAX74FUJ68Accident · 2 fatalClosedLockheed PV-2 · Winslow, AZNTSB MIA70F0134Accident · No injuriesClosedLockheed PV-2 · Macon, GANTSB MIA70F0040Accident · Serious injuriesClosedLockheed PV-2 · Sebring, FLNTSB MIA68A0080Accident · No injuriesClosedLockhead PV-2 · Macon, GANTSB LAX68A0034Accident · Minor injuriesClosedLockheed PV-2 · Palm Sprngs, CANTSB MIA67A0130Accident · No injuriesClosedLockheed PV-2 · Kissimmee, FLNTSB ANC67A0063Accident · 1 fatalClosedLockheed PV-2NTSB DEN66A0057Accident · 2 fatalClosedLockheed PV-2 · Phoenix, AZNTSB MIA66A0040Accident · No injuriesClosedLockheed PV-2 · Tupelo, MSNTSB OAK66A0008Accident · 2 fatalClosedLockheed PV-2 · Hayward, CANTSB MIA65A0102Accident · No injuriesClosedLockheed PV-2 · Bainbridge, GANTSB MIA65A0097Accident · No injuriesClosedLockhead PV-2 · Laurel, MSNTSB UNK64X1269Accident · Minor injuriesClosedLockheed PV2 · Hilo Hawaii (Pacific Ocean)
Back to Lockheed PV-2