NTSB investigations: Lycoming O&VO-360 series, 1982, 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\") = 1982
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") = 1982
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 FTW82FA382Accident · 3 fatalField investigationFinal reportPiper PA-24-260 · Paris, TXThe PA-24 had departed rwy 17 at cox field & was climbing at the time of the collision. The plt had reported his intended departure on UNICOM. The AA5B had reported 5 mi sw of the arpt descending through 5,000 ft. for landing. The head-on collision occurred…NTSB FTW82DA365Accident · Serious injuriesFinal reportBeech 23 · Fort Worth, TXThe plt stated the stall warning sounded every time he tried to climb & the acft settled into trees. The acft was 7 lbs over max gross weight requiring 2,369 ft to clear a 50 ft obstacle.NTSB FTW82DA362Accident · No injuriesFinal reportPiper PA-28-180 · Weslaco, TXThe plt overshot an approach to rwy 13 & went around. The crosswind leg was extended to give the plt more room. The plt turned on final & lined up on a street paralleling the rwy. Just prior to touchdown the plt saw the "x" painted on the street & executed a…NTSB FTW82FRG34Accident · 1 fatalFinal reportBeech C23 · Port Aransas, TXWitnesses observed the acft on a high final approach to rwy 12 when a go-around was initiated over the rwy at approximately 150 to 200 ft AGL. The acft started a steep banked right turn to a downwind position. The bank continued and the acft descended rapidly…NTSB FTW82DA308Accident · No injuriesFinal reportBeech C23 · Roaring Springs, TXDuring a landing in calm wind conditions, the aircraft continued off the end of the runway and struck a fence. The pilot stated that he had trouble lowering the flaps and that the brakes would not operate properly. During a subsequent inspection, the brakes…NTSB FTW82FPD17Accident · Serious injuriesFinal reportMooney M20 · Abilene, TXAt about 50-75 ft AGL after takeoff the eng quit. Both tanks contained adequate fuel & no eng malfunctions were found.NTSB FTW82DA193Accident · No injuriesFinal reportPitts Special S-1S · Huntsville, TXThe pilot reported that during flight at 1500 ft AGL, there was a violent explosive failure of the engine and black smoke entered the cockpit. He elected to land between cars on an interstate highway. He cleared over one car, but the driver of the next car…NTSB FTW82FRG28Accident · Serious injuriesFinal reportMooney M20A · San Antonio, TXDuring arrival, the pilot entered the traffic pattern for a landing on runway 30 with a 7 knot tailwind. On final approach, he was not satisfied with his pattern and elected to go-around. During the go-around and climb, a map and checklist fell into the…NTSB FTW82FA152Accident · 2 fatalField investigationFinal reportBeech B23 · Roanoke, TXWitnesses reported that the aircraft appeared to takeoff and climb normally until it reached an altitude of about 100 ft AGL. It then pitched up abruptly to about a 70 deg nose high attitude. After the pitch-up, the aircraft climbed to about 175 to 200 ft…