Bomber Command Memorial Register

Short Stirling W7628

149 SquadronKentStirling

Cliffe, Rochester Upon Medway

Good Record

The Memorial

Type
Obelisk
Inscription
149 SQDN in Memory of Those Killed in the Crash of Stirling Bomber W76280JB in Cliffe on the 24th October 1942 [crew names listed on memorial]

Location

Cliffe, Rochester Upon Medway, Kent

Community Connection

Every memorial has a story — why it was built, who campaigned for it, and what it means to the local community. If you know the story behind this memorial, we would love to hear it.

Share this memorial's story

Remembrance

Do you know of any commemorative events or annual services held at this memorial? We would love to hear from local communities who remember.

Share remembrance information

Aircraft & Operation Details

Aircraft Type
Stirling
Serial Number
W7628
Squadron
149 Squadron
Date of Loss
1942-10-24

Crew

We don't yet have crew details for this memorial. Do you know who served aboard this aircraft?

Family connections, service records, or details from the memorial inscription would help us honour these crew members by name.

Share crew information

Nearby Memorials

Handley Page Hampden P4399
11.8 miles away
Kent
Greensted Juxta Ongar Lancaster Memorial
20.4 miles away
Essex
Aircrew of Lancaster PB512
20.4 miles away
Essex
Australian Aircrew Lost Over Europe
28.0 miles away
Greater London
Short Stirling LK116
28.7 miles away
Essex

Sources

IWM War Memorials Register (official_database)
Credits & Acknowledgements
Record compiled by
IWM War Memorials Register
Last updated 2026-04-12

Do you have additional information, photographs, or corrections for this record? We welcome contributions from researchers, families, and local communities.

Suggest a correction or addition

Can You Help Complete This Record?

This record for Short Stirling W7628 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