Greetings all,I am trying to program the following route from KEWR-KBOS.....MERIT ORW ORW082 PVD263 PVD ORW3. I would assume that after ORW, I fly the 082 degree radial until intercepting the PVD263 radial, and then turn direct to PVD. How do I program this into the FMC? I tried ORW082 and ORW/082, and couldnt get it to work. What is the correct way of doing it? Many thanks.

- Im pretty sure you need to define the distance as well. Example-ORW082/10

What you're doing doesn't make too much sense, RW. Either select the ORW3 ARR in the FMC, or fly it with the MCP. If you have the ability to program radials in to the FMC, you should be able to select the correct ARR and LNAV/VNAV. If you can't then you'd fly it in Class1 Nav, using the VORs.It's like asking how to teleport a car. What do you need a car for if you can teleport?

You know you can do this the old-fashioned way - track the two radials using the AP VOR/LOC mode and the VOR ND mode. That is allowed in real life... In fact I'll bet that's what would really be done in this case - the process for putting this kind of thing into the FMC is likely not worth the time. You'd have to make a PBD waypoint far out along the ORW 082 radial and then do a direct to with a 082 INTC CRS to that waypoint. Then as you were approaching the PVD 263 radial, you'd have to do another direct to with an INTC CRS of 083 (reciprocal of 263, since that would be outbound not inbound). Use the FIX page to draw the two radials for situational awareness in map mode...

Couldn't you plot out the intersection & enter the lat/long for that point?

Yesterday on VATSIM I had the routeKPHL PHL8 DITCH V312 DRIFT V308 ORW WOONSWhy is the V312 and V308 needed here? Don't I go directly from DITCH to DRIFT then to ORW? I don't get the V312 or V308 concept here. I know they are precise airways, but is DITCH V312 DRIFT a different route than DITCH to DRIFT.I still can't figure how to program the V312 on the LEGS page. It says waypoint not found in database.

use the left side of the page to enter airways, the right is for way points.DIRECT DITCHV312 DRIFTV308 ORWDIRECT WOONSthat is roughly what it should look like. It is best to file the route with airways. While it may make no difference in terms of the FMC and its functions, but the airways is a specific radial from point to point using VORs and such as guidance to ensure that you are on that airway and passing by the appropriate intersections, and filing it as thus is telling the ATCers that this is how you are flying from point to point.Flying in something like the 737, you are most likely not getting around manually flying and tuning the NAV radios in such a way to fly from point A to point B, as the FMC is doing this all for you, but you are doing the same nonetheless, either you doing the grunt work or the computers doing it for you.

Okay, what you're trying to do is just going to confuse controllers and me, a pilot. You wouldn't file that route. You probably wouldn't be cleared on that route if you did for some reason.You would file MERIT-ORW.ORW3.Those radials are already on the STAR and you're already filed the STAR, so don't complicate matters.Technically, you could put in a fix by using radial/radial ORW083/PVD263, but like I said, that's already contained in the STAR.The leg is also only 28nm long. If I was doing it RW, no FMC, once I crossed ORW, I'd just start tracking on the PVD263 inbound. 14 nm at 280kts doesn't last long enough to worry about a VOR COP.

I think Airways should be entered under the VIA column within the FMC RTE page 2 and on (left side LSKs), and waypoints should be entered under the TO column.I you get a chance to read the initial Tutorial again, explanation provided in the Enroute entry section (pages 22-24) is pretty clear. Enjoy it !All right, info already provided above by Scott. Sorry for duplicate...

Edited December 10, 201114 yr by leaderchris

...Created waypoints can be keyed into the scratch pad in any of the following ways:1. Place-Bearing Distance2. Place-Bearing Place Bearing3. Lat/Lon4. Along WptPLACE-BEARING?DISTANCE(PBD)a. Type ORW082/10 to s/p (Bearing Entry requires 3 digits)b. Place after the proper wpt-ORW (LSK2L)becomes ORW01 (sequential no. from 01 to 49 for RTE 1)c. Close up route DISCO, check, and EXECute...FMC USER GUIDE..Bill Bulfer and ###### GiffordI used this and it does work.If anyone would like the book (its costly, but well worth it)http://www.afeonline...roducts_id=1599Hope this helpsI've attached a 'screen dump' of this on FMC and ND. TUN01 is my PBD waypoint

Couldn't you plot out the intersection & enter the lat/long for that point?

How would you do that in the cockpit?

Yesterday on VATSIM I had the routeKPHL PHL8 DITCH V312 DRIFT V308 ORW WOONSWhy is the V312 and V308 needed here? Don't I go directly from DITCH to DRIFT then to ORW? I don't get the V312 or V308 concept here. I know they are precise airways, but is DITCH V312 DRIFT a different route than DITCH to DRIFT.I still can't figure how to program the V312 on the LEGS page. It says waypoint not found in database.

Please read the first tutorial flight included with the plane, it explains the airway concept in detail. DITCH to DRIFT direct is not the same thing as DITCH to DRIFT via V312. V312 is like a highway, there can be turns, intermediate waypoints along it between the on and off points etc...

Okay, what you're trying to do is just going to confuse controllers and me, a pilot. You wouldn't file that route. You probably wouldn't be cleared on that route if you did for some reason.You would file MERIT-ORW.ORW3.Those radials are already on the STAR and you're already filed the STAR, so don't complicate matters.

The route he posted is the most commonly filed one on flightaware if you go look... real flights actually are filed with it. I've seen the same thing with KTUS-KABQ: BURRO2 CIE SSO J104 ONM212029 ABQ185

Gents-There are a number techniques that you can use to create visual references for yourself on the ND to assist with complex arrival and departure procedures. (Some procedures give you conditions based on passing certain radials or distances from a known fix.)You can create them visually on your NAV display by using the FIX page.I'll be back a bit later with a few examples. I was playing around with complex departure procedures a few weeks ago- and having the ability to create visual references for yourself on the ND makes your life significantly easier...

Wow....this was a bit more involved than I thought it would be. My initial thinking was this: Flying the 082 radial after ORW, you would eventually get to the PVD263 radial. Wouldn't that intersection be just like an unnamed waypoint? If indeed that intersection had a waypoint name (eg: "ABCDE"), then the route would have been ORW ABCDE PVD. I had assumed that intersection/unnamed fix could have been programmed into the FMC.

How would you do that in the cockpit?

Maybe I misunderstood. I was under the impression he was generating a flight flan from scratch, which would generally be done before filing it & entering the cockpit. If this is the case all he should need is a chart and a straight edge.

The route he posted is the most commonly filed one on flightaware if you go look... real flights actually are filed with it. I've seen the same thing with KTUS-KABQ: BURRO2 CIE SSO J104 ONM212029 ABQ185

Well, I stand corrected. I have a feeling there's something going on with that STAR. (Turboprops following the route, but no being able to accept the STAR, for instance.)They might clear you "as filed" but en route they'll probably just clear you via the arrival. However, there's really no point in making that waypoint since it's contained in the STAR.