NTSB investigations: Lycoming 0-320 series
240 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Overrun”. 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, newest first
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.\"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\" = 340))
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."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" = 340))
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 FTW00LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Pineville, LAThe student pilot's misjudgment of distance/speed during approach resulting in his failure to attain the proper touchdown point.NTSB CHI99LA237Accident · No injuriesLimited investigationFinal reportCessna 172L · Montezuma, IAthe pilot inadvertently landed on the wrong runway and exceeded the proper touchdown point on the runway. Factors associated with the accident were the gusty tailwind, the fence, and the ditch.NTSB NYC99LA137Accident · No injuriesLimited investigationFinal reportCessna 172 · Ravenna, OHThe pilot-in-command's failure to maintain aircraft control during landing.NTSB NYC99LA094Accident · No injuriesLimited investigationFinal reportCessna 172M · Lumberton, NJThe pilot's misjudgment of altitude and distance which resulted in a runway overrun.NTSB CHI99LA118Accident · No injuriesLimited investigationFinal reportCessna 172M · New Hudson, MIThe pilot's misjudgment of speed and distance and his failure to execute a go-around. A related factor was the crosswind.NTSB NYC99LA066Accident · No injuriesLimited investigationFinal reportCessna 172N · Berlin, NJThe pilot in command's failure to obtain the proper touch down point on the runway, and failure to perform a go-around. A factor relating to the accident was a sudden wind shift.NTSB LAX99LA109Accident · No injuriesLimited investigationFinal reportCessna 172P · Death Valley, CAThe pilot's use of an excessive approach reference speed and his misjudged distance/speed relationship to the runway, which resulted in a landing overrun. The pilot's failure to execute a timely go-around was also causal.NTSB LAX99LA082Accident · No injuriesLimited investigationFinal reportCessna 172L · Santa Paula, CAThe instructor pilot's misjudged altitude and speed, which resulted in a failure to attain the proper touchdown point causing an overrun and collision with a block wall. A factor was the wet runway, which may have hindered brake effectiveness.NTSB CHI98LA315Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Redwood Falls, MNthe pilot's not following proper short field landing procedures.NTSB NYC98LA134Accident · No injuriesLimited investigationFinal reportCessna 172 · Westminster, MDthe pilot's misjudgment of distance and speed during the approach/landing, and his delay in initiating a go-around. The quartering tailwind was a related factor.NTSB CHI98LA254Accident · No injuriesLimited investigationFinal reportCessna 172P · Abilene, KSThe student pilot's failure to plan his approach so as to be able to stop the airplane on the runway, and the instructor pilot's delay in taking control of the airplane, so as to correct the student's mistake. A factor contributing to this accident was the…NTSB IAD98LA020Accident · No injuriesLimited investigationFinal reportCessna 172M · Blue Bell, PAThe pilot's failure to attain the proper touchdown point, and his failure to make a go-around, while there was sufficient runway remaining.NTSB NYC98LA027Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Pittstown, NJthe pilot's misjudgment of distance and speed during the approach, and her failure to perform a go-around.NTSB SEA98LA005Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Vashon, WAA misjudged soft field takeoff. Factors include wet grass.NTSB ATL97LA109Accident · No injuriesLimited investigationFinal reportCessna 172M · Athens, TNthe pilot's failure to initiate a go-around. The pilot's misjudged approach was a factor.NTSB CHI97LA189Accident · No injuriesLimited investigationFinal reportCessna 172P · Fowlerville, MIfailure of the pilot to either attain proper touchdown point for landing or go around while he had sufficient airspeed and runway remaining.NTSB ATL97LA076Accident · No injuriesLimited investigationFinal reportCessna 172M · Perry, GAthe pilot misjudged his distance/airspeed during the approach to land, and touched down long on the runway.NTSB FTW97LA203Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Bridgeport, TXThe pilot's misjudgment of distance and altitude. A contributing factor was a tailwind.NTSB LAX97LA199Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAthe student pilot's misunderstanding of the controller's clearance during an aborted touch-and-go landing.NTSB NYC97LA075Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Butler, PAthe pilot's misjudgment of distance and speed on final approach; his failure to attain the proper touchdown point; and his failure to perform a go-around, while there was still sufficient airspeed and runway remaining, which resulted in an overrun and…NTSB NYC96LA162Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Sodus, NYThe pilot's failure to obtain the proper touchdown point, which resulted in insufficient runway to stop the airplane, and the subsequent overrun. Factors in the accident were the wet grass runway surface, and the pilot's lack of recent flying experience.NTSB FTW96LA300Accident · No injuriesLimited investigationFinal reportCessna 172P · Owasso, OKInadequate maintenance by maintenance personnel resulting in inoperative brake system during an aborted takeoff. A factor was the downhill runway condition.NTSB SEA96LA056Accident · No injuriesLimited investigationFinal reportCessna 172P · Cashmere, WAthe pilot's selection of the wrong runway for landing, by not observing a procedure to land uphill during calm wind conditions, and his subsequent failure to retract the flaps during landing roll, as recommended by the airplane's short-field landing…NTSB NYC95LA227Accident · No injuriesLimited investigationFinal reportCessna 172RG · Pittsburgh, PAthe pilot's failure to obtain the proper touchdown point and excessive airspeed which resulted in an overrun and a subsequent collision with a trailer off the departure end of the runway.NTSB FTW95LA386Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Kerrville, TXthe pilot's inadequate preflight preparation and his failure to use all the available runway. A factor was the dark night.NTSB BFO95LA054Accident · No injuriesLimited investigationFinal reportCessna 172N · Head Waters, VAthe pilot's poor planning/decision making in the attempted departure. Contributing factors are the wet, recently mowed grass airstrip, and the embankment/downhill grade encountered during the aborted takeoff.NTSB FTW95LA220Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Stephenville, TXThe pilot's failure to execute a go-around. Factors were the excessive airspeed and high glidepath during the approach.NTSB CHI95LA129Accident · No injuriesLimited investigationFinal reportBeech B19 · Omaha, NEThe pilot misjudged distance and speed. A factor was turbulence.NTSB FTW95LA110Accident · No injuriesLimited investigationFinal reportCessna 172M · Boulder, COThe pilot's premature rotation.NTSB CHI95LA072Accident · No injuriesLimited investigationFinal reportStuart/Wagner Mountain Eagle · Halliday, NDThe pilot's premature lift-off and delayed aborted takeoff.NTSB CHI94LA326Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Brookfield, WIthe commercial pilot's poor planning/decision making. A related factor is the wet, grass runway selected for landing.NTSB CHI94LA305Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Jackson, MNthe pilot's selection of unsuitable terrain for takeoff and his delay in aborting the takeoff. Factors in the accident were the soft terrain and the ditch.NTSB NYC94LA157Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Pennington, NJThe pilot's misjudged distance and speed during an aborted takeoff which resulted in an overrun. A contributing factor was the wet grass.NTSB FTW94LA228Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Ravenna, TXThe pilot overshooting the landing and his failure to execute a G0-around. The wet grass was a factor.NTSB NYC94LA102Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · New Philadelphi, OHThe pilot's inadequate decision and his delay in aborting the takeoff, which resulted in an overrun of the runway and collision with obstaclesNTSB LAX94LA228Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Sonoma, CAThe pilot's failure to attain the proper touchdown point and his failure to initiate a go-around.NTSB CHI94LA171Accident · No injuriesLimited investigationFinal reportCessna 172N · Mackinac Island, MIExcessive airspeed and a failure to attain the proper touchdown point on the runway. Factors related to the accident were the wet runway and the fence which was contacted.NTSB SEA94LA102Accident · No injuriesLimited investigationFinal reportCessna 172L · Colville, WAThe pilot's failure to attain a proper touchdown point, and his excessive airspeed at the point of touchdown. Factors include the student pilot's lack of recent experience, and a ravine off the end of the runway.NTSB NYC94LA060Accident · No injuriesLimited investigationFinal reportCessna 172K · Dayton, OHthe pilot's failure to maintain directional control which resulted in a runway overrun. Factors are the pilot's improper recovery from a bounced landing, and his lack of experience.NTSB LAX94LA086Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAThe pilot's delayed decision to abort the takeoff and improper use of the airplane's throttle.NTSB SEA94LA033Accident · No injuriesLimited investigationFinal reportCessna C-172N · Idaho Falls, IDThe pilot's failure to attain the proper touchdown point. Factors include tailwind conditions and an airport perimeter fence.NTSB BFO93LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Painesville, OHThe pilot's attempt to land with excessive airspeed, his improper use of the brakes, and his delay in performing remedial action.NTSB NYC93LA179Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · West Mifflin, PAThe pilot's misjudgement of speed and distance, which resulted in a landing overrun of the runway. Factors were an embankment and the pilot not being able to abort the landing.NTSB CHI93LA332Accident · No injuriesLimited investigationFinal reportCessna 172M · Lincoln, NEthe pilot's failure to attain the proper touchdown point.NTSB ANC93LA142Accident · No injuriesLimited investigationFinal reportCessna 172 · Black Rapids, AKThe pilot's improper in-flight planning/decision, and his delay in taking remedial action. Factor was the rough, uneven terrain.NTSB CHI93LA290Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Troy, MIIs the pilot not attaining the proper touchdown point, not flying a proper glidepath, and not performing a go around.NTSB NYC93LA136Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Voluntown, CTThe pilot's failure to achieve the proper touchdown point which resulted in an overrun of the runway and collision with trees. A factor is the pilot's improper compensation for the wind condition.NTSB CHI93LA196Accident · No injuriesLimited investigationFinal reportCessna 172N · St. James, MIThe pilot landed too long on a wet runway.NTSB MIA93LA119Accident · No injuriesLimited investigationFinal reportCessna 172M · Ochopee, FLThe pilot's poor judgement in attempting the takeoff from the parking ramp when a 12,000-FT runway was available.NTSB ANC93LA052Accident · No injuriesLimited investigationFinal reportCessna 172M · Kasigluk, AKThe pilot's improper planning/decision and delay in aborting the takeoff. Factors related to the accident were: loose gravel on the surface of the runway and the snowbank (berm) on the overrun (stopway).