NTSB investigations, NC
15 cases where the sequence of events included Landing gear not configured.
Cases per year
| 2009 | 3 |
|---|---|
| 2010 | 1 |
| 2011 | 1 |
| 2015 | 2 |
| 2018 | 1 |
| 2023 | 2 |
| 2024 | 4 |
| 2026 | 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\" = 'NC' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '095' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\"))
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" = 'NC' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '095' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")) 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 ERA26LA213Accident · No injuriesClass 4 · LimitedFinal reportCessna 177RG · Statesville, NCThe pilot’s failure to extend the landing gear prior to landing.NTSB ERA24LA354Accident · No injuriesClass 4 · LimitedFinal reportBeech 300 · Asheboro, NCThe pilot’s failure to extend the landing gear before landing.NTSB ERA24LA351Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 680 · Washington, NCThe flight crew’s failure to properly configure the airplane before landing and the captain’s subsequent failure to recognize the landing gear aural warning, which resulted in a gear-up landing. Contributing to the accident was the flight crew’s inadequate…NTSB ERA24LA307Accident · No injuriesClass 4 · LimitedFinal reportBeech 95-B55 · Greenville, NCA landing with the nose gear retracted as a result of an intermittent landing gear relay.NTSB ERA24LA186Accident · No injuriesClass 4 · LimitedFinal reportCessna 210 · Concord, NCFailure of a landing gear extension system hydraulic hose, which resulted in a landing with the landing gear retracted.NTSB DCA23FA339Accident · No injuriesClass 3 · FieldFinal reportBoeing 717-200 · Charlotte, NCA fatigue fracture of the upper lock link that initiated along scratch features on the lower surface at the parting line of the forged aluminum component. Contributing to the accident was the overhaul facilities noncompliance with Service Bulletin 717-32-002.NTSB ERA23LA262Accident · No injuriesClass 3 · LimitedFinal reportBurton Searey · Sherrills Ford, NCThe pilot’s failure to configure the amphibious airplane’s landing gear before conducting a forced landing to a lake after a loss of engine power. Also causal was the occluded gascolator and the pilot’s lack of knowledge about the airplane’s fuel system,…NTSB GAA19CA017Accident · No injuriesData collectionFinal reportCessna 177RG · Albermarle, NCThe pilot's improper decision to attempt a gear-up glide to the runway and his subsequent failure to extend the landing gear before landing. Contributing to the accident was the pilot's failure to use a checklist before landing.NTSB ERA15LA273Accident · No injuriesLimited investigationFinal reportBeech 35-C33 · Wilmington, NCThe pilot's failure to ensure that the landing gear was in the down and locked position before touchdown, which resulted in a landing with the gear in transit.NTSB ERA15CA169Accident · No injuriesData collectionFinal reportBellanca 17 31A · Siler City, NCThe pilot's failure to ensure that the airplane's landing gear was down and locked prior to touchdown.NTSB ERA11LA461Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Elizabethtown, NCThe improper securing of a “B” nut on the power turbine control (Py) line by unknown maintenance personnel, which resulted in a total loss of engine power. Contributing to the accident was the pilot's failure to use the manual fuel override switch.NTSB ERA10CA156Accident · No injuriesData collectionFinal reportPiaggio P180 · Greensboro, NCThe pilot's failure to properly configure the landing gear for landing. Contributing to the accident was the pilot's diverted attention looking for traffic and manipulating the secondary trim controls.NTSB ERA10LA004Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Whiteville, NCThe pilot's improper flare and subsequent hard landing during an intentional gear-up landing following multiple mechanical malfunctions. Also causal to the accident was an inoperative landing gear emergency-down valve which had blockage for undetermined…NTSB ERA09CA254Accident · Minor injuriesData collectionFinal reportAmerican Longevity Searey · Littleton, NCThe pilot's failure to ensure the landing gear was properly configured for the water landing.NTSB ERA09LA130Accident · No injuriesLimited investigationFinal reportCessna 550 · Wilmington, NCA loss of engine power due to the crew's inadequate in-flight fuel monitoring.