NTSB investigations: Lycoming O&VO-360 series, 1983, TX
9 cases on aircraft whose registry engine model is Lycoming O&VO-360 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 | 14 |
|---|---|
| 1965 | 14 |
| 1966 | 14 |
| 1967 | 18 |
| 1968 | 14 |
| 1969 | 7 |
| 1970 | 12 |
| 1971 | 8 |
| 1972 | 9 |
| 1973 | 5 |
| 1974 | 7 |
| 1975 | 7 |
| 1976 | 7 |
| 1977 | 10 |
| 1978 | 9 |
| 1979 | 3 |
| 1980 | 7 |
| 1981 | 3 |
| 1982 | 9 |
| 1983 | 9 |
| 1984 | 4 |
| 1985 | 7 |
| 1986 | 4 |
| 1987 | 5 |
| 1988 | 4 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 5 |
| 1992 | 4 |
| 1993 | 4 |
| 1994 | 5 |
| 1995 | 5 |
| 1996 | 3 |
| 1997 | 4 |
| 1998 | 3 |
| 1999 | 3 |
| 2000 | 4 |
| 2001 | 4 |
| 2002 | 3 |
| 2003 | 5 |
| 2004 | 4 |
| 2005 | 2 |
| 2006 | 3 |
| 2007 | 6 |
| 2008 | 5 |
| 2009 | 3 |
| 2010 | 3 |
| 2011 | 4 |
| 2012 | 2 |
| 2014 | 3 |
| 2015 | 3 |
| 2016 | 7 |
| 2017 | 3 |
| 2018 | 6 |
| 2019 | 3 |
| 2020 | 2 |
| 2021 | 7 |
| 2022 | 1 |
| 2023 | 8 |
| 2024 | 3 |
| 2025 | 2 |
| 2026 | 5 |
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 year(c.\"eventDate\") = 1983
AND c.\"eventStateOrRegion\" = 'TX' 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 ('41514'))
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") = 1983
AND c."eventStateOrRegion" = 'TX' 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 ('41514'))
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 FTW84LA046Accident · No injuriesLimited investigationFinal reportMooney M20C · Mcgregor, TXIn order to take off on rwy 35, acft must utilize rwy 4/22 enroute from the arpt ramp. As the Mooney taxied onto rwy 4/22 it was struck by the pitts rolling out on rwy 22. While on base leg, the plt of the pitts saw the Mooney taxiing toward rwy 4/22 &…NTSB FTW84LA002Accident · No injuriesLimited investigationFinal reportGrumman American AA-5B · Midland, TXThe acft stalled and landed hard off the side of the rwy during a forced landing. The plt said the engine was misfiring during initial climb at 150-200 ft AGL. He tried to land on the remaining rwy. The plt later said he thought the power loss was due to…NTSB FTW83LA380Accident · No injuriesLimited investigationFinal reportMooney M-20C · Midland, TXThe acft collided with a fence post during taxi for takeoff. The acft was allowed to drift right of the center of the taxiway. The collision veered the acft to the right and damaged the wing. The accident occurred at dusk.NTSB FTW83LA376Accident · Minor injuriesLimited investigationFinal reportBeech C23 · Iowa Park, TXDuring a landing, the acft floated about 1/3 to 1/2 of the way down the rwy before touching down. The plt was unable to stop on the remaining rwy & the acft continued off the end & hit a ditch. An exam of the brakes revealed two discrepancies. The temp was…NTSB FTW83LA337Accident · No injuriesLimited investigationFinal reportBeech C23 · Longview, TXThe acft crashed during a forced landing after the engine quit on the downwwind leg of the traffic pattern. The flt had taken off shortly before with one tank almost full and one almost empty. The fuel selector valve was found in the 'off' position after the…NTSB FTW83FA254Accident · 5 fatalField investigationFinal reportPiper PA-28-180 · Haskell, TXThe acft crashed while on a flt in an area where thunderstorm warnings were in effect. There were no known witnesses to the actual crash, but 2 or 3 local residents heard an acft eng at about the estimated time of the accident. One resident about 1/4 mi from…NTSB FTW83LA215Accident · 2 fatalLimited investigationFinal reportCessna 177B · Port Aransas, TXDuring a wx briefing, the non-instrument rated plt was told to expect no significant en route wx, but was advised of lower ceilings along the coastline, later that night. There were no records of en route wx briefings. When the acft was about 40 mi northwest…NTSB FTW83LA091Accident · No injuriesLimited investigationFinal reportGrumman American AA-5B · Nacogdoches, TXDuring arrival, the acft was high on final approach. The plt elected to continue the landing with full flaps, but after touchdown, he was unable to stop on the remaining runway. After overrunning the runway, the acft nosed over in a 10 ft drainage ditch.NTSB FTW83LA077Accident · No injuriesLimited investigationFinal reportCessna 172RG · San Angelo, TXThe acft had reached an alt of 3500 ft MSL when the engine started to lose power. The pilot turned back toward his departure airport. The engine then lost all power and the pilot elected to land in a plowed field with landing gear down. When the acft touched…