NTSB investigations: Piper PA-32R-300, NJ
8 cases on aircraft the registry lists as Piper PA-32R-300. 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
| 1978 | 1 |
|---|---|
| 1981 | 1 |
| 1991 | 2 |
| 1994 | 1 |
| 1997 | 1 |
| 2002 | 1 |
| 2009 | 1 |
Where
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.\"eventStateOrRegion\" = 'NJ' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213'))
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."eventStateOrRegion" = 'NJ' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213'))
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 ERA09MA447Accident · 9 fatalClass 1 · MajorFinal reportPiper PA-32R-300 · Hoboken, NJ(1) the inherent limitations of the see-and-avoid concept, which made it difficult for the airplane pilot to see the helicopter until the final seconds before the collision, and (2) the Teterboro Airport local controller’s nonpertinent telephone conversation,…NTSB NYC03FA021Accident · 2 fatalField investigationFinal reportMooney M10 · Fairfield, NJThe inadequate visual lookout of both pilots. Factors in the accident were the FAA controller's failure to provide a traffic advisory, the improper decision among the three controllers to leave only one controller in the cab, and night conditions.NTSB NYC97LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Lumberton, NJThe pilot's delay in initiating remedial action to arrest an excessive descent rate during a go-around. A crosswind condition was a contributing factor.NTSB BFO94LA046Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Berlin, NJThe pilot not maintaining clearance from obstacles (trees) during final approach which resulted in a collision with a tree and a subsequent uncontrolled descent until colliding with the ground.NTSB NYC92LA027Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R · Caldwell, NJThe pilot allowed the airplane to get too low on final approach during a night visual landing. Factors in the accident were: the pilot improperly planned the approach, dark night and a lack of flight experience in night operations.NTSB NYC91LA198Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Atlantic City, NJThe failure of the pilot of N6877M to insure the runway was clear prior to pulling onto the runway.NTSB NYC82DHA02Accident · No injuriesClosedPiper PA-32R · Princeton, NJNTSB NYC78FA092Accident · 5 fatalClosedPiper PA-32R · Robbinsville, NJ