NTSB investigations, 1996
12 cases where the first occurrence was “Wheels up landing”.
Cases per year
| 1993 | 2 |
|---|---|
| 1994 | 2 |
| 1995 | 12 |
| 1996 | 12 |
| 1997 | 12 |
| 1998 | 17 |
| 1999 | 17 |
| 2000 | 18 |
| 2001 | 21 |
| 2002 | 19 |
| 2003 | 10 |
| 2004 | 13 |
| 2005 | 16 |
| 2006 | 17 |
| 2007 | 15 |
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\") = 1996
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\" = 232)
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") = 1996 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" = 232) 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 NYC97LA009Accident · Serious injuriesLimited investigationFinal reportMcDonnell Douglas MD-80 · Jamaica, NYFailure of the nose landing gear upper lock link.NTSB MIA96LA224Accident · No injuriesLimited investigationFinal reportBeech 58 · Panama City, FLfailure of the pilot to extend the landing gear before touchdown, which resulted in an inadvertent wheels-up landing. Factors relating to the accident were: the pilot allowed his attention to be diverted, and the resultant interference with his landing…NTSB FTW96LA336Accident · No injuriesLimited investigationFinal reportBeech E-55 · Brownwood, TXThe pilot's failure to extend the landing gear. Factors were the pilot's failure to use a checklist, his diverted attention, and the landing gear warning horn not sounding.NTSB SEA96LA141Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Paris, IDthe pilot forgot to extend the landing gear before landing. Factors relating to the accident were: an interuption of the pilot's habit pattern, when he circled to provide time for another airplane to takeoff as he entered the traffic pattern; and his failure…NTSB SEA96LA121Accident · No injuriesLimited investigationFinal reportBeech 35 · Aurora, ORfailure of the non-certificated pilot to ensure that the landing gear was properly extended for landing. The non-certificated pilot's diverted attention was a related factor.NTSB CHI96LA155Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201 · Lafayette, INthe flight instructor's inadequate supervision and the dual student's failure to extend the landing gear. Factors were the distraction of the flight instructor and the student's failure to use checklist procedures.NTSB CHI96LA144Accident · No injuriesLimited investigationFinal reportBeech B55B · Manhattan, KSthe pilot's failure to properly extend the landing gear. A factor was his failure to follow checklist procedures.NTSB LAX96LA165Accident · No injuriesLimited investigationFinal reportCessna T210N · Paradise, CAthe pilot's failure to follow landing gear extension procedures by not confirming that the gear was fully extended prior to touchdown. A contributing factor was the interference/alteration of the pilot's customary habit pattern due to his response to a…NTSB FTW96LA162Accident · No injuriesLimited investigationFinal reportCessna T210R · Albuquerque, NMthe pilot's failure to extend the landing gear. Factors were his failure to follow the checklist and his diverted attention due to other traffic.NTSB SEA96LA058Accident · No injuriesLimited investigationFinal reportBeech 35 · Laurel, MTthe pilot's failure to extend the landing gear. Factors related to the accident were: an inoperative gear warning system, the dark night, and the pilot's failure to follow the checklist.NTSB FTW96FA118Accident · Minor injuriesClass 1 · FieldFinal reportMcDonnell Douglas DC-9-32 · Houston, TXthe captain's decision to continue the approach contrary to Continental Airlines (COA) standard operating procedures that mandate a go-around when an approach is unstabilized below 500 feet or a ground proximity warning system alert continues below 200 feet…NTSB SEA96LA045Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Camas, WAFailure of the pilot to ensure that the landing gear was extended before landing.