If we don't discuss these things we will lose momentum. As keeping up to date with a developing SOP provides an continuing challenge for the more experienced members as well.
When talking about SOP and Brevity, It's always good to provide background to how you reached your conclusions, as having an understanding to for example the difference between "tally" and "visual" help's you remember to use the right call.
In the case of "Push" the only background we have is that you hate it
My thoughts on push brevity.
"Push victor 130" - for me it's associated with pushing button's on the radios
"Pushing thru angels 10" - informative call of your (or flights) current attitude, informing that you are currently in a climb.
"Climb to angels 10" - a directive/order call telling you to change alt.
Using different Brevity on informative v.s. directive R/T, I think is good practise as radio quality settings will not be on "max" all the time.
When writing Brevity SOP i suppose you looking to de-conflict words that sound similar (start with the same pronunciation) in a similar context.
Mind you also that all thou I can chat a bit in english it's not my native language, and some blokes around here have more or less of an accent going on.
I prefer and use "Lead" myself when I operate.
All thou in my world "Lead" represents the Leading/Commanding aircraft of the flight which might not necessarily be Tiger-One.
Lead might pass command to tiger-3 if he for some reason has to leave the AO, for various reasons. Tiger 3 is still Tiger 3 but also Tiger Lead?
As for TGP on target I can talk/practise with you any time. (when I'm back home)
My few findings.
- TAD to EXP2 mode, when working target AO.
- Hook on tad to "hook cursor" (check distance from reference to other positions, especially friendly A/C if your lead. break em off if they do not tally)
- Set a waypoint on target location, either from briefing or initial contact with JTAC. (if Lead give grids to all of your flight and use same name on waypoint) I usually call this point ECHO.
- Set a second waypoint close by or when the first target is called out ECHO-TWO, I use this as "current" tasking or target. (normally have this selected on hud)
If I get tasked to hit a target I replace the coordinates on ECHO-TWO and slew the TGP on that target.
- Drop markpoints every time you spot a group or single target on the TGP.
- Set SPI using the TAD on the MFCD, and slew your TGP to that SPI.
- After initial orientation and placing of orbit/IP point, turn MAP off on the TAD.
- Don't try and fly formation and go heads down at the same time, de-conflict flight in altitude and "set up shop" at least 15nm out.
- Set a tight45° orbit and use the time when the TGP is blind to gather S/A by eyeballing the A/O and check friendly A/C locations on the TAD.
- Change bullseye on CDU anchor page, to the ECHO WP. Set HUD to ON.
- Zoom out WIDE, when slewing the TGP, if something looks like something investigate with NARROW (china fwd) and return to search in wide.
I could probably continue with the list but I've got to hit the sack.
Oh! and Neil how do you change the slew rate on the TGP?
Best
David
