NTSB investigations, 1995
30 cases where the first occurrence was “Undershoot”.
Cases per year
| 1982 | 102 |
|---|---|
| 1983 | 62 |
| 1984 | 60 |
| 1985 | 45 |
| 1986 | 35 |
| 1987 | 44 |
| 1988 | 30 |
| 1989 | 30 |
| 1990 | 22 |
| 1991 | 20 |
| 1992 | 33 |
| 1993 | 36 |
| 1994 | 43 |
| 1995 | 30 |
| 1996 | 28 |
| 1997 | 28 |
| 1998 | 16 |
| 1999 | 21 |
| 2000 | 17 |
| 2001 | 8 |
| 2002 | 14 |
| 2003 | 19 |
| 2004 | 18 |
| 2005 | 24 |
| 2006 | 13 |
| 2007 | 22 |
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\") = 1995
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 390)
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") = 1995 AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 390) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run 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 LAX96LA088Accident · No injuriesLimited investigationFinal reportCessna 150L · Quartzite, AZthe pilot's misjudgement of his distance and altitude relationship to the runway, which resulted in an undershoot and failure to achieve the proper touchdown point for landing.NTSB CHI96LA057Accident · No injuriesLimited investigationFinal reportBeech 58 · Minneapolis, MNthe pilot-in-command's abrupt maneuvering during the circling approach. The factors involved were the airframe ice and fog.NTSB SEA96LA030Accident · No injuriesLimited investigationFinal reportCessna 170B · John Day, ORThe pilot's failure to maintain a proper glidepath.NTSB ANC96LA018Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · Nanwalek, AKThe pilot's inadequate compensation for wind conditions. A factor in the accident was the variable wind.NTSB LAX96LA069Accident · No injuriesLimited investigationFinal reportCessna 172 · Ocotillo Wells, CAthe failure of the pilot to maintain a proper glide path on final approach.NTSB BFO96LA023Accident · No injuriesLimited investigationFinal reportBeech A23-24 · New Carlisle, OHthe pilot-in-command's failure to reach the proper touchdown point. Related factors were the pilot's failure to obtain/maintain the proper glidepath during the approach, and the rough/uneven terrain encountered after the airplane touched down short of the…NTSB CHI96FA034Accident · 2 fatalField investigationFinal reportErcoupe 415-C · Stafford, KSthe pilot misjudged his distance and altitude and flew into transmission wires. A factor was the pilot's lack of recent night flying experience.NTSB DCA96MA008Accident · Minor injuriesClass 1 · MajorFinal reportMcDonnell Douglas MD-83 · East Granby, CTthe flightcrew's failure to maintain the required minimum descent altitude until the required visual references identifiable with the runway were in sight. Contributing factors were the failure of the BDL approach controller to furnish the flightcrew with a…NTSB NYC96FA024Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Ashville, NYthe pilot's misjudgment of altitude and distance to the runway during an approach to land. Factors relating to the accident were: the night and adverse weather conditions.NTSB NYC96LA020Accident · No injuriesLimited investigationFinal reportCessna 414A · Grt Barrington, MAthe pilot's inadequate compensation for wind conditions, which resulted in an undershoot of the proper touchdown point for landing. Factors relating to the accident were: the unfavorable wind conditions and the exposed runway lip.NTSB FTW96LA020Accident · No injuriesLimited investigationFinal reportCessna 182P · Kingston, OKthe pilot's inadequate compensation for the wind gusts. Factors were the gusts and the dark night conditions.NTSB CHI96LA012Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-260 · Wakeeney, KSFailure of the pilot to maintain sufficient altitude and airspeed on final approach to reach the proper touchdown point for landing. A factor relating to the accident was: the pilot's selection of the wrong runway for landing.NTSB FTW96LA016Accident · No injuriesLimited investigationFinal reportCessna 182E · Fort Collins, COa fatigue failure of the right main landing gear. Factors were the pilot's failure to attain the proper touchdown point and his inadequate compensation for the crosswind conditions.NTSB BFO96LA008Accident · No injuriesLimited investigationFinal reportGrumman American G-1159 · Cleveland, OHthe pilots' failure to attain the proper touchdown point and avoid obstacles (construction barricades) during the landing flare/touchdown. Related factors were: the sunglare, which limited in the pilots' visual lookout during the approach, and the unavailable…NTSB ANC95LA159Accident · No injuriesLimited investigationFinal reportCessna 206 · Homer, AKThe pilot's inadequate compensation for the wind conditions, which resulted in his failure to reach the proper touchdown point for landing. Factors related to the accident were: the variable wind condition, and rising terrain (no overrun) at the approach end…NTSB NYC95LA216Accident · Minor injuriesLimited investigationFinal reportPiper J-3 · Boothbay Harbor, MEthe pilot's misjudgment of distance and altitude, while on final approach to land. Factors relating to the accident were: sunglare, and the pilot's lack of visual cues (visual perception).NTSB SEA95LA187Accident · No injuriesLimited investigationFinal reportCessna 177B · Yamhill, ORThe pilot's failure to maintain a proper glidepath. A factor contributing to the accident was the sunglare.NTSB CHI95LA207Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Linton, NDThe pilot's misjudging distance and altitude. The pilot's lack of total experience in type of operation was a factor.NTSB SEA95LA131Accident · No injuriesLimited investigationFinal reportCessna 172F · Homedale, IDThe pilot misjudged distance and altitude during the approach. The downdraft was a factor.NTSB BFO95LA061Accident · Serious injuriesLimited investigationFinal reportConsolidated-Vultee BT-13B · Oxford, CTthe pilot's failure to maintain sufficient altitude/clearance from terrain. The low ceiling was a related factor in the accident.NTSB SEA95FA103Accident · 2 fatalField investigationFinal reportCessna 177RG · Kent, WAThe pilot's misjudgment of distance and altitude during the approach. Factors in the accident were the dusk light condition and the shadows.NTSB FTW95LA204Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Baytown, TXThe pilot failed to maintain the proper glidepath during landing.NTSB LAX95LA164Accident · Serious injuriesLimited investigationFinal reportSchweizer SGS 2-33A · Peoria, AZthe pilot's misjudged evaluation of the weather, and his inadequate compensation for the gusting winds and downdrafts.NTSB ANC95LA038Accident · No injuriesLimited investigationFinal reportCessna 152 · Anchorage, AKA failure of the instructor pilot to adequately supervise the student pilot's landing approach. The student pilot's failure to maintain a proper altitude and distance to the runway touch-down point, and a snow berm at the approach end of the runway were…NTSB SEA95LA069Accident · No injuriesLimited investigationFinal reportScheibe Flugzeugbau Bergfalke II-55 · Bozeman, MTThe pilot misjudged his altitude and distance from the runway. A factor was the pilot's failure to obtain the current altimeter setting.NTSB CHI95LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Lakeville, MNThe pilot misjudged distance and altitude during landing.NTSB NYC95LA057Accident · Minor injuriesLimited investigationFinal reportBeech C23 · Warwick, NYthe pilot allowed the airplane to get too low on the approach, during a simulated engine out landing, which resulted in impacting high bushes, and landing short of the runway.NTSB CHI95LA076Accident · No injuriesLimited investigationFinal reportBeech V35A-TC · Pembina, NDthe pilot's misjudgement of the actual altitude of the airplane. Factors were the visual illusion caused by the snow covered runway environment and the whiteout weather condition.NTSB CHI95LA068Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-181 · Brookfield, WIThe instructor's failure to maintain clearance with trees. Factors associated with the accident were the trees and the night lighting conditions.NTSB MIA95FA053Accident · 2 fatalField investigationFinal reportLarson, C.H. Cozy MK IV · Wauchula, FLDistance vs. altitude misjudged by the pilot-in-command while on short final approach. Additionally, altitude/clearance not maintained while on short final approach resulting in the collision with an unmarked static power line.