HI,I have just made a short trip on the route between GOOY and GOGS. The plane was scheduled to cross "TITOR" waypoint whose coordinates (reported both on FSNav and GPS)are N13.00.00 W018.00.00. The plane just flew over it but RC shouted at me telling I had to go back. The waypoint is considered as "passed" if you are not more than 7 miles from it, and the small RC window showed "1" Nm before actually I started to fly away from it, therefore everything should have been OK. I was wondering why this happened, and then if we must update the AIRAC cycle just like I normally do with my aircrafts. Maybe that was the problem?Thank youLorenzo

was it a departure procedure? did you miss something earlier?if you can duplicate the problem, make a log, as outlined in the pinned post at the top of the forumbe sure you click debug, before loading the .plnjd

In departure/approach airspace your waypoint credit range is within two nm, five if center. We are talking about 40 nm from departure/destination where the range changes. Did TITOR progress of the screen or did the direction change and the distance to it start increasing? Remember if you do miss a credit you can select the extended menu and then Direct To Checkpoint and then select a waypoint from the list presented. This will become the next waypoint in the RC window status area.RC uses the coordinates of the waypoints in your .pln file. If you are using an FMC or GPS with their own waypoint location database and this waypoint location is different in your plan, then this could be causing problems.If you are handling the comms with no pilot autoreply enabled, make sure you have acked promptly RC ATC commands. If any "ack" prompts are displayed and you cross a waypoint while this is up, you may not get credit for passing the waypoint. Also be sure if this waypoint is within a crossing restriction that you have met that restriction and you might be commanded to follow delay vectors until you are at the desired altitude.

Hi Guys,no this wasn't part of the DP, anyway shall try to duplicate the problem.CheersLorenzo

Hi,yesterday I have tried but everything went fine, I suspect It depends on the fact that I have flown the entire plan without asking for "DCT TO" as I did the first time, anyway I will try again..RegardsLorenzo

I am using Vas-FMC to build my flight plan and convert it in .pln file and it work perfectly with Radar Contact except when I add coordinate points like N13.00.00 W018.00.00. When I add way points like that it doesn't want to take it. Any idea of the problem.Thanks guysAl

you would have to send me the .pln.if the .pln is not properly formatted, then rc is not going to handle it correctlyjd

Here's the .PLN file. Let em knwo if you received it correctly.ThanksAL

how or who put these 3 points in the .pln?waypoint.7=, N50.00.0/W100.00.0, , N50.00.0/W100.00.0N00* 0.000', E50* 0.000', +000000.00,waypoint.8=, N50.00.0/W110.00.0, , N50.00.0/W110.00.0N00* 0.000', E50* 0.000', +000000.00,waypoint.9=, N49.00.0/W120.00.0, , N49.00.0/W120.00.0N00* 0.000', E49* 0.000', +000000.00,the format isn't even correct.

I put it myself with my vas-fmc program. The points are all working fin e except points like N50.00.0/W100.00.0.How should I entered it. This is how I have to enter it with VAS-FMCTHanksAl

First of all, there is an ICAO naming convention for waypoints, here's a copy from the FAQ's at vroute.info :-If you need to enter exact waypoint coordinates in a flight plan, which is pretty common when coding North Atlantic Tracks (NATs) and other oceanic routes, here's how to do it: On northern hemisphere: (00N-90N)Our example is on 60N:7 letter coordinates : 5 letter ICAO fix60N180W-60N100W : 60N80-60N0060N099W-60N001W : 6099N-6001N60N000E-60N099E : 6000E-6099E60N100E-60N179E : 60E00-60E79 That goes for all latitudes on the northern hemisphere. So we are on the60N, starting at 180W (60N80) and moving to the east ending in 179E (60E79). On southern hemisphere: (00S-90S)60S180W-60S100W : 60W80-60W0060S099W-60S001W : 6099W-6001W60S000E-60S099E : 6000S-6099S60S100E-60S179E : 60S00-60S79 Such encoded waypoints (i.e. 60S79) can be also typed into standard navigation computers, i.e. 737 FMC. Thanks to Johann M. Kjartansson for preparing the instruction. Now to the FS .pln file, each field in the file has a purpose and must be correctly formatted to work, also each field is seperated by a comma,waypoint.x=REGION, FIXNAME, , FIXNAME, FIXTYPE, LON, LAT, ALT, AIRWAYREGION = ICAO region code e.g. LF: France, EG: United Kingdom, ED: Germany, (max 2 chars), blank if an Airport or no regionFIXNAME= ICAO code for Airport, waypoint, VOR etc. (max 5 chars)FIXTYPE= A: Airport, V: VOR, N: NDB, I: Intersection. (max 1 char)LON/LAT= Longitude and Latitude expressed in Degrees and Decimal minutes/seconds, the format must be N/S/E/W(x)xx* xx.xx' .ALT= Altitude in feet. Seems to be the Airport AMSL, +000000.00 for all other waypoints.AIRWAY= ICAO Airway code e.g. UL607, UM859, UG1 etc. can also be used for SID/STAR name e.g. NED1A, SAM3C etc. Blank if no name.Following this format, your 3 waypoints above should read :-waypoint.7=, 50N00, , 50N00, I, N50* 0.00', W100* 0.00', +000000.00,waypoint.8=, 50N10, , 50N10, I, N50* 0.00', W110* 0.00', +000000.00,waypoint.9=, 49N20, , 49N20, I, N49* 0.00', W120* 0.00', +000000.00,vasFMC will also accept the standard ICAO format 50N00, 50N10, 49N20, which is much quicker than typing out the full Lat/Lon co-ords.Hope this helps..........Adrian W.