Maritime record MHG54706 - Brisk: Wick Harbour, Wick Bay, North Sea

Summary

No summary available.

Location

Grid reference ND 368 505 (point)
Map sheet ND35SE
Geographical Area MARITIME

Map

Please click on the map to select a feature
100 m
100 m

  • Center map here
  • Add a marker
  • Zoom in
  • Zoom out

Type and Period (1)

Full Description

RCAHMS Canmore description:
ND35SE 8146 c. 368 506
N58 26.3 W3 5.1
NLO: Wick Bay [name centred ND 376 506]
Wick [name: ND 362 508].
(Classified as Auxiliary Lugsail [lugger]: no cargo specified, but registration cited as WK 96, and date of loss as 31 October 1920). Felicity: this vessel was damaged in a storm at Wick Harbour, and broken up. Capt. McDonald.
Registration: Wick.
(Location of loss cited as N58 26.33 W3 5.00).
I G Whittaker 1998.
The location assigned to this record is essentially arbitrary. Wick or Pulteneytown Harbour (ND35SE 66.00) is centred at ND 36820 50670.
The remains of this vessel were evidently removed without delay from this constrained location.
Information from RCAHMS (RJCM), 25 November 2010. <1>

Sources/Archives (1)

  • <1> Dataset: RCAHMS. 01/2011. Annual update from Canmore. Digital.

Finds (0)

Protected Status/Designation

  • None recorded

Related Monuments/Buildings (0)

Related Events/Activities (0)

Record last edited

Apr 26 2011 11:30AM

Comments and Feedback

Do you have any questions or more information about this record? Please feel free to comment below with your name and email address. All comments are submitted to the Heritage Portal maintainers for moderation, and we aim to respond/publish as soon as possible. Comments, questions and answers that may be helpful to other users will be retained and displayed along with the name you supply. The email address you supply will never be displayed or shared.

This site is using a trial version of cloudscribe TalkAbout Comment System

Please purchase a license activation to remove this message

Be the first to comment!
Log in Log in to post a comment You can post new comments as Guest, but you must login to reply to comments.