Jump to content

Runway assignment error at Aerosoft's EDDF


Recommended Posts

Today I had a strange problem I haven't seen before, when I loaded a saved EFB route from ESSA-EDDF I received the error message you normally get when the runway identification between the nav data and FSX doesn't match. Was very surprised since I did this flight many times before without any problems.

 

Looking at the DataProvider window I got even more confused because it said 07L and 25R couldn't be assigned to an FSX runway but looking at the last line in the DataProvider window it reads 'Available FSX runways at this airport are as follows: 18, 36, 07R, 25L, 07C, 25C, 07L, 25R

 

What could cause this?

Link to comment
Share on other sites

Just downloaded the rev 2 of the latest AIRAC cycle and installed it but never got the message I usually get from EFB when starting it after installing the NAV data so let's see what happens on next flight. But maybe there isn't a message from EFB for new NAV data unless you installed a completely new AIRAC cycle...?

Link to comment
Share on other sites

Still same problem after installing rev 2 of the latest AIRAC cycle, am I the only one seeing this issue with Aerosoft's EDDF and where exactly is the problem - within the scenery, the NAV data or EFB? Would be the NAV data I guess since that is the only thing of the three that has changed lately...

Link to comment
Share on other sites

This seems to be the same problem I posted about for KSTL. Runways 7L and 25R are listed twice in "wpnavapt.txt"

 

FRANKFURT/MAIN EDDF07C13123068 50.032617 8.534631110.5506800329

FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078110.3006800305 <--

FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078111.7506800305 <--

FRANKFURT/MAIN EDDF07R13123068 50.027542 8.534175110.9506800328

FRANKFURT/MAIN EDDF18 13123178 50.034169 8.525931000.0017800326

FRANKFURT/MAIN EDDF25C13123248 50.045128 8.586981111.5524800364

FRANKFURT/MAIN EDDF25L13123248 50.040053 8.586531111.1524800362

FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717111.3524800353 <--

FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717109.7524800353 <--

 

Jerry

Link to comment
Share on other sites

On a second note it seems the problem is not as easy as simply removing one of the lines because in fact they are not totally equal, see the answer below I received from Richard at Navigraph.

 

Hi again Richard,

I believe I have found the "problem" with EDDF 07/25R ... The problem is that EFB doesn´t support multiple ILS frequencies.

 

Here a short part of the airport-file:

FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078110.3006800305 <- IFEL

FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078111.7506800305 <- IFNE

FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717111.3524800353 <- IFWR

FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717109.7524800353 <- IFNW

 

Both runways had two ILS frequencies and therefore the 07L/25R are twice in the file. It looks like, that EFB can´t handle this but I can´t remove it because both are identical, excluding the frequency and the glideslope (3°/3.2°). I don´t know which frequency will be used in FSX and/or addons. Sorry Richard, but it looks like, this is really a EFB issue and should address there.

 

Thank you,

Richard

Link to comment
Share on other sites

Hi Richard and Jerry,

 

thanks for the report.

 

It's true, EFB Version 1.x cannot handle multiple ILS frequencies, but EFB reads the frequencies from the BGL files, not from the wpnavapt.txt file.

 

I will have a look on how to fix this with the next version 1.3.7.

Link to comment
Share on other sites

×
×
  • Create New...