csanchezdll

Takeoff from intersection does indeed happen in RL, it is even common at some airports. The key point is runway occupation time: backtrack usually takes a lot of time, which is (mostly) useless if the runway is long and the plane is light. I have heard ATC ask a light plane on an intersection if it will require backtrack, with some liner on the glidepath, and clearing for immediate T/O after pilot answers he won't. Of course final word is on the PIC. I guess for airliners might not be so usual, but for light aircraft operating in big fields mixed with commercial traffic, it happens every day. Sadly, seems Vox does not support it. Thanks! Carlos

Hi! Does anybody know if VoxATC supports T/O from an intersection. Yesterday I flew from LEXJ, which has a taxiway that goes about 3/4 to the way to the runway threshold, and ATC instructed to line-up runway 29 (wich the usual "press 0 to backtrack"). Instead of requesting backtrack, I lined up in that position, which was more than enough for my BE36 to go airborne. However, I never got the T/O clearance, and after waiting for a while I restarted VoxATC and this time I taxied to the runway threshold and everything worked. Is it possible to request T/O from an intersection? Maybe in expert mode? (which I am not yet using). Thanks! Carlos

Yes, I am using the default traffic AI. I will contact official support then, and in the meanwhile you gave me the idea of replacing the AI with WoAI to try to workaround the error. Thanks! Carlos

I was flying a Turbine Duke V2, B60T, callsign TFKDP. I had seen several other GA flights during the flight, I think most has callsigns TFxxx (icenlandic registrations), as well as commercial flights. I do not remember hearing any communication with a Gxxxx flight. Examining VoxATC log from previous flights in the area I can see that in fact usually I see flights with icelandic (TF), finnish (OY) and UK (G) registrations, so I think you might be pointing in the right direction. I do not know why Vox cannot create a Gxxxx registration, thought. I have checked my callsign has no dashes or any other strange characters, just TFKDP. What else could I check? Thanks Jay!

Hi all, During a flight over Iceland, BIVM to BIAR, VoxATC 7.41 suddenly gave me a fatal error halfway trought the descent to destination. I had logging disabled, so I enabled it and re-enabled Vox. It initialized correctly, the text saying "Tune Akuryeri Tower on..." appeared briefly, and then again FATAL ERROR. I have been examining the log and I can see what seems to be an error message just before the FATAL ERROR, saying "Cannot create unique G callsign" and then a traceback of the internal procedure names. Has anyone experienced something like this? 851798031 Ins Text set : Tune to akureyri tower 118.200 851798062 Prompt disabled 851798109 Prompt Text set : ElevationDataSharp::GetFile Downloading elevation hgt file: N65W019.hgt ElevationDataSharp::GetFile Downloading elevation hgt file: N65W019.hgt SrtmDownloader::DownloadBinaryToFile N65W019.hgt not available on server (maybe all sea) SrtmDownloader::DownloadBinaryToFile N65W019.hgt not available on server (maybe all sea) ElevationDataSharp::GetFile Downloading elevation hgt file: N65W018.hgt SrtmDownloader::DownloadBinaryToFile N65W018.hgt not available on server (maybe all sea) ElevationDataSharp::GetFile Downloading elevation hgt file: N66W019.hgt SrtmDownloader::DownloadBinaryToFile N66W019.hgt not available on server (maybe all sea) ElevationDataSharp::GetFile Downloading elevation hgt file: N66W018.hgt SrtmDownloader::DownloadBinaryToFile N66W018.hgt not available on server (maybe all sea) Simconnect version 10.0.66.0 FAF position not found in :Localizer runway one three FAF :FF13 The approach Localizer runway one three has no FAF position FF13 FAF position not found in :Localizer runway one three FAF :RKF13 The approach Localizer runway one three has no FAF position RKF13 FAF position not found in :R NAV runway one three FAF :RKF13 The approach R NAV runway one three has no FAF position RKF13 16:55:56.2785429 Current Position = 65.1555002779643 -18.8100361706555 14823.7679585174 IN 16:56 From :orbit seven fourteen: reykjavik center IN 16:56 From :orbit seven fourteen: IN 16:56 From :orbit seven fourteen: orbit seven fourteen IN 16:56 From :orbit seven fourteen: IN 16:56 From :orbit seven fourteen: with you at IN 16:56 From :orbit seven fourteen: flight level IN 16:56 From :orbit seven fourteen: one four zero IN 16:56 From :orbit seven fourteen: IN 16:56 From :orbit seven fourteen: Terminator IN 16:56 From :reykjavik center: orbit seven fourteen IN 16:56 From :reykjavik center: IN 16:56 From :reykjavik center: reykjavik center Cannot create unique G callsign at com.intworkings.voxatc.CallsignImpl.CreateGCallsign() at com.intworkings.voxatc.CallsignImpl.CreateCallsign(AircraftType typeIn) at com.intworkings.voxatc.FlightPlanner.CreateArrivalAircraft(BGLFlightPlan bglFp_, AircraftType acType_, Aerodrome adIn_, Int32 quadrant_) at com.intworkings.voxatc.FlightPlanner.GetArrival(Aerodrome adIn, Int32 quadrant) at com.intworkings.voxatc.ApproachPortal.GetFlightPlan() at com.intworkings.voxatc.AirspacePortalBase.GetNextAircraft() at com.intworkings.voxatc.ApproachPortal.GenerateTraffic() at com.intworkings.voxatc.Airspace.GenerateAppTraffic() at com.intworkings.voxatc.Aerodrome.GenerateTraffic() at com.intworkings.voxatc.AerodromeAircraftGenerator.GenerateTraffic(Dispatcher dispIn) at com.intworkings.voxatc.Dispatcher.Run() 851815550 Ins Text set : FATAL ERROR! disable VoxATC IN 16:56 From :reykjavik center: IN 16:56 From :reykjavik center: roger IN 16:56 From :reykjavik center: IN 16:56 From :reykjavik center: Terminator I have my navigation data updated using fsAerodata with current AIRAC (1711). Thanks, Carlos

Hi Jay, I have used ADE in the past mostly to get the airport diagrams of custom airports (which do not always match RL published charts). I agree with you the tool is fantastic. Once I start usign it seriously for editing, I will byt the ProKey (9.99$ is almost a giveaway for it). BR Carlos

Thanks Jay, that is what I thought. In fact, I have checked the airport BGL with ADE and the old approach (including SARAM point) is there, so that is where it gets its data from. I think I will be using ADE quite a lot for a while Carlos

Hi all, I made an IFR flight on my C172 from BIVM to BIKF (Iceland) yesterday, with VoxATC. Mostly uneventful: I was cleared to EL1W departure, and at EL direct to KEF; once near KEF, I was told to expect vectors to ILS RWY 29. However, as ATIS had said RWY 02 was in use, I had prepared that approach beforehand, so I asked for ILS RWY 02. The strange thing happened then. I was cleared to ILS RWY 02, but told to report at SARAM. I could not find it on my charts. After some googling, I found SARAM was a holding point in ILS RWY 02 approach to BIKF some time ago (found it on some 2011 charts), but it is not present on current approach plates. My question therefore is: where does VoxATC get approach data? I know it takes SID/STAR from Navigraph updates, but I suspect approachs are taken from FSX BGLs (which are quite old). Can someone confirm this? Thanks! Carlos