NTSB investigations: Lycoming 0-320 series, IL
13 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Hard landing”. 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
| 1983 | 1 |
|---|---|
| 1986 | 2 |
| 1990 | 1 |
| 1996 | 3 |
| 1997 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 2 |
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 c.\"eventStateOrRegion\" = 'IL' 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')
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\" = 200))
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 c."eventStateOrRegion" = 'IL' 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')
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" = 200))
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 CHI06CA227Accident · No injuriesData collectionFinal reportCessna 172M · Cahokia, ILThe pilot's inadequate flare. A factor was the night light conditions.NTSB CHI06CA185Accident · Minor injuriesData collectionFinal reportCessna 172K · Sullivan, ILThe pilot's misjudged flare and his improper recovery from the bounced landing which led to a loss of directional control and subsequent collision with crops and the ground.NTSB CHI05CA253Accident · No injuriesData collectionFinal reportRobinson R22 Beta · Rockton, ILThe pilot's excessive descent rate on approach for landing and the settling with power condition subsequently encountered. Contributing factors were the pilot's failure to reduce the descent rate prior to entering the settling with power condition and his…NTSB CHI04LA063Accident · No injuriesLimited investigationFinal reportPiper PA 28-161 · Lansing, ILThe improper flare by the pilot due to his diverted attention during landing. Factors were the pilot's failure to execute a go-around, the overload of the right main landing gear, and the snowbank.NTSB CHI03LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Carbondale, ILThe pilot failed to properly recover from a bounced landing which resulted in the airplane porpoising.NTSB CHI97LA111Accident · No injuriesLimited investigationFinal reportCessna 177 · Rantoul, ILthe student pilot's improper flare and improper recovery from a bounced landing.NTSB CHI97LA026Accident · No injuriesLimited investigationFinal reportCessna 172P · Waukegan, ILthe pilot's improper recovery from a bounced landing. A factor was the pilot's misjudging the flare.NTSB CHI96LA326Accident · No injuriesLimited investigationFinal reportCessna 172 · Chicago, ILthe pilot's improper flare and improper recovery from a bounced landing. A factor relating to the accident was: the pilot's lack of experience (or lack of training) in recovery from bounced landings.NTSB CHI96LA097Accident · No injuriesLimited investigationFinal reportCessna 172P · West Chicago, ILthe student pilot's misjudging the flare. A factor was the gusts.NTSB CHI90LA122Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, ILThe student's improper flare, improper recovery from a bounced landing, and failure to maintain directional control. The crosswind was a related factor.NTSB CHI86LA116Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Seneca, ILThe plt was landing on a 2300 ft rwy with a 80 degree x-wind. The acft bounced hard on touchdown and the plt attempted a go-around with 25 degrees of flaps extended. The airspeed was deteriorating so the plt elected to re-land. During the roll-out the acft…NTSB CHI86LA112Accident · No injuriesLimited investigationFinal reportCessna 177 · Lacon, ILThe pilot stated he was maintaining a steep approach angle to clear trees at the approach end of the 2200 ft. runway. He flared late, landing hard and damaging the firewall.NTSB CHI83LA427Accident · No injuriesLimited investigationFinal reportCessna 172 · Carbondale, ILThe instructor plt (CFI) was providing a dual check-out for a private plt in the Cessna 172. After flying in the local area, they returned to the arpt to practice touch-and-go landings on rwy 18. The winds were reported from 190 deg at 20, gusting 25 KTS. On…