NTSB investigations: Lycoming O&VO-360 series, 2005
10 cases on aircraft whose registry engine model is Lycoming O&VO-360 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 | 9 |
|---|---|
| 1983 | 6 |
| 1984 | 9 |
| 1985 | 12 |
| 1986 | 7 |
| 1987 | 11 |
| 1988 | 8 |
| 1989 | 8 |
| 1990 | 8 |
| 1991 | 2 |
| 1992 | 9 |
| 1993 | 9 |
| 1994 | 7 |
| 1995 | 7 |
| 1996 | 2 |
| 1997 | 4 |
| 1998 | 9 |
| 1999 | 3 |
| 2000 | 7 |
| 2001 | 9 |
| 2002 | 8 |
| 2003 | 9 |
| 2004 | 9 |
| 2005 | 10 |
| 2006 | 9 |
| 2007 | 9 |
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\") = 2005
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')
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") = 2005
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')
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 DFW06CA070Accident · No injuriesData collectionFinal reportBeech C23 · Eureka Springs, ARThe pilot's failure to maintain directional control while landing and his delay in aborting the landing.NTSB CHI06CA035Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Imperial, NEThe pilot not maintaining airplane control during the takeoff.NTSB MIA05CA151Accident · No injuriesData collectionFinal reportCessna 177B · Olive Branch, MSThe failure of the pilot to maintain directional control during the landing roll resulting in an on ground collision with a runway light and subsequent collapse of the nose landing gear.NTSB DEN05CA120Accident · No injuriesData collectionFinal reportCessna 172RG · Fort Collins, COthe pilot's failure to maintain directional control. Contributing factors were the crosswind, the pilot's failure to compensate for the wind conditions --- allowing the airplane to touch down without being properly aligned with the runway --- and the flight…NTSB CHI05CA208Accident · No injuriesData collectionFinal reportPiper PA-28-181 · Willard, MOThe airplane overran the runway and hit a utility pole due to the pilot's delayed decision making and his failure to execute a go-around. Contributing factors included the exessive airspeed during the final approach, the high density altitude, the…NTSB ANC05CA114Accident · No injuriesData collectionFinal reportCessna 170B · Fairbanks, AKThe pilot's inadequate compensation for the gusty wind conditions, which resulted is a loss of directional control during landing. A factor associated with the accident was the gusty wind condition.NTSB LAX05LA247Accident · Minor injuriesLimited investigationFinal reportBeech B23 · Fallbrook, CAThe pilot's failure to maintain directional control during the landing rollout.NTSB SEA05CA135Accident · No injuriesData collectionFinal reportCessna 170B · Laurel, MTThe flight instructor's failure to maintain directional control during the landing roll, which resulted in an inadvertent ground loop. A contributing factor was the flight instructor's diverted attention to talking with the student.NTSB CHI05LA158Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Allegan, MIThe inadequate aircraft control by the PA-28-180 pilot while the airplane was stopped.NTSB CHI05CA089Accident · Serious injuriesData collectionFinal reportFranz RV-6 · Howell, MIThe pilot's failure to maintain directional control during the landing rollout which resulted in the aircraft departing the runway pavement and nosing over. An additional cause was the pilot's inadequate compensation for the crosswind condition. Contributing…