NTSB investigations: Lycoming I0360 series, 1991
27 cases on aircraft whose registry engine model is Lycoming I0360 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
| 1964 | 28 |
|---|---|
| 1965 | 40 |
| 1966 | 58 |
| 1967 | 89 |
| 1968 | 73 |
| 1969 | 72 |
| 1970 | 80 |
| 1971 | 65 |
| 1972 | 67 |
| 1973 | 76 |
| 1974 | 68 |
| 1975 | 81 |
| 1976 | 76 |
| 1977 | 96 |
| 1978 | 110 |
| 1979 | 70 |
| 1980 | 70 |
| 1981 | 78 |
| 1982 | 51 |
| 1983 | 57 |
| 1984 | 47 |
| 1985 | 33 |
| 1986 | 44 |
| 1987 | 36 |
| 1988 | 33 |
| 1989 | 33 |
| 1990 | 29 |
| 1991 | 27 |
| 1992 | 31 |
| 1993 | 26 |
| 1994 | 27 |
| 1995 | 26 |
| 1996 | 25 |
| 1997 | 22 |
| 1998 | 30 |
| 1999 | 37 |
| 2000 | 42 |
| 2001 | 59 |
| 2002 | 53 |
| 2003 | 51 |
| 2004 | 58 |
| 2005 | 37 |
| 2006 | 38 |
| 2007 | 46 |
| 2008 | 29 |
| 2009 | 28 |
| 2010 | 37 |
| 2011 | 27 |
| 2012 | 47 |
| 2013 | 35 |
| 2014 | 31 |
| 2015 | 35 |
| 2016 | 42 |
| 2017 | 31 |
| 2018 | 30 |
| 2019 | 43 |
| 2020 | 28 |
| 2021 | 22 |
| 2022 | 26 |
| 2023 | 22 |
| 2024 | 29 |
| 2025 | 25 |
| 2026 | 20 |
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 year(c.\"eventDate\") = 1991
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41515'))
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 year(c."eventDate") = 1991
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41515'))
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 NYC92LA040Accident · No injuriesLimited investigationFinal reportPiper PA28R-200 · Piqua, OHThe pilot allowed the airplane to get too low on short final and struck the terrain short of the runway. Factors in the accident were the proper glide path was not maintained, resulting in the intended touchdown point not being attained.NTSB CHI92LA040Accident · No injuriesLimited investigationFinal reportMooney M20J · Morris, MNFailure to maintain proper glidepath. A factor related to the accident is the failure to perform remedial action, the dark night, and the snow shower in progress at the time.NTSB CHI92LA036Accident · Minor injuriesLimited investigationFinal reportPiper PA28R-200 · Lakeville, MNThe failure of both pilots to maintain visual separation from each other. Contributing factors to this accident were an inadequate visual lookout by both pilots and the pilot-in-command's failure to follow procedures and directives.NTSB BFO92LA008Accident · No injuriesLimited investigationFinal reportMooney 20F · Basye, VAThe pilot misjudged the altitude and distance to the runway. Factors were the gusty weather conditions and the pilot's delay in executing a go around.NTSB MIA92LA016Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Daytona Beach, FLThe failure of the pilot in command of N136AT to maintain clearance from N3110R while diverting her attention to close her door during taxi to takeoff.NTSB SEA92LA005Accident · No injuriesLimited investigationFinal reportHughes 269B · Hillsboro, ORThe failure to maintain rotor RPM. Factors include inadequate preflight planning, overconfidence in aircraft's ability, and non-suitable terrain.NTSB CHI92LA004Accident · No injuriesLimited investigationFinal reportBeech 95 · Elkhart, INThe inadequate amount of hydraulic fluid present in the normal brake system.NTSB CHI91LA304Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Atchison, KSDelayed remedial action by the pilot in command. Factors related to the accident are a misjudged approach by the pilot in command, and complacency on the part of the FAA inspector.NTSB CHI91LA287Accident · Minor injuriesLimited investigationFinal reportBeech A23 · Lake Elmo, MNA loss of engine power for undetermined reasons. A factor contributing to the accident was the unsuitable terrain on which the pilot had to land.NTSB NYC91LA233Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200 · Easton, PAAn overrun after the pilot-in-command landed long on a short, wet runway. A factor related to the accident was the failure of the pilot to make a go-around.NTSB LAX91LA382Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Redwood City, CAThe fatigue failure of the number two connecting rod and rod cap due to an engine overspeed condition which the rods and rod caps were exposed at some undetermined historical point.NTSB CHI91LA281Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Newark, ILThe pilot's poor inflight planning/decision making. A related factor was: the wet, slippery condition of the grass runway.NTSB NYC91LA219Accident · Serious injuriesLimited investigationFinal reportMooney M20F · Meadville, PAEngine failure resulting from the fatigue failure of the number 2 cylinder exhaust valve and the subsequent forced landing at night. A factor related to the accident was the restricted visibility.NTSB SEA91LA217Accident · Serious injuriesLimited investigationFinal reportBeech B24R · Shady Cove, ORImproper re-installation of an oil line by maintenance personnel, which resulted in an oil leak from a loose line and subsequent seizure of the engine. Uneven terrain in the emergency landing area was a related factor.NTSB LAX91LA314Accident · No injuriesLimited investigationFinal reportPiper PA28R-200 · So. Lake Tahoe, CAEngine failue due to the failure of the crankshaft resulting from failure induced by a non-metallic inclusion in the shaft.NTSB SEA91LA155Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R · Milford, UTFuel exhaustion, and the pilot's misjudgment of proper descent rate. Factors include inadequate preflight planning, poor in-flight decision, becoming lost/disoriented, and a fence.NTSB SEA91LA137Accident · Minor injuriesLimited investigationFinal reportHughes 269B · Warrenton, ORThe pilot failed to maintain proper rotor speed during a simulated autorotation.NTSB SEA91LA130Accident · Minor injuriesLimited investigationFinal reportHughes 269A-1 · Canby, ORA hard landing after an undetermined loss of power. Factors include an excessive emergency descent rate.NTSB CHI91LA186Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Pulaski, WIThe pilot's failure to select a proper touchdown point. A factor in the accident was inadequate runway maintenance by airport personnel.NTSB CHI91LA179Accident · No injuriesLimited investigationFinal reportLake LA-4-200 · Battle Creek, MIAircraft control by the dual student was not maintained, remedial action by the CFI was delayed, which resulted in a stall/mush. A factor related to the accident was rough water caused by a power boat wake.NTSB NYC91FA140Accident · 1 fatalField investigationFinal reportPiper PA-28-151 · Shelburne, VTPremature lift-off by the pilot, which resulted in a subsequent stall/mush and collision with trees. Factors related to the accident were: the pilot's inadequate preflight planning/preparation, and the unfavorable wind condition.NTSB SEA91LA104Accident · No injuriesLimited investigationFinal reportHughes 269B · Grand Ronde, ORThe pilot inadvertently interfered with the controls.NTSB CHI91LA156Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201 · Grand Forks, NDThe pilot's failure to maintain directional control during the landing roll. Related to the accident was the pilot's lack of total experience.NTSB CHI91LA131Accident · No injuriesLimited investigationFinal reportEnstrom F-28A · Grand Ledge, MIThe student's failure to maintain a proper altitude and clearance from the terrain along with the cfi's failure to adequately supervise the student's actions. A factor contributing to the accident was the inadequate visual lookout available due to the night…NTSB MIA91LA112Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Sanford, FLExcessive flare by the dual student during the forced landing following a simulated engine failure shortly after takeoff. Also, failure of the student to maintain vs, and failure of the CFI to take remedial action.NTSB FTW91LA041Accident · No injuriesLimited investigationFinal reportHughes 269C · Knowles, OKThe pilot's failure to maintain a proper descent rate during the maneuver and his delay in initiating the go-around.NTSB CHI91LA085Accident · No injuriesLimited investigationFinal reportMooney M2OE · Rush Hill, MOThe pilot's failure to refuel the airplane. A factor related to the accident was unsuitable terrain.