Sign in to follow this  
solvair

assigned wrong STAR

Recommended Posts

It has happened in some flights when in the airport arrival dominated south wind. VoxATC (ATC center) assigns me a STAR oriented north runway, and finally the approach ATC allows me to land on a runway south oriented, according to the winds, that IS NOT ASSOCIATED WITH ASSIGNED STAR,

 

With the new version 6.49 solved the problem of updating the weather at destination, but this is not transferred to the assigned STAR.

 

as an example, a flight I did yesterday: LEMD-LEBL. VoxATC assigned me STAR "CASPE2S", which is associated to the runways in LEBL 7L / 7R. I use ASNext with static weather (for short flights, download the actual weather, not update throughout the flight), so I expected that the active runway for landing would 25L / 25R, Finally assigned me approach runway 25L

 

Can anyone clarify me if this is normal or is it a VoxATC problem?

 

Thank you for your attention

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

"download the actual weather, not update throughout the flight), so I expected that the active runway for landing would 25L / 25R"

 

Did you tune ATIS before arrival to see winds and landing runway?

 

Or check Active sky Report for ATIS arrival winds before your flight?

Share this post


Link to post
Share on other sites

Thanks for your answer, Vonmar

 

I get the weather on arrival in several ways:

1. I print (pdf) the asnext briefing and copied it on my tablet
2. Consult the Wx report in FSCaptain, configured to read data from the corresponding file current_wx_snapshot.txt
3. Sometimes, tune the ATIS

I recognize that option 3 rarely use it because I have always found that matches any of the other two options.
I suppose that tune the ATIS is most realistic ... but I "nasty habit" of doing it other ways.

 

my flight plans created with fsbuild, with Navigraph AIRAC cycles always updated.

 

As I said, with the new version 6.49 there is no problem with the weather at destination ... the problem I see now in the allocation of the STAR associated with the runway in use

 

Thanks again for your interest

Share this post


Link to post
Share on other sites

Here it is:

 

LEMD SID PINAR UN870 PONEN UT600 CASPE STAR LEBL

 

Departing in 14L, arrival at 25L, is as follows:

 

LEMD PIN1UV PINAR UN870 PONEN UT600 CASPE CA1DCT LEBL

 

(there are other STAR that according to the AIRAC can be assigned to that runway, but that VOX assigned me: CASP2S, is for 7L / 7R runways)

Share this post


Link to post
Share on other sites

"LEMD PIN1UV PINAR UN870 PONEN UT600 CASPE CA1DCT LEBL"

 

I never tried adding airways to a FSX flight plan.

Share this post


Link to post
Share on other sites

That is the flight plan I enter in the FMC PMDG 737-800NGX !, I usually fly.

When I load the flight plan in FSX, I do which is created in FSBuild (I think it would be any flight planner, this is the one I use), as I said above. In the example, LEMD-LEBL.PLN loaded

 

Subsequently, we can save it in FSX, then LEMD-LEBL.FLT file is created. But (if I remember correctly, since version 6.20) this is not necessary for VOXATC load the flight plan

Share this post


Link to post
Share on other sites

Can you post your flight plan that was used / loaded into FSX that gave you the problem with VOXatc?

 

"if I remember correctly, since version 6.20) this is not necessary for VOXATC load the flight plan"

Are you sure?

Share this post


Link to post
Share on other sites

MMMM, here goes something wrong  :huh:  ... I've been happily using VOXATC several years, loading flight plans as I have described  :rolleyes:  ... well, maybe Google Translation is playing tricks on me :unsure: ... Forgive me if I do not understand you well

Here you can see the flight plan that appears in FSX, on the flight I put an example, giving problems when the active runway at destination is oriented south (south wind):

 

LEMD D144E D125Y D169R RBO PINAR SEGRE BRITO PISUS PONEN CASPE VLA D247J SLL LEBL

 

I want to be clear that for me VoxATC is the best FSim ATC program by far ... and I think I have tried almost all

Share this post


Link to post
Share on other sites

I have the same problem with last version of voxatc (6.52).

 

The asigned STAR have nothing to do with the approach.

This happend to me in many airports using voxatc.

 

I use PFPX for make the flight plan, and ASN for the weather.

 

I contact the developer but he do not answer me.

Share this post


Link to post
Share on other sites

I think in the AIRAC have no information that tell what STAR is for what runway (in case the airport have diferent STAR for diferent wunway).

 

You get this information looking the charts and usiong the logic. The last waypoint of the STAR is the first poin of the arrival. But the arrival can have diferent transitions as well.

 

 

All this "premisses" need to be programed in voxatc for the atc give you the correct STAR with the correct arrival (transition include).

And because this is not programed, i recive crazy vectors from atc on the arrival also, until i decide to set "no vectors for approach" for every flight plan i fly.

 

¿Does the producer going to program this or give a solution for manualy set the STAR/approach?

Share this post


Link to post
Share on other sites

The problem arises when the first waypoint of the STAR is about 60 nm farther of the destination airport. Voxatc not read properly the weather and will always give us the star oriented north runway.

I have no choice but to disable voxatc, and rehabilitate approximately 35 nm of the destination. when tune approach, assigned me the right runway in use.

 

Some time ago I asked Tegwin help, who told me he knew the problem and was working on solving the issue.

Share this post


Link to post
Share on other sites

But i have this problem also in the SID.

The ATIS told me one runway 07R

The SID clearence is for another runway 25L

But the taxi instructions are for 07R again...

Finally i takeoff from 07R but then the atc get crazy because i do not follow the cleared SID.

Share this post


Link to post
Share on other sites

Another test

 

 

ATIS

 

IN 2428327 From :el prat:  This is el prat Terminator

 
IN 2429840 From :el prat:  information
IN 2430948 From :el prat:  charlie
IN 2431650 From :el prat:   Terminator
 
IN 2431665 From :el prat:  one four one eight zulu Terminator
 
IN 2433974 From :el prat:  in use
IN 2434583 From :el prat:  runway two five left Terminator
 
IN 2436595 From :el prat:  wind
IN 2437001 From :el prat:  three
IN 2437516 From :el prat:  one
IN 2437828 From :el prat:  zero
IN 2438233 From :el prat:  degrees
IN 2438935 From :el prat:  six
IN 2439247 From :el prat:  knots Terminator
 
IN 2439762 From :el prat:  visibility
IN 2440776 From :el prat:  greater than two zero kilometers
IN 2443990 From :el prat:   Terminator
 
IN 2444005 From :el prat:  cloud Terminator
 
IN 2444801 From :el prat:  few at
IN 2445409 From :el prat:  two thousand five hundred feet
IN 2448420 From :el prat:   Terminator
 
IN 2448436 From :el prat:  temperature
IN 2449543 From :el prat:  two two 
IN 2450354 From :el prat:  dew point
IN 2451259 From :el prat:  one five 
IN 2452164 From :el prat:   Terminator
 
IN 2452180 From :el prat:  q n h
IN 2452694 From :el prat:  one zero one six
Cannot read surface wind in METAR
IN 2454301 From :el prat:    Terminator
 
IN 2454676 From :el prat:  no sigg
IN 2455378 From :el prat:  advise you have
IN 2456891 From :el prat:  information
Terminated ryanair811
IN 2457998 From :el prat:  charlie

 

CLEARANCE

 

IN 2525516 From :barcelona clearance:  air europa one one six

IN 2526077 From :barcelona clearance:  
IN 2526093 From :barcelona clearance:  cleared to
IN 2526358 From :barcelona clearance:  kastrup
IN 2526545 From :barcelona clearance:  airport
IN 2526732 From :barcelona clearance:  
IN 2526748 From :barcelona clearance:  mopas three quebec (25L)
Cannot read runway taxi speed config settingInput string was not in a correct format.
IN 2527200 From :barcelona clearance:  departure
IN 2527434 From :barcelona clearance:  
IN 2527450 From :barcelona clearance:  then as filed
IN 2527778 From :barcelona clearance:  
IN 2527793 From :barcelona clearance:  maintain
IN 2527996 From :barcelona clearance:  flight level
IN 2528308 From :barcelona clearance:  one three zero
IN 2528667 From :barcelona clearance:  
IN 2528683 From :barcelona clearance:  expect
IN 2528839 From :barcelona clearance:  flight level
IN 2529151 From :barcelona clearance:  three six zero
IN 2529509 From :barcelona clearance:  one zero minutes after departure
ATIS Metar at kastrup LOB&A0 000000Z 00000KT&D463NG 100KM&B-450&D5450 CLR 22/15 Q1016 
IN 2530321 From :barcelona clearance:  
IN 2530336 From :barcelona clearance:  departure frequency
IN 2530820 From :barcelona clearance:  one one eight decimal zero five
IN 2531600 From :barcelona clearance:  
IN 2531615 From :barcelona clearance:  squawk
IN 2531771 From :barcelona clearance:  three zero two two
IN 2532224 From :barcelona clearance:  
IN 2532239 From :barcelona clearance:   Terminator
 

 

TAXI INSTRUCTIONS

 

IN 4100096 From :barcelona ground:  air europa one one six

IN 4100658 From :barcelona ground:  
IN 4100673 From :barcelona ground:  taxi to holding point
IN 4101204 From :barcelona ground:  runway zero seven right
IN 4101781 From :barcelona ground:  
IN 4101797 From :barcelona ground:  via
IN 4101875 From :barcelona ground:  kilo sierra
IN 4102155 From :barcelona ground:  juliet niner
IN 4102467 From :barcelona ground:  quebec sierra
IN 4102795 From :barcelona ground:  and golf one two
IN 4103201 From :barcelona ground:  
IN 4103216 From :barcelona ground:   Terminator
 

 

 

Why this problem?

Share this post


Link to post
Share on other sites

I've never had that problem for SID. I use ASNext. It is important to make sure that the weather engine inject information into the simulator before enabling VoxATC. However, in LEBL I happened that I was VoxATC fatal error when started taxiing. This I have solved in this airport with ADE editor, assigning the 7R / 25L runway for takeoffs and 7L / 25R for landings.No more fatal error in LEBL.

Share this post


Link to post
Share on other sites

I use ASN too. I do not have any problem with the weather injection and i allways open ASN before FSX.

 

Before i have many  fatal error before taxi (LEBL, WSSS for exemple) same you told me.

But after update to last version i stop to have the fatal error and start to get this crazy "active runway changes".

So i thing the voxatc producers do not repair the problem, but just remove the simptom, the fatal error.

 

How can i repair this problem with ADE editor?

What is the problem cause?

Share this post


Link to post
Share on other sites

Note: Read through the end before you do anything.

 

Open ADE, edit airport, open the "List" tab , click "Runways", edit the runway that interests you, open the "Pattern" tab and put .... "Primary" Takeoff YES Landing NO, "Secondary" Takeoff YES Landing NO... and click OK. Then you go to another rwy (assuming you have more than one, when VoxATC jams) ... and put otherwise: Takeoff NO and Landing YES.
Then, compile and substitute the new * .bgl by former ... BEFORE, make a backup copy of the original!

 

The shortest rwy used for takeoffs, the longest for landing (assuming the shortest rwy is long enough for takeoffs)

 

It seems that VoxATC hangs if used more than one runway for takeoffs and landings (at least that's my experience)

Share this post


Link to post
Share on other sites

Just curious, what were the winds?  What runways were active at the time? It is not completely uncommon for the active runway to have a tailwind in the real world.  Usually nothing major, but sometimes due to traffic flow and such, a runway into the wind is not possible.

Share this post


Link to post
Share on other sites

 

It is not completely uncommon for the active runway to have a tailwind in the real world.

True ... but to a certain limit. A tailwind up to 6 knots is generally accepted as safe for landing or takeoff. But in flight simulation, at least VoxATC not assigned a runway tailwind although heavy traffic.

 

The issue is that VoxATC assigned ALWAYS a STAR to a North oriented or about whether the first waypoint of the STAR is more than 60 nm to airport  ...  but later approach ATC assigns the correct runway according to the headwind (from 6.52 version)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this