NTSB investigations, 2005
16 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\") = 2005
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") = 2005 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 LAX06LA034Accident · No injuriesLimited investigationFinal reportBeech H35 · Kingman, AZa touchdown with the gear partially extended. A factor in the accident was an inoperative landing gear warning horn.NTSB ATL06LA014Accident · 1 fatalLimited investigationFinal reportMooney M20M · Summerville, SCThe pilot's failure to follow the pre-landing checklist which resulted in a gear up landing and subsequent propeller strike. The pilots improper decision to attempt a go-around after the propeller strike, resulted in a loss of engine power and subsequent…NTSB LAX06CA028Accident · No injuriesData collectionFinal reportLearjet 25D · Sacramento, CAthe pilot's failure to extend the landing gear and to verify they were in the down and locked position prior to touchdown. A related factor was his diverted attention.NTSB LAX05CA304Accident · No injuriesData collectionFinal reportBeech 95-B55 · Porterville, CAthe pilot's failure to extend the landing gear prior to landing.NTSB CHI05CA258Accident · No injuriesData collectionFinal reportPiper PA-44-180 · Fertile, MNThe flightcrew's failure to extend the landing gear prior to touchdown, and the flight instructor's inadequate supervision of the flight.NTSB DFW05CA206Accident · No injuriesData collectionFinal reportCessna 182T · Houston, TXThe gear-up landing as result of the separation of the hydraulic line in the landing gear extension system.NTSB DEN05CA134Accident · No injuriesData collectionFinal reportEclipse HXB · Albuquerque, NMthe pilot's failure to extend the landing gear prior to landing. A contributing factor was the pilot's failure to complete the before landing checklist.NTSB ANC05LA130Accident · No injuriesLimited investigationFinal reportCessna 441 · Anchorage, AKThe pilot's failure to lower the airplane's landing gear during landing, which resulted in an inadvertent wheels up landing.NTSB IAD05FA125Accident · 2 fatalField investigationFinal reportPiper PA-32R-301 · West Chester, PAThe pilot's improper decision to abort the landing after the airplane contacted the runway. A factor in the accident was the pilot's failure to ensure the landing gear was extended during the landing.NTSB DCA05MA095Accident · Minor injuriesMajor investigationFinal reportBoeing 747-200 · Aganathe flight crews' failure to verify that the number of landing gear annunciations on the second officer’s panel was consistent with the number specified in the abnormal/emergency procedures checklist, which led to a landing with the nose gear retracted.NTSB LAX05LA198Accident · No injuriesLimited investigationFinal reportCessna 210 · Watsonville, CAthe pilot's failure to extend the landing gear prior to landing.NTSB ANC05CA078Accident · No injuriesData collectionFinal reportPiper PA-31-310 · Manokotak, AKThe pilot's failure to extend the landing gear. A contributing factor was the pilot's failure to use the checklist.NTSB DFW05CA122Accident · No injuriesData collectionFinal reportBeech BE-55 · Midland, TXThe pilot's failure to extend the landing gear which resulted in a gear-up landing. A contributing factor was the pilot's failure to follow the checklist.NTSB SEA05CA078Accident · No injuriesData collectionFinal reportShannon Lancair Legacy 2000 · Bend, ORThe pilot's failure to put the landing gear down for landing.NTSB LAX05LA178Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-26A · Blythe, CAthe pilot's failure to lower the landing gear prior to landing. A factor to the accident was the pilot's diverted attention due to the flap system anomaly.NTSB NYC05LA056Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Millville, NJThe flight instructor's failure to lower the landing gear during landing.