NTSB investigations: Piper PA-32-260
9 cases on aircraft the registry lists as Piper PA-32-260, where the first occurrence was “Hard landing”. 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
| 1983 | 1 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 2 |
| 1992 | 1 |
| 2002 | 1 |
Where
Latest 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 ('7103206')
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\" = 200))
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 ('7103206')
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" = 200))
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 FTW02LA181Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Pecos, TXThe pilot misjudged the landing flare resulting in a hard landing. A contributing factor was the dark night conditions.NTSB CHI92LA135Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Sidney, NEWas an inadvertent stall/mush during landing by the pilot. A factor related to the accident was lack of recent total experience.NTSB NYC91LA018Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Bally, PAThe pilot's improper recovery from a bounced landing and his failiure to maintain directional control.NTSB MIA90LA140Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Boca Raton, FLThe pilots failure to flare the airplane for landing resulting in the hard landing.NTSB CHI90LA025Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Mcleansboro, ILThe pilot-in-command's failure to maintain control of the aircraft while recovering from a bounced landing.NTSB DEN88LA144Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Colorado Spring, COThe plt and pax departed st. louis and stopped twice enroute due to wx. The plt was given landing clearance on rwy 17 at Colorado springs and the wind was reported to be from 190 degrees at 12 KTS. Witnesses at the arpt stated N4878S 'porpoised' several times…NTSB ATL85LA126Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Blairsville, GADuring flt, the plt encountered unfavorable winds & rain, then became concerned about his fuel supply. He diverted to Blairsville & was landing when a gust of wind blew the acft side ways. The plt re-aligned the acft with the rwy, but it suddenly dropped &…NTSB CHI84LA171Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Marion, INThe student plt reported that during a landing, he reduced the power too soon & flared the acft too high, then the acft bounced about 8 to 10 ft in the air. The hard landing resulted in spar damage to the right wing.NTSB CHI83LA230Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Waukegan, ILThe student was receiving a high performance checkout. During the third landing the acft landed hard.