Add Information to Record of a Person who served during the Second World War on The Wartime Memories Project Website

Add Information to Record of a Person who served during the Second World War on The Wartime Memories Project Website



Additions will be checked before being published on the website and where possible will be forwarded to the person who submitted the original entries. Your contact details will not be forwarded, but they can send a reply via this messaging system.


225284

Sgt. R. C. Findlayson

Royal Air Force 166 Squadron

Because of a soldier's bible, I am involved with Tain Museum in the north of Scotland and have become involved in researching a Roderick Finlayson who was a piper in the First World War. Members of his family moved to Aberdeen-shire and I have established that a Rory Finlayson (possibly a nephew) left the area about 1939 to join the RAF to be a pilot. (Rory may be a family name for Roderick)

I have received a copy extract from Bomber Command Losses 1945. On page 93 it relates that Lancaster 111 from 166 Squadron, operating out of RAF Kirmington was shot down over Pforzheim; two of the crew survived; one being a Sgt. R. C. Finlayson who became a POW. On page 206 listing POW's Jan - May 1945 and under Squadron 166 Sgt. R.C. Finlayson is also listed there. I am trying to confirm if Sgt. Finlayson is a a member of the family I am researching. Can anyone help?



Please type your message:     

We recommend you copy the text about this item and keep a copy on your own computer before pressing submit.
Your Name:            
Email Address:       @

**Please type the first part our your email in the first box (eg. john.smith) the @ sign is added automaticallly, please type the second part in the second box (eg. gmail.com). Do not enter your full email in each box or add an @ sign or random spaces.**

Please type in the code shown here: CAPTCHA Image   

If you are unable to read the code please click here.

If you have received an error message for incorrect code, please click to refresh the code before resending. This should overcome the error message.