NTSB investigations: Piper PA-28-235
11 cases on aircraft the registry lists as Piper PA-28-235, 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 |
|---|---|
| 1986 | 2 |
| 1987 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2002 | 1 |
| 2006 | 1 |
| 2007 | 2 |
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 ('7102810')
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 ('7102810')
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 SEA07CA123Accident · No injuriesData collectionFinal reportPiper PA28-235 · San Jose, CAWind shear encounter during approach for landing.NTSB LAX07FA103Accident · 3 fatalField investigationFinal reportPiper PA-28-235 · Tooele, UTThe pilot exceeded the design stress limits of the airplane, which resulted in the in-flight separation of the wings and horizontal stabilizers. Contributing to the accident were the night lighting conditions, clouds, turbulence and icing conditions.NTSB ANC06FA089Accident · 1 fatalField investigationFinal reportPiper PA-28 · Manley Hot Spng, AKThe pilot's continued cruise flight into known adverse weather conditions, his failure to maintain aircraft control while maneuvering, and his exceeding the design stress limits of the airplane, which resulted in an in-flight break-up. Factors associated with…NTSB ANC02FA025Accident · 1 fatalField investigationFinal reportPiper PA-28-235 · Manokotak, AKThe pilot's continued VFR flight into instrument meteorological conditions, and subsequent collision with terrain during cruise flight. Factors in the accident were low ceilings, snow, and mountainous snow-covered terrain.NTSB DEN99FA012Accident · 2 fatalField investigationFinal reportPiper PA-28-235 · Buffalo, WYThe non-instrument rated pilot's initiated flight into adverse weather conditions and inadvertently flew into IMC weather conditions. Factors were the low ceiling weather conditions, the dark night light conditions, and a non operating VOR navigational aid.NTSB CHI98LA034Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-235 · Ulysses, KSthe pilot's continued flight into adverse weather conditions, his failure to activate the pitot heat system, and his failure to maintain clearance from the terrain. Factors associated with this accident were: the pilot did not obtain a preflight weather…NTSB SEA96FA036Accident · 1 fatalField investigationFinal reportPiper PA-28-235 · Lehi, UTcontinued VFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain sufficient altitude and/or clearance from mountainous terrain. Factors relating to the accident were: darkness, low ceiling, and snow.NTSB NYC87FA244Accident · 2 fatalField investigationFinal reportPiper PA-28-235 · Altoona, PAThe aircraft departed cleveland, oh at approx 0915 hours on an unauthorized flt to atlantic city, NJ. The plt was not authorized to operate the aircraft or conduct the flt due to his license having been revoked in 1977 for repeatedly violating FARS. Near…NTSB NYC87FA021Accident · 2 fatalField investigationFinal reportPiper PA-28-235 · Jamestown, NYThe non-inst rated plt had received a telephone wx briefing prior to the planned flt. Marginal VFR wx was forecast for the route with vis 1/8 mile and fog. The acft was located aprx 24 hrs later in a heavily wooded area about 200 yds east of and parallel to…NTSB CHI86FA200Accident · 4 fatalField investigationFinal reportPiper PA-28-235 · Shelby, INThe non-instrument rated pilot initiated the VFR flight from wheeling, IL, to madison, IN, IN marginal weather conditions. The wreckage was found on the afternoon of the following day about 26 miles south of gary, IN. The aircraft sustained an in-flight…NTSB LAX82FA050Accident · 1 fatalField investigationFinal reportPiper PA-28-235 · 10nm N. Of Mcna, AZWhile on a cross country flight the pilot flew into weather which included severe to moderate icing conditions. Although the weather was forecast for the intended route of flight in a SIGMET it was not provided to the pilot during the initial weather…