Email:
John Woodside

FS2004 Dambuster Flight

 

Dambuster Routes
(Click to enlarge)

After the recent Channel 4 production on simulating the original flight of 617 Squadron to the Mohne dam I thought it would be of interest to see how easy it would be for users of the FS2004 default scenery to fly. I chose the route flown by Waves 1 and 3 on the night and although I managed to reach the dams I found that the flight threw up some headaches - both in navigation and in flying skills.

Advantages the real crews had

  1. The original force flew low level and used a continually updated nav plot with visual backup to confirm course. Essential tools used were the navigator <g> and accurate maps (and good eyesight).
     

  2. Original crews were a cohesive and experienced group. En route navigation would have been second nature to them and aircraft managements skills would have been first class divided amongst several individuals.

The Navigator would have plotted the route on a map, obtained track and distance values for each leg plus timings between turning points. Once in the air the aircraft would have flown at an accurate speed with heading and en route times being recalculated by the Navigator to take into account any wind effects. Confirmation of turning points would have been by visual observation aided by further visual sightings whilst en route (by several crew members) to confirm track was accurate.

Essentially the navigation was a matter of flying an accurate heading for an exact amount of time. We can do this in FS2004 but some of the other skills or facilities are harder to emulate.

Limitations using FS2004

  1. We may not have the correct aircraft management skills as we are pilot, navigator and flight engineer in one. Workload may be unduly high if off course and trying to correct navigational errors whilst flying the aircraft at the same time.
     

  2. Visual clues in FS2004 are nowhere near those in real life so it is difficult to ensure en route track accuracy and turning point locations.
     

  3. Visual clues at night in FS2004 are almost nil. The real crews used a lot of water features (good reflection from these on a moonlit night) but that's completely out of the question in FS2004 - there is no way you could fly up a canal at 200ft at night in FS because I'd doubt you'd even see it.
     

  4. Scampton isn't in the default scenery. Actually neither is the dam - but the lake created by it is.

Solutions

The major problem is that we don't have resources that the original crews had whilst, paradoxically, having far superior facilities in FS2004. It is easy enough to enter the route in FSNav and have the autopilot fly it, but to emulate the original flight more closely it would be better to fly the mission in an accurate a manner as possible.

The prime consideration here is navigation with pilot skills coming a close second.  This depends upon the individual and so the solution will vary according to your skills. Some users may decide to hand fly the aircraft. Others might elect to use A/P Hdg Hold whilst some might opt for both Hdg Hold and IAS Hold. Match the solution to your known skills.

There is no solution to the night navigation limitations in FS2004 and I can see why the BBC chose to fly the exercise in either daytime or dusk.

Scampton is available as add-on scenery for FS2004. Look in the usual sim sites for the Scampton files by John Young.

Essential Skills

1. You must fly an accurate heading. Must, must, must.

2. You must fly an accurate speed.

3. For the speed you are flying you must be able to calculate en route times.

Route

Leg Track
(T)
Track
(M)

Dist
(nm)

Speed
(kts)
Time
Scampton to Southwold 126 131 99.95 207 00:28:58
Southwold to Coast 119 123 83.82 207 00:24:18
Coast to Roosendaal 102 106 30.70 207 00:08:54
Roosendaal to Beek 091 093 44.49 207 00:12:54
Beek to Rees 062 064 31.56 207 00:09:09
Rees to Ahsen 096 098 34.00 207 00:09:51
Ahsen to Ahlen 080 081 21.73 207 00:06:18
Ahlen to Mohne 155 157 18.32 207 00:05:19

Note: Do not use headings from FSNav as they are Great Circle bearings, not Rhumb Line.

I used a fairly fast en route speed of 220mph (207kts). If you use a different speed make sure you calculate the en route times accurately. These should be to the nearest second - it can make a lot of difference!

I will admit that I flew the route initially at 2000ft. This enabled me to map read with reasonable accuracy. Had I developed better skills (or FS2004 scenery was better) I could have reduced this considerably.

If you add wind to FS2004 I wish you the best of luck in working out revised headings and speeds. I did not try this because of workload - but I may add random wind for a second flight. The main problem here is determination of track error - there is little in FS2004 to provide this on some legs.

FSNav Route - Just click on the link to download the FSNav route for the flight.

Flying the route

Before you start out I'd suggest using a stopwatch or similar as you WILL need to count down the seconds.

Below is a description of the route flown with suggestions as to easing your workload.

Scampton to Southwold.

After take off from Scampton I strongly suggest a turn northwest and climb to operational height and settle down to the correct cruise speed. Once the aircraft is established in both speed and height turn back towards Scampton and set course from directly overhead. Start your timer. You should get a reasonable course check on crossing the Wash - either use the map above or use the map in FSNav (but turn your aircraft position in FSNav off as that would be an unfair advantage).

Hethel is 77nm from Scampton and it would be a good point at which to confirm navigation accuracy. If you are correctly on course it should pass about 1nm to port. I would also suggest a time check as airspeeds can vary slightly in FS2002. At my speed I should have passed it after 22min 20sec but I was 1 min late. I therefore revised my ETA at Southwold and added 1min to all legs around 77nm long and 30sec to all legs about 38nm long.

As you approach Southwold you should see a lake immediately to starboard and the town itself right on the coast.

Southwold to the Dutch Coast

This is all over water so the only check you will get is when you approach the coast. If you are on track you should see a long inlet with two small islands at its mouth. Your turning point is the northern tip of the long island.

Dutch coast to Roosendaal

Once on course for Roosendaal you should be flying towards the apex of a long tongue of land. You cross the coast just left of the apex. As you approach your ETA you should see Roosendaal quite clearly.

Roosendaal to Beek

A tricky leg in FS2004. Turn onto the new heading and you will see a highway running obliquely left for a short while before it goes out of view..

After 12nm you will see the airfield at Gilze Rijen off to port. The highway runs alongside this airfield and then turns slightly south, coming back almost on your track as you cross a small town (Goirle).

As you pass over Goirle you should see the Wilhelmina Canal appear, running from left to right. The raid aircraft flew along this canal at extremely low level. You can follow the canal or maintain accurate course and speed as you wish but if you try the former don't get lost! The canal initially goes south of planned track but then turns and runs parallel with you until it enters the outskirts of Eindhoven. If you have maintained heading you will pass just north of Eindhoven and will see the airport off to starboard.

After Eindhoven keep a good lookout as the turning point is not far away - neither is it especially visible in FS2004. The canal turns slightly north after Eindhoven and gradually converges on track. It should be underneath you again just as it finishes running through a long wood. After the wood the canal crosses a highway - and stops. THIS IS YOUR TURNING POINT. If in doubt turn at the road.

Beek to Rees

There is nothing much to see on the leg from Beek to Rees so it is important you got the last turning point right. About the only visual clue is the town of Goch which you should pass over some 20nm from the turning point.

Just after passing Goch you should spot the shape of the Rhine. It should be like a large S on it's side - a convex bend to your left and a concave bend to your right. Rees is on the riverside right in the middle of the S. You should also spot a small lake on the inside of the bend to the left of Rees. This is a crucial identification point.

Rees to Ahsen

Rees to Ahsen is 34nm with little to help you check your course as you skirt around the north of the industrial Ruhr complex.

After 22nm you will see a road follow your track for a short distance with a built up area to your right. Beyond this is a further built up area to your left with a small lake behind it. Keep watching the lake. As it passes abeam you to port start the timer. 60 seconds after passing the lake turn onto your next course. This should be well before you get to the town approaching you.

Ahsen to Ahlen

Your inital course should take you just north of the town that was approaching and along some woods (mainly to your left).  This is a short leg and you should soon see Ahsen appear in the distance.

Your next turn is rather sharp onto south so take account of the aircraft turning circle. If your turn rate is good wait until you are over the town. If the turn rate is slow start your turn just as the edge of the town disappears under your view. Here I am assuming you are using normal zoom and are in limited panel or no panel view.

Ahlen to Mohne

This final run should take you to the middle of the Mohne reservoir's lake.

If you are using the default scenery the area will be distinctly lacking in obvious hills but it is still undulating. The water height is 707ft AMSL.

I've done my bit - it is up to you now.. <g>