Eivind Fosse 818131 Posted November 1, 2009 at 01:02 PM Posted November 1, 2009 at 01:02 PM Hi, 1 - The LoA states that an aircraft shall be climbed to ABOVE FL300. If that aircraft is already at FL330 (an acceptable level), is there a way to avoid the Cooperation Altitude to show FL300? 2 - Can someone please tell me in more detail how to use, and what results I should get, when using the DEPAPT: and ARRAPT: lines in the Sector subsection? I've tried playing with those, but I do not see what happens... Eivind Link to comment Share on other sites More sharing options...
Stephan Boerner 945550 Posted November 1, 2009 at 01:39 PM Posted November 1, 2009 at 01:39 PM 1. Hm, I think it does not display the FL300 in that case. If you correctly set the FL300 for climb and not for descend, it should then display the current FL330 as Coop Alt. That is at least what happens if there is an coop altitude set for descend, and the aircraft is already below that altitude. 2. If you activated the "Set active APT by owned sectors" setting in general settings, the DEPAPT and ARRAPT lines tell ES, which airports are activated based on what sectors. They are simpl lists, seperated by ":". 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...
Eivind Fosse 818131 Posted November 1, 2009 at 08:24 PM Author Posted November 1, 2009 at 08:24 PM Great! The answer to question #2 was exactly what I was after! Thank you. Please also take a look at the following problem: Take a look at this Enroute chart for Northern Norway: http://www.ippc.no/norway_aip/current/AIP/EN_ENR_6_2-7_en.pdf As you can see pilots will normally file, for a flight from Lakselv, Banak to Tromsø Langnes: BNR M609 TRO The problem is regarding the [Mod - Happy Thoughts]ignments of SIDs and STARs in such cases. The SID for rwy 17 at Banak: http://www.ippc.no/norway_aip/current/AIP/AD/ENNA/EN_AD_2_ENNA_4-1_en.pdf As you can see you would normally issue a BIGSI 1J SID for traffic to Tromsø. And for rwy 35: http://www.ippc.no/norway_aip/current/AIP/AD/ENNA/EN_AD_2_ENNA_4-3_en.pdf Then it would be DONEX 1K. The problem is, as you maybe can see, that the SID's do not have a common termination point. And it does not connect to the filed FPL. So how can I code this into the ESE file? I would of course have it that if RWY 17 is in use at Banak, and you've filed the FPL as stated above, ES will [Mod - Happy Thoughts]ign the correct BIGSI 1J SID to your aircraft. How can I do this? The same problem is true for inbound traffic to Tromsø: It seems to me that since the flight end at TRO (ref the FPL), and not HTK - no STAR is [Mod - Happy Thoughts]igned for the flight... You can also see that traffic from the south will most likely have filed: SJA M609 TRO If you take a look at the STAR chart again you'll see that the STARs SJA 7M (19) and LURAP 1L (01) are the two valid STARs for traffic from the south. Unfortunately I do not know how to write this into the ESE - so that if rwy 19 is in use the SJA 7M will automatically be [Mod - Happy Thoughts]igned if your flight has filed a FPL as above... As of today no STAR is [Mod - Happy Thoughts]igned... I hope you can help. It would be really appreciated! The LoA between Banak and Bodø Control is as follows in the ESE as of today: ; ; ENNA ; COPX:ENNA:17:ABANU:*:*:ENNA TMA:ENBD 4R:10000:*:ABANU COPX:ENNA:17:BIGSI:*:*:ENNA TMA:ENBD 4R:10000:*:BIGSI COPX:ENNA:35:AKORU:*:*:ENNA TMA:ENBD 4R:10000:*:AKORU COPX:ENNA:35:DONEX:*:*:ENNA TMA:ENBD 4R:10000:*:DONEX COPX:ENNA:*:LAPVI:*:*:ENNA TMA:ENBD 4R:10000:*:LAPVI COPX:*:*:VALTO:ENNA:17:ENBD 4R:ENNA TMA:*:11000:VALTO COPX:*:*:RANON:ENNA:17:ENBD 4R:ENNA TMA:*:11000:RANON COPX:*:*:BA:ENNA:35:ENBD 4R:ENNA TMA:*:11000:BA COPX:*:*:GAGSA:ENNA:35:ENBD 4R:ENNA TMA:*:11000:GAGSA ; ; ENNA, Banak ; SID:ENNA:17:ABANU1J:ENNA PG ABANU SID:ENNA:17:BIGSI1J:ENNA PG BIGSI SID:ENNA:17:LAPVI1J:ENNA PG BNA VALTO LAPVI SID:ENNA:35:AKORU1K:ENNA BNA AKORU SID:ENNA:35:DONEX1K:ENNA BNA DONEX SID:ENNA:35:LAPVI1K:ENNA BNA VALTO LAPVI STAR:ENNA:17:DONEX1U:DONEX VALTO BILVI BNA ENNA STAR:ENNA:17:LAPVI1U:LAPVI VALTO BILVI BNA ENNA STAR:ENNA:17:SONOV1U:SONOV BNA ENNA STAR:ENNA:17:TEMBA1U:TEMBA BILVI BNA ENNA STAR:ENNA:35:BIGSI1V:BIGSI PG ENNA STAR:ENNA:35:GOGUD1V:GOGUD PG ENNA STAR:ENNA:35:LAPVI1V:LAPVI BNA PG ENNA and for Tromsø: ; ; ENTC, Tromsø ; SID:ENTC:01:AND3A:ENTC KV AND SID:ENTC:01:BAREG1A:ENTC BAREG SID:ENTC:01:IDLIN1A:ENTC IDLIN SID:ENTC:01:LENSA2A:ENTC LENSA SID:ENTC:01:LOMVI3A:ENTC KV LOMVI SID:ENTC:01:ROSKO1A:ENTC KV ROSKO SID:ENTC:19:AND3B:ENTC KBV AND SID:ENTC:19:BAREG1B:ENTC TRO BAREG SID:ENTC:19:BDF3B:ENTC KBV BDF SID:ENTC:19:IDLIN1B:ENTC KBV IDLIN SID:ENTC:19:IDLIN1W:ENTC KBV TRO IDLIN SID:ENTC:19:IDLIN1X:ENTC TRO IDLIN SID:ENTC:19:LENSA2B:ENTC KBV LENSA SID:ENTC:19:LOMVI3B:ENTC KBV KV LOMVI SID:ENTC:19:LOMVI3X:ENTC TRO KV LOMVI SID:ENTC:19:ROSKO1B:ENTC KBV ROSKO SID:ENTC:19:TIL1B:ENTC KBV TIL STAR:ENTC:01:AND4L:AND KBV ENTC STAR:ENTC:01:HTK4L:HTK KBV ENTC STAR:ENTC:01:LURAP1L:LURAP MOLON KBV ENTC STAR:ENTC:01:TULDA4L:TULDA KBV ENTC STAR:ENTC:19:AND4M:AND MACKA KV ENTC STAR:ENTC:19:BJO5M:BJO KV ENTC STAR:ENTC:19:FOR4M:FOR KV ENTC STAR:ENTC:19:HTK6M:HTK KV ENTC STAR:ENTC:19:SJA7M:SJA GIBMO MACKA KV ENTC ; ; ENTC ; COPX:ENTC:01:AND:*:*:ENTC CTR:ENTC TMA:9000:*:AND COPX:ENTC:01:BAREG:*:*:ENTC CTR:ENTC TMA:9000:*:BAREG COPX:ENTC:01:IDLIN:*:*:ENTC CTR:ENTC TMA:9000:*:IDLIN COPX:ENTC:01:LENSA:*:*:ENTC CTR:ENTC TMA:9000:*:LENSA COPX:ENTC:01:LOMVI:*:*:ENTC CTR:ENTC TMA:9000:*:LOMVI COPX:ENTC:01:ROSKO:*:*:ENTC CTR:ENTC TMA:9000:*:ROSKO COPX:ENTC:19:AND:*:*:ENTC CTR:ENTC TMA:9000:*:AND COPX:ENTC:19:BAREG:*:*:ENTC CTR:ENTC TMA:9000:*:BAREG COPX:ENTC:19:BDF:*:*:ENTC CTR:ENTC TMA:9000:*:BDF COPX:ENTC:19:IDLIN:*:*:ENTC CTR:ENTC TMA:9000:*:IDLIN COPX:ENTC:19:LENSA:*:*:ENTC CTR:ENTC TMA:9000:*:LENSA COPX:ENTC:19:LOMVI:*:*:ENTC CTR:ENTC TMA:9000:*:LOMVI COPX:ENTC:19:ROSKO:*:*:ENTC CTR:ENTC TMA:9000:*:ROSKO COPX:ENTC:19:TIL:*:*:ENTC CTR:ENTC TMA:9000:*:TIL COPX:*:*:MOLON:ENTC:01:ENBD 3R:ENTC TMA:*:11000:MOLON COPX:*:*:LURAP:ENTC:01:ENBD 3R:ENTC TMA:*:11000:LURAP COPX:*:*:TRO:ENTC:01:ENBD 4R:ENTC TMA:*:11000:TRO COPX:*:*:*:ENTC:01:ENBD 4R:ENTC TMA:*:11000: COPX:*:*:KV:ENTC:19:ENBD 4R:ENTC TMA:*:11000:KV COPX:*:*:TRO:ENTC:19:ENBD 4R:ENTC TMA:*:11000:TRO COPX:*:*:GIBMO:ENTC:19:ENBD 3R:ENTC TMA:*:11000:GIBMO COPX:*:*:MACKA:ENTC:19:ENBD 3R:ENTC TMA:*:11000:MACKA COPX:*:*:*:ENTC:19:ENBD 3R:ENTC TMA:*:11000: Thank you! Link to comment Share on other sites More sharing options...
Gergely Csernak Posted November 5, 2009 at 08:50 PM Posted November 5, 2009 at 08:50 PM Eivind, As far as I see it a simply wrong FP and it will never be fixed automatically by the system. If someone flies the BIGSI1J SID then the FP route shoud look like BIGSI ATA M609 ... as the planned route joins to the M609 airway only at ATA and never at BNR. In this case the SID will be added automatically. I may even think about extending the SID definition in the ESE file as SID:ENNA:17:BIGSI1J:ENNA PG BIGSI ATA This can be used in case all traffic after BIGSI will fly to ATA. But it still requires a FP like ATA M609 ... Gergely. EuroScope developer Link to comment Share on other sites More sharing options...
Recommended Posts