Is there anything we can adjust on our end regarding callsigns? The limitation we run into is that we can’t change flight-number callsigns mid-flight, and we also can’t have different aircraft flying under the same callsign unless they actually departed as a single flight. This applies to all GAF operations, whether event-related or regular day-to-day missions.
Because each aircraft or element must keep the callsign it departed with, and because different squadrons operate independently, we can’t consolidate everyone into a single “Flight of XX” once airborne.
If there’s anything within those constraints that we can modify to make things smoother for ATC, we’re happy to explore it.
4 Likes
If “flight of XX” isn’t used, separation criteria are not met and controllers should separate the aircraft, either by vectoring, warnings or even reports.
This does not happen during real life procedure’s
It may not be like that in real life, but that’s how it is in IF.
Understood. The only issue is that GAF can’t always use a single ‘Flight of XX’ callsign because of how our callsigns are structured. GAF follows real world procedures That’s why I asked. just trying to find a workable solution that fits both IFATC rules and how military aviation operate.
We really do empathize with ATC and appreciate the work you all do. ( I’ve been in IFATC my self ) The only reason we bring this up is because, for military aviation, there’s currently a big gap in realism. We’re just trying to find a solution that keeps us compliant while also making military operations feel closer to what they should be.
4 Likes