Miguel Frias Posted September 21, 2010 at 10:31 AM Posted September 21, 2010 at 10:31 AM Hi, I was controlling in EURN_FSS now and a pilot has a flight plan heading north to ENSB. His flight plan was: KO B141 SPB G34 NILAT A936 RATLA UP853 TRO UP600 ISD Which is correct and send him in a normal route to ENSB. However, Euroscope is showing the route like this: The red arrow shows the continuation of UP600 but to the north which is what should have been shown. Miguel Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted September 23, 2010 at 05:44 PM Posted September 23, 2010 at 05:44 PM Actually I just checked the en-routes maps for Sweden and Norway. Did you check if ISD was accepted or there was a error for it or that the destination was typed correctly ? Because what ES is showing is indeed UP600, but it's southern part, so something after UP600 was wrong, either the ISD or destination. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Miguel Frias Posted September 23, 2010 at 08:25 PM Author Posted September 23, 2010 at 08:25 PM I put it in my flight planner that I programmed and it worked like a charm. Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted September 23, 2010 at 08:33 PM Posted September 23, 2010 at 08:33 PM Can you repeat the bug (when I was talking about the error in the route or the departure, I was referring for a typo error in that case)? EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Miguel Frias Posted September 23, 2010 at 08:38 PM Author Posted September 23, 2010 at 08:38 PM The destination is in the image, it is correct. I can't remember now if it showed correctly in the flight plan. But I think it'll show without errors since you see a blue/cyan line not a red line. But not sure on this. Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted September 23, 2010 at 08:42 PM Posted September 23, 2010 at 08:42 PM A blue line actually shows "direct to", if it was correctly extracted (with no errors) it would have been green... EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Juha Holopainen Posted September 25, 2010 at 10:47 AM Posted September 25, 2010 at 10:47 AM Maybe your airway file is outdated or somehow corrupted and doesn't have the part of UP600 continuing northbound from TRO? I tested the situation with a simulator scenario, and the route was displayed correctly (using an airway file for AIRAC cycle 1009). Link to comment Share on other sites More sharing options...
Miguel Frias Posted September 26, 2010 at 09:05 PM Author Posted September 26, 2010 at 09:05 PM Hmm... this is the Eurocontrol sector so maybe that could be it. I don't know if we are keeping the AIRAC cycles completely up to date, although I think we are. Miguel Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Johan Grauers Posted September 26, 2010 at 09:39 PM Posted September 26, 2010 at 09:39 PM Maybe you can have a look in your routes file and see Miguel? If you don't know what to look for upload it here and someone can take a look at it perhaps (I could probably do it for example). Johan Grauers Event Coordinator - vACC Scandinavia Link to comment Share on other sites More sharing options...
Miguel Frias Posted September 26, 2010 at 10:01 PM Author Posted September 26, 2010 at 10:01 PM The .sct file has the following lines referring to UP600 (already sorted by latitude for convenience): UP600-> N054.01.44.000 W006.03.58.000 N054.35.41.000 W005.35.53.000 ; ROTEV-GOTNA UP600-> N054.35.41.000 W005.35.53.000 N054.53.00.000 W005.09.32.000 ; GOTNA-BLACA UP600 N054.53.00.000 W005.09.32.000 N055.18.48.000 W004.47.02.000 ; BLACA-TRN UP600 N055.18.48.000 W004.47.02.000 N055.52.14.000 W004.26.45.000 ; TRN-GOW UP600 N055.52.14.000 W004.26.45.000 N056.22.09.000 W003.27.49.000 ; GOW-FINDO UP600 N056.22.09.000 W003.27.49.000 N056.26.33.000 W003.22.07.000 ; FINDO-PTH UP600 N056.26.33.000 W003.22.07.000 N057.18.38.000 W002.16.02.000 ; PTH-ADN UP600 N057.18.38.000 W002.16.02.000 N057.57.00.000 E000.35.45.000 ; ADN-FORTY UP600 N057.57.00.000 E000.35.45.000 N058.23.24.000 E002.49.44.000 ; FORTY-KLONN UP600 N058.23.24.000 E002.49.44.000 N058.52.30.210 E005.38.24.550 ; KLONN-ZOL UP600 N058.52.30.210 E005.38.24.550 N059.19.35.000 E007.30.00.000 ; ZOL-SOTIR UP600 N059.19.35.000 E007.30.00.000 N059.55.45.040 E010.16.09.500 ; SOTIR-TRF UP600 N059.55.45.040 E010.16.09.500 N060.11.30.330 E011.04.27.910 ; TRF-GRM UP600-> N060.11.30.330 E011.04.27.910 N060.42.50.000 E011.22.41.000 ; GRM-ROKOV UP600-> N060.42.50.000 E011.22.41.000 N061.06.03.000 E012.00.10.000 ; ROKOV-OMORO UP600-> N061.06.03.000 E012.00.10.000 N061.29.59.100 E012.40.04.500 ; OMORO-XELVI UP600-> N061.29.59.100 E012.40.04.500 N062.23.42.600 E013.12.05.300 ; XELVI-OVDAL UP600-> N062.23.42.600 E013.12.05.300 N063.59.46.600 E014.14.36.600 ; OVDAL-NETAV UP600-> N063.59.46.600 E014.14.36.600 N064.36.41.900 E014.40.40.400 ; NETAV-ATLEM UP600-> N064.36.41.900 E014.40.40.400 N065.56.46.600 E015.41.41.700 ; ATLEM-BAMIP UP600-> N065.56.46.600 E015.41.41.700 N067.15.43.000 E016.48.48.000 ; BAMIP-LIVLI UP600-> N067.15.43.000 E016.48.48.000 N068.01.39.000 E017.06.04.000 ; LIVLI-GILEN UP600 N068.01.39.000 E017.06.04.000 N069.05.25.000 E018.16.02.000 ; GILEN-LURAP UP600 N069.05.25.000 E018.16.02.000 N069.42.10.040 E018.59.48.310 ; LURAP-TRO UP600 N069.42.10.040 E018.59.48.310 N070.37.20.000 E019.00.38.000 ; TRO-BETMA UP600 N070.37.20.000 E019.00.38.000 N074.30.07.000 E019.05.10.200 ; BETMA-BJO UP600 N074.30.07.000 E019.05.10.200 N076.00.00.000 E017.07.55.000 ; BJO-BARNI UP600 N076.00.00.000 E017.07.55.000 N078.03.40.800 E013.36.01.100 ; BARNI-ISD Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted September 27, 2010 at 08:56 AM Posted September 27, 2010 at 08:56 AM What Juha was talking about was not the .sct file, but the Airway.txt file. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Miguel Frias Posted September 27, 2010 at 11:36 AM Author Posted September 27, 2010 at 11:36 AM I can't actually find the connection between BJO - BARNI - ISD on the Airway.txt file. I got a new AIRWAY.txt and this one has the ISD VOR so it should work now. Thought this file was already up-to-date but I guess it wasn't. Thanks everyone. Miguel Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Marvin Palmer Posted September 28, 2010 at 03:44 PM Posted September 28, 2010 at 03:44 PM Miguel, the default AIRWAYS.txt is rather old (last free update), but if you go to navigraph and purchase the FSNAV AIRAC, then you will have an up to date file (AIRWAYS.TXT) Link to comment Share on other sites More sharing options...
Johan Grauers Posted October 23, 2010 at 01:54 PM Posted October 23, 2010 at 01:54 PM Digging this thread up with these two screens from controlling Sweden control today: It seems there's something wrong with the routeredout of UP600 towards ENSB, not sure what though (I haven't had time to check thoroughly though) Johan Grauers Event Coordinator - vACC Scandinavia Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted October 23, 2010 at 03:50 PM Posted October 23, 2010 at 03:50 PM OK, next time when that has happened, copy the FP route and send it to xumepoc(at)abv(_dot_)bg. Also Johan can you check your Airac version. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Johan Grauers Posted October 23, 2010 at 06:04 PM Posted October 23, 2010 at 06:04 PM Airac should be 1009 (using ESAA 1009 sectorfile for Sweden). Route for SEGLH was RASEN UT317 NOVRI UP853 TRO UP600 ISD EI-JSA had also filed the last leg as TRO UP600 ISD So it seems there's something going wrong at TRO. I will send it over to your mail aswell Johan Grauers Event Coordinator - vACC Scandinavia Link to comment Share on other sites More sharing options...
Miguel Frias Posted October 23, 2010 at 06:19 PM Author Posted October 23, 2010 at 06:19 PM Thanks Johan, this is exactly what I saw as well. It's not a common flight so it's hard to catch it on the scope. Miguel Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted October 23, 2010 at 06:25 PM Posted October 23, 2010 at 06:25 PM Thanks Johan, will test it. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Johan Grauers Posted October 23, 2010 at 06:40 PM Posted October 23, 2010 at 06:40 PM Cheers Todor, you have my mail now aswell so just let me know if you need more info Johan Grauers Event Coordinator - vACC Scandinavia Link to comment Share on other sites More sharing options...
Todor Atanasov 878664 Posted October 24, 2010 at 10:07 AM Posted October 24, 2010 at 10:07 AM Well found the reason. It is the airway.txt file fault. Here is the route with the tested airac 0912 And then here is with the airac 1005 The missing info is about ISD on these lines: Airac 0912 BARNI 76.000000 17.131944 14 UP600 H BJO 74.501945 19.086167 29000 Y 0 N Airac 1005 BARNI 76.000000 17.131944 14 UP600 H BJO 74.501945 19.086167 29000 Y ISD 78.061333 13.600306 29000 Y ISD 78.061333 13.600306 14 UP600 H BARNI 76.000000 17.131944 29000 Y 0 N Simply replace the first line from 1005 to 0912 and add the second line from 1005 to 0912 and test it. EuroScope BETA Tester/Board of Designers Link to comment Share on other sites More sharing options...
Johan Grauers Posted October 25, 2010 at 06:57 PM Posted October 25, 2010 at 06:57 PM Got my file updated now, just need someone to fly the route to test it, thanks Todor Johan Grauers Event Coordinator - vACC Scandinavia Link to comment Share on other sites More sharing options...
Recommended Posts