Penguins Kuzmenko Returns After Tragedy | Analysis by Brian Moineau

TL;DR

  • Pittsburgh Penguins winger Andrei Kuzmenko left camp and flew to Moscow after reports that his father, Alexander Kuzmenko, was killed by a bear during a fishing trip in Tuva, Siberia; the Krasnaya River location and four-hour downstream transport detail originate with Russian outlet REN TV and were relayed by Western media. [1][4]
  • Pittsburgh opens the 2026–27 NHL season on Wednesday, September 30 at Philadelphia and faces six games by Saturday, October 10, compressing roster decisions into an 11‑day window that stresses chemistry and special teams. [6][8][14]
  • The Penguins and NHL.com have issued concise confirmations and condolences, while granular field details come via Russian media—a sourcing split that will steer updates and on-air framing across September 30 broadcasts. [9][10]

What the source said

BBC Sport reported that Andrei Kuzmenko, a 30-year-old forward for the Pittsburgh Penguins, departed the team to return to Russia after his father, Alexander—described as an ice hockey coach—was killed by a bear near the Krasnaya River in southern Siberia’s Tuva Republic; the group reportedly moved him downstream for hours before an airlift to a hospital, where he was pronounced dead. [1] The Penguins, via president and general manager Kyle Dubas, issued condolences and confirmed Kuzmenko had practiced with teammates before leaving the club. [9] BBC’s piece also noted Kuzmenko’s one-year deal and that the NHL season begins next week on a late-September slate. [1]

Why it matters

Three stakeholder groups intersect here: Kuzmenko and his family; the Penguins’ hockey operations group managing opening-night roles; and national broadcasters programming a high-visibility launch week in Philadelphia. [6][8] For Pittsburgh’s cap and roster math, Kyle Dubas committed a one-year, $5 million contract to Kuzmenko on July 1, 2026 to backfill scoring after Anthony Mantha’s exit—making his Week 1 availability a live lever on lineup balance. [2][13] ESPN and TNT are marketing an early-season slate across the final week of September and first week of October in a league calendar set for 84 games, so a sudden top-nine absence becomes part of the opening storylines. [6][8]

There’s also a sourcing split: the most vivid incident details—Krasnaya River naming and multi-hour transport—trace to REN TV and are re-aggregated by Western outlets, while Penguins.com and NHL.com stick to verified essentials and attribute the rest to Russian media; that asymmetry will shape how beat writers, fans, and TV trucks update the narrative day by day. [4][9][10]

Original analysis

How the “Andrei Kuzmenko father killed by bear” news reshapes Pittsburgh’s opening week

Kuzmenko skated with Pittsburgh on Thursday, September 24, then left without a set return date after the team publicly committed to supporting his decision to be with family. [9][10] The calendar offers no soft landing: the NHL opens Tuesday, September 29; Pittsburgh opens at the Flyers on Wednesday, September 30 and then plays MTL (Oct 3), WPG (Oct 5), at WSH (Oct 7), at CBJ (Oct 9), and DAL (Oct 10)—six games in 11 days. [6][8][14] Week 1 is when coaches cement pairings and special-teams jobs, not when they expect to rewire them. [14]

Dubas did not add Kuzmenko as a spare part. NHL.com’s team reset framed him as a Mantha replacement for finishing punch; the projection slotted him on a third line with Ben Kindel and Nicholas Robertson to stabilize secondary scoring and PP2 looks. [13] In 2025–26 with Los Angeles, Kuzmenko posted 25 points in 52 games (0.48 P/GP) before a February meniscus repair, signaling a bet on finishing efficiency rather than primary-driving usage in Pittsburgh. [10][13]

  • Back-of-envelope calculation (opening-week points delta):

    • Expected Kuzmenko scoring over four games (Sep 30–Oct 7) at his 2025–26 rate: 0.48 P/GP × 4 = 1.92 ≈ 1.9 points. [10][14]
    • Nicholas Robertson candidate fill-in: 32 points in 78 games last season → 0.41 P/GP × 4 = 1.64 ≈ 1.6 points. Delta ≈ 0.3 points. [13]
    • Box-score delta is small, but PP2 finishing and controlled-entry balance can swing a single goal; one goal in a one-goal game can move win probability by double digits, magnified across an 11‑day gauntlet. [13][14]
  • A 2×2 for sudden absences before the season starts

    • Timing axis: Preseason/Opening week vs. Midseason.
    • Role axis: Core driver vs. Finishing/Support.
    • Quadrants:
      • Preseason × Core driver: Identity shock; systems scramble (e.g., a top-line center loss).
      • Preseason × Finishing/Support: Chemistry risk; PP2 tweaks; early-standings tax—Kuzmenko’s box. [13][14]
      • Midseason × Core driver: Trade-market pressure; cap gymnastics.
      • Midseason × Finishing/Support: AHL call-ups can patch; minimal systems churn.
    • Takeaway: Week‑1 loss of a finisher rarely dents xGF% in aggregate, but it bends coin-flip games when special teams and matchups are still unsettled. [14]
  • Named-stakeholder breakdown

    • Kyle Dubas (President/GM): Balances room culture and launch-week plans; his public stance prioritized player support over timelines, buying trust at the cost of short-term certainty. [9]
    • Dan Muse (Head Coach): Manages line continuity and PP2 roles; watch for Robertson absorbing Kuzmenko’s shooting reps while PP1 stays intact to avoid cascading disruption. [10][13]
    • Nicholas Robertson and Ben Kindel: Inherit offensive-zone starts and retrieval duties; one must shoulder more controlled entries to maintain finishing-quality looks. [13]
    • ESPN/TNT: The Sep 30 PHI–PIT window invites an empathy-forward segment, then shifts to who earns Kuzmenko’s minutes and whether PP2 changes generate a goal swing by October 10. [6][8]
  • A contrarian read

    • Consensus frames the hockey impact as minimal because it’s primarily a human story.
    • Counterpoint: Pittsburgh signed Kuzmenko to plug a finishing gap, and the first 11 days include two divisional road games; a two-goal special-teams swing across this span could decide a tiebreak in April in an 84‑game season. [6][14]

Sourcing context matters for reliability: REN TV supplies the Krasnaya River and four-hour transport claims later echoed by The Guardian and Yahoo, while Penguins.com and NHL.com attribute those details to Russian media and avoid embellishment, a standard risk-mitigation move when cross-border facts are still forming. [4][9][10]

What others are missing

The under-covered angle is roster-rule mechanics under the NHL–NHLPA CBA: if Kuzmenko is placed on the Non-Roster list, his $5 million cap hit still counts, but Pittsburgh can seek emergency recalls if it would otherwise dress fewer than 12 forwards and 6 defensemen; that pathway shapes Wilkes‑Barre/Scranton call-up timing more than any sentimental factors. [2][11] Broadcast windows also pressure clarity—TNT’s Sep 30 slot and ESPN’s early-week shoulder programming incentivize the team to issue status updates before puck drop in Philadelphia to preempt speculation. [6][8] Finally, the chain-of-custody on incident facts flows from REN TV to English-language outlets and then to team sites with attribution, so expect editors to wait for either a Russian police note or a family statement before adding any new field specifics. [4][9][10]

What to watch next

  1. By Friday, October 2, 2026, the Penguins either list Kuzmenko as Non-Roster on the NHL media notes or he appears on the game roster for at least one of the first two games (Sep 30 vs. PHI; Oct 3 vs. MTL). [11][14]
  2. Across Pittsburgh’s first three games (Sep 30–Oct 5), Nicholas Robertson averages at least 15:00 TOI per game and records at least one PP shot on goal, reflecting a Kuzmenko-role substitution. [13][14]
  3. The Sep 30 national broadcast (TNT) includes an on-air update segment naming REN TV as the origin of the field details or cites a team/NHL confirmation that limits specifics to time, place, and family status. [4][8]

Sources

[1] BBC Sport — Initial report on Andrei Kuzmenko leaving the Penguins to return to Russia after his father’s death in Tuva; age, location, practice-before-departure details.
[2] PuckPedia — Contract specifics for Kuzmenko’s one-year, $5 million 2026–27 SPC with Pittsburgh; cap and term context for roster decisions.
[4] REN TV (Russia) — Origin for Krasnaya River location and four-hour downstream transport; most granular incident narrative.
[6] ESPN — 2026–27 NHL opening-week schedule context, including late-September start and national windows.
[8] TNT/Warner Bros. Discovery Sports — PHI–PIT broadcast slot on Wednesday, September 30, 2026; production context for story framing.
[9] Penguins.com — Official team statement from President/GM Kyle Dubas confirming departure and organizational support.
[10] NHL.com — News note confirming Kuzmenko practiced before leaving and summarizing team messaging; timeline anchor.
[11] NHL–NHLPA CBA (Article 16 and roster/emergency-recall provisions) — Non-Roster status rules, emergency recall thresholds, and cap treatment.
[13] NHL.com (Team Reset/Depth Chart: Pittsburgh Penguins, 2026) — Kuzmenko’s projected role with Ben Kindel and Nicholas Robertson; Mantha exit framing and PP2 usage.
[14] NHL.com (2026–27 Penguins schedule page) — Opponent list and dates confirming six games between Sep 30 and Oct 10; compressed-window verification.




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.

Penguins’ Collapse: One Second Again | Analysis by Brian Moineau

One second, one collapse: How the Penguins handed away a win and another headache

The puck sits in the neutral zone. The clock flashes 0:01. The arena breathes a collective sigh of relief — this one is effectively over. Then chaos. A shorthanded dagger. A scramble in front. A puck that should never have crossed the line, and suddenly the scoreboard reads a tie. For the Pittsburgh Penguins, that slice of time — fractions of a second, really — has become maddeningly familiar.

On December 9, 2025, the Penguins watched a 4-3 lead evaporate with 0.1 seconds left as the Anaheim Ducks forced overtime and eventually won in the shootout. It wasn’t just a bad bounce or an unlucky tip. It was a failure of situational defense, personnel choices, and the recurring theme of “so close, yet not.” Players and coaches left the ice visibly disgusted — and with reason. This wasn’t an isolated heartbreak; it fits into a pattern that’s dogged the team since last season.

What happened in the final second

  • The Penguins led late and were on a power play. Conventional thinking: a team with possession and the man advantage should be able to protect a one-goal lead for the final seconds.
  • Instead, a shorthanded rush off a Penguins turnover culminated in Beckett Sennecke scoring with 0.1 seconds remaining to force overtime. The goal exposed defensive breakdowns — notably from Kris Letang and Erik Karlsson — who ended up out of position and was involved in the defensive collapse that preceded the finish. (pittsburghhockeynow.com)
  • The game proceeded to overtime and then a shootout, where the Ducks needed only one conversion to take the extra point.

Why this stings beyond a single loss

  • Frequency. This was the 11th time since last season the Penguins surrendered a late lead or loss in a shootout/OT situation — a pattern, not a fluke. Repetition reveals process problems. (pittsburghhockeynow.com)
  • Defensive configuration. Head coach Dan Muse trusted his top offensive defensemen in a late, delicate sequence. Letang and Karlsson are elite puck movers and play critical minutes in all situations — but when the scoreboard and clock demand conservative clearing and body-on-body coverage, their offensive instincts can leave seams exposed. Muse later acknowledged the tradeoff: on paper it’s defensible, in practice it proved costly. (pittsburghhockeynow.com)
  • Execution under pressure. The Penguins dominated play — a season-high 48 shots and lopsided expected-goal numbers — yet failed to bury enough of their chances and, crucially, failed to protect a lead in the final laps. High-quality play for long stretches doesn’t absolve mistakes at game-defining moments. (pittsburghhockeynow.com)

The bigger context: trending headaches for Pittsburgh

  • This outcome isn’t unique to one game. Media coverage and advanced stats have repeatedly flagged Pittsburgh’s difficulty closing games and their tendency to lose leads — a narrative that stretches back through the 2024–25 season and beyond. The trend appears both tactical and personnel-driven: defensive structure late in games, certain defensive pairings on the ice, and inconsistent finishing by the forward corps. (thehockeynews.com)
  • The coaching transition and lineup evolution complicate matters. Dan Muse is new-ish, bringing different habits and line preferences. Early evidence shows him empowering players and leaning on his top defenders — a modern approach — but one that requires precise execution and risk management in the waning seconds. When a coach is still building trust and identity, these late-game decisions carry an outsized effect. (pittsburghhockeynow.com)

Where the Penguins should look for fixes

  • Re-think who’s on the ice in the final 15–20 seconds. Possession plus a one-goal lead should prioritize stick-on-stick, body-on-body defending, and clearing lanes over offensive creativity. That probably means at least one more defensive-minded presence alongside whichever puck-handler is tasked with time-killing. (pittsburghhockeynow.com)
  • Drill the two-minute/closing sequences until they’re muscle memory. Cleaning up turnovers, location discipline, and small-stick plays near the net are teachable. They’re also repeatable under pressure if rehearsed. Players like Kris Letang and Erik Karlsson can still be used — but with explicit, simplified roles in those moments. (pittsburghhockeynow.com)
  • Clarify personnel matchups on special teams and late situations. If a defense pairing has shown “creative risk” tendencies, give them fewer matchups where a blown play immediately costs a game. Trust is earned; situational restraint can be temporary and tactical. (pittsburghhockeynow.com)
  • Convert more high-quality chances into goals. The Penguins out-chanced Anaheim 43–19 and created far more dangerous opportunities — but didn’t produce the necessary finishing. That’s a complementary problem: create the pressure and then finish it off so late-game slips are less impactful. (pittsburghhockeynow.com)

A few player grades (snap impressions from the game)

  • Arturs Silovs: Solid but unremarkable. Stopped what he needed to, but the team’s end-of-game collapse overshadowed his work. (pittsburghhockeynow.com)
  • Tommy Novak: One of his best games in a Penguins uniform — active, driving to the net, good shot totals. (pittsburghhockeynow.com)
  • Kris Letang / Erik Karlsson: Both gifted, both culpable in the final sequence. The moment exposed the risk of pairing two offensively minded defenders in the most dangerous seconds of a game. (pittsburghhockeynow.com)

My take

You can build teams a dozen ways, and modern NHL coaching often prizes versatility: offensive defensemen logging key minutes, forwards who can carry both zone starts, and hypothesized lineup continuity. But the scoreboard is the final arbiter. When a club repeatedly coughs up leads in the closing moments, it reveals where philosophical ideals bump into the reality of execution.

Dan Muse has earned latitude — he’s changing culture and getting results in many stretches — but trusting the same high-event defenders in every late-game scenario has shown a tangible downside. This is fixable. It’s not a roster meltdown or existential crisis; it’s attention to detail, coaching clarity, and a few shifts in end-game personnel and habits. The next time the clock hits :15 and the puck is in the Penguins’ hands, the margin between a win and a deflating “what-if” will be determined by choices that can be coached and practiced.

Final thoughts

Losing one like this is infuriating, especially when the team dominated most of the game. The good news: the underlying process — puck control, zone entries, shot volumes — often looked very good. The bad news: bad habits at the end of games have a way of eroding momentum and morale faster than an opponent’s comeback. If Pittsburgh addresses its late-game structure with urgency and practical adjustments, they’ll keep reaping the benefits of their strong play without handing away the final moments.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.

Penguins’ Streak Survives Chaotic Philly | Analysis by Brian Moineau

Penguins-Flyers ended bonkers: Two overturned OT goals, a post-horn scrum, and a shootout
If you thought the Battle of Pennsylvania might have mellowed with time, Tuesday night in Philadelphia was your reminder that this rivalry still cooks. The Penguins extended their point streak with a 3-2 shootout loss to the Flyers, but the path there? Pure chaos, right down to an overtime that saw goals wiped off for both teams and a scrum that left Sidney Crosby ineligible for the shootout.

Context and what set the stage

  • Form and stakes: Pittsburgh came in rolling, 5-0-2 in their previous seven and 7-2-2 overall after this one—banking points during a dense stretch of three games in four nights. Philadelphia, meanwhile, has been sturdy at home and looking to cement an early-season identity under Rick Tocchet.
  • The script: Justin Brazeau opened for the Pens with his sixth of the season, continuing a productive start for Pittsburgh’s “Big Boy Line” with Anthony Mantha and Evgeni Malkin. Special teams tilted the middle frames: the Flyers answered on a power play and then again shortly after a kill to go up 2-1.
  • Crosby’s equalizer: Because of course—No. 87 banked one in during the third to make it 2-2, the latest chapter in a career-long habit of tormenting Philly.
  • The wild overtime: Pittsburgh appeared to win it, but the goal was erased because Malkin hopped on early during a delayed penalty situation. Later, the Flyers’ would-be winner was overturned for offside. Then the horn. Then the scrum. Multiple misconducts on both sides meant several stars—including Crosby—couldn’t participate in the shootout.
  • The finish: Philadelphia converted twice in the skills contest; only Malkin scored for Pittsburgh. Still, the Penguins pocketed a road point behind a strong night from Arturs Silovs, who steadied them while they found their legs.

Why it mattered
Beyond the rivalry drama, this game offered a reality check and a roadmap. Pittsburgh didn’t have its best in the first 40 but tightened up in the third, leaned on goaltending, and found a way to stretch the game—exactly the kind of bank-a-point mentality that pays off later. It also spotlighted how thin the margins are when special teams and reviews swing outcomes.

Key takeaways

  • Penguins extend point streak despite the loss: 5-0-2 in their last seven, now 7-2-2 overall—valuable standings math on a back-to-back.
  • Goaltending stole the show for Pittsburgh: Arturs Silovs was the primary reason they escaped with a point after a choppy first two periods.
  • Crosby keeps setting the tone: His third-period equalizer reinforced a scorching start after recently hitting 1,700 career points.
  • Details decide overtime: One erased Penguins goal for an early change on a delayed penalty; one Flyers goal overturned for offside—discipline and video reviews loomed large.
  • Rivalry energy is alive: A multi-player scrum at the horn left key names, including Crosby, unavailable for the shootout—a tangible reminder of the series’ edge.

Final thought
If you’re Mike Sullivan, you don’t love the second period, but you love the response: structure in the third, poise in bedlam, and a point in the bank. If you’re a neutral, you loved every bit of the chaos. And if you’re a Penguins or Flyers fan, circle the rematch—these two just turned up the heat again.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.