Jordan Vogt-Roberts directed Kong: Skull Island. Jordan Vogt-Roberts burned himself severely. These are two things that did in fact happen. It would seem obvious to connect these dots together but to be fair, that's just not how it all worked out. While the set of a massive action film like Kong might be the place one might expect to get their face burned off, the story of how Vogt-Roberts ended up in intensive care is a bit more mundane, if no less serious.
So, while a great story about a massive Kong: Skull Island special effect that went haywire would make for a better story, Jordan Vogt-Roberts is forced to admit to Uproxx that the reality wasn't nearly that. There was no suffering for his art here. Just suffering apparently.
The accident took place about two years ago. It was January of 2015 when the director informed the public via social media that he'd been seriously burned. He posted an image of his burned hand as well as his completely bandaged face. The good news, if there was any, was that most of his face was apparently saved by his beard.
Now, following two years of healing, Jordan Vogt-Roberts is about to see the long process of Kong: Skull Island finally come to an end. The film is set for release this Friday and sees Tom Hiddleston and Brie Larson travel to the home of one of the most famous monsters in the history of film. Kong takes place in the same universe as the recent Godzilla, a fact which will eventually lead to the two behemoths meeting on screen at some point down the road.
Early reviews have been mostly positive, which hopefully will help make those burn scars hurt a little bit less. Jordan Vogt-Roberts next project will be a movie based on the Metal Gear Solid video game. Hopefully, he will receive fewer injuries during that project.
CinemaBlend’s resident theme park junkie and amateur Disney historian. Armchair Imagineer. Epcot Stan. Future Club 33 Member.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.