NTSB investigations: Lycoming 0-320 series, 2002
37 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Loss of control - on ground/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 | 50 |
|---|---|
| 1983 | 46 |
| 1984 | 41 |
| 1985 | 31 |
| 1986 | 40 |
| 1987 | 46 |
| 1988 | 37 |
| 1989 | 28 |
| 1990 | 36 |
| 1991 | 34 |
| 1992 | 23 |
| 1993 | 32 |
| 1994 | 26 |
| 1995 | 32 |
| 1996 | 24 |
| 1997 | 43 |
| 1998 | 42 |
| 1999 | 28 |
| 2000 | 38 |
| 2001 | 43 |
| 2002 | 37 |
| 2003 | 35 |
| 2004 | 36 |
| 2005 | 39 |
| 2006 | 41 |
| 2007 | 22 |
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\") = 2002
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')
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\" = 260))
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") = 2002
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')
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" = 260))
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 NYC03LA047Accident · No injuriesLimited investigationFinal reportPiper PA-18A 150 · Blairstown, NJThe pilot's failure to maintain directional control during the landing roll.NTSB ATL03LA024Accident · No injuriesLimited investigationFinal reportCessna 172N · Cartersville, GAThe student pilot's failure to maintain directional control, during the landing roll resulted in the on ground collision with a ravine.NTSB LAX03LA039Accident · No injuriesLimited investigationFinal reportCessna 172N · Hollister, CAthe pilot's failure to maintain directional control of the airplane.NTSB LAX03LA023Accident · No injuriesLimited investigationFinal reportCessna 172M · Mesquite, NVThe pilot's failure to maintain directional control during takeoff. A contributing factor was the ditch.NTSB NYC03LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Morristown, NJThe student pilot's failure to maintain directional control during takeoff.NTSB ATL03LA005Accident · No injuriesLimited investigationFinal reportCessna 172 · Opa Locka, FLThe pilot' inadequate evaluation of weather information, and the selection of the wrong runway that resulted in an attempted takeoff with a tailwind and the subsequent loss of control during takeoff.NTSB IAD02LA096Accident · No injuriesLimited investigationFinal reportCessna 172N · Bumpass, VAThe pilot's failure to maintain directional control during the landing. A factor was the narrow runway width.NTSB NYC02LA189Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Titusville, PAThe student pilot's failure to maintain directional control during the landing roll.NTSB LAX02LA271Accident · No injuriesLimited investigationFinal reportMooney M20 · Sierraville, CAthe pilot's decision to attempt takeoff in crosswind conditions that likely exceeded the capability of the airplane, and, his subsequent failure to maintain the airplane's proper alignment over the runway. Also causal was the pilot's premature liftoff and…NTSB LAX02LA265Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-160 · Ruth, CAThe pilot's inadequate compensation for the wind conditions and failure to maintain control.NTSB MIA02LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Tarboro, NCThe failure of the solo student to maintain directional control of the airplane during the takeoff roll/run which resulted in the airplane veering off the runway and impacting trees, incurring substantial damage.NTSB ATL02LA151Accident · No injuriesLimited investigationFinal reportCessna 172M · Dahlonega, GAThe pilot's improper recovery from a bounced landing and failure to maintain directional control resulting in the airplane going off the left side of the runway and colliding with a ditch.NTSB ANC02LA085Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Port Alsworth, AKThe pilot's inadequate compensation for wind conditions during the landing roll, resulting in a nose over. A factor associated with the accident was a wind gust.NTSB DEN02LA077Accident · No injuriesLimited investigationFinal reportCessna 150L · Hurricane, UTpilot's failure to maintain directional control during landing roll, resulting in an inadvertent ground loop.NTSB CHI02CA211Accident · No injuriesData collectionFinal reportCessna 172N · Spearfish, SDThe probable cause of this accident was the pilot's failure to maintain directional control of the airplane during the takeoff roll. Differences in control forces and aircraft handling due to initiating the takeoff without fully retracting the flaps is a…NTSB NYC02LA137Accident · No injuriesLimited investigationFinal reportCessna 177 · Millville, NJThe pilot's improper bounced landing recovery. A factor was the dark night conditions.NTSB IAD02LA066Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Providence, RIThe student pilot's failure to maintain directional control during the landing.NTSB NYC02FA126Accident · 1 fatalField investigationFinal reportPiper PA-18-150 · Farmingdale, NJThe pilot's failure to maintain directional control during takeoff.NTSB NYC02LA121Accident · No injuriesLimited investigationFinal reportCessna 172N · Lynchburg, VAThe pilot's failure to maintain control of the airplane, a factor was the tailwind.NTSB MIA02LA117Accident · No injuriesLimited investigationFinal reportCessna 172N · Marietta, GAthe pilot's failure to maintain directional control during the takeoff roll, which resulted in the airplane departing the left side of the runway, impacting with a gully and nosing over.NTSB IAD02LA061Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Rutland, VTThe pilot's failure to maintain directional control during the takeoff attempt.NTSB LAX02LA199Accident · No injuriesLimited investigationFinal reportCessna 172M · Saint Johns, AZthe pilot's inadequate compensation for wind conditions resulting in a loss of directional control and collision with terrain. Related factors were the wind gusts, crosswind and soft terrain.NTSB ANC02LA048Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Fairbanks, AKThe student pilot's failure to maintain directional control of the airplane during the landing roll, which resulted in the right wing striking the ground.NTSB ANC02LA047Accident · No injuriesLimited investigationFinal reportCessna 172 · Bethel, AKThe pilot's failure to maintain directional control of the airplane during the landing roll resulting in the right wing striking the runway.NTSB CHI02LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Appleton, WIThe pilots failure to maintain directional control of the airplane during the takeoff roll resulting in the subsequent impact with terrain.NTSB ATL02LA073Accident · No injuriesLimited investigationFinal reportCessna 172P · Pensacola, FLThe pilot's inadequate compensation for a crosswind and his failure to maintain directional control during the landing roll. Contributing to the accident was the pilot's decision to land with a tailwind.NTSB NYC02LA080Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Belmar, NJThe student pilot's failure to maintain runway alignment during landing. A factor in the accident was the winds.NTSB LAX02LA122Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Vacaville, CAThe pilot's failure to maintain directional control.NTSB IAD02LA038Accident · No injuriesLimited investigationFinal reportCessna 172P · Ocean City, NJThe pilot's inadequate compensation for wind and his failure to maintain directional control.NTSB SEA02LA047Accident · No injuriesLimited investigationFinal reportCessna 172N · Longmont, COThe student pilot's failure to maintain directional control during landing. Factors included the student pilot's lack of experience, an icy runway, and a mound of snow adjacent to the runway.NTSB NYC02LA066Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Atlantic City, NJThe pilot's failure to obtain a proper touchdown point.NTSB DEN02LA025Accident · No injuriesLimited investigationFinal reportCessna 172N · Durango, COthe pilot's failure to maintain directional control during the landing roll. Contributing factors were the crosswind and the pilot's fatigue from lack of sleep.NTSB LAX02LA080Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-1 · San Diego, CAThe pilot failed to maintain directional control after encountering a gust of wind during the landing roll. Factors were the unexpected wind gusts and the soft terrain adjacent to the runway.NTSB CHI02LA076Accident · No injuriesLimited investigationFinal reportCessna 172N · Ottumwa, IAthe student pilot failed to maintain directional control during takeoff. A contributing factor was the snowbank.NTSB LAX02LA070Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Payson, AZFailure of the pilot to maintain directional control of the airplane. A contributing factor was the premature raising of the flaps.NTSB CHI02LA068Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Iowa Falls, IAThe pilot's inadequate compensation for the crosswind condition and the subsequent failure to maintain control of the airplane. Factors associated with the accident were the crosswind and the rough terrain encountered.NTSB ATL02LA039Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe pilots failure to maintain directional control during landing roll that resulted in a collision with an airport sign. Factors were wet runway surface and wind gust.