OpenAirDocs.org

NTSB investigations: Piper PA-28-151

14 cases on aircraft the registry lists as Piper PA-28-151, where the first occurrence was “Overrun”. 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

19822026

Where

Open the map

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 ('7102805', '7104223')
      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\" = 340))
  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.

NTSB MIA04CA118Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Sugar Loaf Key, FLThe failure of the pilot to attain the proper touchdown point resulting in a landing overrun and subsequent on-ground collision with trees.Jul 24, 2004 · N4590F · Substantial damageNTSB CHI00LA128Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Fulton, MOthe pilot's poor inflight planning which resulted in exceeded the proper touchdown point on the runway. A factor associated with the accident was the ditch that the airplane contacted.May 6, 2000 · N8641E · Substantial damageNTSB CHI98LA315Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Redwood Falls, MNthe pilot's not following proper short field landing procedures.Aug 15, 1998 · N4576F · Substantial damageNTSB SEA98LA005Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Vashon, WAA misjudged soft field takeoff. Factors include wet grass.Oct 19, 1997 · N5987F · Substantial damageNTSB LAX94LA228Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Sonoma, CAThe pilot's failure to attain the proper touchdown point and his failure to initiate a go-around.May 30, 1994 · N44630 · Substantial damageNTSB BFO93LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Painesville, OHThe pilot's attempt to land with excessive airspeed, his improper use of the brakes, and his delay in performing remedial action.Sep 19, 1993 · N6294J · Substantial damageNTSB CHI91LA010Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Manning, IAAirspeed was not attained and aborted takeoff was delayed by the pilot. Factors related to the accident were: over confidence in aircraft's ability to takeoff on the short, grass runway and a dirt embankment on the departure end of the strip.Jun 11, 1991 · N44300 · Substantial damageNTSB NYC89LA115Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Matawan, NJThe pilot's inadequate action after encountering tailwind conditions during landing.Apr 13, 1989 · N43663 · Substantial damageNTSB NYC88LA245Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Carlton Center, NYPlt stated he was landing to the west and touched down about half way down a 2,000 ft grass strip. The plt also said the grass was wet and the wheel braking was ineffective. The plt elected to keep the airplane on the ground due to obstacles at the end of the…Sep 29, 1988 · N43610 · Substantial damageNTSB CHI87LA202Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Delft, MNThe acft was loaded close to its gross wt limit & the plt atmtd to takeoff on a 2160 ft strip, using short field takeoff techniques. The acft became airborne for a short time, however, it began to settle. The plt elected to abort the takeoff, but was unable…Aug 10, 1987 · N4935F · Substantial damageNTSB NYC85LA167Accident · Minor injuriesLimited investigationFinal reportPiper PA28-151 · Chatham, MADuring the final approach to runway 24, the aircraft was too high and fast. The pilot decided to land on the runway instead of going around. According to the pilot, the aircraft landed too FAR down the runway and went over the end.Jul 13, 1985 · N5405F · Substantial damageNTSB LAX84LA362Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Sacramento, CAThe plt stated he landed a little long on the 2800 foot dirt road and was unable to stop. The acft traveled off the end of the road and collided with a river bank.Jun 22, 1984 · N44190 · Substantial damageNTSB DEN82DA203Accident · No injuriesFinal reportPiper PA-28-151 · Near Darby, MTSince the shook mountain resort airport was new to the pilot, he called the airport to get further information. He stated that the person who answered reported it was a nice day and the wind sock had blown down. During arrival, he approached from the…Sep 22, 1982 · N32180 · Substantial damageNTSB NYC82DA048Accident · No injuriesFinal reportPiper PA-28-151 · Pittstown, NJAfter arriving from alexandria, NJ with an instructor pilot, the student made two practice landing at the Pittstown airport without incident. However, on a subsequent solo flight, the student pilot landed long on the 2000 ft runway. He stated that he ran off…Mar 10, 1982 · N8787F · Substantial damage