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.


208151

Sgt. Arthur Langley Chisman

Royal Australian Air Force 460 Sqdn

from:East Finchley, London

(d.19th Oct 1944)

I knew that I had been named after my parent's best man at their wedding but had not investigated very far. They had told me he had died during the war and was in the Air Force. Both my parents are now dead and I was looking through old photos when I came across one with the name of their best man on it. In the past I had looked for Chisholm or similar but the actual spelling is Chisman. A little bit of investigation with the help of Google and http://www.ozatwar.com and I have found out the following: Their best man was Arthur Langley Chisman who joined 460 Squadron, Royal Australian Air Force flying Lancasters as Flight Engineer (only British aircrew were trained for this role). He was killed along with all but one of the crew of the Lancaster on 19th October 1944, leaving behind his wife Mary.



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.