NTSB investigations: Boeing A75N1(PT17), 2000
3 cases on aircraft the registry lists as Boeing A75N1(PT17). 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
| 1964 | 43 |
|---|---|
| 1965 | 25 |
| 1966 | 39 |
| 1967 | 28 |
| 1968 | 35 |
| 1969 | 28 |
| 1970 | 20 |
| 1971 | 21 |
| 1972 | 20 |
| 1973 | 32 |
| 1974 | 30 |
| 1975 | 23 |
| 1976 | 19 |
| 1977 | 12 |
| 1978 | 10 |
| 1979 | 14 |
| 1980 | 11 |
| 1981 | 12 |
| 1982 | 10 |
| 1983 | 9 |
| 1984 | 5 |
| 1985 | 5 |
| 1986 | 5 |
| 1987 | 8 |
| 1988 | 3 |
| 1989 | 8 |
| 1990 | 6 |
| 1991 | 5 |
| 1992 | 5 |
| 1993 | 9 |
| 1994 | 6 |
| 1995 | 4 |
| 1996 | 3 |
| 1997 | 3 |
| 1998 | 8 |
| 1999 | 4 |
| 2000 | 3 |
| 2001 | 3 |
| 2002 | 4 |
| 2003 | 4 |
| 2004 | 3 |
| 2005 | 2 |
| 2006 | 2 |
| 2007 | 3 |
| 2009 | 4 |
| 2010 | 5 |
| 2011 | 5 |
| 2012 | 3 |
| 2013 | 1 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 7 |
| 2017 | 4 |
| 2018 | 3 |
| 2019 | 1 |
| 2020 | 1 |
| 2021 | 5 |
| 2022 | 4 |
| 2023 | 4 |
| 2024 | 5 |
| 2025 | 2 |
| 2026 | 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 year(c.\"eventDate\") = 2000
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1380134'))
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 year(c."eventDate") = 2000
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1380134'))
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 MIA01LA010Accident · No injuriesLimited investigationFinal reportJim Price Pitts Special S · Indiantown, FLThe failure of the pilot of N56JP, during landing rollout, to see and avoid N49713, who was turning off the runway after landing from the opposite direction, resulting in the 2 aircraft colliding on the runway.NTSB NYC00LA204Accident · No injuriesLimited investigationFinal reportBoeing PT17 · Easton, MDThe pilot's failure to maintain aircraft control.NTSB CHI00LA195Accident · Serious injuriesLimited investigationFinal reportBoeing Stearman A75N1(PT17) · Windsor, MOfuel exhaustion and the pilot abruptly applying normal brakes during the landing roll. Factors relating to this accident were the precautionary landing, and the pilot's inadequate in-flight planning/ decision.