solvair

I have completed a successful flight with P2A (LEVC-LEBL) ... has only missed one little thing: when Ground, Tower or Centre told me current QNH, said "...qnh one..." (missing the last three digits) when I expected "qnh one zero zero niner...". Nevertheless, I answered "qnh one zero zero niner", P2A does not recognize, and it kept saying "qnh one"...then I forget this and continue with the flight I take this opportunity to ask for "a wish": Would it be possible (and realistic) that the SID and STAR were spoken and acknowledged by voice by name, or at least pronounced with ICAO phonetic alphabet? Best regards

take note. I'll try.

in LEBB frecuencies Ground and Clearance/Delivery are the same: 121.700. Tune that frecuency, ask for clearance, receipt data, readback correct...so...I want to contact Ground to ask Pushback and engine start, but only receive the request "contact Ground on 121.7". I tried retune, I have also requested frequency change to Grnd... but does not work. I can't go on...without cheating Regards

Thanks for the quick reply

I see some major airports lack the Tower frequency, or Ground ...For example LEMD, where we see several Tower frequencies but none Ground I would like to edit the database to add the missing frequencies (that exist in the real airports) , but I have not seen any button to edit the database (as it is in the version P2A v1). Is it possible to edit and modify the database (P2A V2)? regards

Of course, before this, was IFR clearance, requested taxi to runway 30, etc ... I received "lineup and wait", I stepped on the runway, stopped ... but never received takeoff clearance Thanks for the quick reply, Dave. Fans of flight simulation need a good ATC and you're doing a good job.

Using P3D v3.2, PMDG 737-800, airline tfc at 35% I have noticed that traffic is not automatically updated, you have to "restart", pressing the button twice to display traffic (deactivate / reactivate display traffic) Still, there is some lack of coordination between the simulator and p2A: yesterday I wanted to make a flight, hold short on the takeoff runway. A plane was on final, landing ... I waited ...lands and I asked permission to take off: ATC responds "lineup and wait" ... I stand at the head of rw ... the plane just landed just left the rw ... but never receiving takeoff clearance. Spend a few minutes ... the rw empty, desperate speak "still waiting for takeoff clearance, rw 30"...ATC unresponsive, does not understand me, I get angry and turn off the simulator. It would be nice p2a interact and talk with the other planes and, being on the same frequency, you may have an idea of what goes around Today the problem I've had in the end: the last communication with the ATC has been, by approach "fly assigned star". I landed without having heard the request to change to Tower frequency nor the consequent clearance to land. Another thing, every time I run P2A I have to go to config and click on "use decimal instead point" (flight usually in Europe), that option is not saved, you have to give each time we run P2A! Regards

only fails in this FP??!!: route LEMD SID PINAR UN870 PONEN UT600 CASPE STAR LEBL, from PINAR I want to load airway UN870 to PONEN...but only load to PISUS, that is the first point starting with P of that airway in alphabetical order (PISUS, PIVUS, PONEN, PORLI...as shown in the list) I have tried other flight plans and only fails this ?! Regards

My flight plan: LEMD PINAR UN870 PONEN UT600 CASPE LEBL. Load the SID, open PINAR to load airway UN870 to PONEN, click "Load"...there are no changes As I said in my first post, I tested with the flight plan of the tutorial: KLAX... KSFO...no load airways too Thanks for your quick response. I'm waiting for a new version that solves this problem

Hello friends, I get not create a flight plan with airways No way to load airways. From initial waypoint, choose airway, final waypoint, click "load"...close the window, but noting happens: no load airway nor waypoints. I tried to follow step by step tutorial instructions for IFR flight plan, but, unlike in the tutorial, does not load airways I tried to uninstall and reinstall V2. Tested with version 2.0.0.1 and the latest 2.0.0.9. I bought pilot2atc about ten days ago, I remember that when I installed it and tried it for the first time (v 2.0.0.6), it was carrying airways ... I do not know what happened. I do not know if it's a bug, or some detail that I forget Using Flight Simulator Prepar3d v3.1 How do you solve?

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)

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)

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.

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.

On flights that I have made since version 6.49, winds and other conditions VoxATC match ASNext ... but ... I meet another problem: STAR whose starting waypoint is far more than 60 nm from the airport destination, VoxATC (center) always assigns me a STAR associated with oriented North runway ... after, ATC approach indicates the runway I agree well with the winds, correcting, if a better runway with headwind. I notified Techwin the problem and told me he was looking for ways to fix it. Sorry, I mistyped Tegwyn

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

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

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)

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

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

In the fmc of fscaptain I can display anytime metar destination. I think both rc as pfe even proatcx can read metar provided by active sky, fsgrw, etc.. (I tested with the three atc addons and these two weather engines) ... I think the problem is clearly voxatc, and the solution is a new version of voxatc read the metar those weather engines, which, of course, include arrival airport

It's a real shame to restart voxatc to achieve correct winds, substract all grace. Sometimes, the STAR star before ~ 100 nm, so the assignment of STAR may not be good.

I think this add-on requires FSUIPC registered, that does not make the same. I already tried the FSUIPC option: did not work

It seems the problem has been resolved, at least in my case. I think there was a problem of "synchronization". Read ASNext help, and gave me an idea (page 30). I bought a license from the add-on FS Real Time (http://www.3dsoftworks.net/products/fsrealtime/download.asp) , I made a couple of flights and ... surprise: VoxATC gives me the correct landing runway (headwind)

Ah! agree, sorry. The sqwawk "3013" is the first code that assigns VoxATC when enabled. If you disable and act immediately enable, sure assign "3013". It's the same when you start and you hear the ATIS, anytime VoxATC starts saying "information BRAVO" By the way, Tegwin answered me as follows: "Try enlarging the radius of the weather being generated by AS Next" I'm afraid that is not possible with ASNext