# NTSB CEN21LA073: Bellanca 17-30A, N28067, Arden Hills, MN, December 3, 2020 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: December 2, 2020, 21:15 local (Dec 3, 2020, 03:15 UTC) - Place: Arden Hills, MN - Coordinates: 45.048053, -93.187572 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.0481&lon=-93.1876&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Central Region - Parties: FAA - NTSB case key (mKey): 102368 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN21LA073 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/102368/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=102368 - Page: https://openairdocs.org/ntsb/CEN21LA073 ## Probable cause Incorrect connecting rod installation, which resulted in the failure of the nos. 5 and 6 connecting rods and subsequent total loss of engine power. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine (reciprocating): recip engine power section](https://openairdocs.org/ntsb-findings/01058520): Aircraft › Aircraft power plant · Incorrect service/maintenance (probable cause); cases with it: [Bellanca 17-30A, 1 case](https://openairdocs.org/ntsb-findings/01058520/cases.md?model=1220433), [All aircraft, 233 cases](https://openairdocs.org/ntsb-findings/01058520/cases.md) - [Engine (reciprocating): recip engine power section](https://openairdocs.org/ntsb-findings/01058520): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [Bellanca 17-30A, 1 case](https://openairdocs.org/ntsb-findings/01058520/cases.md?model=1220433), [All aircraft, 233 cases](https://openairdocs.org/ntsb-findings/01058520/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Bellanca 17-30A, 15 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=1220433), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) ## Analysis The pilot reported that he heard a loud “bang” and the engine began to vibrate and ultimately lost complete power. He executed a forced landing to a highway during which the airplane struck a car and a highway divider which resulted in substantial damage to both wings. Postaccident engine examination revealed that the Nos. 5 and 6 connecting rods had failed. Further examination revealed two undamaged rod nuts within the oil pan that had no remnant of a rod bolt within the threaded portion of the nut. Additionally, a rod bolt, although damaged, was complete from bolt head to threaded shank and did not have a nut on the threaded portion. Review of maintenance records revealed that the Nos. 1, 4, and 6 cylinders had been removed and replaced due to low compression about 8 years and 396 hours before the accident, but it is not known if the connecting rods were removed at this same time. The most recent engine overhaul was completed 16 years before the accident, and it had accumulated about 1,296 hours time-in-service since the overhaul. Based on the available evidence, the loss of engine power was likely due to improper connecting rod installation that resulted in the loss of connecting rod bolt torque, separation of the rod bolt nuts, and subsequent failure of the Nos. 5 and 6 connecting rods. ## Factual narrative On December 2, 2020, about 2115 central standard time, a Bellanca 17-30A, N28067, was substantially damaged when it was involved in an accident near Arden Hills, Minnesota. The pilot and passenger and an occupant of the motor vehicle were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated the accident flight was a night sightseeing flight around the city. About 10 minutes after takeoff, he heard a loud “bang,” and the engine began to vibrate. Shortly thereafter, the engine lost power completely. The pilot made a gear-down forced landing on an interstate highway. During the landing roll, the airplane struck a vehicle and highway divider. Postaccident examination revealed both wings were bent. In addition, a hole was observed on the top of the engine crankcase, and the cylinder Nos. 5 and 6 connecting rods were missing. An engine examination revealed a large amount of metal debris in the oil pan. The oil filter also contained metal chips and filings. Recovered fragments included portions of the two connecting rods, the corresponding rod caps, and the associated rod bolts and nuts. Two rod cap nuts were found loose in the oil pan without any portion of the associated rod cap bolts. In addition, one rod bolt retained by the connecting rod was recovered but did not have a nut on the threaded end. The other rod bolts exhibited mechanical damage, separated threaded portions, or were not located. Airplane maintenance records indicated that the engine had accumulated 1,296 hours since overhaul which was completed about 16 years prior to the accident. A maintenance entry dated September 13, 2012, indicated that the Nos. 1, 4 and 6 cylinders were removed and reinstalled due to low compression. It is not known if the connecting rods were removed at this time. According to the most recent annual inspection, completed on October 7, 2020, the engine had accumulated 396 hours since the removal and replacement of cylinder Nos. 1, 4, and 6. The No. 6 cylinder was replaced about 8 years and 396 hours time-in-service prior to the accident. ## Aircraft - Registration: [N28067](https://openairdocs.org/aircraft/N28067), registered now, S/N 79-30966, built 1979 (OpenAirDocs) - Reported make and model: BELLANCA 17-30A - Registry model: [Bellanca 17-30A](https://openairdocs.org/model/bellanca-17-30a) (registry code 1220433) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 79-30966 - Year built: 1979 - Airframe hours: 3187 - Engines: Continental IO-550F4 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 7, 2020, 18 hours before - Departed: KANE, Blaine, MN - Equipment: ADS-B, Auto-pilot, Onboard weather, Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 52; injuries: none; commercial; airplane ratings: single-engine land, single-engine sea; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review October 12, 2020; seat: left; restraint: 3-point; flight hours: 5,000 total, 2,800 in this make and model, 5,000 as pilot in command, 75 in the last 90 days, 25 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night - Visibility: 10 statute miles - Lowest ceiling: 2,200 ft - Temperature: 30 °F, dew point 20 °F - Altimeter: 30.10 inHg ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20201202017439A](https://openairdocs.org/incident/20201202017439A), Dec 2, 2020: Bellanca 17-30A, Blaine, MN, Substantial damage. 2020-12-02 N28067, 1979 Bellanca, took off from anoka, MN airport (kane) at about 2100L. The plan was a scenic night flight over minneapolis to see the city… ## Docket (4 files) The files NTSB released with the investigation on September 28, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=102368. 15.3 MB in all. - NTSB form 6120.1-2, pilot-operator aircraft accident report (item 1, PDF, 9 pages, 651 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11717467&FileExtension=pdf&FileName=NTSB%20Form%206120.1-2,%20Pilot-Operator%20Airxcraft%20Accident%20Report-Rel.pdf_Redacted.pdf - Screenshot of accident location (item 2, PDF, 1 page, 310 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=11716437&FileExtension=pdf&FileName=Screenshot%20of%20Accident%20Location-Rel.pdf - Accident photos (item 3, PDF, 7 pages, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14464657&FileExtension=pdf&FileName=Photos-Rel.pdf - Maintenance record excerpts (item 4, PDF, 9 pages, 12.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=14464667&FileExtension=pdf&FileName=N28067%20logs%20pdf_Redacted-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.