Falcon BMS is not alone in the way that we have multiple menu pages with repeated similar commands.
The way I got around it was to use a large prefix set for each flight member that commands exist for (Wingman, Element, and the entire Flight), where the 4th and 1st aircraft do not have radio menu items specifically.
Then inside each final command, I could tell where the command needed to be sent. I left many comments in my profile and though some of my methods are very advanced, you can feel free to use it as a way to understand methods for these sorts of evaluations. It is dynamic in that most variables are preset in the KEYPRESS_INIT command which loads when the profile loads, this way the individual commands can use keywords in the dynamic keypress variable button press names themselves.
Check it out, feel free to use bits as you wish (but if it's for public distribution, and you want to copy entire sections, please leave the attribution in tact --- otherwise, use anything you want, modify it however you want, or not)
I'm a Falcon nut, happy to help out a fellow Viper Driver if you have any questions! Cheers!
*probably should have said -- the BMS profile I'm referring to is linked in my sig ↓↓↓