NTSB investigations: Lycoming IO-540 series
39 cases on aircraft whose registry engine model is Lycoming IO-540 series, where the first occurrence was “In flight collision with terrain/water”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1982 | 3 |
|---|---|
| 1983 | 2 |
| 1984 | 1 |
| 1986 | 2 |
| 1987 | 1 |
| 1989 | 2 |
| 1990 | 1 |
| 1991 | 2 |
| 1992 | 3 |
| 1994 | 2 |
| 1995 | 1 |
| 1997 | 1 |
| 1999 | 2 |
| 2000 | 2 |
| 2001 | 4 |
| 2002 | 3 |
| 2003 | 2 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 2 |
| 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41530', '41585')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 230))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41530', '41585')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 230))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 CHI08CA013Accident · No injuriesData collectionFinal reportCessna 182 · Middlefield, OHThe proper touchdown point not obtained by the pilot and the inadequate supervision by the certified flight instructor during landing. A contributing factor was the rough terrain encountered during landing.NTSB LAX07LA054Accident · 2 fatalLimited investigationFinal reportJohn Lauer Harmon Rocket II · Bakersfield, CAThe pilot's failure to maintain terrain clearance during an aerobatic maneuver.NTSB ANC06LA029Accident · 1 fatalLimited investigationFinal reportCooper Harmon Rocket ll · McKittrick, CAThe pilot's failure to maintain altitude/clearance while performing intentional low altitude aerobatic flight maneuvers. Factors associated with the accident are the low altitude aerobatic flight maneuvers.NTSB NYC06FA034Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Burlington, VTThe pilot's failure to follow the published instrument flight procedure, which resulted in an in-flight collision with terrain. Factors in the accident were the local air traffic controller's inadequate monitoring of the MSAW system, and his delayed…NTSB CHI04CA250Accident · No injuriesData collectionFinal reportPiper PA-32-301 · Crivitz, WIThe proper touchdown point not attained by the pilot during landing. The road and tailwind were contributing factors.NTSB MIA03FA065Accident · 1 fatalField investigationFinal reportAerofab Lake 250 · Weirsdale, FLThe inadequate flare by the pilot-in-command on the calm water resulting in the in-flight collision with the water and subsequent nose over.NTSB CHI03LA236Accident · 1 fatalLimited investigationFinal reportPolsgrove Bluegrass Express · Grafton, ILUndetermined.NTSB IAD03FA004Accident · 1 fatalField investigationFinal reportCessna 182S · Brownville Jct, METhe pilot's failure to maintain sufficient altitude while flying in mountainous terrain at night. A factor was the night lighting conditions.NTSB IAD03FA001Accident · 1 fatalField investigationFinal reportPiper Aerostar 602P · Bradford, PAThe pilot's failure to follow the published instrument approach procedure, which resulted in an early descent into trees and terrain. A factor was the night, instrument meteorological conditions.NTSB LAX02FA073Accident · 1 fatalField investigationFinal reportPiper Aerostar 601P · Stonyford, CAthe pilot's failure to maintain terrain clearance during cruise flight, which resulted in the in-flight collision with mountainous terrain. Factors in the accident were the mountainous terrain and the dark night light conditions.NTSB CHI01LA261Accident · No injuriesLimited investigationFinal reportMcIntosh Steen Skybolt · Lebanon, INThe pilot misjudged his altitude during the landing. A factor was the soybean crop which the airplane contacted.NTSB NYC01LA120Accident · Minor injuriesLimited investigationFinal reportPiper PA-32RT-300 · Ithaca, NYThe pilot's failure to follow the published instrument approach procedure.NTSB ANC01LA056Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Emmonak, AKThe pilot's inadvertent stall while maneuvering. A factor associated with the accident was soft, snow-covered terrain.NTSB DEN01LA054Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Angel Fire, NMthe pilot's failure to maintain control of the airplane during landing. Contributing factors were the crosswind, the pilot exceeding the published maximum demonstrated crosswind component, and the snow bank.NTSB NYC00LA111Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · East Haddam, CTThe private pilots failure to obtain the proper touchdown point and the CFI's delay in remedial action.NTSB IAD00LA021Accident · 2 fatalLimited investigationFinal reportWood Seawind 3000 · Cumberland Gap, VAThe pilot's continued flight from visual flight rules into instrument meteorological conditions.NTSB ANC99LA039Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Chefornak, AKThe pilot's selection of an unsuitable landing site. A factor associated with the accident was rough and uneven terrain.NTSB ATL99FA048Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Cartersville, GAIn flight collision with terrain for undetermined reasons.NTSB SEA97LA140Accident · Minor injuriesLimited investigationFinal reportRepublic RC-3-1 · Monument Valley, UTthe pilot's inadequate preflight planing/preparation, and his failure to maintain sufficient altitude or clearance from the terrain. Factors relating to the accident included: high, gusty, variable winds, and terrain induced downdrafts.NTSB BFO95LA062Accident · 1 fatalLimited investigationFinal reportBerg Steen Skybolt · Bath, NYthe pilot's failure to maintain sufficient altitude/clearance to avoid trees while performing aerobatic maneuvers. Related factors are the low altitude at which the maneuver was initiated and the delayed recovery/pull-up.NTSB CHI94LA218Accident · No injuriesLimited investigationFinal reportCallair A9B · Minot, NDthe pilot's failure to maintain clearance from the wheat field. A factor was the turbulence.NTSB MIA94FA067Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Sugarloaf Key, FLWas the failure of the pilot-in-command to perform a visual lookout and maintain his altitude. Contributing to the accident was the dark night, over water, visual descent.NTSB ANC93LA019Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Scammon Bay, AKThe pilots VFR flight into IMC conditions, and his failure to maintain sufficient altitude while maneuvering. Contributing to the accident were the whiteout snow and fog conditions.NTSB ANC92LA140Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Togiak, AKThe pilot's improper preflight planning/decision, and his delay in aborting the takeoff. Contributing factors were the berm and the standing water on the runway.NTSB MIA92LA068Accident · 3 fatalLimited investigationFinal reportPiper PA-32-301 · Atlantic Ocean (Atlantic Ocean)Undetermined. The airplane crashed in the Atlantic Ocean and was not located.NTSB ATL91LA169Accident · Minor injuriesLimited investigationFinal reportBates, Frank L Skybolt · Yatesville, GAThe pilot's failure to maintain a proper altitude during maneuvering flight.NTSB FTW91DRA03Accident · No injuriesFinal reportBronner Skybolt · Alvin, TXThe pilot's failure to maintain terrain clearance. A factor was the pilot's decision to perform a low pass.NTSB SEA90LA147Accident · Minor injuriesLimited investigationFinal reportLake LA-250 · Rawlins, WYPilot's improper planning/decision, and his misjudgement of the aircraft's climb capability in conditions of high density altitude and unanticipated atmospheric conditions. The high density altitude and rising terrain were related factors.NTSB ANC89LA139Accident · No injuriesLimited investigationFinal reportMaule M-5 · Nebesna Glacier, AKThe pilot allowed the aircraft to inadvertently touch down, he delayed making a go-around, and he did not maintain sufficient speed to continue the go-around. Contributing factors were: the pilot's selection of unsuitable terrain, high vegetation in the…NTSB CHI89LA110Accident · No injuriesLimited investigationFinal reportMaule MX-7-235 · Indianapolis, INImproper compensation for wind conditions by the pilot, his failure to maintain runway alignment, and his misjudgement of wingtip clearance above the ground as he was maneuvering to avoid the runway & VASI lights. The crosswind and runway/vasi lights were…NTSB LAX87DVA03Accident · No injuriesFinal reportEagle DW-1 · Modesto, CADuring an aerial application flight, the pilot stated that just after the aircraft became airborne, it began to lose altitude and struck a canal bank at the end of the dirt strip. There were no reported mechanical failures or malfunctions. The acft was loaded…NTSB MIA87FA004Accident · No injuriesField investigationFinal reportSmith, Ted Aerostar Aerostar 600 · Jacksonville, FLReportedly, during an ILS approach to land, the pilot did not use the company approved checklist and landed with the gear retracted.NTSB FTW86LRA04Accident · Minor injuriesFinal reportEagle DW-1 · Bremond, TXAccording to the pilot, the aircraft was being operated by thompson flyers of garwood, inc., rt 1, box 214, marlin, TX. In agricultural aircraft operations under FAA ag operation certificate no. SW-HOU-97-AG. The aircraft had completed its last swath run…NTSB NYC85LA033Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Prospectville, PAPlt stated he allowed the acft to go low on final approach. Collision with terrain separated the landing gear but plt recovered control as acft rebounded and executed a successful go-around. Plt diverted with escort to nearby military arpt where CFR…NTSB NYC83FA254Accident · 3 fatalField investigationFinal reportBellanca 17-31ATC · Provincetown, MAThe acft crashed in cape cod bay during a night x-country flt. Two sections of wooden wing identified as from the same make and model as the missing acft were recovered from the bay during the 3 days following the flt of the acft. Other identified parts of…NTSB CHI83FA138Accident · No injuriesField investigationFinal reportPiper PA-601P · Wheeling, ILAfter making an ILS approach to rwy 16, the plt was cleared to circle and land on rwy 34. As he turned final, he was to the west side of the runway and was too high to land, so he made a left turn-around back to rwy 34. Tower personnel turned the rwy lights…NTSB CHI82DA256Accident · No injuriesFinal reportPiper PA-32RT · Mackinac, MIAircraft landed wheels up. No malfunction of the landing gear system could be found.NTSB LAX82DA239Accident · No injuriesFinal reportCessna R182 · Fresno, CAWhen the landing gear was extended to demonstrate an approach-to-landing stall, there was no safe indication. The gear was recycled but the nose gear would not extend. All attempts to extend the nose gear, including the use of the emergency extension hand…NTSB SEA82DA080Accident · No injuriesFinal reportEagle DW-1 · Sprague, WAThe pilot had checked out in this make and model of aircraft on the preceeding day. On the day of the accident, he was spraying fertizer in a crosswind condition. He stated that he was on a downhill swath run in gusty conditions when he deployed the controls…