NTSB investigations: Lycoming 0-320 series, 1983

22 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 per year

19822026
NTSB investigations: Lycoming 0-320 series, 1983 per year, 1982–2026: 240 cases
198215
198322
198419
198512
19865
19876
198810
198911
199014
199110
199215
199312
19949
19957
19963
19978
19984
19998
20008
20014
20029
20039
20047
20056
20065
20072

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\") = 1983
    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\" = 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.

NTSB MKC84LA007Accident · No injuriesLimited investigationFinal reportCessna 172M · Blairstown, MOThe plt reported that after he started to takeoff, the acft had rolled aprx 1500 ft when he felt the airspeed was not sufficient, so he aborted. He was unable to stop on the remaining rwy. Before stopping, the acft went thru a shallow ravine. Subsequently,…Oct 12, 1983 · N755RB · DestroyedNTSB LAX83LA457Accident · No injuriesLimited investigationFinal reportCessna 172P · Glendale, AZReportedly, the plt landed long. He then applied braking action & 1 wheel locked. At that point, the acft was still going too fast to stop on the remaining rwy & there was insufficient rwy to go around. The plt steered the acft off the end of the rwy & it…Sep 25, 1983 · N55264 · Substantial damageNTSB ATL83LA380Accident · No injuriesLimited investigationFinal reportCessna 172 · Mocksville, NCThe acft overran the rwy during a no-flap landing roll-out. The plt reported that he had electrical failure after takeoff and returned to land but he was unable to extend the flaps. The approach was high and fast but the plt continued and touched down long.…Sep 24, 1983 · N737DR · Substantial damageNTSB NYC83LA250Accident · No injuriesLimited investigationFinal reportCessna C172M · Dover, DEThe acft ran off the end of the rwy, groundlooped, and collided with a tree during an effort to avoid a blast fence. The landing, made at night with touchdown occurring too FAR down the rwy. An approach had already been abandoned due to excessive airspeed,…Sep 20, 1983 · N64006 · Substantial damageNTSB CHI83LA432Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Carthage, ILThe acft collided with a ditch during landing. The acft bounced and floated during landing. The pilot said he thought hewas too FAR down the rwy for a go-around so he applied the brakes. The acft skidded off the rwy end into a ditch. The pilot thought a gust…Sep 18, 1983 · N1443E · Substantial damageNTSB CHI83LA409Accident · No injuriesLimited investigationFinal reportCessna 172M · Grand Marais, MNThe plt took off from the departure point after an unexpected 1/2 hr delay. By the time he arrived at his destination, it was dark. No rwy lighting sys was installed, so someone at the arpt drove a car to rwy 27 to light up the approach end with the head…Sep 3, 1983 · N1857V · Substantial damageNTSB CHI83LA396Accident · No injuriesLimited investigationFinal reportCessna 172 · Princeton, ILThe turf rwy was wet from recent rains. The plt stated that during takeoff, the acft had accelerated to near the rotation speed when it was slowed by a soft spot in the rwy near mid field. At the same point, an upslope portion of the rwy was encountered & the…Aug 28, 1983 · N12862 · Substantial damageNTSB FTW83LA408Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Winslow, ARThe plt stated that his anxiety during the approach delayed his decision to abort a long landing. After touchdown he attempted to turn at the end of the rwy but, the acft collided wth a stump and damaged the rt wing. The plts anxiety was based on another…Aug 24, 1983 · N1656J · Substantial damageNTSB NYC83LA205Accident · No injuriesLimited investigationFinal reportCessna 172 · Atlantic City, NJThe acft landed long and fast, ran off the end of the rwy & collided with a fence.Aug 8, 1983 · N66098 · Substantial damageNTSB CHI83LA367Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Franksville, WIThe acft was intentionally groundlooped as the acft was not stopping at the runways end. The pilot said the brakes malfunctioned. The mechanic who worked on the acft after the accident said brakes were available even though brake fluidwas low. The mechanic…Aug 6, 1983 · N2843Z · Substantial damageNTSB FTW83LA355Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Cashion, OKThe plt was told that the sod strip was 1800 ft long. His calculated takeoff distance to clear a 50 ft obstacle was 1720 ft. however, the actual length of the sod strip ws 1300 ft. during the takeoff roll, the plt realized he would not be able to clear the 30…Jul 31, 1983 · N5999V · Substantial damageNTSB NYC83LA176Accident · No injuriesLimited investigationFinal reportGrumman American AA-5 · West Kingston, RIThe acft overran the rwy hit VASI lights and rolled down an embankment during landing. The pilot was under some pressureto get on the ground because of a hyperventilating passenger. The pilot reported he increased his rate of descent by lowering the acft…Jul 13, 1983 · N6043L · Substantial damageNTSB ANC83LA115Accident · No injuriesLimited investigationFinal reportCessna 172P · Mckinley Park, AKThe plt stated that he was unable to locate the windsock. While on final for rwy 16 'things' did not feel right, but he continued into a long, fast tailwind landing. As he neared the end of the rwy he deliberately groundlooped the acft to avoid going over a…Jul 5, 1983 · N54633 · Substantial damageNTSB ATL83LA236Accident · No injuriesLimited investigationFinal reportCessna 172 · Gastonia, NCThe pilot was on a asr approach and sighted the runway at 1/2-mile out at an altitude of 800 feet AGL. Touchdown was made at about half way down the runway at 68 KTS with 40 degrees of flaps. Braking was less than good and the acft hit a barrier at runways…Jun 22, 1983 · N5284D · Substantial damageNTSB NYC83LA145Accident · No injuriesLimited investigationFinal reportCessna 172M · Block Island, RIThe plt reported that during a landing, the brakes failed & he was unable to stop on the rwy. The acft ran off the end & came to rest in bushes with substantial damage. According to the plt, the outboard pressure plate & lining had separated from each brake.…Jun 5, 1983 · N6901H · Substantial damageNTSB MIA83LA142Accident · No injuriesLimited investigationFinal reportCessna 172M · Arcadia, FLThe plt reported that on his approach to land, his speed was higher than normal & the acft touched down well past the normal touchdown point. He was unable to stop on the remaining rwy. The acft went off the end of the rwy & collided with a ditch. The plt…May 15, 1983 · N9558V · Substantial damageNTSB CHI83LA217Accident · No injuriesLimited investigationFinal reportCessna 172 · Mchenry, ILThe acft went off the departure end of runway 09 during landing and nosed over. The weather as reported by the operator,was scattered clouds, more than 5 miles visibility and winds calm. Runway 09 had been in use all day. The pilot stated that his approach…May 13, 1983 · N53242 · Substantial damageNTSB LAX83LA187Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Fair Oaks, CAThe acft collided with terrain when it overran the runway on a pleasure flight. Night visual meteorological conditions prevailed. The pilot stated that upon arrival he was unable to see the 'wind indicator', however, when he saw an acft land to the north he…Apr 9, 1983 · N2348T · Substantial damageNTSB SEA83LA075Accident · No injuriesLimited investigationFinal reportCessna 172 PII · Snohomish, WAThe plt stated he misjudged the approach to land and landed on the last 1/3 of the runway. Brakes were applied during landing roll but the acft rolled off the end of the runway, struck a ditch with the nosewheel and came to rest inverted.Apr 5, 1983 · N52807 · Substantial damageNTSB ATL83LA138Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Stone Mountain, GAThe aircraft overran the departure end of the runway and collided with an embankment during an aborted takeoff. The student pilot did not file a flight plan or check the weather for this flight. The weather was VMC but the pilot startedthe takeoff down wind.…Mar 19, 1983 · N8593N · DestroyedNTSB FTW83LA120Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Winslow, ARDuring dual instructional flt, the student plt was practicing a short field takeoff. After lifting off into ground effect, he elected to abort the takeoff when he did not think the acft was accelerating fast enough. The instructor pilot (CFI) stated that he…Feb 17, 1983 · N9981W · Substantial damageNTSB CHI83LA106Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Vernon, ILThe aircraft ran off the end of a runway and collided with a ditch. The student pilot on his first solo cross country had become disoriented and landed 95 miles off course. He had been flying 2 hours and 30 minutes. He was supposed to reach enroute stop after…Feb 10, 1983 · N8222W · Substantial damage