FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC16FA065 · Hefty Polar Cub

10 Sept 2016 · Anchorage, AK, United States

Hefty Polar Cub · Accident: loss of control in flight while maneuvering

From Anchorage, AK to Anchorage, AK

Report a problem

Event

NTSB case
ANC16FA065
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Hefty Polar Cub

Aircraft type
Hefty POLAR CUB
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N62905
Operator
Unknown
Onboard fatalities
Unknown
Route
From Anchorage, AKTo Anchorage, AK
Aircraft age
About 20 years (built 1996)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Personnel issues › Physical

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The private pilot departed in his float-equipped, experimental, amateur-built airplane during day visual meteorological conditions. According to a friend of the pilot, the purpose of the flight was to fly over a proposed hunting site and then return.

About 90 minutes later, multiple witnesses saw the airplane complete two, low-level, high-speed, 360° right turns over a residential neighborhood. The witnesses said that the airplane's first 360° turn was accomplished at an altitude between 150 and 200 ft above ground level, but the second turn was much lower. Witnesses near the accident site reported that, as the airplane completed the second, steep, 360° turn, the nose of the airplane pitched down, and the airplane began a rapid nose-down descent. The engine rpm then increased significantly, and the wings rolled level just before the airplane impacted a stand of tall trees adjacent to a home. The airplane subsequently descended onto a neighborhood road and came to rest inverted. A postcrash fire ensued about 30 seconds after impact, which quickly engulfed the entire airplane.

According family members and close friends, this was highly unusual behavior for this pilot.

Postaccident examination of the airplane's exhaust system revealed that the muffler can assembly was cracked around most of its circumference near the inlet portion of the muffler, which would have allowed exhaust gases to enter the cockpit/cabin. Toxicology tests revealed 48% carboxyhemoglobin (carbon monoxide) in the pilot's blood. The pilot was a nonsmoker, and nonsmokers normally have no more than 3% carboxyhemoglobin. The pilot's cause of death was extensive blunt force trauma including lacerations of the aorta, heart, and liver, and there was no soot found in his trachea. Although there was a postimpact fire, given the extensive blunt force injuries the pilot sustained and the lack of soot in his trachea, it is likely that the pilot's elevated carboxyhemoglobin level was from acute exposure to carbon monoxide during the 90-minute flight and not from postimpact fire.

Carboxyhemoglobin levels between 10% and 20% can result in confusion, impaired judgment, and difficulty concentrating, and the pilot's 48% carboxyhemoglobin level likely resulted in severe impairment.

No aircraft maintenance records were located for the airplane, which the pilot had built in 1996, so it is unknown when the muffler was last inspected or maintained. Additionally, due to the extensive postimpact fire, it was not possible to determine if the airplane was equipped with any type of carbon monoxide detection equipment. According to friends of the pilot, he conducted all maintenance on the airplane.

Probable cause

The pilot's severe impairment from carbon monoxide poisoning in flight, which resulted in a loss of control and a subsequent collision with trees and terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC16FA065
Event ID
20160912X71238
Case number
ANC16FA065
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-09-11.
  • API snapshot SHA-256: 9b29fe4b73571726b917891404683d941574b8abd2b01b23d1071077e9d2f7f7; retrieved 2026-09-14T22:00:04.952Z.