Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Private plane carrying Post Malone makes emergency landing at New York airport

Two of the plane's wheels blew out during takeoff 

Chelsea Ritschel
in New York
Tuesday 21 August 2018 23:18 BST
Comments
Post Malone confirms he is safe after emergency plane landing (Getty)
Post Malone confirms he is safe after emergency plane landing (Getty)

Musicians Post Malone and Andrew Watt have safely landed after the plane they were on was forced to make an emergency landing.

The pair were aboard a Gulfstream plane headed to the UK from New Jersey’s Teterboro Airport when the plane began to malfunction during takeoff.

The rapper and Watt were among 14 other passengers aboard when two of the private jet's left tyres blew out.

After the pilot realised what had happened, he prepared for an emergency landing - burning off fuel as he headed for Westfield Barnes Regional Airport in Springfield, Massachusetts before diverting and landing safely at Stewart International Airport in New Windsor, New York.

Malone, 23, whose real name is Austin Post, confirmed his safety on Twitter, where he also responded to those who had wished him harm.

“I landed guys. Thank you for your prayers. Can’t believe how many people wished death on me on this website. f*ck you. But not today,” the Rockstar singer tweeted.

Malone was originally headed for London Luton Airport, according to People magazine, where he is supposed to perform Friday at the Reading Festival in Reading, England.

The rapper’s manager Dre London was also reportedly on board the plane.

Gulfstream IV jets, the type of aircraft Malone was reportedly on, are typically used for business travel, and can hold more than 12 passengers.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in