Hi All,I have been getting used to the 737 and am still learning all the ins and outs of the FMC. In cruise, using Radar Contact, the controllers issue crossing restrictions, usually 40 NM from the last waypoint. I have attempted to program the FMC using the same technique as shown in Mr. Metzinger's tutorial, defining a waypoint in reference to another waypoint, with additional speed and altitude info, but can't seem to get the aircraft to meet the crossing restriction.Can anyone please help with the proper keystrokes, etc., for programming a crossing restriction? The RC contollers keep busting my chops!!!Thanks in Advance,Brad StreeterKKLS

>Hi All,>Can anyone please help with the proper keystrokes, etc., for>programming a crossing restriction? The RC contollers keep>busting my chops!!!>>Thanks in Advance,>Brad Streeter>KKLSBrad,can you give a specific example? If you can, I can try and tell you what you'd need to punch into the FMC.Also, you've got to be sure you EXEC'ed the changes after you put them in.

Hi Timothy,A flight I have been using to get the full idea of the NG and FMC goes something like this:KSMF-FROGO6.FRA-AVE-SADDE6-KLAXControllers give me 250KT/10000Ft crossing restriction 40 NM from SMO. I have attempted to define the waypoint using FIXRAD/DIS, with the fix of SMO, don't recall the radial (something like 310), 40 NM distance , then entering 250/10000 and executing after correcting any type of DISCO. The aircraft is usually at FL180 or lower when I get the crossing restriction.I know I'm doing something wrong. The auto pilot will usually start decending, however it does not stay on the prescribed descent path and I end up missing the restriction. Perhaps you can check this out and let me know if I need to lower other altitudes along the waypoints after clearance to lower altitude. Radar contact has me descending before the T/D figured by the FMC.Hope I gave you enough info. You have written a great tutorial and it is much appreciated.Kind Regards,Brad StreeterKKLS

>Hi Timothy,>A flight I have been using to get the full idea of the NG and>FMC goes something like this:>KSMF-FROGO6.FRA-AVE-SADDE6-KLAX>Controllers give me 250KT/10000Ft crossing restriction 40 NM>from SMO. I have attempted to define the waypoint using>FIXRAD/DIS, with the fix of SMO, don't recall the radial>(something like 310), 40 NM distance , then entering 250/10000>and executing after correcting any type of DISCO. The aircraft>is usually at FL180 or lower when I get the crossingPart of the problem is that when your controller gives you a crossing restriction, he's expecting you to manage your descent. If he then descends you to another altitude, UNLESS he repeats the crossing restriction, it's not valid, because you have a new clearance. Most of the virtual ATC controllers are sharp enough to let you manage your own descents, but occasionally...But, as captain, never hesitate to fly the airplane - dial in the crossing altitude and hit LVL CHG if needed, even if it means you get down "early". Or dial in the altitude and use VS mode and adjust VS until the green prediction arc is on the waypoint.Frankly, once you're working with an approach controller, FMC flying is often rare - they're always changing thing by giving you vectors or altitude changes, and it's frequently not worth it to try and punch that stuff into the FMC.Here's the better way to put the crossing restriction in the FMC - if you're following the programmed route, just put in SMO/-40 as the waypoint (that translates to "40 miles before SMO on the programmed route" and insert it before SMO, and put in your speed/alt restrictions, then EXEC it.Hope this helps.

Thanks Timothy, your response answers my questions!! Now, back to that pesky controller!!Thanks Again,Brad StreeterKKLS

Brad,Another restriction you might get, for example, is (

Brad,As a frequent user of Radar Contact I have a strategy for meeting the crossing restriction which works well for me.Assuming the landing runway is known I add up the distances between each waypoint starting with the landing runway and working backwards until I'm close to 40 miles. Radar Contact v3 is different from earlier versions in that it does not calculate the distance as the crow flies but bases the 40 mile distance on the sum of the remaining waypoints.If the waypoint closest to the 40 mile point (we'll call it ABC) was actually at 36 miles I would create a new waypoint 4 miles before ABC. In all probability it would be a lat/lon and once entered in the FMC would show up as WPT1 (assuming no other lat/lon waypoints were present). Then enter 250/10000 against that waypoint and you're in business.I use FSNav to determine the exact point of the crossing restriction.Hope that helps!Cheers,

Thanks for all the tips! I'm sure I'll get this all squared away. I love it when the learning curve steepens up a bit!!Brad StreeterKKLS

hi is Radar contact compatible with fs9

I am tempted to say that FS9 is compatible with Radar Contact but I won't ;-) Yes, it's fully compatible. For more info I suggest you visit the Radar Contact forum.Cheers,

Hi Brtad and hi Ray, I strongly echo Ray's great advice. If you purchase RC I think you'll simply love the program, that is, if one can love an object.Cheers men