Question, reading VOXATC instruction says to setup the SID/Star and point it to your NavData AIRAC cycle folder. Now it mentions Level D 767, but also that it can use navigraph data.

 

Well, I do not own Level D 767, but I do own AivlaSoft EFB and I tried pointing VOXATC to the NavData folder for aivlasoft, but I do not ever here a departure using the SID. My IFR clearance from clearance delivery only ever includes C,A,T

 

C = Clear to

A = Altitude

T = Transponder code

 

I never get the R or F, to make C,R,A,F,T

 

R = Route

F = Departure Frequency

 

 

Tower always give me a, after departure proceed direct instructions.

 

Must be doing something wrong.

 

Thanks,

Ray

realkewl,

 

You do not have to own the Level-D 767 to get SID/STARS to work, but you will have to buy and download the latest Level-D FMS file from Navigraph.

 

After installing you will have a new folder Level-D/Navdata under your FSX folder. Point to this in the VoxATC settings.

 

If you want SID/STAR clearances you will have to take this into account when you are creating flight plans.

E.g. if from charts you know that 'point A' is the fix point of the SID, then you must make this the first way-point of your flight plan.

Same goes for STAR where the entry point for the STAR must be the last way-point of your flight plan.

Thanks...that's kind of what I thought was happening (needing Level D's FMS NavData...and nobody elses).

 

Here's where I get even more confused. How does one determine what SID/STAR is going to be used. Take for example a very busy airspace KLAX. There's over a dozen SID's, you will not know which runway is in use until after you start VOXATC...and VOXATC needs a flightplan before it will start correctly. So, this is like putting the cart before the horse. Correct me if I'm wrong.

 

VOXATC directions says make sure you have the SID/STAR entry point in your flight plan...but how will you know what runway is in use until after your start VOXATC and get the ATIS? Hmmm...

 

Thanks,

Ray

May I ask what route planner are you using? Just to see what is available for you at the moment.

 

If you use RouteFinder from within EFB, it will already gives a correct flight plan (more or less). First waypoint is a common end point for any number of SIDs. Same goes for the route end and STAR.

 

What I am saying is that you don't add SID or STAR to your flight plan. You listen to the ATIS => you get the runway in use. From the runway in use and your first waypoint you can pretty well guess what SID VoxATC will clear you to fly.

 

Small addition: you should have your SID exit point and STAR entry point in your flight plan.

Here's a quick example from my yesterdays flight from EDDV to EBBR.

 

Flight planner gave me the following route: OSN L980 PAM N872 WOODY

 

There are many SIDS available in EDDV, but only OSN5F, OSN6G, OSN8S, OSN9Y end at OSN, which is the first waypoint in my flight plan. What ever the winds are, I'll be flying one of those SIDs.

 

Runway 9L was active yesterday (using real world weather), so only OSN9Y SID was possible for runway in use and my flight plan.

 

Same logic goes for the STAR.

Thanks...that's kind of what I thought was happening (needing Level D's FMS NavData...and nobody elses).

 

Here's where I get even more confused. How does one determine what SID/STAR is going to be used. Take for example a very busy airspace KLAX. There's over a dozen SID's, you will not know which runway is in use until after you start VOXATC...and VOXATC needs a flightplan before it will start correctly. So, this is like putting the cart before the horse. Correct me if I'm wrong.

 

VOXATC directions says make sure you have the SID/STAR entry point in your flight plan...but how will you know what runway is in use until after your start VOXATC and get the ATIS? Hmmm...

 

Thanks,

Ray

 

realkewl,

 

You will have to study the charts for this to work.

 

Lets take KLAX as an example and say that we want to fly from KLAX to PANC.

KLAX has many runways and not all have similar SIDs, so you will have to find an SID that is available from all runways.

The GORMAN (GMN Vortac) departure is available from all runways, so you set this as the starting point in your flight plan.

VoxATC will then give you the GORMAN departure, no matter which runway is used for departure.

 

Some airports around the world will have different SIDs for different runways, so there you will either have to second guess which runway will be chosen and have saved the appropriate flight plan in advance OR you can just lets VoxATC give a generic SID (if one exists).

May I ask what route planner are you using? Just to see what is available for you at the moment.

 

If you use RouteFinder from within EFB, it will already gives a correct flight plan (more or less). First waypoint is a common end point for any number of SIDs. Same goes for the route end and STAR.

 

What I am saying is that you don't add SID or STAR to your flight plan. You listen to the ATIS => you get the runway in use. From the runway in use and your first waypoint you can pretty well guess what SID VoxATC will clear you to fly.

 

Small addition: you should have your SID exit point and STAR entry point in your flight plan.

 

Hmm...I never tried to use RouteFinder. So do you have Level D FMS NavData also? Or was you able to point VOXATC to Aivlasoft NavData Folder?

 

So, in order for you to listen to the ATIS you have to enable VOXATC, then create flight plan, then disable/enable VOXATC to work, right?

Just to make sure that we are on the same page, I'll try to describe navdata to you, the way I see it.

 

Navigraph and Aerosoft publish an updated version of the navdata 12-13 time a year (each version is called a cycle). This years first cycle was number 1201 and the current cycle is 1211.

 

Each time a cycle is published, the providers (Navigraph and Aerosoft) release the same data in different formats (called datasets): for Aivlasoft EFB, Level-D, PMDG and so on. When you by a cycle, you are able to access all the datasets (removes the need to by Level-D aircraft, if you only need Level-D dataset for VoxATC)

 

You can think of the cycle being a book and datasets being different language translations of the same book. Lets say that EFB only understands english and VoxATC/Level-D speaks spanish. Now to your question: "was I able to use EFB NavData in VoxATC?" Unfortunately not because the VoxAtc doesn't speak the "same language" as EFB.

 

What I think is happening that you have yet to buy a cycle from Navigraph or Aerosoft and you are using the default dataset that came with EFB. If this is the case, I would suggest you head over to the providers stores and see which of then is more suitable for you.

 

Hope this helps!

 

So, in order for you to listen to the ATIS you have to enable VOXATC, then create flight plan, then disable/enable VOXATC to work, right?

 

I have done things the way it was mentioned in the manual.

 

First you create/import a flight plan (I only use the FSX flight planner to import the flight plan I created in EFB). Then you save your flight. Only after that, you enable VoxATC and listen to ATIS.

OK that explains what is happening...I do not have the correctly formatted NavData set.

 

Thanks!!!

-Ray