Duke of Buccleugh (1831 ship)

Duke of Buccleugh was an East Indiaman launched in 1831. She made one voyage for the British East India Company (EIC) and then traded between England and India until she was lost in 1840.

For other ships with the same name, see Duke of Buccleugh (ship).

The East India Ship 'Duke of Buccleuch', (Captn Alexr Henning) in a Hurricane off the Mauritius, attempting to wear; George Philip Reinagle, Edward Duncan, & W.J. Wade – National Maritime Museum, Greenwich
History
United Kingdom
Name: Duke of Buccleugh
Namesake: Duke of Buccleuch
Owner: Robert Green
Builder: Green, Wigram's & Green, at Blackwall.
Launched: 14th April 1831
Fate: Wrecked 1840
General characteristics
Tons burthen: 576​1⁄94[1] or 618​2⁄94,[2] or 619[3] (bm)
Length: 135 ft 6 in (41.3 m)
Beam: 31 ft 7 in (9.6 m)
Depth of hold: 10 ft 6 in (3.2 m)

EIC voyage (1831–1832): The EIC chartered on 29 April 1831 for £8 9s per ton for a voyage to Bengal and return.[4] Captain Alexander Henning sailed from the Downs on 10 June. Duke of Buccleugh reached Madras on 22 September, and arrived at Calcutta on 10 October. Homeward bound, she was at Madras on 18 January 1832 and the Cape on 10 March. She reached St Helena on 30 March and arrived back at her moorings on 8 May.[3]

From 1832 to 1840 Duke of Buccleugh was in private trade to India.

Fate: In 1840 she wrecked on Palmira Reef, near Calcutta.[1]

Citations and references

Citations

  1. Green, Wigram's & Green Ship builders and ship owners: Duke of Buccleugh.
  2. Hackman (2001), p. 93.
  3. British Library: Duke of Buccleugh (2).
  4. Hardy (1835), p. 162.

References

  • Hackman, Rowan (2001). Ships of the East India Company. Gravesend, Kent: World Ship Society. ISBN 0-905617-96-7.
  • Hardy, Horatio Charles (1835). Supplement to a Register of Ships Employed in the Service of the ... East India Company from 1760 to the Conclusion of the Commercial Charter, Etc.
gollark: Thus, THOUGHTS WANTED.
gollark: I had another idea, which was to not have virtual channels and just have virtual point-to-point links then use magic™ to find connected subgraphs of things, but this would also be complex.
gollark: Is it to just maintain a list of "bridging" links and do inter-virtual-channel routing on those? This would be a bit flaky and complex I think.
gollark: Is the system to just merge the virtual channels? This would be problematic to unmerge later.
gollark: But then I realized that this had a significant problem; what happens if virtual channels A and B both connect to Discord channel 124091724?
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.