39 minutes ago, edetroit said:

Alphasearcher2 is what you want. https://www.alpha-india.net/forums/index.php?topic=9633.msg92195

Thanks, I just downloaded it.

Edited April 4, 20197 yr by Skywatcher

This is an example of a complex aircraft (IFLY744) flying a real world route from Seattle-Tacoma to London Heathrow. Navigraph for the IFly744 providing the latest database and charts. From that I write the required waypoints for the FS FlightPlanner and FS ATC.

First the real world flight plan:

KSEA YXC DCT 5130N11000W 5330N10000W 5330N09000W 57N080W 5830N07000W DCT FASSA DCT SINGA DCT SAVRY DCT 60N050W 60N040W 59N030W 58N020W DCT SUNOT DCT KESIX DCT MIMKU DCT KELLY UL10 WAL UY53 NUGRA BNNIB EGLL

The first thing that intrigued me were these custom waypoints 5130N11000W 5330N10000W 5330N09000W 5830N07000W I had not seen the type before .... anyway they need to be entered into the legs page and not the route page. Once entered they display slightly differently.

I wrote this plan into the Navigraph planner and my IFLY FMC.

Navigraph will give me the coords for all the waypoints in the plan. I then write all the new waypoints for the FS database. Then write the flightplan again with the FSFlightPlanner (incl SID /STAR's and Approach ) so that FSATC will be able to follow my flight perfectly.

I Opened my UK2000 EGLL Afcad with ADE to make sure the BNN 1B STAR was there (BNN transition)

I always change the transition height to what the glide slope capture height should be (ILS IAF) So that when FSATC clears me for the correct ILS approach with transition it also tells me the correct height to be at when I intercept the glide slope (always nice to be reminded.)

Note: Those custom waypoints I mention earlier will not be in any aero.sors update. 😉

To see all this happen including how to ask for transitions and not accept vectors from FSATC check my latest video:

   

 

Edited April 4, 20197 yr by edetroit

On 4/4/2019 at 4:07 AM, edetroit said:

Not for me I use Navigraph. Two things here.

1, These are for complex aircraft that can use their databases. 

They do not update the FS navdatabase which is what we are talking about here. An updated FS database is needed for FS flight planning and FSATC.

2. Just because you pay does not mean there are no bugs.

For all textures (aircraft, scenery etc) DXT3fixer or Alphasearcher (I use both)

You will find something needs fixing 99% of the time.

Wrong. No bugs with NavDataPro.

37 minutes ago, PebbleBeach said:

Wrong. No bugs with NavDataPro.

No bugs with Navigraph either. My point is they both do diddley squat for the default FS navdatabase.

I still standby payware does not equal no bugs.

Edited April 6, 20197 yr by edetroit

I've been using Hervé Sors' navdata updates for years without issues in the US areas. I do know if you use it and run the default FS9 map, it will crash if you try to display airways. So before installing, make sure to disable the display of airways or don't open the map.

I flew a lot around the Anchorage area up until about 6 years ago using the Carenado 206, so I was happy when I found his FS9 updates. I stumbled on them shortly after the real-world ANC VOR on Fire Island was decommissioned and the new TED VOR came online.