NTSB investigations: Piper PA-24-260
10 cases on aircraft the registry lists as Piper PA-24-260, where the first occurrence was “In flight encounter with weather”. 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 | 2 |
| 1985 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 2002 | 1 |
| 2005 | 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 ('7102406')
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\" = 240))
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 ('7102406')
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" = 240))
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 IAD05LA137Accident · 1 fatalLimited investigationFinal reportPiper PA-24-260 · Tiffin, OHThe pilot's decision to takeoff in weather below the published takeoff minimums, which resulted in spatial disorientation and the airplane's collision with trees and terrain. Factors in the accident were the instrument meteorological conditions, and the…NTSB FTW02FA192Accident · 4 fatalField investigationFinal reportPiper PA-24-260 · Gorman, TXThe pilot's loss of control and the exceedence of the design limits of the airplane which resulted in an in-flight break-up. A factor was inadvertent VFR flight into IMC.NTSB LAX96FA275Accident · 2 fatalField investigationFinal reportPiper PA-24-260 · Tennant, CAthe pilot's continued flight into known adverse weather conditions.NTSB FTW95FA402Accident · 5 fatalField investigationFinal reportPiper PA-24B-260 · Westcliffe, COVFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain sufficient altitude or clearance from mountainous terrain. Factors relating to the accident were: the light conditions at dusk, the adverse weather…NTSB LAX89FA106Accident · 3 fatalField investigationFinal reportPiper PA-24-260 · Julian, CAThe pilot's poor judgement of intentionally flying into an area of known forecast icing conditions which resulted in a loss of control and an inflight breakup of the aircraft. Contributing factors were the pilot's overconfidence in his personal ability by…NTSB DEN86LA224Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Monument Valley, UTThe plt was on an approach for landing when the acft began to settle. He said that increasing power did not seem to have an effect. Subsequently, the acft landed hard, collapsing the nose gear. The plt believed that he had encountered wind shear during the…NTSB MKC85FA089Accident · 2 fatalField investigationFinal reportPiper PA-24-260 · Wakeeney, KSOn a x-country flt from dodge city, KS, to hill city, KS, the plt encountered IFR wx conditions around Wakeeney, KS. The IFR conditions were not forecast for his area of flt. A 2000 CST observation at hill city, KS, was indicating IFR conditions existing aprx…NTSB ATL84FA064Accident · 1 fatalField investigationFinal reportPiper PA-24-260B · Mcdonald, TNThe plt received 2 wx briefings before takeoff & was provided flt precautions of IMC to continue beyond 0900 EST. Also, he was advised that the mountains would be occasionally obscured & icing could be expected to the west below 6000 ft. during both…NTSB MIA84FA036Accident · 2 fatalField investigationFinal reportPiper PA-24-260 · Kathleen, FLThe acft impacted in a swampy area in a fast dive which separated about 6 ft of the left wing. The acft was being vectored on radar when it suddenly began to steer erratically and go off the radar scope. The plt had radioed that he 'must have gone over some…NTSB FTW82FRG26Accident · 2 fatalFinal reportPiper PA-24-260 · Kingsville, TXOn 3/17/82 a wx briefer advised the pilot all of Texas would be under instrument meteorological conditons on the morningof 3/18/82. There was no record of a flt plan filed by the pilot of N8988P and the departure time from Kingsville could not be determined.…