NTSB investigations, IN
13 cases where the first occurrence was “Undershoot”.
Cases per year
| 1982 | 1 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1989 | 4 |
| 1994 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1999 | 1 |
| 2001 | 1 |
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.\"eventStateOrRegion\" = 'IN' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'IN' AND c."eventCountry" = 'USA' 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 CHI01LA317Accident · No injuriesLimited investigationFinal reportBeech 200 · Indianapolis, INThe pilot not maintaining the proper ILS glide slope during the approach and the pilot not executing a missed approach. Contributing to the accident was the rain/mist.NTSB CHI00LA026Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Rochester, INthe pilot did not obtain the proper touchdown point. Factors included the closed runway and the culvert.NTSB CHI97LA154Accident · No injuriesLimited investigationFinal reportCessna 340A · Fort Wayne, INthe pilot did not comply with the decision height and his attention was diverted from his cockpit scan. The factors involved were the weather conditions were at landing minimums and a flight to his destination alternate was not performed.NTSB CHI96LA289Accident · Minor injuriesLimited investigationFinal reportMrotek Minicab GY20 · Albion, INthe pilot's misjudgment of distance and altitude during the approach to land, and his failure to attain the proper touchdown point. Factors relating to the accident were: the uneven and uphill terrain conditions at the approach end of the airstrip.NTSB CHI94LA341Accident · No injuriesLimited investigationFinal reportDooley, James M Velocity · Valparaiso, INthe pilot-in-command's improper use of the elevator trim. A factor was the pilot-in-command's lack of total experience in type of aircraft.NTSB CHI89LA190Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201 · Delphi, INThe pilot-in-command's failure to properly compensate for the high sink rate that developed on final approach to land. Factors related to the accident were: the downdraft and the student pilot's failure to maintain a proper rate of descent on final approach.NTSB CHI89LA177Accident · No injuriesLimited investigationFinal reportCessna 177B · Auburn, INFailure of the pilot to maintain directional control during the landing, which resulted in a ground swerve. Contributing factors were: the pilot's misjudgement of distance, speed, and altitude on final approach and high vegetation (tall grass & brush) beside…NTSB CHI89LA111Accident · No injuriesLimited investigationFinal reportBoeing E75 · Shelbyville, INThe pilot allowed his attention to be devaited, misjudged altitude and distance to the runway while on final approach, and failed to maintain clearance above the power lines. Contributing factors were: the power lines and parked aircraft.NTSB CHI89LA072Accident · No injuriesLimited investigationFinal reportBeech A60 · Indianapolis, INThe pilot misjudged altitude and/or distance to the runway wile on final approach to land. Factors related to the accident were: dark night and pilot fatigue.NTSB CHI86LA157Accident · No injuriesLimited investigationFinal reportBrantly Helicopter B-2B · Griffith, INThe student plt & instructor (CFI) were on a dual instructional flt, practicing landings. During an apch to rwy 8, the student began to undershoot on final apch. As the helicopter was apchg a fence near the apch end of the rwy, he became alarmed & applied aft…NTSB CHI85LA223Accident · No injuriesLimited investigationFinal reportPiper PA-31-T · Rochester, INWhen the plt reduced power & flared, the acft touched down short of the rwy. The acft sustained substanitial damage when the landing gear struck the edge of the raised rwy surface.NTSB CHI84LA240Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Indianapolis, INPlt stated airspeed appeared too fast on final so a go-around was initiated. Power was advanced and plt raised the flaps which were full down. Plt stated, when flaps came up the acft started sinking and it settled into trees off the end of rwy. Plt stated…NTSB CHI82DA055Accident · No injuriesFinal reportPiper PA-38-112 · Lebanon, INWhile the instructor was demonstrating recovery procedures from a low approach, the main gear struck snow on a small rise about 400 feet short of the runway. Subsequently, the pilot was forced to land in about 18 inches of snow and the gear failed. The…