NTSB investigations, NV
13 cases where the first occurrence was “Loss of engine power(partial) - mech failure/malf”.
Cases per year
| 1986 | 1 |
|---|---|
| 1987 | 1 |
| 1988 | 1 |
| 1989 | 2 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1994 | 2 |
| 1998 | 1 |
| 2000 | 1 |
| 2007 | 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\" = 'NV' 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\" = 352)
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" = 'NV' 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" = 352) 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 SEA07IA201Incident · No injuriesIncident investigationFinal reportCirrus Design SR22 · Reno, NVThe failure of the left turbocharger as a result of a production defect in the unit's compressor due to a machining process change by the manufacturer that was made without formal documentation or substantiation.NTSB LAX00GA297Accident · 1 fatalFinal reportBell 412 · Cold Springs, NVfailure of the compressor turbine disc due to cyclic fatigue brought about by repeated operation near or above the engines' temperature/power limits by company personnel over an extended period of time. Factors in the accident were: 1) the high density…NTSB LAX98LA244Accident · Minor injuriesLimited investigationFinal reportBellanca BL-17 · Winnemucca, NVLoss of engine power due to a missing cotter key and jam nut, the use of an improper nonapproved part by other maintenance personnel, and failure to safety the installation which subsequently lead to a throttle/carburetor linkage disconnect.NTSB LAX95LA022Accident · No injuriesLimited investigationFinal reportForney F-1 · Searchlight, NVthe pilot's failure to maintain directional control by improperly compensating for the existing wind conditions. The leaking cylinder, the prevailing crosswind, the soft terrain, and the dirt bank were factors in this accidentNTSB LAX94FA165Accident · 2 fatalField investigationFinal reportAyres S-2R · Reno, NVAn undetermined problem with the engine oil system, a decision to fly the airplane with a known deficiency, and progressive (partial) failure of the engine master rod and bearing.NTSB LAX92LA395Accident · Minor injuriesLimited investigationFinal reportAbrams/Nuding Quickie Q2 · Minden, NVFuel starvation for undetermined reasons. A factor in the accident was the unsuitable nature of the terrain for the forced landing attempt.NTSB LAX91LA229Accident · No injuriesLimited investigationFinal reportGlaser-Dirks DG-500M · Minden, NVAn engine failure produced as a result of the pilot improperly adjusting the carburetor mixture jet.NTSB LAX90FA311Accident · 1 fatalField investigationFinal reportCessna 411 · Fallon, NVFailure of the pilot to perform emergency procedures for loss of engine power (including his failure to feather the propeller of the affected engine). Factors related to the accident were: inadequate maintenance, contamination in the fuel system, and overheat…NTSB SEA89LA045Accident · Serious injuriesLimited investigationFinal reportPiper PA-31 · Sparks, NVThe pilot's misjudgement of the forced landing profile. Contributing to the accident was the failure of the right turbocharger and the pilot's improper handling of the landing gear system.NTSB SEA89LA034Accident · No injuriesLimited investigationFinal reportCessna 210 · Carson City, NVSeparation of the throttle cable due to wear as power was applied for a landing go-around. Contributing to the accident was rough terrain at the touchdown point of the forced landing.NTSB SEA89FA015Accident · 2 fatalField investigationFinal reportBeech 65 · Elko, NVApprox 10 min after t/o, the pilot stated he was returning to land due to a problem. On final the acft rolled inverted and descended nose down into a residence. Engine exam revealed a failed supercharger intermediate drive shaft gear resulting in loss of…NTSB SEA88IA017Incident · No injuriesIncident investigationFinal reportBeech E18S · Reno, NVShortly after takeoff, and after the landing gear was raised, the pilot noticed an over-temperature of the right engine. A power reduction was made and afterwards symptoms of a compressor stall occurred. The pilot then shut down the right engine. A 180 degree…NTSB SEA86LA148Accident · No injuriesLimited investigationFinal reportMooney M20-C · Paradise Valley, NVA forced landing was made due to a very rough running engine accompanied by backfiring. It was discovered on engine examination that the spark plugs were worn beyond service limits. During landing roll a cattle guard was struck with the wing tips.