When a friendly pilot gets shot down, a radio beacon has a chance of spawning on the ground. No particular information given on the location, unless AWACS or WM reports anything
If the pilot survived the ejection, then there will be text messages simulating radio-calls from the downed pilot transmitted on guard within a certain radius and at certain intervals. Any BLUEFOR assets can acknowledge the transmission via F10 to get more information regarding location of the pilot
The pilot will start to move towards BLUEFOR (general direction) after 3-4 hours from landing. This should give any on-hand CSAR the ability to do a mission, and should create variation if CSAR needs to be scheduled for the next day
AOC can schedule a CSAR mission on the next cycle if no CSAR is available at the current time
Greater and greater possibility for the pilot to die or get captured as time progresses - to say a maximum of 48hrs where the beacon will de-spawn and he will essentially be MIA.
I was thinking something like this:
When a friendly pilot gets shot down, a radio beacon has a chance of spawning on the ground. No particular information given on the location, unless AWACS or WM reports anything
If the pilot survived the ejection, then there will be text messages simulating radio-calls from the downed pilot transmitted on guard within a certain radius and at certain intervals. Any BLUEFOR assets can acknowledge the transmission via F10 to get more information regarding location of the pilot
The pilot will start to move towards BLUEFOR (general direction) after 3-4 hours from landing. This should give any on-hand CSAR the ability to do a mission, and should create variation if CSAR needs to be scheduled for the next day
AOC can schedule a CSAR mission on the next cycle if no CSAR is available at the current time
Greater and greater possibility for the pilot to die or get captured as time progresses - to say a maximum of 48hrs where the beacon will de-spawn and he will essentially be MIA.