UK embassy apologises for 'burning White House' tweet

@UKinUSA tweet The controversial tweet was posted on Sunday

Related Stories

The British embassy in Washington has apologised after tweeting a picture of a White House cake surrounded by sparklers, "commemorating" the burning of the building 200 years ago.

The US presidential residence was set on fire by British forces in 1814 during the "War of 1812" with the United States.

A number of Twitter users said the embassy's tweet was "in poor taste".

The embassy later said: "Apologies for earlier Tweet."

It added: "We meant to mark an event in history & celebrate our strong friendship today."

'Only sparklers!'

British troops led by Maj Gen Robert Ross attacked and burned public buildings including the Capitol, Washington Navy Yard and the president's mansion during the conflict.

It was the only time that a foreign power has captured and occupied Washington.

The offending tweet on Sunday read: "Commemorating the 200th anniversary of burning the White House. Only sparklers this time!"

The British embassy message, published on its official Twitter account, has been retweeted more than 4,000 times.

One user questioned: "Is this suppose [sic] to be funny"?

Another wrote: "I think this is in extremely POOR TASTE."

An apology was issued on the account two hours after the original message.

More on This Story

Related Stories

More US & Canada stories

RSS

Features

  • photo of patient zero, two year-old Emile OuamounoPatient zero

    Tracking first Ebola victim and how virus spread


  • A young Chinese girl looks at an image of BarbieBarbie's battle

    Can the doll make it in China at the second attempt?


  • Prosperi in the 1994 MdSLost in the desert

    How I drank bat blood and urine to survive in the Sahara


  • Afghan interpetersBlacklisted

    The Afghan interpreters left by the US to the mercy of the Taliban


  • Flooded homesNo respite

    Many hit by last winter's floods are struggling to pay soaring insurance bills


BBC © 2014 The BBC is not responsible for the content of external sites. Read more.

This page is best viewed in an up-to-date web browser with style sheets (CSS) enabled. While you will be able to view the content of this page in your current browser, you will not be able to get the full visual experience. Please consider upgrading your browser software or enabling style sheets (CSS) if you are able to do so.