STOWE, Vt. — Vail Resorts has been fined more than $27,000 for safety violations after a Stowe Mountain Resort employee was thrown from a zip line ride and died last fall.
Scott Lewis, 53, of Stowe hit the anchoring platform that was holding the line and could not be revived on Sept. 23, police said.
Investigators found that a component of the lanyard supporting Lewis had not been properly inspected or replaced as the manufacturer recommended, WCAX-TV reported. Investigators also found in the report last month that the resort failed to provide training to each employee required to use the equipment, the news station reported. The report also noted that Lewis was traveling at more than 80 mph.
“The employer did not furnish employment and a place of employment which were free from recognized hazards that were causing or likely to cause death or serious physical harm to employees,” the report said.
Vail Resorts, the parent company of Stowe, said it continues to work with Vermont authorities concerning the accident.
“Safety is our highest priority, and Stowe Resort and the entire Vail Resorts family extend our deepest sympathy and support to this employee’s family and friends,” Vail said.
The zip line course will remain closed for an indefinite amount of time, the report said.
Comments are not available on this story. Read more about why we allow commenting on some stories and not on others.
We believe it's important to offer commenting on certain stories as a benefit to our readers. At its best, our comments sections can be a productive platform for readers to engage with our journalism, offer thoughts on coverage and issues, and drive conversation in a respectful, solutions-based way. It's a form of open discourse that can be useful to our community, public officials, journalists and others.
We do not enable comments on everything — exceptions include most crime stories, and coverage involving personal tragedy or sensitive issues that invite personal attacks instead of thoughtful discussion.
You can read more here about our commenting policy and terms of use. More information is also found on our FAQs.
Show less