LSO - Report Overhead Break vs. Approach Report Overhead break
-
I’ve been practicing the Case I recovery TE and am using VoiceAttack with the AVCS Falcon BMS profile. Whenever I use my voice to report overhead break I see that VoiceAttack selects the Report Overhead break from the Approach page and I never get the paddle call from the LSO. So I am wondering if the “Report Overhead Break” is different on the LSO page than the one on the Approach page? My mind tells me that they should be the same but who knows…this is BMS and I’ve learned not to assume anything. Maybe the LSO page version is coded to inform the LSO about the break.
Anyone can help a salty dog out?
-
@Todd1215 Yep it appears to be a different.
I think one or two other comms on the carrier page also overlap … “report airborn”?
But otoh I think you can ask carrier for wind speed / QNH etc on normal comms page… so, yeah that’s BMS for you.
-
@Todd1215 ,
To tell the carrier you are breaking and to differentiate it from a land-based break call, preface your voice command with “Carrier”. I also use Voice Attack and AVCS profile. The break command I use is: “Carrier break left”. Give that a try.Using the AVCS “create new voice command” order, you can also create new voice commands for that call that wwill properly invoke the correct response for a carrier approach instead of a land-based overhead approach. @SemlerPDX can probably give you some better advice here on how to do that.
Also,if you get a bolter or wave-off, when you have cleared the deck, you have to make that break call AGAIN to alert the LSO that you are back in the go-around profile. Otherwise you may not get “Paddles Contact” when you are back in the groove.
Hope that helps.
Regards,
Tomcattwo
(VoiceClone) -
@airtex2019 said in LSO - Report Overhead Break vs. Approach Report Overhead break:
I think one or two other comms on the carrier page also overlap … “report airborn”?
They won’t overlap if you use @Tomcattwo “approach” … +1 btw.
Separate carrier and ground with “prefix” (eg … Carrier, Mother) for carrier ops.Cheers
-
Thanks for all the recommendations . I am familiar with making new commands in AVCS so I will give that a go and separate some of the overlap commands for Carriers.
-
@Todd1215 Presently, the non-descript commands such as “report airborne” or “report overhead break” (and some others) can be changed to be the default for some other group if desired, like if you use the carrier more than airbases, you might want that one to be the default for “overhead break” without having to preface it with “Carrier”.
Please refer to the infographic in the AVCS4 BMS Command Reference for more info:
https://veterans-gaming.com/semlerpdx-avcs/profiles/commref/bms41.html/
(say, “Open the Command Reference”, to view this webpage anytime)