NTSB investigations, KS
15 cases where the first occurrence was “Undershoot”.
Cases per year
| 1982 | 2 |
|---|---|
| 1983 | 3 |
| 1984 | 2 |
| 1986 | 2 |
| 1988 | 1 |
| 1989 | 1 |
| 1991 | 1 |
| 1993 | 1 |
| 1995 | 2 |
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\" = 'KS' 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" = 'KS' 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 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 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 CHI93LA186Accident · Minor injuriesLimited investigationFinal reportErcoupe 415C · Derby, KSThe pilot in command's misjudged approach to landing.NTSB CHI91LA304Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Atchison, KSDelayed remedial action by the pilot in command. Factors related to the accident are a misjudged approach by the pilot in command, and complacency on the part of the FAA inspector.NTSB MKC90LA031Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Osage City, KSThe pilot misjudged distance and altitude to the runway while on final approach to land. Factors related to the accident were: dark night and static wires.NTSB MKC88LA090Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T1A2 · Horton, KSThe PIC was executing touch and go lndgs when he reportedly experienced a shift in wind conditions. The acft impacted the ground short of the rwy. He said that the wings suddenly lost lift resulting in a high descent rate. The PIC reported no mechanical flt…NTSB MKC86LA180Accident · No injuriesLimited investigationFinal reportPiper PA-28-150C · Junction City, KSThe c.f.I. Stated that this flight was to be an aircraft checkout of another instructor. After some air work they proceeded to a nearby airport to practice takeoffs and landings. While on final approach for a practice short field landing the aircraft…NTSB MKC86FA113Accident · No injuriesField investigationFinal reportSwearingen SA226 · Hutchinson, KSThe capt rprtd that during arrival, the apch seemed normal until he flared to land on rwy 17. At that time, he heard a loud 'pop' as the landing gear contacted the rwy surface. Subsequently, the left main gear collapsed & the acft veered off the rwy. An exam…NTSB MKC85LA019Accident · No injuriesLimited investigationFinal reportCessna R172E · Junction City, KSPilot was experiencing communications difficulties, diverted from destination to nearby uncontrolled arpt due to traffic considerations. Plt was unable to contact UNICOM and elected to circle for traffic and wind evaluation. Best runway for wind direction was…NTSB MKC84LA070Accident · No injuriesLimited investigationFinal reportCessna 182 · Derby, KSDuring an apch from the south in gusty wind conditions, the acft crossed over wires & shrubbery with 20 deg of flaps. The plt reported that before reaching the rwy, the'lost air & descended straight down.' The acft touched down in mud, short of the rwy. The…NTSB MKC84LA012Accident · No injuriesLimited investigationFinal reportCessna 150F · Garnett, KSThe acft collided with trees during final approach to land on a local night flight. The weather was VMC with a 12 mile visibility reported. The pilot reported that during final approach for a full stop landing the acft struck the tops of some trees which…NTSB MKC83FA108Accident · Serious injuriesField investigationFinal reportBeech D55 · Gardner, KSThe plt was cleared for an ILS rwy 35 approach & given the Kansas city downtown arpt (23 mi NE) wx as 900 ft broken & 6 mi visibility. The tower was closed & the control zone was not in effect raising minimums. The plt stated his ILS glide slope indication…NTSB MKC83FA066Accident · Serious injuriesField investigationFinal reportPiper PA-28R-200 · Wichita, KSThe acft was cleared to make the approach and to descend not below 2300 ft. the pilot descended from 3000 after he reported passing hance, the final appoach fix. He descended to 2300 ft at 500 ft a minute and leveled the acft and lowered the landing gear. The…NTSB MKC82DA121Accident · No injuriesFinal reportPiper PA-28-180 · Lawrence, KSThe pilot entered the traffic pattern for landing on runway 19. He stated he was not aware of construction on the runwayuntil the aircraft's nose was lowered during the landing roll. By then, the aircraft's speed was too slow to go-around. He turned off the…NTSB MKC82DA119Accident · No injuriesFinal reportGulfstream AA-5B · Mankato, KSDuring a flight from des moines, Iowa to lamar, Colorado, the pilot elected to land at Mankato, Kansas for fuel. Reportedly, the pilot landed on runway 17 with the wind from 190 at 18 gusting 24 knots. The pilot stated that he established a steep, no flap,…