NTSB investigations: Lycoming 0-320 series, 1999, TX
13 cases on aircraft whose registry engine model is Lycoming 0-320 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 | 25 |
| 1966 | 30 |
| 1967 | 27 |
| 1968 | 34 |
| 1969 | 33 |
| 1970 | 30 |
| 1971 | 16 |
| 1972 | 24 |
| 1973 | 14 |
| 1974 | 20 |
| 1975 | 18 |
| 1976 | 26 |
| 1977 | 23 |
| 1978 | 23 |
| 1979 | 24 |
| 1980 | 19 |
| 1981 | 22 |
| 1982 | 25 |
| 1983 | 14 |
| 1984 | 11 |
| 1985 | 11 |
| 1986 | 13 |
| 1987 | 6 |
| 1988 | 7 |
| 1989 | 7 |
| 1990 | 8 |
| 1991 | 10 |
| 1992 | 11 |
| 1993 | 16 |
| 1994 | 4 |
| 1995 | 8 |
| 1996 | 13 |
| 1997 | 13 |
| 1998 | 10 |
| 1999 | 13 |
| 2000 | 11 |
| 2001 | 9 |
| 2002 | 17 |
| 2003 | 20 |
| 2004 | 14 |
| 2005 | 10 |
| 2006 | 14 |
| 2007 | 7 |
| 2008 | 13 |
| 2009 | 10 |
| 2010 | 11 |
| 2011 | 12 |
| 2012 | 7 |
| 2013 | 7 |
| 2014 | 10 |
| 2015 | 11 |
| 2016 | 8 |
| 2017 | 7 |
| 2018 | 6 |
| 2019 | 6 |
| 2020 | 13 |
| 2021 | 9 |
| 2022 | 11 |
| 2023 | 10 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 11 |
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\") = 1999
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 ('41508'))
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") = 1999
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 ('41508'))
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 FTW00LA042Accident · No injuriesLimited investigationFinal reportKing Lancair 235/320 · Sterling City, TXThe fatigue fracture of the propeller attaching bolts, due to improper torque during the installation of the propeller by other maintenance personnel. A factor was the lack of suitable terrain for the forced landing.NTSB FTW99LA269Accident · No injuriesLimited investigationFinal reportCessna 172N · Longview, TXThe pilot's improper touchdown technique, which resulted in the airplane porpoising.NTSB FTW99LA250Accident · No injuriesLimited investigationFinal reportCessna 177 · Austin, TXFuel exhaustion as a result of the pilot's failure to refuel the airplane.NTSB FTW99LA200Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Alvaredo, TXThe student pilot's failure to maintain a proper glidepath during his short-field approach.NTSB FTW99LA181Accident · Minor injuriesLimited investigationFinal reportPitts Special S-1C · Temple, TXThe loss of engine power due to fuel starvation, as a result of fuel moving away from the fuel supply outlets during maneuvering with a low fuel level, and the pilot's failure to maintain clearance with the power lines during the ensuing forced landing.NTSB FTW99FA153Accident · 2 fatalField investigationFinal reportMooney M20B · Mesquite, TXThe failure by both pilots to maintain visual lookout. A factor was the inadequate radio communications maintained by both pilots while in the traffic pattern.NTSB FTW99LA146Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Palacios, TXThe pilot's failure to maintain clearance with terrain. A factor was the high vegetation.NTSB FTW99LA141Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Roanoke, TXThe partial loss of engine power for an undetermined reason. A factor was the lack of suitable terrain for the forced landing.NTSB FTW99LA133Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Lancaster, TXThe pilot's inadequate preflight inspection which resulted in fuel exhaustion and the subsequent total loss of engine power.NTSB FTW99LA118Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Cleburne, TXThe pilot's improper flare which resulted in a hard landing and his improper recovery procedures from a bounced landing.NTSB FTW99LA114Accident · No injuriesLimited investigationFinal reportCessna 172N · Cleburne, TXThe pilot's failure to maintain adequate altitude/ clearance from the wires.NTSB FTW99LA108Accident · No injuriesLimited investigationFinal reportCessna 172M · Midlothian, TXThe pilot's failure to maintain clearance with the powerlines. Factors were the low ceilings and the dusk light illumination.NTSB FTW99LA090Accident · No injuriesLimited investigationFinal reportCessna 172N · Orange, TXThe student pilot's failure to maintain directional control during landing touchdown. A factor was the muddy drainage ditch.