NTSB investigations, 2001
14 cases where the first occurrence was “Gear collapsed”.
Cases per year
| 1982 | 8 |
|---|---|
| 1983 | 12 |
| 1984 | 12 |
| 1985 | 17 |
| 1986 | 11 |
| 1987 | 7 |
| 1988 | 4 |
| 1989 | 11 |
| 1990 | 6 |
| 1991 | 9 |
| 1992 | 7 |
| 1993 | 4 |
| 1994 | 18 |
| 1995 | 11 |
| 1996 | 6 |
| 1997 | 11 |
| 1998 | 9 |
| 1999 | 21 |
| 2000 | 9 |
| 2001 | 14 |
| 2002 | 18 |
| 2003 | 11 |
| 2004 | 6 |
| 2005 | 12 |
| 2006 | 13 |
| 2007 | 18 |
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\") = 2001
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\" = 190)
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") = 2001 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" = 190) 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 SEA02LA018Accident · No injuriesLimited investigationFinal reportLuscombe 8C · Olympia, WADirectional control not maintained during the landing roll. Factors include main gear overload and standing water on the runway.NTSB MIA02LA035Accident · No injuriesLimited investigationFinal reportCessna 175A · Fairhope, ALThe pilot's failure to check wind conditions prior to landing resulting in a landing with a tailwind, on a wet runway, and damage to the airplane during a ground loop in an attempt to stop the airplane before over running the runway.NTSB SEA02LA015Accident · No injuriesLimited investigationFinal reportCessna 402B · Pasco, WAthe pilot's failure to keep the aircraft from touching down short of the displaced threshold, and his failure to maintain directional control after the aircraft's left main gear tire deflated as a result of impacting the lip at the beginning of the subject…NTSB CHI02LA018Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201T · Peoria, ILThe gear collapse for undetermined reasons during the landing roll. A factor was the pilot not using a proper touchdown point by landing long.NTSB NYC02LA007Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Philadelphia, PAThe collapse of the right main landing gear for undetermined reasons.NTSB CHI01LA330Accident · No injuriesLimited investigationFinal reportColonial C-2 · Faribault, MNThe failure of the landing gear shock strut.NTSB ANC01LA145Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Tanana, AKAn unlocked landing gear mechanism during landing roll. A factor associated with the accident was an electrical system failure.NTSB ATL01LA112Accident · No injuriesLimited investigationFinal reportCessna 210K · Bessemer, ALFailure of the landing gear-down lock mechanism, which resulted in the pilot's inability to control the airplane. A factor was the trees.NTSB LAX01TA284Accident · No injuriesFinal reportAero Commander 500S · Elko, NVThe main landing gear collapsed for undetemined reasons.NTSB CHI01LA279Accident · No injuriesLimited investigationFinal reportGlobe GC-1B · Traverse City, MIThe pilot not following the emergency landing gear extension procedures. Factors were the failure of the hydraulic motor, and the landing gear locks not engaged.NTSB FTW01LA170Accident · No injuriesLimited investigationFinal reportCessna T210N · Amarillo, TXthe pilot's failure to verify that the landing gear was extended and locked before landing. A contributing factor was a tripped landing gear motor circuit breaker, which resulted in the failure of the main landing gear to fully extend and lock.NTSB DEN01LA114Accident · No injuriesLimited investigationFinal reportPiper PA-34-200 · Provo, UTinadvertent retraction of the landing gear by the pilot rated student during landing roll. A contributing factors was the failure of the instructor to adequately supervise the student.NTSB ATL01LA058Accident · No injuriesLimited investigationFinal reportPiper PA-44-180 · Brooksville, FLThe fatigue failure of the left main landing gear strut that resulted in collapse of the landing gear.NTSB CHI01LA079Accident · No injuriesLimited investigationFinal reportCessna 310R · Cahokia, ILThe collapse of the left main landing gear during landing roll for undetermined reasons.