There follows below a list of the all of the operations flown by 550 Squadron and the aircraft involved on each. The information used to build this page was taken in the first instance from the lists provided on the original Squadron Association web-site, but has been augmented by new information gathered since that time (squadron operations logs, individual aircrew log books, and other sources).
This information is not yet complete: it has been build from the a number of sources (documentary and people) and compilation of complete lists is an ongoing task that is expected to take quite some time to complete. So please don't shout just yet if you spot an omission - work continues to build a more complete, and accurate, list.
Do however shout if you spot an error! Please email any corrections or information to the contact details in the link at the bottom of the page.
Operation Summary: The column headers should be fairly self-explanatory. The term "aborted" as used here covers a number of possibilities:
Aircraft Deployed: When a link to a particular aircraft is given, this indicates aircraft known to have taken part in this raid (in the records currently available to the web-site author). A record of whether the aircraft returned or failed to return (FTR) is also logged.
Servicemen Deployed: Names of the crew in the operation.
Station Summary: This section is the information from the RAF North Killingholme Station Record Book for the operational date (if available).
Definitions of the abbreviations used are available: here.
The amount of data in the database is growing and this is resulting in the "all operations/targets" list getting rapidly bigger and thus slower to generate. There are options to display shorter, more quickly generated, reports if you want to home in on something specific. For example, there are options to generate reports on operations to a single target, or by single aircraft (to all targets) or by single aircraft to a single target. There is, on the database-reports summary page, a short user guide (PDF format) on how to do this.
(Y / N)
|Hildesheim||22 Mar 1945||22 Mar 1945||N||The Squadron was called to put up 16 aircraft on operations. All took off without incident at approx. 11.30 hours. The attack, a small one, was on HILDESHEIM, 20 miles SE of Hannover. Formation, outward bound to the target, was good in almost perfect weather conditions. Although the leader took the main force rather close by Osnabruck and Hanover, there was an almost complete absence of flak at the target and crews had no difficulty in visually identifying it, marked in an accurate and concentrated style. Soon the Master Bomber had to give directions to aim wiht the smoke as a guiode and within a few minutes the whole of the built up areas was a mass of smoke and dust. The smoke, rising to 15000 ft, could be seen from 200 miles. "C2" (F/L Parsons) was hit by heavy flak and had two fuel takes holed, "L" (F/S Wilson) was hit by incendiaries over the target, the port wing tip and aileron being damaged. All the Squadron's aircraft returned safely to base. F/O Davidon DFC and his crew completed their tour with this operation. 4 aircraft and crews on the flying training programme spent 14 hours in the air.|
|Aircraft Deployed||Servicemen Deployed||Aircraft Service Number||Returned
|Comments||Crew Details||ME540||Returned||Primary at 15,000 ft at 14.04||
F/O G E Mearns (P)
Sgt F Norris (F/Eng)
F/Sgt W G Kelly (Nav)
Sgt J F McKeen (A/B)
Sgt D O'Neil (W/Op)
Sgt A Colin (R/AG)
Based on the data in the lists displayed above, and keeping in mind that data is still being updated and thus not yet complete, the following statistics are generated:
|MAX Aircraft deployed
in single operation
(Hildesheim, 22 Mar 1945)
These details were last updated: 01 March 2021
this list is still being built and will take some time to complete
what is currently displayed is believed accurate but much more is still to be added
This note describes the options currently available to produce a smaller, more manageable list and also describes planned future enhancements to the reporting facility.
Return to the top of the page.