Argument for SL-requested air strikes

1. COs can't do it fast enough.
   With fighters, we can strike every 20-30 seconds. COs are too busy.
   With the bomber, we can strike every 10 seconds. COs are too busy to issue the jets orders every 10 seconds.
   LISTEN! The COs really don't actually want this job!
   (NOTE: There are occasions where the CO needs to designate a priority air strike that no SL would call in.)
2. COs don't have enough information.
   They can use the targets that players have spotted - but the jets can see that too.
   They can use the UAV - but the jets can see that too.
   They can use the scan - but it doesn't tell them what is armor or helo or infantry.
   They can use what the squads tell them - but the squads can just tell the jets.
   In EVERY case, there is ANOTHER problem. The CO doesn't know what the priority targets are. We may all see that someone has spotted a tank off on the horizon. But ONLY a squad knows (within the 20-second window), WHICH target they NEED eliminated to complete their mission.
   The jets don't know. The CO doesn't know ALL THE TIME. The information must be shared for us to be effective. If someone goes through the trouble of hitting the TS PTT key to call an airstrike, we darn well know they need it, and we WILL BE THERE.
   Otherwise, we spend our time wandering around wondering if the kills we get make any difference other than costing the enemy a ticket or 2.
3. Proof is in the pudding.
   During the scrim, a CO previously commended for his use of air squads, and another CO who actually has spent time flying - both of these COs recognized for excellence, one of them determined to keep in mind to use the jet squad well - failed to use the jet squad with ANY reasonable effectiveness. NO DISCREDIT TO THEM. None at all. I am convinced that the tools necessary to do that job well just aren't in the CO role. They didn't, because they couldn't.
   The best thing a CO can do for his squads concerning the jets is say, "Here squads, here are some jets. Use them as you see fit, until I need them for something specific."

Protocol for SL-requested air strikes
First, read this thread:
http://www.tacticalgamer.com/battlefield-2-ranked-vanilla/58463-sls-pilots-get-set-up-call-air-strikes.html

Successful protocol
SL2: Squad 2 requesting air strike.
531: Airstrike available, Squad 2.
SL2: Tank, northeast of our position.
531: Airstrike ETA 20 seconds.
SL2: Airstrike positive. (or "Airstrike successful." or "Good kill." or "Target down.")

Once familiarity with the protocol is established, it can be shortened. This is helpful, because air strikes can often be completed inside 10 seconds.
Successful protocol - abbreviated
SL2: Squad 2 air strike.
531: Go squad 2.
SL2: Tank, northeast.
531: ETA 10 seconds.
SL2: Airstrike positive.


Special conditions:

Not available
SL2: Squad 2 air strike.
531: Negative, Squad 2. (or "Airstrike not available, Squad 2.")

Airstrike failed
SL2: Squad 2 air strike.
531: Go squad 2.
SL2: Enemy armor, northeast of our position.
531: ETA 10 seconds.
SL2: Airstrike negative. (Give new target info)
Examples: Target moving north. Target same location. Wrong target killed. (We hit the jeep instead of the Tanks. Oops.)

Abort
SL2: Squad 2 air strike.
531: Go squad 2.
SL2: Enemy armor, northeast of our position.
531: ETA 30 seconds.
SL2: Abort air strike, target down. (Target has been killed already)


Protocol for CO-ordered air strikes
CO: Creates attack marker waypoint
CO: "Target: helo" (NOTE: 2 words. Loud and clear.)
531: "ETA: 20 seconds"

There are only 2 excuses for not complying with a COs air strike order:
1. Currently dogfighting ("Strike unavailable-dogfight")
2. Jet is down ("Strike unavailable-jet down")

If either is the case, report that to the CO instead of giving an ETA.