shortie
06-09-2005, 03:53 PM
These rules are intended to avoid unintentional attacks on friendly submarines by airborne platforms.
Problem:
Sonobouy receivers in the P-3 and the MH-60 offer only limited opportunity to classify submarines in dense traffic areas. Especially SSKs are very hard to classify, as the low noise source level of the sub and sound propagation usually leaves only the first 50Hz line visible. This line is also present on most civilian vessels.
The attack has to be carried out as soon as possible to avoid loosing contact to the submarine, so the time required to drop additional bouys and the time until the bouy is fully deployed and transmits data often is too long to avoid being counter-detected by the submarine.
Pilots try to avoid entering the sam-range of the submarine unless necessary to drop sonobouys or to release weapons.
Rules:
Submarines should post a no-attack area using the chat window by posting
sets of coordinates in which a friendly submarine is operating
a longitude or latitude (e.g. south of 5400N or east of 14000E)
a combination of latitude and longitude
a circular area defined by center position and range
These areas may be updated as the mission progresses and the subs travels through the area. If a sub intends to transit to a specific point, the no-attack area may be established as a corridor defined by the waypoints a sub intends to use.
Inside this area, only submarine launched asw weapons are allowed to be releasedunless the submarine establishing the area authorizes an specific attack.
Outside this area, air-launched and sub-launched asw weapons are permitted.
WARNING!
It should be noted that it is not only prohibited to release asw weapons inside prohibited areas but also asw weapons have to be programmed in a way to avoid them entering prohibited areas on their run (e.g. no circling runs near the boundary).
Mission builders are requested to include a graphical depiction of no-attack areas using the mission editor and also ensure that AI submarines do not leave this area.
Problem:
Sonobouy receivers in the P-3 and the MH-60 offer only limited opportunity to classify submarines in dense traffic areas. Especially SSKs are very hard to classify, as the low noise source level of the sub and sound propagation usually leaves only the first 50Hz line visible. This line is also present on most civilian vessels.
The attack has to be carried out as soon as possible to avoid loosing contact to the submarine, so the time required to drop additional bouys and the time until the bouy is fully deployed and transmits data often is too long to avoid being counter-detected by the submarine.
Pilots try to avoid entering the sam-range of the submarine unless necessary to drop sonobouys or to release weapons.
Rules:
Submarines should post a no-attack area using the chat window by posting
sets of coordinates in which a friendly submarine is operating
a longitude or latitude (e.g. south of 5400N or east of 14000E)
a combination of latitude and longitude
a circular area defined by center position and range
These areas may be updated as the mission progresses and the subs travels through the area. If a sub intends to transit to a specific point, the no-attack area may be established as a corridor defined by the waypoints a sub intends to use.
Inside this area, only submarine launched asw weapons are allowed to be releasedunless the submarine establishing the area authorizes an specific attack.
Outside this area, air-launched and sub-launched asw weapons are permitted.
WARNING!
It should be noted that it is not only prohibited to release asw weapons inside prohibited areas but also asw weapons have to be programmed in a way to avoid them entering prohibited areas on their run (e.g. no circling runs near the boundary).
Mission builders are requested to include a graphical depiction of no-attack areas using the mission editor and also ensure that AI submarines do not leave this area.