NTSB investigations: Piper PA-44-180
6 cases on aircraft the registry lists as Piper PA-44-180, where NTSB found Not determined, general. 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
| 2008 | 1 |
|---|---|
| 2012 | 1 |
| 2014 | 1 |
| 2015 | 1 |
| 2017 | 1 |
| 2025 | 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 ('7104402', '7104406')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '05000000')))
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 ('7104402', '7104406')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f."findingCode", '05000000')))
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 ERA25LA096Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-44-180 · Pompano Beach, FLThe separation of the securing hardware for the right main landing gear upper and lower torque links for undetermined reasons, which prevented extension of the right main landing gear.NTSB WPR17FA151Accident · 2 fatalField investigationFinal reportPiper PA 44-180 · Marineland, FLA loss of control in flight for reasons that could not be determined based on the available information, which resulted in an in-flight breakup.NTSB ERA15LA225Accident · No injuriesLimited investigationFinal reportPiper PA44 · Miami, FLThe failure of the nose landing gear upper drag link knee bolt due to reverse-bending fatigue, which was likely preceded by excessive bearing wear due to reasons that could not be determined based on the available evidence.NTSB ERA14IA370Incident · No injuriesIncident investigationFinal reportPiper PA-44-180 · Jacksonville, FLThe nose landing gear collapse for reasons that could not be determined because examination of the airplane revealed no anomalies.NTSB CEN12LA516Accident · No injuriesLimited investigationFinal reportPiper PA-44-180 · Grand Forks, NDThe loss of directional control during landing roll, which resulted in a runway excursion. The reason for the loss of directional control could not be determined because postaccident examination did not reveal any malfunctions or anomalies that would have…NTSB SEA08LA073Accident · Minor injuriesLimited investigationFinal reportPiper PA-44-180 · Piru, CAThe loss of engine power for undetermined reasons. Contributing factors were the lack of suitable terrain for the forced landing and dark night conditions.