Prince Harry's Motorcade Caught in a High-Speed Crash




Prince Harry's Motorcade Caught in a High-Speed Crash - Prince Harry was headed to the Invictus Games on Thursday, Sept. 11, when a vehicle in his motorcade was involved in a high-speed crash.

The Telegraph UK reported that one of Harry's police outriders collided with a white Toyota Prius. One eyewitness told the paper that the Range Rover carrying Prince Harry took "evasive action."


Prince Harry's Motorcade Caught in a High-Speed Crash

The paper reported that Harry's driver allegedly feared a possible terrorist attack, and "steered his vehicle through the damaged vehicles at speed before coming to a stop several hundred feet up the road."

According to the Telegraph, Prince Harry, 29, asked his motorcade to stop, but his security personnel advised they drive on. Firefighters had to cut the roof off the Prius to take the driver out of the damaged vehicle. Officers, not in Harry's car, stopped to help the injured parties.

A spokesperson for Harry told the Telegraph late Thursday, "The prince was obviously very concerned and wanted to make sure the men were okay. He is relieved to hear they are both in a stable condition."

A spokesperson for Scotland Yard also updated reporters on the incident and the drivers' conditions. "The police motorcyclist was displaying warning lights, as it was providing security escort at the time," the spokesman said.

"The male rider of the police motor vehicle suffered injuries. He has been taken to hospital for treatment. His condition at this early stage is described as stable. The male driver of the Prius also suffered injuries. He was taken to hospital for treatment. His condition at this early stage is also described as stable. The condition of the injured parties is not thought to be life threatening at this stage. Police officers remained at the scene and provided assistance."

This article originally appeared in : Prince Harry's Motorcade Caught in a High-Speed Crash | usmagazine.com | September 12, 2014 10:25 AM




No comments:

Post a Comment