Steve Suddaby has been compiling a database of Allied bombing missions over the Western Front, which he has generously offered to make available to any other researchers who may find it of value.
You may download a copy (in Excel .xlsx format) here. His notes follow, and may be downloaded here.
Care and Feeding of the
Suddaby Western Front Bombing Database
I am offering this database of Allied bombing raids on the Western Front as a research tool for anyone studying the First World War. It should be useful for determining what bombing units were flying in what vicinity on a particular day, what their losses were, what places got bombed, the casualties and property damage that occurred, and so on.
General Observations about the Database
The database contains almost 7000 records of bombing raids and reports from the American Bombing Survey (ABS) on air raids, alerts, damage, casualties, etc. It represents over 20 years of work, but I have not copyrighted this to make it as accessible as possible to researchers. You should feel free to download it, re-sort it, make calculations from it, whatever. I would be grateful, though, if you’d be kind enough to cite it in publications when you do use it (Suddaby Western Front Bombing Database, www.overthefront.com, downloaded [date]).
It is important to understand that in almost every way, this is only a partial record of bombing on the Western Front. The raids listed (French, British, American, and Italian) are concentrated in the Rhineland and in areas reachable from the French and later American sectors of the Western Front. It records relatively few raids flown in Flanders (i.e., from the British and Belgian sectors of the front). There were many French bombing raids that are not included because their unit war diaries were not put on the web by the French government.
Even though it was a herculean effort, there are many gaps in the data collected by the American Bombing Survey. The US Air Service personnel who conducted that survey could only visit locations west the Rhine because the Allied occupation did not take place farther east with only the exception of a few bridgeheads. Information on bombing raids against German aerodromes and against rail stations closer to the front lines often could not be collected because the German army had taken it with them when they retreated. For reasons that are not clear, many locations recorded human casualties but not property damage or vice-versa. Many factories in particular were meticulous in recording direct damage from bombs falling, lost production costs, and duration of time they were shut down, but kept no records of employees killed or wounded. (Go figure…) In a row containing ABS data (showing what happened on the ground), the first few cells are in turquoise to easily distinguish them from the data about aircraft dropping bombs. The original data for the ABS can be found most easily on the website www.fold3.com in the Gorrell Papers, Section R, Investigation of Damage Done by Allied Bombing. (There is a charge to use this data, but it’s still easier than buying and slogging through the microfilm like I did in the 1990s.)
I should point out that some of the data is complete. All of the raids of Britain’s Independent Force and the RNAS No.3 Wing are listed. Also complete are the raids of the French Groupe de Bombardement 1 (GB1), the original GB2, and bombing attacks by French dirigibles.
Important Details You Need to Understand to Use the Database
Down-in-the-Weeds Descriptions of Each Data Element
The information below can be seen in the spreadsheet itself by passing the cursor over the column headings. When you do that, a Comment box will appear. The information there is being printed below so you can also use this document to look up the descriptions of the data.
Cells A-E are in white if they are a record of bombs being dropped. They are in turquoise if they are bombing survey data that indicates what happened when the bombs hit the ground.
A night raid might be described in the records as being over the night of, say, 3/4 November 1916. If so, the date given here is 3 Nov. 1916. For the bombing survey data (turquoise color), it might be known precisely that the target was attacked at 0230 hours the morning of 4 Nov. 1916, so the survey data would be listed on that date rather than 3 Nov. This means that the sorting of the database might put the results of the raid (turquoise) one full day after the report of the bombing squadron instead of immediately after it.
[Self-evident. No comment written.]
Numbers w/o letters are British squadrons. Most other labels are for French escadrilles or groupes. A few are US Air Service squadrons (e.g., US20) or Italian (It.) Gruppo XVIII.
If "Yes", the entire mission was aborted without dropping any bombs.
Targets in Alsace - Lorraine often had German names as well as French names, e.g. Treves or Trier. Sometimes the alternate name is given in column AI.
Semicolons are used in this column and the Target Location column to keep track of multiple entries.
For example, Location entry is A,B,C; D,E and Target Description is Airfields; Rail Stns.
This means the squadron hit airfields at A, B, C and rail stations at D & E.
T=Tactical (troops, camps, ammo dumps)
If a summary entry contains more than one target type and over 50% of the bomb weight falls on one type, then the entry is assigned that target type. "O" is used as a last resort where distribution of bombs is unknown or no target type is in the majority.
Used for US Bombing Survey entries. 1 is an actual raid; 0 is just an alert where no bombs were dropped.
Summary Rec (T/F) or Comments
Marked TRUE if entry is a summary for an entire unit where multiple locations were bombed. This field and "Complete" allow keeping some stats on a complete squadron (like how many reached any target) and keeping stats on the bombs that fell on any one location. For many single entries, however, I don't use this field and simply put comments here. Otherwise comments can be found in Column AL.
Marked TRUE if entry is a complete record for what the unit did on that raid.
Bomb Wgt (LB)
Bomb weight in lbs actually dropped on target(s). Doesn't include bombs carried on planes that returned to base or were shot down without dropping bombs. If this is blank, the bomb weight is unknown, not 0. If cell is in light green, this is an estimate. I rarely made estimates - only when I had very good info upon which to base an estimate.
Number of bombing sorties. A bomber that took off twice to attack targets twice in one night is counted as 2 sorties even if one of the two resulted in aborting due to mechanical problems. Fighter escorts that carry no bombs are not counted anywhere in this database, though they may be mentioned in the comments. If this entry is blank, it is unknown rather than 0.
# of sorties that resulted in the bomber returning w/o dropping bombs on any recognizable target due to weather.
# of sorties that resulted in the bomber returning w/o dropping bombs on any recognizable target due to mechanical trouble.
# of sorties that resulted in the bomber returning w/o dropping bombs on any recognizable target due to any other reason like getting lost, airsickness, etc.
# of aircraft (sorties) diverted to a secondary target due to weather.
# of aircraft (sorties) diverted to a secondary target due to mechanical trouble.
# of aircraft (sorties) diverted to a secondary target due to crew disorientation (getting lost).
# of planes (sorties) that dropped bombs on SOME recognizable target. This cell being blank means that the number is unknown.
# of aircraft missing. This number is zero if I was positive no a/c were missing or if it seemed very likely that none were missing based on the consistency of the record in telling the whole story of what happened to all the squadron's a/c.
# aircraft force-landed without damage. This was recorded in the British IF data, so I kept it as a category. This number is zero if every plane is accounted for in the records or if the records are consistent in mentioning problems like force-landings when they occurred. The French war diaries often are consistent in this way.
# a/c force-landed with damage. This was recorded in the British IF data, so I kept it as a category. This number is zero if every plane is accounted for in the records or if the records are consistent in mentioning problems like force-landings when they occurred. The French war diaries often are consistent in this way.
Record number kept by George Williams, who gave me the original British data compiled from the PRO.
An air fight here means that the German airplanes got close enough to the bombers for the bombers or their escorts to shoot back at the fighters. German fighters sniping at a bomber formation from a ridiculously long range with no response is not counted in this database as an air fight.
"Voisin" means Voisin 3, 4, or 5.
Earliest takeoff time of unit in military time.
Latest time a plane from that unit returned to base in military time.
Bombing Time or Midpoint
Known time when bombs were dropped or midpoint of T.O. & RTB times.
If several a/c made the same trip, this is the longest.
Base for French raids is frequently from "Les escadrilles de l'aéronautique militaire française", SHAA.
Distance From Base (Km)
One-way distance by air, rounded to the nearest 5km.
Casualty data recorded by the USAS Bombing Survey. Blank cell means data is missing, not necessarily zero.
[Same as above]
Direct damage from bombs hitting the target. Source is bombing survey. Blank cell means missing data, not necessarily zero.
Damage in Luxembourg and occasionally occupied France is given in francs in the bombing survey. During WWI, 1 Luxembourg Franc = 1 Belgian Franc = 0.80 German Marks. Blank cell means missing data, not necessarily zero damage.
# of bombs found by local authorities at target (info from bombing survey) or number of bombs dropped listed in squadron records. All types of bombs included in the latter count, including incendiaries.
Time Lost (Hours)
Time a facility was out of action or nonproductive due to bomb damage or stopping due to bomb raid or alert.
Examples: trains stopped moving during alerts; a rail station might be nonfunctioning until track damage is repaired, a bridge or factory might be out of commission until it is repaired; a factory might stop work during an alert while the workers took shelter.
Other Cost (Marks)
Indirect costs from air raids or alerts -- generally lost production during an alert where no bombs hit the facility.
Other Cost (Francs)
[No comment made. Same as above.]
Alternate Location Name
In Alsace & Lorraine, many cities and towns had two names - 1 French and 1 German.
Raid or Alert Length (Hrs)
The duration of the raid or alert in hours is often given in the Bombing Survey data. This frequently matches "time lost" if production or transportation stopped only for the duration of that particular raid/alert.
Page #, Maurer Maurer, v.IV, or other Reference
If entry is just a number, it is a page number from Vol.IV of the USAF "History of the US Air Service", written by Maurer Maurer.
NARA 990 refers to microfilm Roll#58 of the Gorrell Records (the very last one). The target locations are listed alphabetically on the microfilm.
"War Diary" refers to the Journal des marches et operations put on the internet by the French government. The records are JPEG images of pages, so each one has an Image number that is part of the file name.
"G.K. Williams Summary" is data compiled by George Kent Williams for his dissertation research at Oxford (1987). It includes information from these documents: Approximate Results, Detailed Raid Report, War Diaries, The War in the Air Appendices, & Squadron Histories. Raid times have been added to this data from Keith Rennles, Independent Force, 2002.
Comments are here if they are not in Column I.
If you sort this database in a different way and you want to return it to the original order, use this column rather than the date/time columns. This will put the summary records immediately above their subrecords and put ABS data after the bombing records for the same day.