NTSB investigations: Lycoming IO-540 series, VA
20 cases on aircraft whose registry engine model is Lycoming IO-540 series. 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
| 1969 | 1 |
|---|---|
| 1980 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 1991 | 1 |
| 1994 | 1 |
| 1997 | 3 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2006 | 1 |
| 2007 | 1 |
| 2008 | 1 |
| 2016 | 1 |
| 2017 | 1 |
| 2018 | 1 |
| 2022 | 1 |
| 2023 | 1 |
Where
Latest 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\" = 'VA' AND c.\"eventCountry\" = 'USA'
AND 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'))
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" = 'VA' AND c."eventCountry" = 'USA'
AND 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'))
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 ERA23FA108Accident · 1 fatalClass 3 · FieldFinal reportPiper PA-32R-301 · Dayton, VAThe pilot’s controlled flight into terrain while descending over mountainous terrain at night.NTSB ERA22LA259Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32R-301 · Spencer, VAThe pilot’s failure to extend the landing gear before landing. Contributing to the accident was the pilot’s failure to use the landing checklist.NTSB ERA18FA187Accident · 2 fatalField investigationFinal reportRobinson R44 · Williamsburg, VAThe pilot's failure to safely operate the helicopter due to his impaired cognitive and physical abilities, which resulted in a loss of control.NTSB GAA18CA017Accident · Serious injuriesData collectionFinal reportYoung David E Pitts S1 C · Farmville, VAThe pilot’s failure to see and avoid the other airplane landing in the opposite direction on the runway. Contributing to the accident was the pilot’s failure to use the correct runway call sign in his radio communications.NTSB GAA16CA110Accident · Minor injuriesData collectionFinal reportPiper PA32RT · Melfa, VAThe pilot's inadequate compensation for a gusting crosswind during landing, which resulted in an aerodynamic stall, impact with a structure, and subsequent postimpact fire.NTSB ERA09FA029Accident · 2 fatalField investigationFinal reportPiper PA-24 · Red Hill, VAThe pilot's failure to maintain aircraft control due to an improper repair to the stabilator, which resulted in an in-flight failure of the stabilator. Contributing to the accident was the descent in turbulence, at airspeeds above the maximum structural…NTSB NYC07LA104Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Richmond, VAThe improper installation of the right brake assembly by maintenance personnel.NTSB NYC06LA185Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R-300 · Blacksburg, VAA partial loss of engine power for undetermined reasons, which resulted in a forced landing after takeoff, and subsequent collision with trees.NTSB IAD01LA046Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · King George, VAThe failure of cylinder case and thru studs due to fatigue, which resulted in a loss of engine power over unsuitable terrain.NTSB IAD00LA021Accident · 2 fatalLimited investigationFinal reportWood Seawind 3000 · Cumberland Gap, VAThe pilot's continued flight from visual flight rules into instrument meteorological conditions.NTSB NYC99LA063Accident · 1 fatalLimited investigationFinal reportPiper PA 32R-301 · Dulles, VAThe FBO employee's diverted attention, resulting in an inadvertent encounter with a rotating propeller.NTSB IAD98FA015Accident · 1 fatalField investigationFinal reportSocata TB-20 Trinidad · Roanoke, VALoss of engine power for undetermined reasons. A related factor was the low ceiling.NTSB NYC98LA015Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Scottsville, VAimproper engine operation by undetermined person(s) that initiated gauling on the connecting rod, and led to its subsequent failure.NTSB NYC97FA080Accident · 2 fatalField investigationFinal reportPiper PA-60-601P · Waterford, VAfailure of the pilot to follow the published instrument (IFR) approach procedure, by failing to maintain the minimum altitude for that segment of the approach.NTSB BFO94LA038Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Norfolk, VAFatigue failure of the engine mounting bolt which resulted in loss of engine power and subsequent on ground collision with the terrain.NTSB BFO91LA063Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · New Market, VAThe pilot's inadequate inflight decision that resulted in VFR flight into IMC.NTSB ATL85FA101Accident · 2 fatalField investigationFinal reportCessna 182R · Burkes Garden, VAThe plt departed manassas without a current wx briefing or filing a flt plan. Plt had also left maps and a list of checkpoints at home. His route of flt was into an area of low ceilings and visibility. The acft crashed into a mountain at the 3850 ft level.…NTSB ATL84LA121Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Warrenton, VAThe CFI shut down one engine during takeoff for a simulated emergency and the plt taking instruction applied the incorrect rudder action during the aborted takeoff and left full power on the operating right engine. The CFI was unableto correct the resulting…NTSB IAD80FID08Accident · Minor injuriesClosedPiper PA-31 · Appomattox, VANTSB IAD70F0060Accident · No injuriesClosedPiper PA-23 · Alexandria, VA