I apologise to those who must have been scratching their heads and thinking 'What is his problem'!

 

No need to apologize, Dave! It was certainly non-standard, but that's where the grey areas are:

-Do you edit the airports.txt to add it in;

-Or do you use the workaround described?

 

Surely you could troubleshoot both, but most are hesitant to go editing random files, and the FMS can seem like it's yelling at you if you don't know that the message is purely informational. You see a lot of that when people ask about route discontinuities - they're not necessarily problems, it's just letting you know. Same thing here.

 

...and none of this is really stuff you'd find in TFM, so it's a good question :wink:

I was able to add Aerosoft's Area 51 to the navdata, following instructions from posts mentioned above, should be able to do the same with Andras.

 

Cheers

TJ

Kyle,

 

I used the workaround by using an airfield reasonably close. I get airborne and then progress the FMC to the relevant waypoint in a similar way that you may wish to route direct to a point as long as you are on a closing heading it seems to work. When I get the chance I will take a longer look at the airport.txt file and try to decode the meaning of all the variables, the Threshold Lat Longs, RW length, elevation and mag hdg are all easy, there are some other pieces of data though that I don't understand so I wouldn't want to alter something and corrupt the file. It is still a work in progress, it is just having the time to explore it further.

 

As I am enjoying myself formation flying on-line I am considering getting TrackIR as I currently do not have enough hands, I think this may take precedence over the airport file for the time being while I wait for the B777.

 

Kind Regards

 

Dave Boreham