Rob Killins 897126 Posted January 27, 2011 at 02:06 AM Posted January 27, 2011 at 02:06 AM Can someone explain the use of "ALTOWNER" How does it differ in use than "OWNER" For example, the heirarchy for the ground sector at MyAirport is: OWNER:MYA_G:MYA_T:MYA_D:MYA_A:MYA_AC:MYA_AA:MYA_RDO (ground:tower:departure:approach:a-centre:centre:FSS) When, why, how could I use ALTOWNER? Link to comment Share on other sites More sharing options...
Stephan Boerner 945550 Posted January 27, 2011 at 09:41 AM Posted January 27, 2011 at 09:41 AM You use ALTOWNER, if there is an alternate ownership scenario that is not (and can not be) covered by the standard ownership rules. Maybe something that is in the LoA with an adjecent that when some specific sector configuration occurs, part of your airspace gets delegated to them. But can not really think of an example now ... haven't had to use that in a long time. Most times using OWNER should just be fine. An ALTOWNER scenario can be selected via Sector Ownership Setup. It is a replacement for the standard OWNER definition that can be manually selected. Stephan Boerner VATEUD - ATC Training Director EuroScope Board of Designers | GVCCS Beta Tester EuroScope Quick Start Guide Link to comment Share on other sites More sharing options...
Rob Killins 897126 Posted January 27, 2011 at 06:05 PM Author Posted January 27, 2011 at 06:05 PM Thanks Stephen ... Consider this ... Terminal sector is shared equally between Departure and Approach positions. Its not quite fair to allocate terminal airspace to APPROACH when DEPARTURE has just as much right to it. We theroretically can have two controllers on simultaneaously covering the same sector. How would one go about setting an ownership hiearchy under this scenario? In other words, terminal airspace is owned by departure when approach is off, owned by approach when departure is off, but what is the proper syntax when both are online? Is this where ALTOWNER would be used? Cheers, Link to comment Share on other sites More sharing options...
Stephan Boerner 945550 Posted January 27, 2011 at 07:24 PM Posted January 27, 2011 at 07:24 PM Well, you basically have two choices then: 1. Split the airspace 2. Work with GUEST As far as I know (which might not be correct for everywhere in the world), two controllers never share the same airspace, so even if you only have one terminal airspace, that one would be internally split by SOPs somehow. So theoretically you should be able to build that split as sectors. Of course you probably won't be able to get your hands on the real world procedures, so that's where you have to start being creative. Look at your SIDs and STARs, look at the regular flight paths and your current SOPs (if there are any), and cut the sector based on that. If you are unable to find a strict split you can work with GUEST at those parts, were airspaces might be crossed. Give APP the parts of all the entry points, and give DEP the part starting from the runways. And you will then have to make different airspaces for the different runway configurations using the ACTIVE statement. But how exactly that is going to look, completely depends on your airspace. (For an example you can have a look at the EDDF APP airspace in the EDGG file.) Stephan Boerner VATEUD - ATC Training Director EuroScope Board of Designers | GVCCS Beta Tester EuroScope Quick Start Guide Link to comment Share on other sites More sharing options...
Recommended Posts