Wow, Nikos. That’s great work getting the BMS approach to come as close as possible to the real world. :clap2:
The main differences is the addition of the OM/MM beacons and the Glide Slope angle of 2.5 degrees.
I do think I remember flying that procedure into Aviano way back in the Falcon AF days. As a pilot, I always make use of all Cockpit Resources so I can exercise CRM (Cockpit Resource Management). Therefore, I’d bring up the ILS cross-hairs on my approach to that airport even if I wasn’t in IFR conditions. Unfortunately, the Glide Slope for that airport in Falcon AF would take you right through a section of ground. If you are a pilot and made the bad assumption that the G/S was calibrated to meet standard approach requirements for obstacle clearance, you could easily follow the GS into the ground without thinking. The probability of that was much higher because you basically only have 2D vision so it was more difficult in Falcon AF to notice you were getting really close to this obstacle. Oops. I should have noticed and disregarded the G/S and pulled up. :doh:
Anyway, thanks again for your work. Maybe someday in the future the dev team will add approach crafting tools in the same fashion as they’ve added some good weather crafting tools. Then guys like you will be able to closer model the real world approaches.
I’d be happy to do coding similar to this myself if I could get added to the dev team. (I’m a retired software engineer with years of software, hardware and real flying experience.) As a real pilot and software engineer I could probably add code to the BMS Avionics code such as making the ILS and TACAN audio knobs work so that you could hear the TACAN ID’s and ILS ID’s in Morse code and vary their volume with those pots in your pit (if you have them).
Also as a Ham Radio operator, I’ve seen several Morse Code audio generator code examples in various programming languages that could be leveraged such that those ID’s are just in Dot and Dash forms (… ._ …_ … = IAVI) somewhere in BMS files and that would make it really easy (as far as I know) to add another Morse Code ID. I haven’t had the time to fly BMS approaches (I’m really busy finishing up my full scale pit build) and see if those Morse Code ID’s are heard. However, I suspect they aren’t since the ILS and TACAN volume controls are not implemented. (Let me know if I’m wrong about those audio Morse Code IDs.)
For me as a pilot, I’d love to see that added although I know most folks wouldn’t be interested in that feature so it would be way down on the feature implementation schedule. However, I’ll bet for those of us that are real pilots with IFR approach experience we would like that feature as it increases the realism of IFR approaches.