NTSB investigations: Piper PA-24
10 cases on aircraft the registry lists as Piper PA-24, where the first occurrence was “Loss of control - in flight”. 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 | 3 |
| 1985 | 1 |
| 1986 | 1 |
| 1991 | 1 |
| 1995 | 1 |
| 1999 | 1 |
| 2000 | 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 ('7102402')
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\" = 250))
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 ('7102402')
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" = 250))
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 NYC00LA072Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Alton Bay, NHThe pilot's failure to maintain control of the airplane during takeoff which resulted in an inadvertent stall. A factor in the accident was the pilot's inadequate compensation for the wind conditions.NTSB ATL99FA081Accident · 4 fatalField investigationFinal reportPiper PA-24-180 · Vicksburg, MSThe pilot's failure to obtain and maintain flying speed that resulted in an inadvertent stall, and the collision with trees. A factor is the dark night.NTSB NYC96FA023Accident · 3 fatalField investigationFinal reportPiper PA-24-180 · Hartford, VTthe pilot's inadequate preflight planning/preparation, his inadequate removal of airframe ice, and his failure to maintain adequate airspeed, which resulted in a stall/spin and an inflight collision with terrain. Factors relating to the accident were: the…NTSB CHI91FA259Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Guide Rock, NESpatial disorientation, and exceeding the design limits of the aircraft. Factors related to the accident are inadequate preflight planning, VFR flight into IMC, flight weather avoidance assistance not followed, excessive altitude, physical impairment…NTSB MKC87FA012Accident · 2 fatalField investigationFinal reportPiper PA-24 · Siloam Springs, ARThe plt had logged 3 hrs of simulated instrument training prior to this accident. He received a wx briefing which reported wx conditions nearby were IFR due to low ceilings and fog. Immediately after takeoff, the acft started a left turn and impacted terrain…NTSB CHI85FA137Accident · 1 fatalField investigationFinal reportPiper PA-24 · Toledo, OHThe plt was obsvd taking medication within 2 hrs bfr flt. A witness identified 1 pill as darvocet-n 100, since she took the same medication. When the plt started the eng, it went to a very hi RPM, as if the throttle was too FAR open. While taxiing to takeoff,…NTSB NYC84FNC06Accident · Serious injuriesFinal reportPiper PA-24-180 · Bingham, METhe acft used, according to various accounts, between 1/2 and 2/3 of the 2300 ft runway on take-off roll. Normal handbook take-off run is 750 ft. passengers stated acft skipped off and touched back down twice before finally becoming airborne. Acft rolled…NTSB ATL84LA189Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Huntsville, ALAfter lift-off & gear retraction, the acft settled back onto the rwy, hit a barrier cable, slid backward aprx 300 ft & crossed a road before coming to rest. The plt reported that the carburetor heat door had come loose. However, an FAA inspector examined the…NTSB MKC84FA103Accident · 4 fatalField investigationFinal reportPiper PA-24-180 · Springdale, ARAbout 3 minutes after takeoff the acft was observed coming out of the 400-600 ft overcast sky in about a 75 deg nose down, right wing attitude. It impacted a 4-strand high voltage powerline prior to impact with the ground. The plt had received his instrument…NTSB NYC83AA208Accident · 4 fatalFinal reportPiper PA-24-180 · Pomona, NJDuring his wx briefing, the plt was advised of an area of rain showers & scattered thunderstorms along his route of flt, as well as flt precautions for occasional moderate turbulence below 8000 ft which was forcast. He departed norfolk at 1500. At about 1630,…