NTSB investigations: Lycoming IO-720 series
10 cases on aircraft whose registry engine model is Lycoming IO-720 series, where the first occurrence was “Loss of control - in flight”. 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 | 1 |
|---|---|
| 1985 | 1 |
| 1987 | 2 |
| 1996 | 2 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41546')
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\" = 250))
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 ('41546')
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" = 250))
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 LAX07LA280Accident · Serious injuriesLimited investigationFinal reportRoot Sherpa · Scappoose, ORA loss of aircraft pitch control due to the fatigue failure of the fuselage tube structure at the flight control stick gimbal mechanism due to an incomplete weld penetration at the root of the weld.NTSB LAX05GA243Accident · Serious injuriesFinal reportAero Commander 680 FL · Las Vegas, NVThe pilot's excessive selection of flaps prior to takeoff, which resulted in a failure to obtain/maintain an appropriate climb airspeed, and an inadvertent stall/mush during takeoff-initial climb. A factor contributing to the accident was a high density…NTSB MIA04LA074Accident · Minor injuriesLimited investigationFinal reportTerry E. Morris Glasair III · Lakeland, FLThe pilot's failure to maintain airspeed and establish a climb during an attempted go-around which resulted in a stall/mush and collision with terrain. His failure to follow air traffic control instructions is a contributing factor.NTSB DEN03LA098Accident · Minor injuriesLimited investigationFinal reportHelio H800 · Cody, WYthe pilot's improper preflight planning and his failure to maintain aircraft control when returning to the airport. Factors contributing to the accident were the oil leak, the attempted precautionary landing, and the downdraft.NTSB FTW97LA061Accident · No injuriesLimited investigationFinal reportPiper PA-24-400 · Broomfield, COfailure of the pilot to maintain proper alignment with the runway, while landing. A factor relating to the accident was: the variable/gusty wind condition with possible windshear.NTSB FTW96LA353Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Hale Center, TXthe pilot's inadequate preflight planning/preparation and failure to obtain and/or maintain adequate airspeed after takeoff, which resulted in an inadvertent stall/mush. The overweight condition of the airplane and high density altitude were related factors.NTSB NYC87DHD05Accident · Minor injuriesFinal reportPiper PA-36-400 · Mullica Hill, NJThe pilot of the PA-36 was spraying chemicals on trees for control of the gypsy moth. He reported that he was unable to clear power lines and dumped his load. The aircraft settled to the ground. The FAA reported that the weight of the aircraft exceeded the…NTSB DEN87LA117Accident · No injuriesLimited investigationFinal reportPiper PA-36-375 · Lamar, COThe commercial plt was on takeoff from a dirt strip with a fully loaded ag acft, for an aerial application flt. After lifting off prematurely, the acft settled to the rwy. The left wing struck a post skidding the acft to the left. After crossing an irrigation…NTSB FTW85FRD03Accident · Minor injuriesFinal reportAdvanced Technology Predator 480 · Welsh, LAThe acft impacted the terrain in an uncontrolled descent during the initial takeoff climb. The plt reported that after takeoff at an alt of aprx 20 ft AGL, the acft rolled 20 to 25 degs to the right. After correcting for the roll, the plt stated, the acft…NTSB MIA82DA183Accident · No injuriesFinal reportPiper PA-36-375 · Astatula, FLThe plt stated the acft failed to become airborne at the usual takeoff point & did not climb when forced into the air. The acft then settled into soft sand.