Lieutenant-Colonel Lord Alexander George Boteville Thynne MP

Alexander Thynne from the Roll of Honour published in The Illustrated London News on 28 September 1918.

Lord Alexander George Boteville Thynne, (17 February 1873 – 16 September 1918), was an army officer and Conservative Party politician.

The third and youngest son of the 4th Marquess of Bath, and his wife Frances Isabella Catherine (née Vesey).

In 1898 failed to win a seat on the London County Council at Islington North. In 1899 he was elected unopposed to the London County Council as a Moderate Party councillor, filling a casual vacancy in the representation of the City of London. He did not defend the seat in 1901, having been commissioned in the Imperial Yeomanry following the outbreak of the Second Anglo-Boer War in 1899, and was serving in South Africa with the 1st (Wiltshire) company of the 1st Battalion. He was later a temporary Lieutenant-Colonel in the Service Battalion of the Wiltshire Regiment and served in the Somaliland campaign of 1903 to 1904.

Returning to Britain, he was elected to the London County Council in 1907 as a Municipal Reform Party councillor for Greenwich.

In January 1910 he was elected to the House of Commons as one of two MPs for Bath.

In March 1910 he was re-elected to the county council, this time as a councillor for Marylebone East.

During the First World War he served with the Royal Wiltshire Yeomanry and was twice wounded at the Battle of the Somme in 1916. The yeomanry were converted to infantry in 1917 as the 6th Battalion of the Wiltshire Regiment. He was killed in action in France with the battalion aged 45.[1] He held both his council and parliamentary seats until his death.

Notes Edit

  1. Thynne, Lord Alexander George. Commonwealth War Graves Commission.

Article in Wikipedia [1].

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.