Bering Air Flight 445 Crash Near Nome: NTSB Final Report

Updated: Jul 30, 2026
A Textron Aviation Cessna 208B Grand Caravan, N321BA, operated by Bering Air as scheduled Flight 445, crashed onto pack ice in Norton Sound near Nome, Alaska, on February 6, 2025. The airplane entered an aerodynamic stall during a workload-heavy descent through severe icing conditions and struck the ice about 12 miles offshore, killing the pilot and all nine passengers. In its final report released July 30, 2026, the NTSB determined that the pilot’s degraded situational awareness and improper stall-recovery inputs were compounded by the airplane’s operation nearly 1,000 pounds above its icing-condition maximum gross weight, a condition the Board tied to a documented pattern of underreported load manifests at Bering Air and to the FAA’s failure to increase oversight despite the carrier’s rapid post-pandemic growth.
Accident Summary
| Date | February 6, 2025 |
|---|---|
| Location | Near Nome, Alaska, United States |
| Aircraft | Textron Aviation Cessna 208B Grand Caravan, N321BA |
| Operation | Part 135 scheduled charter flight, Bering Air Flight 445, Unalakleet to Nome |
| Occupants | 10 total (9 passengers; 1 crew) |
| Fatalities | 10 |
| Phase of Flight | Descent, aerodynamic stall and loss of control |
| Investigation | NTSB, final report AIR-26-05 issued July 30, 2026; FAA named in findings |
This case isn’t about one mistake in the cockpit, it’s about a company that let its pilots fly overweight for weeks and a regulator that never caught the pattern. The NTSB just handed plaintiffs’ counsel the roadmap, pilot workload, weight and balance, operational control, and oversight failure, and that roadmap runs straight through Bering Air’s own flight records.
Bruce Lampert, Aviation Accident Attorney — Katzman, Lampert & Stoll
What Happened
According to the final report, the pilot departed Unalakleet at 1437 Alaska standard time on the third leg of a scheduled round trip, using the autopilot for most of the flight. About 38 minutes after departure, the airplane encountered icing more severe than forecast, including supercooled large droplets, a condition outside the certification envelope for the airplane’s TKS ice protection system even though the system functioned as designed. At 1512, Nome Airport closed both runways for deicing, and the controller told the pilot he could “slow down a little bit” to avoid arriving early.
Engine power was reduced and the airplane’s airspeed decayed from about 160 knots to as low as 99 knots, activating the low airspeed awareness system, which automatically disengaged the autopilot at 1519:35. Over the next several seconds, recorded avionics data show the airplane’s nose pitching up to 10 to 12 degrees, its airspeed falling to about 70 knots at 3,100 feet, and the airplane reaching its maximum wing lift coefficient, the point of aerodynamic stall. The final recorded data point showed the airplane in a 64-degree left bank and 30-degree nose-down attitude, descending at about 7,800 feet per minute. It struck pack ice roughly 12 miles offshore and 32 miles east of Nome Airport.
Aircraft and Operational Context
The accident airplane was a 2020-model Cessna 208B equipped with a TKS ice protection system and a low airspeed awareness system tied to that equipment. The system’s supplement limited the airplane to a maximum gross takeoff weight of 8,807 pounds for flight into known or forecast icing conditions, well below the 9,062-pound weight allowed under a supplemental type certificate for non-icing operations. The NTSB’s investigative calculation placed the airplane’s actual takeoff weight at about 9,798 pounds, roughly 991 pounds above the icing-condition limit, a margin the Board found reduced the airplane’s stall speed cushion in both level flight and banked turns.
The pilot, 34, held a commercial certificate with instrument and multiengine ratings, had logged about 2,500 total flight hours including 1,060 in the 208B, and had completed required cold-weather and icing-specific training within the preceding months. That background does not point to a training gap. It points instead to an operating environment where weight limits were treated as flexible.
Bering Air, based in Nome since 1979, expanded rapidly after a regional competitor’s 2020 bankruptcy left it as the region’s primary carrier, growing to roughly 200 to 215 employees and a 30-airplane fleet by the time of the accident. The carrier had no voluntary safety management system in place and relied on an informal, decades-old process of face-to-face weather discussions rather than a documented flight risk assessment tool.
Accident Investigation
The final report draws on Garmin G1000 avionics data recovered from the airplane, air traffic control recordings between the pilot and Anchorage Center, ADS-B tracking, third-party satellite position data, and a dedicated airplane performance study built from flight-test-validated simulation models. That combination let investigators reconstruct the accident sequence to the second, a level of technical detail that illustrates how the NTSB investigation process moves from preliminary factual gathering to a probable cause determination.
Investigators also went well beyond the accident flight itself, reviewing Garmin-recorded fuel data against pilot-entered figures for 35 flight legs flown by the accident airplane over the ten days before the crash. That review found at least seven flights, including the accident flight and the earlier leg flown that same day, operated above one or both applicable weight limits, with pilot-reported fuel weights consistently lower than the fuel actually onboard. Fact patterns built from records this granular are exactly the kind of evidentiary foundation counsel look for in representative aviation matters involving operational control and record-keeping failures.
Operational and Regulatory Issues
The NTSB determined the probable cause was the pilot’s inadequate airspeed management, driven by workload and degraded situational awareness, and his improper control inputs during the resulting stall. The Board found operation above maximum gross weight also causal, since it reduced the airplane’s stall margin. Contributing factors named in the report were Bering Air’s inadequate safety management, which the Board said allowed routine overweight operations to continue unaddressed, and the FAA’s inadequate oversight, which failed to flag the carrier’s rapid growth and operational complexity as risk factors warranting closer surveillance.
That is a different kind of finding than a single bad decision on one flight. The NTSB’s review of the FAA’s own risk-scoring system, the Safety Assurance System, found that neither operational complexity nor rapid growth had ever been logged as a risk factor for Bering Air in the two years before the crash, despite a Fairbanks-based inspector managing the certificate from more than 500 miles away.
The Board issued two new recommendations to the FAA: requiring upset prevention and recovery training for most Part 135 and 91K operators, and developing explicit surveillance criteria for operators experiencing rapid growth or increased operational complexity. It also reiterated earlier recommendations calling for certificated dispatchers, structured flight data monitoring programs, expanded load manifest requirements for single-engine Part 135 aircraft, and crash-resistant flight recorder systems, none of which existed on the accident airplane.
Aviation Accident Litigation
A final NTSB report with a stated probable cause narrows the evidentiary landscape considerably compared to the preliminary stage, and this one names both an operator and a federal regulator in its causal chain. That combination of findings, pilot performance, an operator’s documented pattern of overweight dispatch, and a regulator’s failure to adjust oversight, tends to shape how liability and damages are analyzed in aviation accident litigation involving Part 135 carriers.
The seven-flight overweight pattern identified through Garmin data cross-referenced against pilot flight reports gives counsel a rare thing this early: a documented, dated record of a systemic practice rather than a single disputed data point. Cases built on that kind of paper trail often track differently than single-incident matters when compared against broader aviation crash verdict trends for commercial and charter operators.
For families pursuing claims after a fatal aviation accident, a final report of this specificity, one that identifies causal and contributing factors by name, can accelerate the process of evaluating claims against both the operator and, where applicable, oversight failures tied to regulatory bodies.
Media inquiries: Journalists covering this accident or related aviation litigation matters may contact Bruce Lampert directly via tdunn@katzmanlampert.com.
Consultation Regarding Aviation Accident Investigations
Families, referring attorneys, and journalists sometimes seek legal consultation or technical insight regarding aviation accidents and investigative issues discussed in these analyses. Inquiries may be directed to Katzman, Lampert & Stoll at the link below.
Aviation Accident Litigation
- Aviation Accident Litigation
- Commercial Airline Accident Litigation
- Private & Corporate Aircraft Accident Litigation
- Military & Government Contractor Aviation Litigation
- Complex Aviation Litigation Methodology
- NTSB Investigations & Civil Aviation Claims
- Federal Preemption in Aviation Product Liability
- Defeating GARA Defenses in Aviation Product Liability Litigation
- For Families and Survivors
MICHIGAN OFFICE
Katzman, Lampert & Stoll
950 West University Dr #101
Rochester, MI 48307
E-mail: Click to use our Contact Form
Toll-Free: (866) 309-6097
Phone: (248) 258-4800
Fax: (248) 258-2825
COLORADO OFFICE
Katzman, Lampert & Stoll
9596 Metro Airport Ave.
Broomfield, CO 80021
E-mail: Click to use our Contact Form
Toll-Free: (866) 309-6097
Phone: (303) 465-3663
Fax: (303) 867-1565
PENNSYLVANIA OFFICE
Katzman, Lampert & Stoll
121 N. Wayne Ave. # 205
Wayne, PA 19087
E-mail: Click to use our Contact Form
Toll-Free: (866) 309-6097
Phone: (610) 686-9686
Fax: (610) 686-9687
