NTSB investigations: Piper PA-23
11 cases on aircraft the registry lists as Piper PA-23, where the first occurrence was “Loss of engine power(total) - nonmechanical”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1984 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1994 | 3 |
| 1996 | 1 |
| 1997 | 1 |
Where
Open the mapLatest cases
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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102302')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 353))
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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102302')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 353))
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 IAD97LA071Accident · Minor injuriesLimited investigationFinal reportPiper PA-23 · Washington, DCtotal loss of power on both engines due to fuel exhaustion as a result of the pilot's improper fuel consumption calculations.NTSB NYC96LA048Accident · No injuriesLimited investigationFinal reportPiper PA-23-150 · Silver Spring, PAA loss of engine power as a result of fuel exhaustion.NTSB MIA94LA197Accident · No injuriesLimited investigationFinal reportPiper PA-23 · San Juan, PRThe failure of the pilot-in-command to maintain directional control following loss of engine power during takeoff. Contributing to the accident was the pilot-in-commands improper aircraft preflight inspection and draining of fuel tanks and his lack of…NTSB FTW94LA094Accident · No injuriesLimited investigationFinal reportPiper PA-23 · Duncan, OKThe pilot's selection of the wrong engine for shut down. A factor was the lack of suitable terrain for the forced landing.NTSB LAX94LA153Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-180 · Fairfield, AZThe flight instructor's inadvertent movement of the left engine propeller control into the feather position, his decision to by-pass suitable landing sites in an attempt to restart the left engine as the aircraft energy and performance capability…NTSB MIA93LA048Accident · Minor injuriesLimited investigationFinal reportPiper PA-23 · Tampa, FLPoor in-flight planning/decision by the CFI resulting in the total loss of engine power from both engines due to fuel exhaustion.NTSB CHI92LA105Accident · No injuriesLimited investigationFinal reportPiper PA-23-150 · Romeoville, ILThe pilot selected unsuitable terrain to make a precautionary landing when he did not receive a safe indication that the landing gear was down and locked. A factor in the accident was inability of the pilot to restart the left engine after intentionally…NTSB ATL90LA034Accident · No injuriesLimited investigationFinal reportPiper PA-23-150 · Jackson, TNLoss of power in both engines (probable fuel starvation) due to improper planning/decision by the pilot(s), and lack of supervision by the instructor. Soft terrain in the emergency landing area was considered to be a factor.NTSB NYC84LA235Accident · No injuriesLimited investigationFinal reportPiper PA-23 · No. Andover, MAThe acft lost power at about 200 ft AGL during takeoff. The plt feathered the right engine and then elected to land on the remaining rwy when the left engine lost power. The acft went off the rwys end with brakes locked. When the acft was examined by FAA…NTSB DEN83LA139Accident · No injuriesLimited investigationFinal reportPiper PA-23 · Jamestown, NDThe acft landed wheels-up with one engine feathered and nosed over during the slide-out. The pilot had intentionally feathered the left engine to 'try out' the acft. The left engine has the only engine driven hydraulic pump. This pump isnecessary to lower…NTSB CHI82FA048Accident · 1 fatalField investigationFinal reportPiper PA-23 · Corydon, INPrior to this flight, the aircraft had not been flown for an extended period. On the day of the accident, it had been sold. The aircraft did not have a current annual inspection and had several maintenance discrepancies. These included problems that prevented…