WebMaximus

Actually I have never paid attention to this information before and it's not a biggy but I do all my flying online and when there isn't any ATC online and you're at an unfamiliar airport it's very handy if you can check what runways are used for takeoffs/landings so you don't make a fool out of yourself in front of other online traffic For instance at ESSA which is my home airport rwy 26 is almost never used for takeoffs and yet I've seen people takeoff from that rwy many times simply because they are unfamiliar with the airport and it's real world OPs and I have then in a friendly way pointed this out to them and most of them are very thankful when they get this kind of info so they know for next time they fly to/from this airport. I'm not sure if I understood exactly what you meant but one thing I was thinking of is if this kind of info could be editable by us the end users...then we could simply help each other by correcting all values that are not correct and in the end have a very good source of info. Naturally this requires that people would take this seriously and not just edit things "out of the blue" without first knowing for fact what they edit/enter is correct but I would like to think most of us EFB users are very serious simmers. Just an idea but could be a good way to increase the accuracy of the information availiable in EFB.

Ok, too bad the information can't be trusted because the information itself is great when you're at unfamiliar airports.

Just noticed when looking at the airport information and more specific the runway information under the runways tab that rwy 08 is indicated as a 'No' when it comes to takeoffs but that is not correct, rwy 08 is very often used for takeoffs IRL at ESSA. Not sure where this info comes from, maybe EFB will just fetch it from FSX or somewhere else but thought I would at least mention it so it maybe can be corrected.

Thanks a lot Andy, I'll give it a try.

Thanks but not sure how to check that and also if that would be the case wouldn't that result in bigger problems? What I've seen is that only one or few taxiways don't have matching names.

I've noticed at several airports that the names of the taxiways on EFB's ground chart doesn't always match the names of the taxiways inside FSX in the scenery. Is that due to a problem with EFB or the scenery? This can get a bit embarrising when you're flying online and ATC asks you to use a specific taxiway and you look at the ground chart in EFB and replies "There isn't such a taxiway" and ATC says "Sure there is, see for yourself when you get there..." and then when I start taxi I see on the sign that ATC was right about the name of the taxiway. I always run a FSX Scenery Data Update whenever I change anything to the scenery and I only fly to airports where I have addon scenery installed, mostly from Aerosoft. Is it anything else I can do at my end to make sure EFB shows what actually is in the scenery like a text/config file or similar I could modify or is this all built into the scenery?

Did you already try what is suggested earlier in this thread?

Hello Urs and thanks for your as always very prompt reply! However as I wrote when I edited my post the problem was solved by itself so I guess the online data simply wasn't updated when I checked and noticed the Approach ATC for EHAM was missing in EFB. So...all is goood

EDIT: You can disregard from my question below, Amsterdam Approach just showed up in EFB so guess it was just some kind of delay. Hi guys! Sorry to wake an old thread up but I have a follow-up question on this. Where does EFB fetch other online controller stations like approach? Just loaded up FSX and EFB and notice Amsterdam Approach is online looking in ServInfo but it doesn't show up in EFB as online and I guess that is because of it's name EHAM_W_APP where EFB is looking for a station called EHAM_APP. Is it possible to add EHAM_W_APP somewhere in the same way I did for EHAA_W_CTR? TIA,

Made a couple of flights with revision 2 of the AIRAC data and all seems to be good now

Thanks Jack, I did use revision 1 of the 1208 AIRAC so I just downloaded and installed revision 2 and will see what happens. Actually it's been a couple of times now when new revisions of the AIRAC data is released without my knowledge so I guess I should head back over to Navigraph and see if they have some newsletter or similar you can subscribe to to get this kind of info. Thanks again for the heads-up!

Ok, I'll have a look next time I hear this noise.

Since installing the latest version of EFB (1.3.5) I get a strange noise lasting for approx 1-2 seconds at some points using the EFB user interface. So far I've noticed this when selecting an alternate airport and when activating a route. Not a big problem since everything still seems to work just fine, just wondering what this sound is and what is causing it. Maybe I shoul also mention that I use EFB in a multi-PC setup, not sure if that could be of importance. Anyone else heard this noise?

Just enroute from LTAI to ESSA flying in Turkish airspace under the control of Ankara Center (LTAA_S_CTR) which for some reason is not picked up by EFB. I have checked the Unknown Callsigns and Invalid Definition Data tabs but can't find it listed in there either. Not sure if these kind of reports help you improve the online ATC coverage in EFB but thought I post this anyway. All the best,

Was just curious, great thing you found it

That is great news, what was the problem - did Route Finder change something on their side?

The problem in this case appears to be more on the RouteFinder side, maybe something changed in the output format? I'm sure though Aivlasoft will look into it and if it's anything that can be fixed on their side, I've always been impressed by their great support and how they listen to their customers problems.

OK, sounds great

Good to know in a way I'm not the only one seeing this problem. Well, I'm sure Urs will chime in here and find a solution as he always does

Hi, Have never seen this before but all of a sudden whenever I try to use the built-in feature using RouteFinder to find a route after the route is generated and I press the OK button to import the route into EFB I receive an error message saying: "Could not read RouteFinder route. The following error occurred: Input string was not in a correct format." Just installed the latest version of EFB I noticed was released a couple of weeks ago hoping that would fix the problem but no luck...I still get this error and I've tried multiple routes and seem to be same problem with any of them. TIA for any help or input on this.

...any other way you can be notified via email when I new update for EFB is available?

Actually I already tried using the line you suggested but for some weird reason when I use it I no longer have any approaches available for ESSA in the FMC and this was even when I only modified Aivlasoft's ESSA.txt file...very weird! So...I reinstalled the latest AIRAC cycle for both Aivlasoft and PMDG and went back to my own suggested lines and now everything is good again. Surely not 100% realistic but at least it's working and hopefully Navigraph will eventually get this issue sorted so you don't need to invent your own fixes like this.

Thanks a lot Travis for your information and thorough explanation, much appreciated! I'll modify according to your instructions right away. One follow-up question though...you said this extra information regarding the FAF at the end of the approach data was specific for Aivlasoft, I take it that means you can't do the same modification for PMDG meaning what you'll see for this approach in EFB and the FMC won't go 100% hand-in-hand after this mod? However adding that second climb to 1500 feet should also be possible for the PMDG data right? Thanks again for your contribution and sharing your knowledge!

That's great news Steve

Yes, the missing data for rwy 26 at ESSA is a known problem and it has been there for many AIRAC cycles now. I found a way to fix it manually though by simply adding 2 lines in the ESSA.txt file in the SIDSTARS folder. First under the Fixes section find this line... FIX FD19R LATLON N 59 47.01048 E 17 59.00466 ...and add this line directly below it... FIX FF26 LATLON N 59 40.779 E 18 6.22416 Then under the Approaches section find this line... APPROACH ILS19RZ FIX CF19R 2500 SPEED 160 FIX OM19R 1400 RNW 19R TRK 185 VECTORS ...and add this line directly below it... APPROACH ILS26 FIX CF26 2500 SPEED 160 FIX FF26 1430 RNW 26 TRK 251 UNTIL 537 HDG 299 VECTORS Now you will have the needed data for approaches into rwy 26 at ESSA again. If you're flying a PMDG aircraft you can use the very same procedure for the PMDG ESSA.txt file making it possible to also choose ILS approaches into rwy 26 in the FMC in the a/c.