Dark Blue Defection (fan expansion for Red Storm) Rulebook

Table of Contents

Table of Contents

• Introduction
• Optional Rules
  • Random Bot Flight Altitude
  • Random Weather
• NSC1: Red Dawn
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC2: Good Old Uncle SAM
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC3: Morning Glory
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC4: Iron Eagle
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC5: Dark Blue Defection
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC6: Operation Colossus
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC7: The Heist
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC8: The Night Witches
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC9: Heavy Rain
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• NSC10: Showdown
  • Mission Briefing
  • Targets
  • Scenario Conditions
  • NATO Order of Battle
  • Warsaw Pact Order of Battle
  • Scenario Special Rules
  • Victory Conditions
• Bot Example of Play

Introduction

Pay attention to the scenario special rules (SSRs) for each scenario. In order for the solo bot to work as intended, the solo bot follows flight plans in all scenarios with exceptions to PAC5.

This expansion provides information and player aids for each scenario in the following format:

Mission Briefings. Mission Briefings in this scenario booklet detail the scenario background, targets, scenario conditions, Order of Battle (OOB), scenario special rules and victory conditions.

Planning Maps. Planning Maps provide a visual aid of the area of operations for each scenario detailing flight plans for either side, objectives, starting force locations, orbit points, rally points and the front line.

Scenario Setup Sheets. Scenario Setup Sheets provide a counter tray template for the OOB to allow quick setup and drawing of counters during the scenario.

Flight Log Sheets. Populated flight log sheets are provided for each flight listed in the OOB, to allow flight tracking of damage, ammo, fuel and aggression levels during a scenario using a dry erase marker.

Bot controlled flights may start the scenario as Undetected Generic Flights. Flight activation will be determined once directed to do so in the SSRs and rolled for as detailed in the OOB briefing section to determine aircraft type.

SAM/AAA Log Sheets are not required. SAM/AAA will start on the map located with radars on where applicable, or will start as warning/flak markers until activated as per the scenario setup instructions. Unactivated SAM/AAA counters are to be placed on the Scenario Setup Sheet until activated along with any acquisition markers. Due to the small scale of the scenarios, SAM units do not need to track ammo.

If SAM/AAA units start the scenario as warning/flak markers, SAM/AAA type will be determined once directed to do so on the SAM/AAA activation tables (PAC5) and rolled for as detailed in the OOB briefing section to determine type.

Optional Rules

Random Bot Flight Altitude

During a scenario, if a bot flight is following a flight plan and has not deviated for any reason, once the flight is within 1 hex of the next waypoint on its flight plan, roll 1D10 on the table below to determine if the bot flight attempts to change altitude:

Roll	Altitude Change
1-3	No Change
4	Spend movement point to dive to deck
5-7	Descend one altitude band as a free move
8-10	Spend movement point to climb one altitude band

If a bot flight reaches a waypoint within 1 hex with no movement points left available, still make an altitude change roll. If the roll is "No Change" or "Descend one altitude band", use the result. If not, attempt to change altitude as the first action on the next turn after activation during the movement phase.

If it is not possible to climb any higher, or descend any lower, treat the attempt as "No Change". Bot flights will never attempt to zoom climb using altitude optional rules. Some scenarios will define a bot flight altitude change at a given waypoint, in this case, do not roll on the altitude change table for those flights when reaching a waypoint.

Random bot flight altitude rules add more dynamics to bot flight movement as they move around a flight plan. When the Player is comfortable with the game system, it is recommended to add this optional rule to every scenario for additional tactical complexity and replayability.

Random Weather

Each scenario has pre-set weather conditions defined in the Mission Briefing. To add further complexity and replayability to a scenario, Players may wish to roll for weather. If the Player wishes to do so, during scenario setup use the Weather Phase rules [ROP 31.1] to roll for weather conditions on the Weather Table in PAC3 and follow the Weather rules [ROP 22].

When rolling for weather, first roll 1D10. On a 1-5 roll on the "Good Weather" table, on a 6-10 roll on the "Poor Weather" table. The NATO Player determines the location of all cloud breaks.

NSC2, NSC4, NSC5, NSC6 and NSC8 use ordnance that cannot be used in certain weather conditions which would make the scenario objectives impossible to achieve. Do not roll on the "Poor Weather" table for these scenarios. Re-roll any "Haze at Deck" and "Haze at Deck and Low" results.

NSC1: Red Dawn

Mission Briefing

After months of increasing tension along the inner-German border, Warsaw Pact commanders launched their offensive into the Fulda Gap. At dawn the next day after the start of the offensive, a small raid group heads towards Kassel Airbase intent on destroying the runway and grounding as many NATO flights as possible ahead of the impending Warsaw Pact armor advance. NATO forces in the area are unprepared. Two flights of F-15's took off at dawn on high alert from Allendorf Airbase as AWACS reported inbound enemy aircraft.

Targets

The NATO objective for this mission is to stop the Warsaw Pact raid group reaching and bombing Kassel Airbase.

Scenario Conditions

• Date: 18 May 1987
• Time of Day: 07:00 (Dawn)
• Detection Level: NATO: D WP: C
• Weather: Clear. Do not roll on the Weather Table.
• Map: The whole map is in play.
• The Front: NATO side is on/west of 6302 6309 5811 5315 5718 5721 5522 5430 5632 6235 6940 6935 7538 7737.
• Closed Airfields: None
• Inherent AAA/IR SAM Coverage: None

NATO Order of Battle

Air Setup

Air Units and Markers:

• US 2 x {2} F-15A, CAP. Aggression Value +0. Set up Undetected adjacent to NATO Orbit Point heading south at deck altitude.
• 1 x Orbit Point in 3422

NATO Pilot Quality

• Regular, F-15A

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 4 x Undetected Generic WP Flights A, B, C, D within 1 hex of WP Orbit Point 1 (6521) heading north at medium altitude.

  Generic Flights A, B, C, D follow flight plan A within 1 hex until activated. Once activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-6519, A2-6515, A3-5108, A4-4511, A5-4514

• If Bot Flight Activation Check is Real Flight roll for flight type:

  Roll	Flight Type
  1-4	Su-24C
  5-10	MiG-29A

• USSR 1 x {4} MiG-29A, Close Escort. Aggression Value +1. Place counter on scenario setup sheet for use when activated.

• USSR 2 x {2} Su-24C, Bombing, Aggression Value +1. Place counters on scenario setup sheet for use when activated.

WP Pilot Quality

• Regular. MiG-29A, Su-24C

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 1 dummy flight. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 2 hexes using clean movement profile for Su-24C at combat throttle.
4. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
5. After activation, if Su-24C Bombing flight, ignore Engagement Actions, Defend as per Bombing assignment and continue on flight plan.
6. After activation, if MiG-29A, follow Close Escort rules. If no Bombing flights are activated, resume Close Escort with closest generic flight. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
7. If a bot flight is activated and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint or resume Close Escort role with closest Bombing flight with ordnance first. If no Bombing flights are activated, resume Close Escort with closest generic flight.
8. At waypoint A4 bot un-activated generic and Su-24C flights must move to low altitude and remain at low altitude for the bombing run.
9. If a generic flight reaches the Target hex (4514) and there are un-activated Su-24C flights remaining, the flight activates as a Su-24C flight and bombs the target as below.
10. When a bot Su-24C flight reaches Kassel Airbase hex (4514) do not roll for bombing attacks. It is assumed they automatically destroy the runway for the purpose of this scenario only.
11. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 6 – SAM Fratricide, 11 - NATO QRA, 14 - Direction Finding, 15 - SEAD Strike.

Victory Conditions

1. There are no victory points in this scenario. Instead, the NATO side wins if it stops the bombing of Kassel Airbase.
2. If a flight of Su-24C's with ordnance reach Kassel Airbase (4514) the mission ends immediately as a NATO defeat.

NSC2: Good Old Uncle SAM

Mission Briefing

Warsaw Pact forces are streaming into the Fulda Gap. NATO forces, caught completely off guard and reeling from surprise attacks are desperate to rally into defensive positions all across the front. NATO aircraft attempting to interdict Warsaw Pact ground forces and slow the advance are under constant fire from complex air defense networks advancing with the ground forces.

NATO Air Command has authorized SEAD operations in an attempt to allow follow on CAS for the troops on the ground. Targets have been identified by recon prior to the mission. F-4G Wild Weasel and F-16C Falcon aircraft are tasked with SEAD to the east of Bad Hersfeld. A flight of F-15A Eagles will fly CAP for the mission.

Targets

The NATO objective for the mission is destroy enemy SA-11 and SA-13 SAM emplacements behind the front line.

Scenario Conditions

• Date: 19 May 1987
• Time of Day: 14:00 (Day)
• Detection Level: NATO: D WP: C
• Weather: Clear. Do not roll on the Weather Table.
• Map: The whole map is in play.
• The Front: The NATO side of the front is on/west of 6202 6008 5611 5315 5718 5419 5222 5225 5230 5534 6037 6441 6940 7639
• Closed Airfields: None
• Inherent AAA/IR SAM Coverage: None

NATO Order of Battle

Air Setup

Air Units and Markers:

• US 1 x {2} F-15A, CAP. Aggression Value +2. Set up Undetected heading east adjacent to NATO Orbit Point 1 at low altitude.
• US 1 x {4} F-16C, SEAD. Aggression Value +1. Set up Undetected heading east adjacent to NATO Orbit Point 2 at low altitude.
• US 1 x {4} F-4G, SEAD. Aggression Value +1. Set up Undetected heading east adjacent to NATO Orbit Point 2 at low altitude.
• Orbit Point 1 in 3624, Orbit Point 2 in 3922

NATO Pilot Quality

• Veteran, F-15A
• Regular, F-16C, F-4G

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 2 x Undetected Generic WP Flights A, B within 1 hex of WP Orbit Point 1 (6922) heading north west at medium altitude.

  Generic Flights A, B follow flight plan A within 1 hex until activated. Once activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-6821, A2-6218, A3-5721, A4-5731, A5-6032.

• Set up 2 x Undetected Generic WP Flights C, D within 1 hex of WP Orbit Point 2 (6630) heading south west at medium altitude.

  Generic Flights C, D follow flight plan B within 1 hex until activated. Once activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: B1-6531, B2-5834, B3-5432, B4-5421, B5-5919.

• If Bot Flight Activation Check is Real Flight roll for flight type:

  Roll	Flight Type
  1-4	MiG-29A
  5-10	MiG-21SPS

• USSR 1 x {2} MiG-29A, CAP. Aggression Value +1. Place counters on scenario setup sheet for use when activated.

• GDR 1 x {2} MiG-21SPS, CAP. Aggression Value +0. Place counters on scenario setup sheet for use when activated.

Ground Setup

Air Defense Units:

• 1 x SA-11 (5925). Set up unlocated with a SAM Warning Marker, radar on.
• 2 x SA-13 (5420, 5227). Set up located.
• 4 x Light Flak (5329, 5325, 5323, 5619). Set up located.

WP Pilot Quality

• Regular, MiG-29A, MiG-21SPS

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 2 dummy flights. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using movement profile for MiG-21SPS at combat throttle.
4. If bot flights reach last waypoint on flight plan, turn around and head back to waypoint 1. Repeat until mission ends.
5. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
6. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint.
7. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 11 - NATO QRA, 14 - Direction Finding, 15 - SEAD Strike.
8. This scenario ends at the end of Turn 12. At that point, roll for recovery for all flights that have not yet recovered.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   6	SA-11 Heavily Damaged
   12	SA-11 Destroyed
   3	SA-13 Heavily Damaged
   6	SA-13 Destroyed
   2	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured

2. The victory total is obtained by subtracting the WP VP total from the NATO VP total. The results can be a negative value. The victory total determines the victory level on the table as follows:

NSC3: Morning Glory

Mission Briefing

Although the suppression of air defenses around the town of Bad Hersfeld on the 19 May was a success, Warsaw Pact ground forces took the town with overwhelming force by late evening the same day. On the morning of 20 May 1987, NATO ground forces are to launch a counter attack to take back the town. NATO air forces have a short window of opportunity to provide CAS to ground troops ahead of the attack before enemy SAM replacements arrive in the area.

Two flights of US A-10A Thunderbolts are tasked with attacking enemy Mech and Armor divisions around Bad Hersfeld. A flight of UK Tornado GR.1's will provide Fast FAC. US F-4E Phantom's are tasked with CAP.

Intercepted enemy transmissions suggest enemy fighter aces Nikolai Krasnov and Nikita Rechkalov may be in the area of operations. Their squadron of Su-27S Flankers are responsible for twenty-four NATO kills on the opening day of the offensive, with Nikolai claiming eight kills and Nikita five. If you are engaged, take them down.

Targets

Bombing flights may target any identified enemy ground forces within the area of operations.

Scenario Conditions

• Date: 20 May 1987
• Time of Day: 10:00 (Day)
• Detection Level: NATO: D WP: C
• Weather: Clear. Do not roll on the Weather Table
• Map: The whole map is in play
• The Front: NATO side is on/west of 5802 5606 5510 5313 5217 5219 4922 4824 5029 5333 5937 6242 6840 7542
• Closed Airfields: Fritzlar, Fulda, Wildflecken
• Inherent AAA/IR SAM Coverage: None

NATO Order of Battle

Air Setup

Air Units and Markers:

• US 1 x {4} F-4E, CAP. Aggression Value +2. Set up Undetected heading north east adjacent to NATO Orbit Point 1 at low altitude.
• UK 1 x {2} Tornado GR.1, Fast FAC. Aggression Value +1. Set up Undetected heading north east adjacent to NATO Orbit Point 1 at low altitude.
• US 2 x {4} A-10A, Bombing. Aggression Value +1. Set up Undetected heading north east adjacent to NATO Orbit Point 2 at deck altitude.
• Orbit Point 1 in 3827, Orbit Point 2 in 3831

Ground Setup

Army Ground Units:

• US 3rd Armor Division, 1 x Mech (4826), 1 x Armor (4929)
• FRG 5th Panzer Division, 2 x Mech (4723, 5020)
• NATO ground forces have no function in this scenario and are there for immersion only, they may be omitted if you wish.

NATO Pilot Quality

• Regular, Tornado GR.1, A-10A
• Veteran, F-4E

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 4 x Undetected Generic WP Flights A, B, C, D within 1 hex of WP Orbit Point 1 (6513) heading south west at high altitude.

  Generic Flights A, B, C, D follow flight plan A within 1 hex until activated. Once activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-6314, A2-5617, A3-5627, A4-5024, A5-6417

• If Bot Flight Activation Check is Real Flight roll for flight type:

  Roll	Flight Type
  1-4	Su-27S
  5-10	MiG-23M

• USSR 1 x {2} Su-27S, CAP. Aggression Value +3. Place counters on scenario setup sheet for use when activated.

• USSR 1 x {2} MiG-23M, CAP. Aggression Value +0. Place counters on scenario setup sheet for use when activated.

• 1 x Rally Point in 6221

Ground Setup

Army Ground Units:

• USSR 79GT Division x Mech (5025) 1 x Armor (5028)
• USSR 27 Guards MRD 2 x Armor (5022, 5220)
• Ground units do not have organic mobile AAA.

Air Defense Units:

• 2 x 2K22 (5127, 5222) set up located with radars turned on.

WP Pilot Quality

• Ace, Su-27S
• Regular, MiG-23M

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 2 dummy flights. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using clean movement profile for MiG-23M at combat throttle.
4. If bot flights reach waypoint 5 on flight plan, turn around and head back to waypoint 1. Repeat until mission ends.
5. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
6. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint.
7. NATO Bombing flights do not follow a flight path in this scenario. Instead, each bombing flight may move so it can attack any identified WP Armor or Mech Division. Each flight may make as many Bombing runs as desired on WP Mech and Armor units, but no other WP ground targets may be attacked. Bombing flights must Abort after all air-to-ground ordnance is expended.
8. NATO Bombing flights may only conduct air-to-ground attacks on WP Armor or Mech Divisions that have been "identified" by a NATO Fast FAC flight. All WP Armor and Mech Divisions begin "unidentified."
9. During each SAM Location Phase, a non-disordered Fast FAC flight may attempt to identify two WP units in the flight's forward or beam arcs. The attempt requires the flight to be within 2 hexes, deck or low altitude, and have a line of sight to the unit. Roll 1d10. Identification succeeds on a roll of 4 or more. Once identified, a WP unit remains identified for the remainder of the scenario.
10. Fast FAC flights are immune from Aborts due to solo random events.
11. Nikolai Krasnov is flying a Su-27S designated as Rostov #1. Nikita Rechkalov is flying a Su-27S designated as Rostov #2. If either aircraft is shot down, the pilot automatically bails out and is recovered by WP forces at the end of the scenario on either side of the front.
12. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 6 – SAM Fratricide, 11 - NATO QRA, 14 - Direction Finding.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   2	Armor / Mech Division Slightly Damaged
   4	Armor / Mech Division Heavily Damaged
   8	Armor / Mech Division Destroyed
   2	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured
   5	Nikolai Krasnov is shot down
   4	Nikita Rechkalov is shot down

NSC4: Iron Eagle

Mission Briefing

Kassel, Fulda and Schweinfurt have fallen. Bad Hersfeld has been retaken by NATO forces thanks to the heroic efforts of NATO pilots but control of the area still hangs by a thread. Warsaw Pact have strength in numbers and are pressing NATO forces with speed and precision all across the front. To the south, the airfields of Emery, Kitzingen and Bamberg have evacuated as many people as possible before destroying the runways to prevent their use by enemy forces.

The evacuation of Schweinfurt was swift, the airbase, although small, now holds strategic importance for Warsaw Pact forces to the south of the front. If the airfield remains operational, supplies, troops and an operational forward airbase will allow Warsaw Pact forces to continue their assault into West Germany at a pace NATO forces are already struggling to contain.

A flight of F-111D/E Aardvark's are tasked with destroying the runway at Schweinfurt. They will be supported by two flights of F-16C Falcons tasked with SEAD ahead of the bombers. F-15A Eagles will fly CAP in the area of operations. An EF-111A Raven is available for Jamming of enemy ground radars and may prove vital in getting the bombers over the target. Enemy fighters are in-bound to the area. The operation needs to be swift and more importantly, on target. The bombers must reach the airfield.

Targets

The NATO objective for this mission is to bomb the runway at Schweinfurt airbase.

Scenario Conditions

• Date: 23 May 1987
• Time of Day: 08.15 (Day)
• Detection Level: NATO: D WP: C
• Weather: Clear. Do not roll on the Weather Table.
• Map: Eastern Map is in play.
• The Front: NATO side is on/west of 5402 5306 4607 4610 4315 4418 4421 5223 5227 4934 4940 5648 6545 7441
• Closed Airfields: Hoxter, Bad Hersfeld, Emery, Kitzingen, Bamberg.
• Inherent AAA/IR SAM Coverage: WP side within five hexes of the front.

NATO Order of Battle

Air Setup

Air Units and Markers:

• US 1 x {4} F-15A, CAP. Aggression Value +3. Set up Undetected heading east adjacent to NATO Orbit Point 1 at low altitude.

• US 2 x {4} F-16C, SEAD. Aggression Value +2. Set up Undetected heading east adjacent to NATO Orbit Point 1 at low altitude.

• US 1 x {4} F-111D/E, Bombing. Aggression Value +1. Set up Undetected heading east adjacent to NATO Orbit Point 2 at low altitude.

• Bombing flight follows NATO flight plan A within 2 hexes:

  Flight Plan: A1-4449, A2-5049, A3-5945, A4-5943, A5-5239, A6-4239, A7-3642

• US 1 x {1} EF-111A, Standoff Jamming. Aggression Value +0. Set up heading east adjacent to NATO Orbit Point 2 at low altitude.

• Orbit Point 1 in 4143, Orbit Point 2 in 4249

• Schweinfurt airbase is target profile A.

NATO Pilot Quality

• Ace, F-15A
• Veteran, F-111D/E
• Regular, F-16C, EF-111A

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 2 x Undetected Generic WP Flights A, B within 1 hex of Orbit Point 1 (6628) heading west at high altitude.

  Generic Flights A, B follow WP flight plan A within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-6428, A2-5228, A3-5237

• Set up 2 x Undetected Generic WP Flights C, D within 1 hex of Orbit Point 2 (7033) heading south west at low altitude.

  Generic Flights C, D follow WP flight plan B within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: B1-6934, B2-5640

• Set up 2 x Undetected Generic WP Flights E, F within 1 hex of Orbit Point 3 (6541) heading south west at medium altitude.

  Generic Flights E, F follow WP flight plan C within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: C1-6441, C2-5745, C3-5142

• If Bot Flight Activation Check is Real Flight roll 1D10 for flight type:

  Roll	Flight Type
  1-3	MiG-29A
  4-6	MiG-23MLD
  7-10	MiG-21SPS

• USSR 1 x {4} MiG-29A, CAP. Aggression Value +2. Place counters on scenario setup sheet for use when activated.

Ground Setup

Air Defense Units:

• 1 x EWR (6238)

SAM Activation Information:

• Frontal SAM Zone. Setup 3 SAM Warning Markers (6044, 5642, 5439) with radar off. 1 SAM Warning marker will be a dummy SAM. Roll for activation when a Player flight is within 2 hexes. Do not apply any modifiers to the roll. Once activated set up SA-13 (A3 or B3) as shown on Scenario Setup Card, located. 1-5 Real SAM, 6-10 Dummy.
• Divisional SAM Zone. Setup 3 SAM Warning Markers (6344, 6039, 5637) with radars on. 1 SAM Warning marker will be a dummy SAM. Roll for activation when a Player flight is within 8 hexes. Do not apply any modifiers to the roll. Once activated set up SA-11 (F or G) as shown on Scenario Setup Card unlocated with a SAM Warning Marker on, radar on. 1-5 Real SAM, 6-10 Dummy.
• Corps/Army SAM Zone - N/A for this scenario.

AAA Activation Information:

• Setup 5 Light AAA, inactive (5841, 5647, 5546, 5038, 5040). Up to 2 Light AAA markers will be dummy AAA. Roll for activation when a Player flight is within 1 hex. Do not apply any modifiers to the roll. Once activated set up a 2K22 located, radar on, in place of the Light AAA marker as shown on the scenario setup card. 1-5 Real AAA, 6-10 Dummy.

WP Pilot Quality

• Veteran, MiG-29A, MiG-21SPS
• Regular, MiG-23M

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 3 dummy flights. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using clean movement profile for MiG-21SPS at combat throttle.
4. If bot flights reach last waypoint on flight plan, turn around and head back to waypoint 1. Repeat until mission ends.
5. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
6. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint.
7. NATO F-16C SEAD flights may jettison ordnance and begin CAP at any point in the mission.
8. Bot flight target priority for Engagement Actions is detected good order flights first.
9. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 11 - NATO QRA, 14 - Direction Finding.
10. This scenario ends at the end of Turn 10. At that point, roll for recovery for all flights that have not yet recovered.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   12	Runway Totally Destroyed
   9	Runway Heavily Damaged
   6	Runway Slightly Damaged
   2	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured
   2	Enemy SAM or EWR unit Totally Destroyed
   1	Enemy SAM or EWR unit Heavily Damaged

NSC5: Dark Blue Defection

Mission Briefing

Nikolai Krasnov has had a long and distinguished military career. Fighting in eight different wars for the USSR over the course of twenty-four years of service. He has seen it all and is a hard man. Despite the many pilots he has killed, he stands by the belief of a code of honor among pilots and combat in the skies, a war of minds and tactics rather than of brute force. It is his way of justifying his ever-increasing tally of confirmed kills.

Nikolai Krasnov is a double agent, and a good one at that. For the last eleven years he has continued to send secret documentation and intelligence to MI6. His time is now up. He has been discovered by a KGB agent after attempting to send vital information about the war effort to NATO forces.

Nikolai Krasnov has fled his position on foot into the hills overlooking Kassel and has called for immediate extraction. Warsaw Pact forces are in pursuit, frantically searching they are closing in on his position. Nikolai must be recovered at all costs.

Targets

The NATO objective for this mission is to destroy air defenses in the area around Nikolai Krasnov's location to clear a way for H-53 flight "Mother" to extract and return him alive to the NATO side of the front.

Scenario Conditions

• Date: 27 May 1987
• Time of Day: 02:30 (Night, Full Moon)
• Detection Level: NATO: D WP: C
• Weather: Clear. Do not roll on the Weather Table.
• Map: The whole map is in play.
• The Front: NATO side is on/west of 4703 4605 4307 4210 4114 4318 4221 4424 4528 4633 4640 5349 6348 7642
• Closed Airfields: Hoxter, Kitzingen
• Inherent AAA/IR SAM Coverage: WP side within five hexes of the front.

NATO Order of Battle

Air Setup

Air Units and Markers:

• US 3 x {4} F-4D, CAP. Aggression Value +2. Set up Undetected heading east adjacent to NATO Orbit Point 3 at medium altitude.
• US 1 x {4} F-111D/E, SEAD. Aggression Value +2. Set up Undetected heading south east adjacent to NATO Orbit Point 1 at medium altitude.
• US 1 x {2} H-53, CSAR. Aggression Value +0. Set up Detected heading north east adjacent to NATO Orbit Point 2 at deck altitude.
• Orbit Point 1 in 3409, Orbit Point 2 in 3919, Orbit Point 3 in 3521

NATO Pilot Quality

• Veteran, F-4D, F-111D/E

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 4 x Undetected Generic WP Flights A, B, C, D within 1 hex of Orbit Point 1 (6622) heading north west at medium altitude.

  Generic Flights A, B, C, D follow flight plan A within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-6421, A2-5316, A3-4716

• Set up 4 x Undetected Generic WP Flights E, F, G, H within 1 hex of Orbit Point 2 (5531) heading west at medium altitude. (Printed as "E, F G, H".)

  Generic Flights E, F, G, H follow flight plan B within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: B1-5331, B2-4731, B3-4718

• If Bot Flight Activation Check is Real Flight roll 1D10 for flight type:

  Roll	Flight Type
  1-3	MiG-25PD
  4-6	MiG-23M
  7-10	MiG-21SPS

• USSR 1 x {4} MiG-25PD, CAP. Aggression Value +2. Place counters on scenario setup sheet for use when activated.

• USSR 1 x {4} MiG-23M, CAP. Aggression Value +1. Place counters on scenario setup sheet for use when activated.

• GDR 3 x {4} MiG-21SPS, CAP. Aggression Value +0. Place counters on scenario setup sheet for use when activated.

Ground Setup

Air Defense Units:

• 1 x SA-13 (4515) set up located.
• 5 x 2K22 (4215, 4416, 4616, 4414, 4614) set up located with radars turned on.

WP Pilot Quality

• Veteran, MiG-25PD.
• Regular, MiG-23M, MiG-21SPS

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 3 dummy flights. A roll of 1-6 is a real flight. A roll of 7-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using clean movement profile for MiG-21SPS at combat throttle.
4. If bot flights reach last waypoint on flight plan, turn around and head back to waypoint 1. Repeat until mission ends.
5. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
6. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint.
7. When H-53 flight lands at target hex, it does not become unready, it may takeoff on the next turn. When flight lands roll 1D10. 4-10 Nikolai Krasnov is recovered. 1-3 Fighting around the extraction point ensues, Nikolai is not recovered. Roll again on each subsequent turn until recovered. Designate which helicopter in the flight recovers Nikolai.
8. H-53 CSAR flight starts the scenario detected and remains detected for the scenario. Do not roll for flight during the detection or tracking phase.
9. Bot flight target priority for Engagement Actions is detected good order flights first.
10. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 11 - NATO QRA, 14 - Direction Finding.
11. This scenario ends at the end of Turn 12. At that point, roll for recovery for all flights that have not yet recovered.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   14	Extract Nikolai Krasnov to NATO side of front
   2	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured
   2	Enemy SAM or AAA unit Totally Destroyed
   1	Enemy SAM or AAA unit Heavily Damaged

2. The victory total is obtained by subtracting the WP VP total from the NATO VP total. The results can be a negative value. The victory total determines the victory level on the table as follows:

NSC6: Operation Colossus

Mission Briefing

Fulda station is an important transport hub of the German railway network in the east Hessian city of Fulda. In times of peace, it is used by about twenty thousand travelers each day. Relocated tracks for a high-speed rail network on the north-south line towards Frankfurt went into operation in December 1986. It is a vital supply point for the whole of East Germany and is now under Warsaw Pact control.

NATO intelligence has discovered a new Warsaw Pact armored train, codename "Colossus" is now operational and has arrived at Fulda station. Next stop Frankfurt. If this train is allowed to reach the outskirts of Frankfurt, it will bring its devastating guns to bare on NATO forces defending the city. It must be destroyed.

NATO Air Command has tasked the RAF with a daring daytime raid of Fulda station, its mission is to locate and destroy the Colossus before it can depart towards Frankfurt.

Targets

The NATO objective for this mission is to destroy the enemy armored train codename "Colossus" located at Fulda station.

Scenario Conditions

• Date: 30 May 1987
• Time of Day: 16:00 (Daytime)
• Detection Level: NATO: D WP: C
• Weather: Clear. Do not roll on the Weather Table.
• Map: The whole map is in play.
• The Front: NATO side is on/west of 3903 3805 3710 3715 3818 3823 3527 3931 3836 4343 5150 6351 6747 7644
• Closed Airfields: Giessen, Friedberg, Hanau, Allendorf, Paderborn.
• Inherent AAA/IR SAM Coverage: WP side within five hexes of the front.

NATO Order of Battle

Air Setup

Air Units and Markers:

• UK 1 x {4} Jaguar GR.1A, Bombing. Aggression Value +3. Set up Undetected heading east adjacent to NATO Orbit Point 1 at low altitude.
• Bombing flight follows NATO flight plan A within 2 hexes: Flight Plan: A1-3427, A2-4627, A3-5130, A4-5132, A5-5135, A6-4936, A7-4136, A8-2729
• UK 1 x {2} Buccaneer S.2B, Laser Designation. Aggression Value +1. Set up heading Undetected east adjacent to NATO Orbit Point 1 at low altitude.
• UK 2 x {4} Harrier GR.3, SEAD. Aggression Value +2. Set up Undetected heading east adjacent to NATO Orbit Point 2 at low altitude.
• UK 1 x {4} Tornado F.2A, CAP. Aggression Value +3. Set up Undetected heading east adjacent to NATO Orbit Point 3 at low altitude.
• UK 1 x {1} Falcon 20F, Jamming. Aggression Value +0. Set up Undetected heading east adjacent to NATO Orbit Point 3 at high altitude.
• Orbit Point 1 in 3227, Orbit Point 2 in 3330, Orbit Point 3 in 2531

NATO Pilot Quality

• Ace, Tornado F.2A
• Veteran, Harrier GR.3, Jaguar GR.1A
• Regular, Buccaneer S.2B, Falcon 20F

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 2 x Undetected Generic WP Flights A, B, within 1 hex of Orbit Point 1 (4718). Flight A heading west at low altitude. Flight B heading East at low altitude.

• Set up 2 x Undetected Generic WP Flights C, D, within 1 hex of Orbit Point 2 (4741). Flight C heading north east at low altitude. Flight D heading north west at low altitude.

• Set up 1 x Undetected Generic WP Flight E, within 1 hex of Orbit Point 3 (6617) heading south at low altitude.

• Set up 1 x Undetected Generic WP Flight F, within 1 hex of Orbit Point 4 (5141) heading north east at low altitude.

• Generic Flights A, B, C, D, E, F, follow WP flight plans detailed below within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  • Generic Flight A: A1-4518, A2-4118, A3-4129
  • Generic Flight B: B1-4540, B2-3937, B3-3934
  • Generic Flight C: C1-4918, C2-5318, C3-5329
  • Generic Flight D: D1-4940, D2-5437, D3-4437
  • Generic Flight E: E1-6619, E2-6630, E3-5230
  • Generic Flight F: F1-5340, F2-6534, F3-4734

• If Bot Flight Activation Check is Real Flight roll 1D10 for flight type:

  Roll	Flight Type
  1-2	MiG-29A

Ground Setup

Air Defense Units:

• 2 x SA-11 (4826, 5138) set up unlocated with SAM Warning Markers, radar on.
• 4 x SA-13 (4328, 5233, 4635, 4135) set up located.
• 5 x 2K22 (4628, 5030, 5034, 4636, 4137) set up located, radars turned on.
• The target hex (5132) contains inherent AAA Heavy Flak.

WP Pilot Quality

• Ace, MiG-21SPS
• Veteran, MiG-29A
• Regular, MiG-23M

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 3 dummy flights. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using clean movement profile for MiG-21SPS at combat throttle.
4. If bot flights reach last waypoint on flight plan, turn around and head back to waypoint 1. Repeat until mission ends.
5. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
6. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint.
7. NATO SEAD flights may jettison ordnance and proceed with CAP at any time during the scenario.
8. Bot flight target priority for Engagement Actions is detected good order flights first.
9. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 11 - NATO QRA, 14 - Direction Finding.
10. This scenario ends at the end of Turn 14. At that point, roll for recovery for all flights that have not yet recovered.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   12	NATO VP for Colossus Totally Destroyed
   9	NATO VP for Colossus Heavily Damaged
   6	NATO VP for Colossus Slightly Damaged
   2	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured
   2	Enemy SAM or AAA unit Totally Destroyed
   1	Enemy SAM or AAA unit Heavily Damaged

NSC7: The Heist

Mission Briefing

Nikolai Krasnov's intelligence has come to fruition. NATO special forces have been tracking the location of a top Warsaw Pact military official for several days.

Marshall of the Soviet Union Sergey Markov is due to fly close to the front on board an IL-76MD Transport on the morning of the 03 June to inspect the area from the air and speak with troops at Kassel Airbase to boost morale.

NATO Air Command has tasked five flights of fighter aircraft with intercepting and re-directing the transport as it makes its way around the rear area of the front line. A NATO flight is to get close to the IL-76MD transport, intimidate its pilots at close range and re-direct the flight back over NATO lines. The transport is to be guided in to land at Rhein-Main Airbase.

Warsaw Pact forces will not be expecting NATO forces to be in the area, nevertheless, the transport will be well protected by Warsaw Pact aircraft. Enemy escort fighters need to be engaged and kept well away from the transport if this mission is to succeed.

Targets

The NATO objective for this mission is to intercept, re-direct and escort the IL-76MD transporting Sergey Markov back to the NATO side of the front and guide it in to land at Rhein-Main Airbase.

Scenario Conditions

• Date: 03 June 1987
• Time of Day: 10:00 (Daytime)
• Detection Level: NATO: D WP: C
• Weather: Clear. Do not roll on the Weather Table.
• Map: The whole map is in play.
• The Front: NATO side is on/west of 3202 3005 3310 3213 3615 3522 3628 3534 3740 4044 5150 6351 6848 7547
• Closed Airfields: Giessen, Friedberg, Allendorf, Brenker Mark, Gutersloh. (Printed as "Brenker" and "Mark, Gutersloh" across a line break.)
• Inherent AAA/IR SAM Coverage: WP side within five hexes of the front.

NATO Order of Battle

Air Setup

Air Units and Markers:

• US 1 x {4} F-15A, CAP. Aggression Value +2. Set up heading east adjacent to NATO Orbit Points 1, 2, 3 or 4 at low altitude.
• US 1 x {4} F-16C, CAP. Aggression Value +1. Set up heading east adjacent to NATO Orbit Points 1, 2, 3 or 4 at low altitude.
• US 2 x {4} F-4E, CAP. Aggression Value +2. Set up heading east adjacent to NATO Orbit Points 1, 2, 3 or 4 at low altitude.
• UK 1 x {2} Tornado F.2A, CAP. Aggression Value +3. Set up heading east adjacent to NATO Orbit Points 1, 2, 3 or 4 at low altitude.
• Orbit Point 1 in 2932, Orbit Point 2 in 2726, Orbit Point 3 in 2720, Orbit Point 4 in 2914

NATO Pilot Quality

• Ace, Tornado F.2A
• Veteran, F-15A, F-4E
• Regular, F-16C

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 4 x QRA Undetected Generic WP Flights A, B, C, D on the ground ready at airfields below with Flight Ready markers:

  • Generic Flight A: Fulda Airbase (5032) heading west.
  • Generic Flight B: Fritzlar Airbase (4521) heading south east.
  • Generic Flight C: Muhlhausen Airbase (6318) heading north west.
  • Generic Flight D: Kassel Airbase (4514) heading east.

• QRA flights become part of the WP chit pool and begin take off during the movement phase on the following turns:

  • Generic Flight A: Turn 1
  • Generic Flight B: Turn 2
  • Generic Flight C: Turn 3
  • Generic Flight D: Turn 4

• USSR 1 x {4} MiG-29A, QRA. Aggression Value +2. Place counter on scenario setup sheet for use when activated.

• GDR 1 x {4} MiG-23MF, QRA. Aggression Value +1. Place counter on scenario setup sheet for use when activated.

• GDR 1 x {4} MiG-21BIS, QRA. Aggression Value +1. Place counter on scenario setup sheet for use when activated.

• USSR 2 x {4} Su-27S, Close Escort. Aggression Value +3. Set up Undetected heading north west adjacent to WP Orbit Point 1 (5533) at medium altitude. Su-27S flights are tasked with Close Escort of USSR IL-76MD transport flight.

• USSR 1 x {1} IL-76MD, Transport. Aggression Value +0. Set up Undetected heading north west at medium altitude adjacent to WP Orbit Point 1 (5533).

Ground Setup

Air Defense Units:

• 3 x SA-11 (5430, 5423, 5118) set up unlocated with SAM Warning Markers, radars turned on.
• 4 x SA-13 (4531, 4525, 4821, 5120) set up located.
• 5 x 2K22 (4730, 4528, 4727, 4724, 4522) set up located with radars turned on.
• 1 x EWR (5426)

WP Pilot Quality

• Ace, Su-27S
• Veteran, MiG-29A
• Regular, MiG-23MF, MiG-21BIS

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 1 dummy flight. A roll of 1-6 is a real flight. A roll of 7-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow Close Escort rules. Generic flights use clean movement profile for MiG-23MF at combat throttle.
4. If Detected enemy flight in same hex or within 9 hexes, go to Engagement Actions on PAC5.
5. If a bot flight is activated and no Detected enemy flights within 9 hexes, return to Close Escort role, use dash throttle if possible. (See SSR 10 for WP QRA flights).
6. USSR IL-76MD transport flight begins the scenario under WP control and follows flight plan A as per scenario setup instructions.
7. During the movement phase, if an activated NATO flight is within one hex of USSR IL-76MD transport flight at the same altitude, there are no WP flights within 2 hexes of the transport and the transport is detected, the NATO Player may attempt to take control of the transport flight. Roll 1D10, on a roll of 4-10, the transport passes to NATO control from that point onwards in the turn. A roll of 1-3 is a failure. The same NATO flight may only attempt control once per turn. If the IL-76MD flight has not moved yet on the turn it changes control, the owning side can move the transport flight if able on the next chit draw.
8. A NATO flight must remain within 2 hexes of IL-76MD flight at the same altitude when under NATO control. If there are no NATO flights within two hexes at the end of a game turn, the IL-76MD flight will return to WP control from the next turn onwards and attempt to re-join flight plan A at the nearest opportunity.
9. If IL-76MD flight is under WP control and reaches waypoint A6 on flight plan A, it must land at Kassel Airbase.
10. If IL-76MD flight is under WP control, once airborne, QRA flights will begin Close Escort of IL-76MD flight. If not in Close Escort range, QRA flights will use dash throttle (generic flights use MiG-23MF dash profile, do not mark off fuel) to enter range and attempt to climb once per turn to match altitude.
11. If IL-76MD flight is under NATO control, all bot flights will use dash throttle (generic flights use MiG-23MF dash profile, do not mark off fuel), attempt to move to medium altitude and attempt to intercept IL-76MD flight until a detected enemy flight is in same hex or within 9 hexes, at which point, go to Engagement Actions on PAC5. If no detected enemy flights are within 9 hexes, continue intercept task. If IL-76MD is back under WP control at any point, resume Close Escort.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   12	NATO VP if IL-76MD lands at Rhein-Main Airbase
   6	NATO VP if IL-76MD ends game under NATO control
   18	WP VP if IL-76MD lands at Kassel Airbase
   8	WP VP if IL-76MD ends game under WP control
   2	NATO VP for WP aircraft Shot Down or Crashed
   3	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured

2. The victory total is obtained by subtracting the WP VP total from the NATO VP total. The results can be a negative value. The victory total determines the victory level on the table as follows:

NSC8: The Night Witches

Mission Briefing

Nikita Rechkalov looked up to Nikolai Krasnov like a father. Not only had she been trained by him, they had been good friends for many years. The news of his defection and revelations of him being a spy had hit her hard. Whilst she found it hard to believe, his defection was a betrayal she could never forgive.

In the weeks before Nikolai's defection, Nikita had formed her own squadron based on an infamous all-female Soviet World War two squadron. It was part of what had inspired her to become a fighter pilot. When granted approval to form her own squadron, Nikita instantly knew the moniker they would be known by, the 588th Night Bomber Regiment "The Night Witches" were reborn.

Already feared by NATO forces, The Night Witches have been flying night raids on NATO targets deep into enemy territory. Every aircraft in the squadron has been painted jet black. The sight of all black aircraft raiding NATO targets even during the day has had the desired effect of driving fear into NATO ground forces.

A large Warsaw Pact raid group has been detected by NATO AWACS as it heads over the front line towards potential targets on the night of the 05 June at 01:00. NATO Air Command has scrambled all available fighters to intercept the group, targets are unknown. If confirmed to be The Night Witches, NATO pilots will need to be on guard and react quickly to any deception and feints as to where the real raid targets are before it is too late to stop them.

Targets

The NATO objective for this mission is to intercept and destroy the Warsaw Pact raid groups before they can hit their targets.

Scenario Conditions

• Date: 05 June 1987
• Time of Day: 01:00 (Night, Full Moon)
• Detection Level: NATO: C WP: C
• Weather: Clear. Do not roll on the Weather Table.
• Map: The whole map is in play.
• The Front: NATO side is on/west of 3402 3406 3513 3616 3519 3524 3628 3534 3940 4243 5150 6351 6848 7547
• Closed Airfields: Paderborn, Giessen, Friedberg, Allendorf.
• Inherent AAA/IR SAM Coverage: WP side within five hexes of the front.

NATO Order of Battle

Air Setup

Air Units and Markers:

• US 2 x {4} F-4D, CAP. Aggression Value +2. Set up heading east adjacent to NATO Orbit Point 1 or 2 at deck altitude.
• FRG 2 x {4} F-4F, CAP. Aggression Value +1. Set up heading east adjacent to NATO Orbit Point 1 or 2 at deck altitude.
• FRG 2 x {2} F-104G, CAP. Aggression Value +1. Set up heading east adjacent to NATO Orbit Point 1 or 2 at deck altitude.
• Orbit Point 1 in 0521, Orbit Point 2 in 0527

Ground Setup

Army Ground Units:

• 3 x NATO HQ (1333, 1526, 1618)

Air Defense Units:

• 3 x Chaparral set up located at the Players discretion at a minimum of 3 hexes apart, west of 24xx.
• 3 x Gepard set up located, radars on, at the Players discretion at a minimum of 3 hexes apart, west of 24xx.

NATO Pilot Quality

• Veteran, F-4D
• Regular, F-4F, F-104G

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 4 x Undetected Generic WP Flights A, B, C, D within 1 hex of Orbit Point 1 (3730) heading west at high altitude.

  Generic Flights A, B, C, D follow flight plan A within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-3530, A2-2530, A3-1634, A4-1333, A5-1329, A6-1727, A7-2527, A8-4235

• Set up 4 x Undetected Generic WP Flights E, F, G, H within 1 hex of Orbit Point 2 (3726) heading west at medium altitude. (Printed as "E, F G, H".)

  Generic Flights E, F, G, H follow flight plan B within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: B1-3526, B2-2926, B3-2323, B4-1523, B5-1526, B6-1824, B7-4224

• Set up 4 x Undetected Generic WP Flights I, J, K, L within 1 hex of Orbit Point 3 (3722) heading west at low altitude.

  Generic Flights I, J, K, L follow flight plan C within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: C1-3522, C2-3122, C3-2418, C4-1618, C5-2016, C6-3216, C7-4221

• If Bot Flight Activation Check is Real Flight roll 1D10 for flight type:

  Roll	Flight Type
  1-2	Su-24C
  3-6	MiG-29A
  7-10	Su-27S

WP Pilot Quality

• Ace, Su-27S (Rostov)
• Veteran, MiG-29A, Su-24C, Su-27S (Vilnius)

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 6 dummy flights. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using clean movement profile for Su-24C at combat throttle.
4. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
5. After activation, if Su-24C Bombing flight, ignore Engagement Actions, Defend as per Bombing assignment and continue on flight plan.
6. After activation, if MiG-29A or Su-27S, follow Close Escort rules. If no Bombing flights are activated, resume Close Escort with closest generic flight. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
7. At waypoints A3 (1634), B4 (1523), C3 (2418), bot Su-24C and un-activated generic flights must move to low altitude and remain at low altitude for the bombing run.
8. If a generic flight reaches an IP for a Target hex and there are un-activated Su-24C flights remaining, the flight activates as a Su-24C flight and bombs the target as per SSR9.
9. When a bot Su-24C flight reaches an IP (1433, 1525, 1719/1718) for the Target hexes roll for bombing attacks against a HQ (Profile D) at the earliest opportunity. Damage assessment is rolled at the end of the scenario.
10. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint or resume Close Escort role with closest Bombing flight with ordnance first, then Bombing flights without ordnance. If no Bombing flights are activated, resume Close Escort with closest generic flight.
11. Nikita Rechkalov is flying a Su-27S designated as Rostov #1. If the aircraft is shot down, the pilot automatically bails out and is recovered by WP forces at the end of the scenario on either side of the front.
12. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 11 - NATO QRA, 14 - Direction Finding, 15 - SEAD Strike.

Generic Bot flights when engaged by the Players SAM/AAA behave exactly the same as a Player flight per the RoP, however as soon as the flight is engaged, roll for bot flight activation and flight type.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   9	WP VP for NATO HQ Totally Destroyed
   6	WP VP for NATO HQ Heavily Damaged
   3	WP VP for NATO HQ Slightly Damaged
   3	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured
   6	NATO VP if Nikita Rechkalov is Shot Down

2. The victory total is obtained by subtracting the WP VP total from the NATO VP total. The results can be a negative value. The victory total determines the victory level on the table as follows:

NSC9: Heavy Rain

Mission Briefing

After a rigorous debriefing and interrogation, Nikolai Krasnov has been pushing to return to active duty with NATO Air Command. His wish has been granted on the basis that the negative propaganda and morale it will inevitably cause to Warsaw Pact forces is worth the risk.

Nikolai has joined the US Air Force. After the loss of many pilots during the early stages of the war, there's no shortage of available squadrons to join. NATO needs as many pilots as they can get, especially with the experience and military intelligence Nikolai will provide on the front line.

NATO Air Command has tasked aircraft under the command of Nikolai Krasnov with a deep strike raid of an enemy cruise missile site located at Quadlinburg, a site identified by the recently captured Sergey Markov.

With the location of the target being so far behind enemy lines, the mission has been held off until bad weather conditions are inbound. With heavy rain and thunderstorms covering most of East Germany, NATO forces are to use the bad weather to infiltrate deep into enemy territory in order to deliver their payload to the target.

Nikolai Krasnov is to lead the bombing run consisting of two flights of US F-111F Aardvarks. The Canadian Air Force is providing SEAD and Close Escort flights for the mission consisting of four flights of CF-18A Hornets.

Targets

The NATO objective for this mission is to destroy a Warsaw Pact cruise missile site located at Quadlinburg.

Scenario Conditions

• Date: 09 June 1987
• Time of Day: 16:00 (Daytime)
• Detection Level: NATO: D WP: D
• Weather: Roll on the Poor Weather Table.
• Map: The whole map is in play.
• The Front: NATO side is on/west of 3902 3906 3710 3812 3616 3522 3628 3534 3940 4243 5150 6351 6848 7547
• Closed Airfields: Paderborn, Allendorf, Giessen, Friedberg
• Inherent AAA/IR SAM Coverage: WP side within five hexes of the front.

NATO Order of Battle

Air Setup

Air Units and Markers:

• CAN 2 x {2} CF-18A, SEAD. Aggression Value +1. Set up heading east adjacent to NATO Orbit Point 1 at medium altitude.

• US 1 x {2} F-111F (Slam), Deep Strike. Aggression Value +3. Set up heading east adjacent to NATO Orbit Point 2 at medium altitude.

• US 1 x {2} F-111F (Jackal), Deep Strike. Aggression Value +2. Set up heading east adjacent to NATO Orbit Point 2 at medium altitude.

• CAN 2 x {4} CF-18A, Close Escort. Aggression Value +2. Set up heading east adjacent to NATO Orbit Point 3 at medium altitude.

• Bombing flights follow NATO flight path A as detailed below within 2 hexes:

  Flight Path A: A1-3705, A2-4705, A3-5103, A4-6903, A5-7204, A6-6010, A7-4610, A8-3516

• Orbit Point 1 in 3703, Orbit Point 2 in 3505, Orbit Point 3 in 3707

NATO Pilot Quality

• Ace, F-111F (Slam)
• Veteran, F-111F (Jackal), CF-18A (Dack, Banks)
• Regular, CF-18A (Ness, Jasper)

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

Undetected Generic WP Flights will be set up at orbit points and become part of the WP chit pool at start of the following movement phases:

• Turn 1, Set up 1 x Undetected Generic WP Flight A within 1 hex of Orbit Point 1 (3917) heading north at low altitude.

  Generic Flight A follows flight plan A within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-3915, A2-3909

• Turn 2, Set up 1 x Undetected Generic WP Flight B within 1 hex of Orbit Point 2 (4717) heading north at medium altitude.

  Generic Flight B follows flight plan B within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: B1-4715, B2-4706

• Turn 3, Set up 2 x Undetected Generic WP Flights C, D within 1 hex of Orbit Point 3 (5717) heading north at high altitude.

  Generic Flights C, D follow flight plan C within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: C1-5715, C2-5706

• Turn 5, Set up 2 x Undetected Generic WP Flights E, F within 1 hex of Orbit Point 4 (6517) heading north at medium altitude.

  Generic Flights E, F follow flight plan D within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: D1-6515, D2-6506

• Turn 8, Set up 2 x Undetected Generic WP Flights G, H within 1 hex of Orbit Point 5 (7317) heading north at low altitude.

  Generic Flights G, H follow flight plan E within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: E1-7315, E2-7306

• If Bot Flight Activation Check is Real Flight roll 1D10 for flight type:

  Roll

Ground Setup

Army Ground Units:

• 1 x WP Cruise Missile Site (7204)

Air Defense Units:

• 2 x SA-12 (A-5211, B-5704) set up unlocated with SAM Warning Markers, radars turned on, array facing west.
• 1 x SA-4 (D1-7107) set up unlocated with SAM Warning Marker, radar turned on.
• 1 x SA-13 (7004) set up located.
• 4 x 2K22 (7203, 7006, 5210, 5703) set up located.
• 4 x Heavy Flak (6702, 6704, 6109, 6210) set up located.
• 1 x EWR (7505)

WP Pilot Quality

• Ace, MiG-29A
• Veteran, MiG-21BIS
• Regular, MiG-23M

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 4 dummy flights. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using clean movement profile for MiG21BIS at combat throttle.
4. If bot flights reach last waypoint on flight plan, turn around and head back to waypoint 1. Repeat until mission ends.
5. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
6. Bot flight target priority for Engagement Actions is detected good order flights first.
7. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint.
8. Nikolai Krasnov is flying a F-111F designated as Slam #1. If the aircraft is shot down, the pilot automatically bails out and is recovered by NATO forces at the end of the scenario on either side of the front.
9. Ignore the following Random Events [PAC5], if rolled: 5 – WP QRA, 11 - NATO QRA, 14 - Direction Finding, 15 - SEAD Strike.
10. This scenario ends at the end of Turn 18. At that point, roll for recovery for all flights that have not yet recovered.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   12	NATO VP if WP CM Site Totally Destroyed
   9	NATO VP if WP CM Site Heavily Damaged
   6	NATO VP if WP CM Site Slightly Damaged
   2	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   7	WP VP if Nikolai Krasnov is Shot Down
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured
   2	Enemy SAM or AAA unit Totally Destroyed

NSC10: Showdown

Mission Briefing

The war is heading towards a stalemate. With the main Warsaw Pact ground offensive stalled by NATO forces, Warsaw Pact High Command has authorized the use of tactical nuclear weapons. The location of NATO Air Command has been determined, hidden in a business district in the city of Essen. Nikita Rechkalov's squadron is tasked with delivering a 300-kiloton payload over the target. The inevitable loss of life will be catastrophic, but Warsaw Pact High Command is gambling on the destruction of NATO's Air Command staff bringing about a swift end to the war and the possible surrender of NATO forces in the area of operations.

As a Warsaw Pact raid group speeds towards Essen, Nikolai Krasnov's flight of F-15A Eagles along with fighters from all available NATO air forces are already airborne and inbound to intercept the incoming enemy aircraft.

At dawn above the skies of Germany, a dogfight is about to begin in which the lives of Nikolai Krasnov and Nikita Rechkalov will collide once again, only this time the fate of Europe and the rest of the free world is in their hands.

Targets

The NATO objective for this mission is to intercept the Warsaw Pact raid groups before they can deliver a 300-kiloton nuclear payload over NATO Air Command at Essen.

Scenario Conditions

• Date: 14 June 1987
• Time of Day: 06:15 (Dawn)
• Detection Level: NATO: C WP: D
• Weather: Roll for Weather using Random Weather.
• Map: The western map is in play.
• The Front: NATO side is on/west of 4102 4005 3708 3714 3918 4021 4226 4431 4638 4843 5148 6152 6849 7447
• Closed Airfields: Giessen, Friedberg, Allendorf, Paderborn, Brenker Mark
• Inherent AAA/IR SAM Coverage: None

NATO Order of Battle

Air Setup

Air Units and Markers:

• UK 1 x {4} Tornado F.2A, CAP. Aggression Value +3. Set up heading north east adjacent to NATO Orbit Points 1, 2 or 3 at deck altitude.
• NE 1 x {4} F-16A, CAP. Aggression Value +3. Set up heading north east adjacent to NATO Orbit Points 1, 2 or 3 at deck altitude. (Printed as "NE".)
• FRG 1 x {4} F-104G, CAP. Aggression Value +3. Set up heading north east adjacent to NATO Orbit Points 1, 2 or 3 at deck altitude.
• US 1 x {4} F-15A, CAP. Aggression Value +3. Set up heading north east adjacent to NATO Orbit Points 1, 2 or 3 at deck altitude.
• US 1 x {4} F-4E, CAP. Aggression Value +3. Set up heading north east adjacent to NATO Orbit Points 1, 2 or 3 at deck altitude.
• CAN 1 x {4} CF-18A, CAP. Aggression Value +3. Set up heading north east adjacent to NATO Orbit Points 1, 2 or 3 at deck altitude.
• During setup, maximum of 2 flights at each orbit point.
• Orbit Point 1 in 1824, Orbit Point 2 in 1121, Orbit Point 3 in 0317.

Ground Setup

Army Ground / Air Defense Units:

• 1 x NATO HQ – NATO Air Command (1211)

NATO Pilot Quality

• Ace, Tornado F.2A, F-16A, F-104G, F-15A, F-4D, CF-18A

Warsaw Pact Order of Battle

Air Setup

Air Units and Markers:

• Set up 6 x Undetected Generic WP Flights A, B, C, D, E, F within 1 hex of Orbit Point 1 (3907) heading north west at medium altitude.

  Generic Flights A, B, C, D, E, F follow flight plan A within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: A1-3706, A2-3404, A3-2204, A4-1209, A5-1211, A6-2011, A7-2509, A8-4109

• Set up 6 x Undetected Generic WP Flights G, H, I, J, K, L within 1 hex of Orbit Point 2 (4114) heading south west at medium altitude.

  Generic Flights G, H, I, J, K, L follow flight plan B within 1 hex until activated. Once Activated follow PAC5 for bot flight instructions. See SSRs for exceptions.

  Flight Plan: B1-3915, B2-3318, B3-2514, B4-1714, B5-1211, B6-1908, B7-2511, B8-4111

• If Bot Flight Activation Check is Real Flight roll 1D10 for flight type:

  Roll	Flight Type
  1-2	MiG-27M
  3-5	MiG-29A
  6-7	Su-27S
  8-10	MiG-21BIS

• USSR 2 x {4} MiG-27M, Bombing. Aggression Value +3. Place counters on scenario setup sheet for use when activated.

WP Pilot Quality

• Ace, MiG-29A, Su-27S, MiG-27M
• Veteran, MiG-21BIS

Scenario Special Rules

1. Bot flights follow all rules in PAC5 with the following exceptions:
2. When activating bot flights, maximum of 4 dummy flights. A roll of 1-5 is a real flight. A roll of 6-10 is a dummy flight. Do not add negative modifiers to the activation roll (PAC5).
3. Generic bot flights ignore ≥ 8 No Engagement attempt Go to Non-Combat Actions on PAC5. Instead follow mission flight plan within 1 hex using clean movement profile for MiG21BIS at combat throttle.
4. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
5. After activation, if MiG-27M Bombing flight, ignore Engagement Actions, Defend as per Bombing assignment and continue on flight plan.
6. After activation, if MiG-29A, Su-27S or MiG-21BIS, follow Close Escort rules. If no Bombing flights are activated, resume Close Escort with closest generic flight. If Detected enemy flight in same hex or within 7 hexes, go to Engagement Actions on PAC5.
7. At waypoints A4 (1209), B4 (1714), bot MiG-27M and un-activated generic flights must move to high altitude and remain at high altitude for the bombing run.
8. If a generic flight reaches the Target hex (1211) and there are un-activated MiG-27M flights remaining, the flight activates as a MiG-27M flight and bombs the target as below.
9. When a MiG-27M flight reaches Target hex (1211), do not roll on the Air-to-Ground Attack Table; the Nuke attack is automatically successful if the bombing aircraft is not shot down, forced to jettison, or crippled prior to the attack. Place a Nuke Attack marker in the target hex. The Essen business district and NATO Air Command is inflicted with Total Destruction. Any airborne flight (other than the flight conducting the attack) in or adjacent to the target hex at the moment of the attack immediately Aborts and all aircraft in the flight are Damaged. For the remainder of the scenario, no flights may enter the target hex. If forced to do so, the flight Aborts and all aircraft in it are Damaged.
10. Bot Close Escort flights must avoid the Nuke blast area while performing Close Escort or during Engagement Actions, unless forced to do so by maneuver actions.
11. If a bot flight is activated away from its flight plan and no Detected enemy flights are within 7 hexes, use combat throttle, move to medium altitude (do not zoom climb) and return to flight plan closest waypoint or resume Close Escort role with closest Bombing flight with ordnance first, then Bombing flights without ordnance. If no Bombing flights are activated, resume Close Escort with closest generic flight.

Victory Conditions

1. At the end of the scenario, both the WP and NATO total their victory points as follows:

   VP	Objective
   12	WP VP for Raid Target Total Destruction
   3	NATO VP for WP aircraft Shot Down or Crashed
   4	WP VP for NATO aircraft Shot Down or Crashed
   2	Enemy aircraft recovers Crippled
   1	Enemy aircraft recovers Damaged
   1	Enemy crew member killed or captured
   6	NATO VP if Nikita Rechkalov is Shot Down
   6	WP VP if Nikolai Krasnov is Shot Down

2. The victory total is obtained by subtracting the WP VP total from the NATO VP total. The results can be a negative value. The victory total determines the victory level on the table as follows:

Bot Example of Play

Below is a brief example of how bot flights behave during these solo scenarios using the waypoints system, variable altitude and activation rolls.

In figure 1 below, 3 bot WP generic flights A, B and C are following flight plan A, heading towards a NATO target in West Germany. A maximum of 2 generic flights are Real flights. A maximum of 1 generic flight is a Dummy flight. As the NATO Player, we don't know which ones are which just yet.

In the Detection phase of Turn 1, generic flight A is Detected, generic flights B and C remain Undetected. Our NATO F-4E flight designated "Vegas" is Detected and on an intercept course.

Figure 1 – Start of T1 movement phase

During the Movement Phase of Turn 1, the WP bot gains the initiative. In the first chit draw, the bot gets to activate all 3 flights. Since there are no Detected NATO flights within 7 hexes, the bot flights follow their flight plan and move at combat throttle using 4 movement points at high altitude as per a scenario special rule for the generic bot flight profile.

As each bot flight moves within 1 hex of a waypoint marker, each flight rolls on the bot Altitude Change table. Generic flight A rolls a 6 to "descend one altitude band for free", then continues moving. Generic flight B rolls a 3 for "No Change" and continues moving. Generic flight C moves into 1 hex range of a waypoint with its last movement point and rolls a 4 to "Spend movement point to dive to deck". However, since the flight has no movement points remaining, the result is treated as "No Change". On the next turn in the movement phase during its activation, generic bot flight C will roll again on the Altitude Change table as its first action, before it expends a movement point, but after any bot flight activation check, if required.

Figure 2 – T1 movement phase, F-4E BVR attempt

Our F-4E flight moves next and we decide to attempt to engage Detected generic flight A in BVR combat (Figure 2). We make our BVR engagement roll and succeed on a roll of 14. At this point, before any maneuver roll is made, the bot flight makes a bot flight activation check. On a roll of a 4, bot generic flight A is a Real flight. The Player then rolls on the bot flight type table and for this example the result is a flight of MiG-29A's designated "Oskin". Not good!

In the resulting maneuver roll, our F-4E flight misses with its BVR shots and the MiG-29A flight passes its morale check with no adverse effects. During the Tracking Phase of Turn 1, the MiG-29A flight becomes Undetected. More bad news!

Figure 3 – T1 movement phase, after BVR attempt

In the Detection Phase of Turn 2, generic flights B and C are Detected and MiG-29A "Oskin" flight remains Undetected. Our F-4E flight remains Detected. This means "Vegas" cannot engage "Oskin" this turn, but they can engage us!

During the Movement Phase of Turn 2, the WP bot gains the initiative again, this time it gets to activate 2 flights. Starting with MiG-29A "Oskin" flight, with our F-4E flight Detected and within 7 hexes, the bot flight rolls on the bot engagement table. This results in a BVR engagement attempt, which is successful. The MiG-29A flight damages 1 of our F-4E's but we roll high on our morale check with no adverse effects. The MiG-29A flight then turns 90 degrees left and moves ahead to end its movement.

Figure 4 – T2 movement phase, MiG-29A activation

The next WP flight to activate is generic flight B. Since our F-4E "Vegas" flight is Detected and within 7 hexes, the bot flights first action is to perform a bot flight activation check before doing anything else. On a roll of a 3, bot generic flight B is a Real flight. The Player then rolls on the bot flight type table and for this example the result is a Su-24M flight designated "Krylov".

Since Su-24M flight "Krylov" is tasked with Bombing, its engagement rules are to "Defend" and it will therefore not attempt to engage our F-4E flight in air-to-air combat. Instead, it moves ahead 3 hexes at combat throttle using the Su-24M laden flight profile at medium altitude (it no longer uses the generic flight movement profile) closer to its raid target. Since the maximum number of Real bot flights has been reached, generic flight C is removed from play as it can only be a Dummy flight. Time for "Vegas" to engage those Su-24M's…

Figure 5 – T2 movement phase, Su-24M activation