CEN16LA343
2016-08-31 · Hibbing, Minnesota, United States · Serious · 1 aircraft · Status: Completed
Airport HIB
Aircraft involved
Probable cause & findings
The pilot's failure to maintain aircraft control, which resulted in impact with terrain near the runway.
Factual narrative
On August 31, 2016, about 1130 central daylight time, a Cessna 170A airplane, N1726D, was substantially damaged while landing on runway 31 at Range Regional Airport (HIB), Hibbing, Minnesota. The pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.The pilot reported that he arrived at HIB about 0800 to preflight the airplane before he departed about 0900 on a pleasure flight to Anderson Field, a private airstrip, located about 25 miles north of HIB near Bear River, Minnesota. The pilot stated that he made 8 uneventful landings at the private airstrip before taking a half hour break on the ground. He noted that the winds were "picking up" when departed the private airstrip about 1100 for the return flight to HIB. The pilot stated that the air was "turbulent" during the return flight to HIB. The pilot stated that his last recollection of the flight was when he entered the traffic pattern for runway 31 at HIB. The pilot was unsure if he "had a bad landing or tried to go around" when the accident occurred. The pilot stated that although he has a brief memory of a first responder speaking to him after the accident, his first substantive memory was after he woke up in the hospital a week after the accident. According to the Hibbing Police Department, an individual called 911 around 1256 to report the accident. There were no witnesses to the final portion of flight. The airplane was examined by a Federal Aviation Administration (FAA) Airworthiness Inspector. The FAA inspector stated that he did not observe any tire skid marks that could be associated with a loss of directional control after the airplane touched down. The initial point-of-impact was where the left wingtip hit the ground about 30 ft from the left edge of the runway. The airplane came to rest in the grass area along the left side of runway 31, about 1,375 ft from the approach end of runway 31 and about 65 ft off the left edge of the runway. The airplane was upright at the accident site and facing southeast. The forward fuselage was crushed aft, which was consistent with a nose-down impact. The wings exhibited upward bending near both wing tips and buckling along both wing roots. The upper wing surfaces were buckled along their entire span. There was no evidence of leading edge wing damage. The aft fuselage and empennage appeared undamaged. Flight control cable continuity was confirmed from the cockpit controls to the ailerons, elevator, rudder, and flaps. Both flaps were found fully retracted, which was consistent with the position of the cockpit flap control lever. Both the pitch trim tab and the associated pitch trim indicator were in a mid-range position. The fuel selector had been turned off by a first responder; however, the first responder noted that there was fuel draining from a fuel line leading to the engine before the fuel selector was turned off. The left main landing gear leg was bent slightly forward. The right main landing gear leg appeared to be undamaged. The right brake system operated normally when tested. The left brake system could not be tested due to a damaged master cylinder; however, the remaining components of the left brake system did not exhibit any anomalies. The tailwheel assembly had fractured where it attached to the tailwheel spring; however, the observed fracture features were consistent with impact related damage. The tail wheel rotated freely and there was no evidence of a malfunction of the tailwheel steering components. The postaccident examination did not reveal any anomalies that would have precluded normal airplane operation during the flight. The engine remained partially attached to the firewall, and the propeller remained attached to the crankshaft flange. Engine control cable continuity could not be verified due to impact related damage. The propeller blades exhibited minor chordwise scratches and leading edge damage. Both propeller blades exhibited aft bends. Compression and suction were noted on all six cylinders in conjunction with crankshaft rotation. The lower spark plugs were removed and exhibited features consistent with normal engine operation. The magnetos remained attached to their respective installation point and provided spark on all posts while the engine crankshaft was rotated. The carburetor had separated from the engine during impact. The postaccident examination did not reveal any anomalies that would have precluded normal engine operation during the flight. The pilot held a private pilot certificate with ratings for single-engine land and sea airplanes. The pilot reported having about 160 hours of total flight experience, of which 21.5 hours were flown in the accident airplane. The pilot received his tailwheel endorsement the day before the accident. The pilot was conducting a personal flight, and his last recollection of the flight was when he entered the traffic pattern for the runway. He stated that he was unsure if he "had a bad landing or tried to go around" when the accident occurred. The airplane came to rest upright in the grass alongside the runway facing southeast; the forward fuselage was crushed aft, which was consistent with a nose-down impact. The flaps were found fully retracted. A postaccident examination of the runway did not reveal any tire skid marks that could be associated with a loss of directional control after the airplane touched down. The initial point of impact was where the left wingtip had hit the ground about 30 ft from the left edge of the runway. The propeller exhibited damage consistent with minimal engine power at impact. The wreckage examination did not reveal any mechanical malfunctions or failures of the airplane that would have precluded normal operation. Based on the available information, the pilot lost airplane control, but it could not be determined if this occurred while landing or during a go-around attempt. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2016_CEN16LA343.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, go-around). All research papers
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- arXiv 2023 · arXiv preprint Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…