Skip to main content
Canada’s most-awarded newsroom for a reason
Enjoy unlimited digital access
$1.99
per week
for 24 weeks
Canada’s most-awarded newsroom for a reason
$1.99
per week
for 24 weeks
// //

Columbus Blue Jackets goaltender Matiss Kivlenieks has died at the age of 24.

Kathy Willens/The Associated Press

A medical examiner in Michigan says an autopsy has determined that Columbus Blue Jackets goaltender Matiss Kivlenieks died of chest trauma from an errant fireworks mortar blast and not a fall as authorities previously reported.

Police in Novi, Mich., said the mortar-style firework tilted slightly and started to fire toward people nearby Sunday night. The 24-year-old Kivleniek was in a hot tub and tried to get clear with several other people, police Lieutenant Jason Meier said.

The fire department and EMTs got to the private home shortly after 10 p.m. and took him to a hospital, where he was pronounced dead, Meier said. The Oakland County Medical Examiner’s office reported preliminary autopsy results Monday afternoon.

Story continues below advertisement

Prior to the autopsy, police said Kivlenieks was believed to have slipped and hit his head on concrete while running from a malfunctioning firework.

“At the moment, we’re pretty certain this was a tragic accident,” Meier said.

The Blue Jackets and Latvian Hockey Federation announced Kivlenieks’s death, with the NHL club saying it resulted from an apparent head injury in a fall. The team’s statement made no mention of fireworks.

Columbus general manager Jarmo Kekalainen tweeted: “Life is so precious and can be so fragile. Hug your loved ones today. RIP Matiss, you will be dearly missed.” Blue Jackets president of hockey operations John Davidson called it a “devastating time” for the team.

“Kivi was an outstanding young man who greeted every day and everyone with a smile and the impact he had during his four years with our organization will not be forgotten,” he said.

“What a tragic loss for all of us who knew him and I am thinking and praying for his family,” former Blue Jackets captain Nick Foligno tweeted. “Heaven gained a darn good goalie and better person Just, way too soon.”

Former Columbus defenceman David Savard learned of it from Foligno.

Story continues below advertisement

“That was a brutal wake-up this morning,” Savard said in French. “That was a good kid with a lot of talent who was going to be a part of the team next year or in the future. That’s extremely sad.”

Kivlenieks’s death came on the eve of Game 4 of the Stanley Cup Final in Montreal, where the Tampa Bay Lightning had a chance to clinch the championship against the Canadiens on Monday night.

NHL commissioner Gary Bettman said Kivlenieks’s “love for life and passion for the game will be deeply missed by all those who have been fortunate to have him as a teammate and a friend.”

The Latvian Hockey Federation called Kivlenieks’s death “a great loss not only for Latvian hockey but for the entire Latvian nation.”

Kivlenieks most recently represented Latvia this spring at the world hockey championship in which he played four games. He played two games for the Blue Jackets and eight for the American Hockey League’s Cleveland Monsters this past season.

A native of Riga, Latvia, Kivlenieks signed with the Blue Jackets as a free agent in May, 2017 and played eight games for the club overall. He was seen as a possible No. 2 goaltender next season if Joonas Korpisalo or Elvis Merzlikins is traded.

Story continues below advertisement

Kivlenieks was at Mid-Ohio Sports Car Course in Lexington, Ohio last Tuesday as a guest of IndyCar driver Alexander Rossi.

Rossi announced that day he was going to race the Baja 1000 in Mexico in November and Kivlenieks took a ride around Mid-Ohio in a Honda Ridgeline to help promote both Rossi and Sunday’s IndyCar race.

“This hits hard,” Rossi tweeted. “Prayers to the family and the team.”

Your Globe

Build your personal news feed

  1. Follow topics and authors relevant to your reading interests.
  2. Check your Following feed daily, and never miss an article. Access your Following feed from your account menu at the top right corner of every page.

Follow topics related to this article:

View more suggestions in Following Read more about following topics and authors
Report an error
Due to technical reasons, we have temporarily removed commenting from our articles. We hope to have this fixed soon. Thank you for your patience. If you are looking to give feedback on our new site, please send it along to feedback@globeandmail.com. If you want to write a letter to the editor, please forward to letters@globeandmail.com.

Welcome to The Globe and Mail’s comment community. This is a space where subscribers can engage with each other and Globe staff. Non-subscribers can read and sort comments but will not be able to engage with them in any way. Click here to subscribe.

If you would like to write a letter to the editor, please forward it to letters@globeandmail.com. Readers can also interact with The Globe on Facebook and Twitter .

Welcome to The Globe and Mail’s comment community. This is a space where subscribers can engage with each other and Globe staff. Non-subscribers can read and sort comments but will not be able to engage with them in any way. Click here to subscribe.

If you would like to write a letter to the editor, please forward it to letters@globeandmail.com. Readers can also interact with The Globe on Facebook and Twitter .

Welcome to The Globe and Mail’s comment community. This is a space where subscribers can engage with each other and Globe staff.

We aim to create a safe and valuable space for discussion and debate. That means:

  • Treat others as you wish to be treated
  • Criticize ideas, not people
  • Stay on topic
  • Avoid the use of toxic and offensive language
  • Flag bad behaviour

If you do not see your comment posted immediately, it is being reviewed by the moderation team and may appear shortly, generally within an hour.

We aim to have all comments reviewed in a timely manner.

Comments that violate our community guidelines will not be posted.

UPDATED: Read our community guidelines here

Discussion loading ...

To view this site properly, enable cookies in your browser. Read our privacy policy to learn more.
How to enable cookies