NTSB investigations: Lycoming I0360 SER A&C
22 cases on aircraft whose registry engine model is Lycoming I0360 SER A&C, 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 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 1995 | 2 |
| 1999 | 1 |
| 2001 | 3 |
| 2002 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 2 |
| 2006 | 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 ('41511')
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 ('41511')
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 MIA08CA019Accident · Minor injuriesData collectionFinal reportLake LA-4-200 · Jacksonville, FLThe pilot's failure to maintain altitude while maneuvering over water. Contributing to the accident was glassy water conditions.NTSB LAX06LA155Accident · Serious injuriesLimited investigationFinal reportPartenavia P68 · Kaunakakai, HIthe pilot's failure to attain a proper climb rate and to maintain adequate clearance from the terrain during the initial climb in dark night conditions, which resulted in an in-flight collision with terrain.NTSB LAX06FA059Accident · 1 fatalField investigationFinal reportCessna 172S · Hana, HICollision with mountainous terrain for undetermined reasons.NTSB LAX05CA137Accident · No injuriesData collectionFinal reportCessna 172S · Gallup, NMthe pilot's premature liftoff and inadequate remedial action, which resulted in the airplane inadvertently recontacting the runway.NTSB ATL05CA030Accident · No injuriesData collectionFinal reportMooney M20J · Statesville, NCthe flight instructors improper use of the flight controls on rotation during a short field takeoff resulting in the airplane becoming airborne, stall, and collision with the ground. A factor in the accident was the instructors failure to brief procedures for…NTSB LAX04LA054Accident · No injuriesLimited investigationFinal reportCessna 172S · Wikieup, AZThe pilot's selection of an en route altitude that did not provide adequate terrain clearance, and resulted in the in-flight collision with terrain. The rising terrain and the blind/box canyon were contributing factors.NTSB CHI02LA154Accident · No injuriesLimited investigationFinal reportMooney M20J · Minneapolis, MNThe pilot's failure to maintain control of the aircraft during an aborted landing.NTSB DEN01FA151Accident · 2 fatalField investigationFinal reportAviat A-1 · Montrose, COthe pilot's intentional abrupt maneuver immediately after takeoff and the subsequent loss of aircraft control. Contributing factors were high density altitude weather conditions, and the airplane improper weight and balance.NTSB NYC01LA191Accident · No injuriesLimited investigationFinal reportMooney M20J · East Greenwich, NJThe pilot's premature liftoff which resulted in an inadvertent stall.NTSB IAD01FA038Accident · 1 fatalField investigationFinal reportPiper PA-28-RT201 · Manassas, VAThe pilot's spatial disorientation due to a night visual illusion. A factor was the dark night condition.NTSB MIA99LA178Accident · No injuriesLimited investigationFinal reportLake LA-4-200 · Charlotte, NCThe pilot misjudged the flare during the landing.NTSB SEA96FA024Accident · 2 fatalField investigationFinal reportBeech C24R · Bozeman, MTfailure of the pilot to follow the specified approach track (proper IFR procedure), and his associated failure to maintain altitude or clearance from mountainous terrain. Factors relating to the accident were: the pilot's failure to abide by the aircraft…NTSB NYC95LA070Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201 · Wilmington, OHThe pilot's failure to maintain adequate terrain clearance during a go around, which resulted in an inflight collision with a snowbank. A factor is the pilot's delay in initiating a go around.NTSB CHI93LA285Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Crookston, MNThe pilot in command's delayed in-flight decision. A factor to the accident is the pilot in command's failure to attain a proper touchdown point.NTSB FTW90LA112Accident · No injuriesLimited investigationFinal reportMooney M-20F · Aledo, TXInadequate preflight planning/preparation, in as much as the performance data was not used by the pilot in command. Factors were the high density altitude, inadequate airspeed, and premature liftoff.NTSB BFO89FA003Accident · 1 fatalField investigationFinal reportPiper PA-28RT-201 · Frederick, MDNonsubmittedNTSB SEA85LA161Accident · No injuriesLimited investigationFinal reportMooney M20-F · Salem, ORThe acft was substantially damaged during an inadvertant gear-up landing. Inspection of the acft revealed the landing gear circuit breaker was popped. When functionally tested, the landing gear operated normally. The gear warning horn was found to be…NTSB LAX84LA336Accident · No injuriesLimited investigationFinal reportStarduster II · Half Moon Bay, CAThe plt said he encountered wind shear at 700 ft AGL, lost control & landed in a field. The plt subsequently walked to a friend's house next to the field to report the occurrence.NTSB DEN84LA029Accident · No injuriesLimited investigationFinal reportPiper PA-18-180 · Colorado Spgs, COThe Piper PA-18, N3594P, was being used to tow a burkhart grob flugzeugbau G103 twin astir, N4246L. At 0950 MST, the wind was reported from 310 deg at 9 KTS. Since the terrain sloped downhill to the south, rwy 17R (covered with hard packed snow) was being…NTSB ATL83LA030Accident · No injuriesLimited investigationFinal reportMooney M20F · Talladega, ALPilot forgot to extend landing gear.NTSB NYC82DA213Accident · No injuriesFinal reportMooney M20J · Matawan, NJThe pilot stated that he had never been at this airport before. During arrival, he landed on runway 27 toward the setting sun with a crosswind from the left. He stated that he touched down firmly on the first 1/3 of the runway, then the aircraft floated…NTSB FTW82DA082Accident · No injuriesFinal reportStarduster II · Taylor, TXDuring a slow roll to the left, the aircraft developed a high rate of descent. The roll was completed just before ground impact which demolished the aircraft.