BMS F-16C/D 4.34 Flight Manual page 152

T.O. BMS1F-16CM-1
Mudhen1 flight:
The general section states which modes will be active upon DTC loading, i.e.: Modes 1, 2 and 4. The
relevant codes are given. Please note that for Panther and Mudhen flights, their Mode 1 codes are the
same, their Mode 2 and Mode 3 codes are different and their Mode 4 keys toggle at the same time.
The IFF Policy is quite important to read if you want to understand what you get as answers when you
interrogate other flights in the campaign.
•
M1 is assigned to a team. All the allies share the same code, which is changed every hour as
stated in the TIME events.
•
M2 is specific to each aircraft. All aircraft have a different M2 code, which does not change.
Panther2 has M2 code 7404 and Mudhen1 has M2 code 3434, so if Mudhen interrogates
Panther with its default M2 interrogator setting Panther will not reply positively and will be
categorised as bogey.
•
M3 is specific to each aircraft as well but (unlike M2) rotates every hour. Panther2 has M3
code 7354 and Mudhen1 has M2 code 4610 until 1000 FT when the codes will switch to 1004
& 2634 respectively.
•
M4 is always assigned per team and the encryption key rotates every 24 hours.
TIME events, as explained above, detail the moment the code changes. POS (Position) events show
any changes specific to ingress or egress, but in this case both are the same with Modes 1, 2 and 4
active throughout the flight.
The above picture comes from another campaign flight brief, not related to our first example. Notice
how it is different in policy. In the briefing above you see active criteria for time changing each hour for
M1 & M3, the M4 key changing at 1200 FT and two position changes (North of STPT 4 for Mode 4 and
South of STPT 9 for Modes 1/2/4); thus active modes should be different during ingress and egress.
BMS 4.34 Dash 1
© Red Dog 2012-2019
BMS 4.34 Change 2.00
Page: 152