A Bering Air commuter plane that crashed near Nome, Alaska, was operating above its weight limits when it encountered severe icing, federal investigators concluded. The Feb. 6, 2025, crash killed the pilot and all nine passengers aboard.
The National Transportation Safety Board found that inadequate airspeed management and improper pilot inputs led to an aerodynamic stall. It also identified the excess weight as causal because it reduced the airplane’s stall margin in already demanding conditions.
The flight encountered severe icing near Nome
The NTSB’s completed investigation says Bering Air Flight 445 departed Unalakleet for Nome at about 2:37 p.m. Alaska time. Roughly 38 minutes later, the Cessna 208B encountered severe icing that included supercooled large droplets. Its ice-protection system was functioning and in use.
Nome’s runways closed briefly for deicing as the plane approached. After a controller suggested slowing to avoid arriving before they reopened, engine power and airspeed decreased. The pilot later added power, but the airspeed fell again and triggered the low-airspeed awareness system, which disconnected the autopilot as designed.
The airplane stalled before striking pack ice
Recorded data showed the aircraft descending rapidly as its airspeed dropped. The pilot made control inputs while the speed continued toward about 70 knots at roughly 3,100 feet above mean sea level. The last position was recorded at 3:20 p.m., seconds after a controller instructed the flight to climb.
The airplane hit pack ice about 12 miles offshore in Norton Sound and 32 miles east of Nome. The moving ice complicated the search and recovery effort. Investigators used avionics information, weather analysis, wreckage evidence and operational records to reconstruct a flight without a conventional cockpit voice or flight data recorder.
Weight reduced the margin above a stall
The airplane had a supplemental modification that allowed a higher maximum weight in ordinary operation, but its ice-protection supplement imposed a lower limit for known or forecast icing. Post-crash calculations placed the takeoff weight at about 9,865 pounds—approximately 1,058 pounds above the icing limit and 803 pounds above the maximum permitted under the payload extension.
Extra weight raises the speed needed to maintain lift at a given configuration. In an icing encounter, contamination can also reduce lift and increase drag. NTSB did not treat weight as the only cause; it found that the combination reduced the available stall margin as workload and situational awareness deteriorated.
Investigators found a broader operational problem
NTSB concluded that Bering Air’s safety management allowed routine flights above weight limits. The public investigation docket includes operational records, interviews, weather material and performance analysis supporting the board’s findings. The agency also cited inadequate Federal Aviation Administration oversight for failing to identify and address the pattern.
The loading problem was not a minor paperwork discrepancy. Investigators compared the operator’s manifest with the contents recovered after the crash and calculated an even higher weight from the physical evidence. Support equipment carried at outstations also added weight. Accurate manifests matter because pilots use the total to determine whether an aircraft can legally and safely depart under the expected weather limitations.
A safety investigation assigns probable cause to prevent recurrence; it is not a criminal trial. The final finding separates the pilot’s actions in the last minutes from organizational conditions that existed before departure, including load control, operational monitoring and regulatory surveillance.
The board issued new recommendations
NTSB recommended that the FAA require upset-prevention and recovery training for most Part 135 and Part 91K operators. It also called for explicit enhanced-surveillance criteria when operators undergo rapid growth, increased complexity, accidents or other changes, including checks that FAA inspector staffing is sufficient.
The board reiterated earlier recommendations involving certificated dispatchers, flight-data monitoring, load-manifest rules and crash-resistant recorders. Those measures address different points in the chain: accurate loading before departure, independent operational control, detection of recurring deviations and better evidence after an accident.
Flight-data monitoring is particularly relevant to repeated deviations that may not produce an immediate incident. Aggregated records can show trends in speed, weight or procedure before a fatal event exposes them. Small commuter operators often serve communities with few transportation alternatives, making reliable oversight important without diminishing the essential service those flights provide.
The finding is final, while responses continue
The NTSB case page lists investigation ANC25MA018 as completed. That makes the probable-cause statement materially different from preliminary information released during the search and early evidence collection. The accident occurred in February 2025; the board’s final findings and recommendations were issued in 2026.
Implementation now depends on recipients, chiefly the FAA, responding to the recommendations. NTSB tracks those responses separately from closing the accident investigation. The completed record says the fatal outcome arose from a stall in severe icing, with excess weight and systemic oversight failures narrowing the path to recovery.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
