I have been using real world flight plans for SWA 737NG. A couple of flights have entries that look like this:DCA266 and one like this CWK040.My question is where on the route page would I enter this so I dont get the not in database error message. I have tried the right and left lsk.Thanks for any helpAndrew

Anyone?Andrew

Hi Andrew,Looks like a NAVAID and a RADIAL to me. But I'm not confident in my answer here... ;-)Regards,

Hi Andrew,I tend to agree with Mats it should be a Navaid/radial format. Can you post one flightplan which includes any or both for a further look.Michael

Gotta be a conditional (part of a stored procedure).Jeppesen inverts the navaid id and distance if greater then 100mn so your DCA226 would actually show up as 26DCA.You can not enter conditional waypoints like (DCA226) which means fly heading until crossing the 226 radial from DCA.If your wpt right before it was DCA, it could be a place-bearing/distance enter, but when entered, it would show up as DCA01*if* the waypoint before happens to be DCA, then it gets entered DCA/226Best I can offerRay

Here is the flight plan in question. I got it from the flight plan forum. Real world SWA plan. I guess it was DCA 246 not 226.SWA934 KBWI-KAUS B733/MN0435F350 DCT FLUKY DCA246 PAUKI DCT MOL J22 VUZ DCT JAN DCT AEX DCT IDU BITER3ThanksAndrew

I

The thought that such a fix may not be availible in MSFS is a good one. So it may just not be availible.Yes there is a KDCA it is Reagan airport near Washington DC. DCA is the associated VOR. Andrew

Hi Guys,Don't konw if it helps but here is my understanding of the route:The segment FLUKY - PAUKI is on the radial 246 from DCA. Now if you analyze the FLUKY waypoint it would correspond to a place/radial/distance waypoint ie. DCA/246/38.8 if it was not in the databaseSo my conclusion is that FLUKY and DCA246 are identical in this route. It may only have been mentioned for those (real world)FMC databases which do not contain the waypoint FLUKY.Does it makes sense to you guys?Michael

Well it looks like a *conditional* waypoint indeed. *246* indicates positive that it is a Radial (three digits=R) and I assume DCA is a VOR. So it should mean that particular heading leg terminated at the 246 R FROM DCA VOR.[h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-5/196432/winglets_lg.jpg

>> Well it looks like a *conditional* waypoint indeed. *246*>indicates positive that it is a Radial (three digits=R) and I>assume DCA is a VOR. So it should mean that particular>heading leg terminated at the 246 R FROM DCA VOR.I use Jepp Flitestar too, and it calls out these GPS-ONLY waypoints that are recognized by realworld ATC, and may show up on charts, but are typically NOT in the databases we use.ACO24 is an example. it defines the intersection of V297 and V6-42 northwest of Akron. but it doesn't show up on the Low Altitude charts. the FMC doesn't recognize it, but my KLN89B in the real airplane does. the 024 refers to the DISTANCE from ACO, and not a radial.If you use real-world flight planning software - you should get the lat/lon of the waypoints, as you can always enter lat/lon into the FMC to define a waypoint.

>Here is the flight plan in question. I got it from the flight>plan forum. Real world SWA plan. I guess it was DCA 246 not>226.>>>SWA934 KBWI-KAUS B733/M>N0435F350 DCT FLUKY DCA246 PAUKI DCT MOL J22 VUZ DCT JAN DCT>AEX DCT IDU BITER3>>Thanks>Andrew>OK, this is not in the format a controller would recognize, but what your waypoints are (having looked at the real charts), and how you'd enter them in the FMC isFLUKY (direct)PAUKI (Direct - and the path between fluky and pauki is the DCA 246 radial)MOL (direct)VUZ (via J22)JAN (direct)AEX (direct)IDU (direct)KAUS (BITER3).If I were filing this flightplan with ATC I'd file:KBWI FLUKY PAUKI MOL J22 VUZ JAN AEX IDU.BITER3 KAUSHope this helps.

Hi Tim,My understanding is that ATC does not recognize these GPS-only waypoint either (real world flying) (if I have my IR written studycorrect :) ).Bruce.

>Hi Tim,>>My understanding is that ATC does not recognize these GPS-only>waypoint either (real world flying) (if I have my IR written>study>correct :) ).>Bruce.>A controller won't recognize it if you ask for it, but DUATS and FSS will let you include them in a flight plan, as the routing computers in Leesburg do recognize them.

Hi folks,>>FLUKY (direct)>PAUKI (Direct - and the path between fluky and pauki is the>DCA 246 radial)Well Tim just confirmed what I was trying to explain earlier. the DCA246 waypoint is not necessary. This happens from time to time in real world plans.I guess if you come across such waypoints again try to enter the one immediately before and the one immediately after in the route and check if the segment is not following the waypoint/radial in question.Michael