Menu Sign In Contact FAQ
Banner
Welcome to our forums

Autorouter issues and questions (merged)

I’m trying to use autorouter and am getting the following error message when trying to create a route

Error: Router engine not reachable — socket connect Connection refused (111)

Have I done something wrong or is the system off-line?

Fly safely
Various UK. Operate throughout Europe and Middle East, United Kingdom

Seems down, or they are updating the software.

I’ve reported it to Achim.

Administrator
Shoreham EGKA, United Kingdom

I just tried to get LOWI-LKKU generatd with the following results.
LOWI N0130F120 RASTA3H RTT Z33 NEMAL L725 LIMRA/N0130F090 L725 LIVDU
L156 LEDVA LEDVA1N LKKU

but Jeppesen is showing Rattenberg two hotel (RTT 2H) only. Jepp is updated this week and looks no AIRAC was to became effective this week. …any ideas what´s wrong here, what I might be doing wrong?

LKKU, LKTB

Jepp has RASTA3H on page 10-3B.

Eurocontrol often allows you to “abort” SID’s early (or join STAR’s late), such as in this case you follow RASTA3H only up to Rattenberg (RTT), but then continue on the airway.

LSZK, Switzerland

oh, you are right, I overlooked 10-3B as I was going RTT direction only…and aslo thanks to strange page order in Jepp TC. I guess I was assigned RASTA3H instead of RTT 2H due to climb graditent, I need to look at the aircraft model I used, I left whatever was there, I was interested just in routing…

BTW – RASTA 3H takes me 59 m east of LOWI (not via RTT) and I see not published route between RASTA and RTT (approx 45 miles back to the west) but it gets validated by https://www.public.cfmu.eurocontrol.int/PUBPORTAL/gateway/spec/index.html so obviously it´s ok.

Last Edited by Michal at 13 Jun 13:30
LKKU, LKTB

Down again – might even be my fault, got an error and on the second try the router is unavailable :-(

Error: Router engine not reachable — socket connect Connection refused (111)

By definition not your fault We’ve made some major changes in how we do routing in the UK and also introduced the 8.33kHz airspace flag which as of two weeks ago is being enforced in several airspaces. There’s still a stability issue in the new code which we hope to resolve within the next days. I’ll monitor the system closely until then.

By definition not your fault

True
But I think I managed to trigger that bug again as the router is down again. I’ll open a case and post the details to you (I don’t think Peter wants this forum to be a ticket system).

Yes, please avoid that particular routing for now. The bug is well understood, just waiting for a fix.

Will do.

548 Posts
Sign in to add your message

Back to Top