Retracing Mackenzie Shirilla’s ‘Hell on Wheels’ drive — and the tiny clue about what really happened at crash site
US News exclusive Retracing Mackenzie Shirilla’s ‘Hell on Wheels’ drive — and the tiny clue about what really happened at crash site By Georgia Worrell Published June 9, 2026, 7:30 a.m. ET See more of our coverage in your search results. Add The New York Post on Google STRONGSVILLE, Ohio – The spot where “Hell on Wheels” driver Mackenzie Shirilla smashed into a building at 100 mph, killing her boyfriend and a close pal, has been repaired and manicured in the years since the headline-grabbing crash.
- ▪US News exclusive Retracing Mackenzie Shirilla’s ‘Hell on Wheels’ drive — and the tiny clue about what really happened at crash site By Georgia Worrell Published June 9, 2026, 7:30 a.m.
- ▪ET See more of our coverage in your search results.
- ▪Add The New York Post on Google STRONGSVILLE, Ohio – The spot where “Hell on Wheels” driver Mackenzie Shirilla smashed into a building at 100 mph, killing her boyfriend and a close pal, has been repaired and manicured in the years since the
New York Post files mainly under news. We currently carry 9,559 of its stories.
Opening excerpt (first ~120 words) tap to expand
US News exclusive Retracing Mackenzie Shirilla’s ‘Hell on Wheels’ drive — and the tiny clue about what really happened at crash site By Georgia Worrell Published June 9, 2026, 7:30 a.m. ET See more of our coverage in your search results. Add The New York Post on Google STRONGSVILLE, Ohio – The spot where “Hell on Wheels” driver Mackenzie Shirilla smashed into a building at 100 mph, killing her boyfriend and a close pal, has been repaired and manicured in the years since the headline-grabbing crash. A large oak tree now stands in the spot where Shirilla blasted through a stop sign and crashed her 2018 black Toyota Camry into a building at 5:30 a.m. on July 31, 2022, after a sleepover at another friend’s house.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at New York Post.
Discussion
0 commentsMore from New York Post
