NTSB investigations: Piper PA-28R-200
27 cases on aircraft the registry lists as Piper PA-28R-200, where the first occurrence was “In flight collision with object”. 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 | 1 |
| 1987 | 4 |
| 1988 | 1 |
| 1990 | 2 |
| 1991 | 2 |
| 1992 | 3 |
| 1995 | 1 |
| 1996 | 2 |
| 1997 | 1 |
| 1999 | 2 |
| 2000 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2005 | 1 |
| 2006 | 3 |
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 ('7102811')
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\" = 220))
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 ('7102811')
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" = 220))
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 NYC06FA169Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Block Island, RIThe pilot's inadequate preflight decision making and his failure to maintain terrain clearance during departure. Contributing, were low ceilings, rain, and thunderstorms.NTSB NYC06FA156Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Philipsburg, PAThe pilot's failure to comply with the published instrument approach procedure, which resulted in controlled flight into trees. Factors in the accident were the low cloud ceiling, and dark night conditions.NTSB CHI06LA139Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Hale, MIThe pilot's inadequate compensation for the crosswind condition and failure to maintain clearance from the tree. Factors were the crosswind and the tree.NTSB DFW05FA099Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Jefferson, TXThe pilot's failure to maintain clearance from an unmarked transmission line. A contributing factor was the low altitude flight.NTSB LAX04LA025Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Pacoima, CAthe pilot's failure to maintain an adequate glide path on final approach and his failure to ensure adequate clearance from obstacles. The dark night was a factor.NTSB NYC02LA113Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-200 · Gettysburg, PAThe pilot's failure to accurately compute takeoff performance and his failure to establish a positive climb resulting in a collision with trees.NTSB CHI01FA025Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Gaylord, MIThe pilot not maintaining proper glideslope and localizer alignment during the precision instrument approach, the pilot continuing flight below the decision height, the pilot not performing a missed approach, and the pilot not maintaining altitude/clearance…NTSB CHI99FA278Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · Grayslake, ILthe pilot not maintaining altitude and clearance. Factors were the light condition of night, the pilot's lack of recent experience in night operations, and the transmission wire.NTSB LAX99FA214Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · Bass Lake, CAInadequate in-flight planning and decision making resulted in a failure to maintain clearance from terrain. A factor in the accident was the pilot's low total time and lack of experience in this make and model of airplane.NTSB FTW97FA122Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Westminster, TXThe pilot's failure to maintain clearance during an intentional low altitude maneuver. A factor was the transmission line.NTSB FTW97FA044Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Fort Worth, TXthe pilots' continued descent of the aircraft below decision height. Factors contributing to the accident were the fog, the dark night illumination, one of the pilot's impairment due to use of marihuana, and both pilots' fatigue.NTSB LAX96LA331Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Oxnard, CAthe instructor's inadequate supervision of the flight, and his delay in taking the controls and initiating a go-around. The student pilot's failure to maintain runway alignment and the proximity of the runway remaining marker were related factors.NTSB CHI95LA178Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Bay City, MIFailure of the pilot to maintain clearance from obstacles and his intentional buzzing.NTSB MIA93FA036Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Tarpon Springs, FLThe pilot's failure to maintain the minumum descent altitude (mda) while on a non-precision instrument approach. Factors which contributed to the accident were: the flight service station (fss) specialist's failure to provide the published notice to airmen…NTSB ATL92FA047Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Raleigh, NCThe failure of the pilot to follow instrument landing procedures by descending below the glide path of the instrument landing system. Factors in the accident were the low ceilings and fog at the airport at the time of the accident.NTSB SEA92IA040Incident · Minor injuriesIncident investigationFinal reportPiper PA-28R-200 · Anacortes, WAA bird impacting the aircraft.NTSB CHI91LA186Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Pulaski, WIThe pilot's failure to select a proper touchdown point. A factor in the accident was inadequate runway maintenance by airport personnel.NTSB LAX91FA116Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Monterey Park, CASuicide.NTSB FTW90LA166Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Denver City, TXThe pilot's improper leaning of the fuel mixture.NTSB CHI90LA094Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Wonder Lake, ILThe pilot's inadequate compensation for wind conditions, and his faiiure to maintain proper altitude on final approach to land. Factors related to the accident were: the trees & snowbank.NTSB BFO88LA080Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Charleston, WVThe plt was executing the ILS rwy 5 apch when he entered fog about 350 ft above the dh. According to the plt, upon reaching the dh he sighted the rwy and continued the apch. Afterward the plt said he deviated left of the localizer centerline and as he was…NTSB FTW88FA038Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Burnet, TXThe pilot arrived in the area of his planned destination and completed the outbound and inbound procedure turns for the NDB runway 17 approach without reported incident. Almost immediately thereafter, the aircraft impacted a large oak tree about 15 feet AGL…NTSB ATL87FA230Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Offerman, GADuring a local flt the acft was observed flying at a level attitude approx 10 ft above a corn field at high speed. The right wing of the acft struck tree branches approx 60 ft AGL during a pull up. A 6 ft section of the right wing separated. The acft climbed,…NTSB CHI87FA153Accident · 2 fatalField investigationFinal reportPiper PA-28R · Milwaukee, WIDrg arr at the Milwaukee/lawrence j timmerman arpt, the plt made 2 atmts to use the localizer 15L apch. After the 2nd missed apch, he elected to divert to Milwaukee/general mitchell fld (mke). At that time, he was adzd the mke wx was 300' ovc, 1/4 mi vis with…NTSB BFO87LA018Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200R · West Point, VAAfter making a low pass over the uncontrolled airport the CFI decided to let the student pilot make a touch and go landing on runway 27 at West Point municipal airport. West Point, Virginia. The maneuver was successfully completed and the aircraft came around…NTSB FTW86LA157Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Afton, OKThe pilot stated he was making a precautionary landing at night due to engine roughness and impacted electrical transmission wires. Investigation failed to disclose any reason for the reported engine roughness.NTSB CHI82DA238Accident · No injuriesFinal reportPiper PA-28-200R · Black River Fal, WIThe pilot stated that during flight, he encountered an engine problem and started to land on a road, but then the engine began to run better, so he continued to his destination. After landing, he discovered that a portion of the vertical stabilizer (about 18…