Old Leake W.5667 Memorial
Old Leake, Lincolnshire
Help us verify this location. This memorial's position is not yet precisely confirmed. If you have local knowledge, photographs, or documentary evidence of the exact site, we'd love to hear from you.
Location
Old Leake, Lincolnshire, Lincolnshire
what3words: ///finishing.tungsten.buzzer
Aircraft & Operation Details
Crew
Memorial Details
Memorial Care
Local Contacts
These local organisations are connected to this memorial and may be able to help with information or visits.
Local remembrance and memorial support
Local authority responsible for memorial upkeep
Further Reading
Forum discussion documenting the Wellington crash at Old Leake on 6-7 February 1943, with contributions from researchers and local historians providing details about the crew and circumstances.
Crash date confirmed as February 194314 OTU unit confirmedFive crew killed
Yorkshire Aircraft database entry for Wellington W5667, recording the aircraft's history including construction by Vickers Armstrongs at Weybridge, reception by 22 MU on 13 March 1941, and transfer to 14 OTU at Cottesmore on 6 November 1942 before its loss.
Built by Vickers Armstrongs, WeybridgeReceived by 22 MU on 13 March 1941Transferred to 14 OTU Cottesmore 6 November 1942Cat.E2/FA Burnt damage classification
Geograph article on East Anglia WW2 aircrew crash memorials including the Old Leake Wellington memorial, as part of a comprehensive survey of Lincolnshire bomber crash sites.
Listed among Lincolnshire crash memorials survey
Sources
- Geograph(website)
Credits & Acknowledgements
Nearby Memorials
Do you have additional information, photographs, or corrections for this record? We welcome contributions from researchers, families, and local communities.
Suggest a correction or additionCan You Help Complete This Record?
This record for Old Leake W.5667 Memorial is partially complete. We’re looking for additional details such as crew information, photographs, narrative history, or source references.
Email admin@bombermemorial.co.uk or contribute directly via our GitHub repository