Sign in to follow this  
Driver170

Radar Contact Dp No Alt Rest.

Recommended Posts

Is this correct of my understanding i want to fly my SID out of edinburgh my home airport.

 

I select no alt rest. And ATC gives me climb to FL060 so if i level off at FL050 ATC won't nag me till 30nm but what happens if i fly above it lets say FL070 ATC will still leave me alone ok i got it BUT...

 

So why give a FL during climb out why can they not just give you clearance without an assigned alt.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

FL060 is still your assigned altitude which is the max you can climb until ATC tells you otherwise (inside the 40nm terminal airspace or not), period.  Think of the 'No Alt Rest' as relief (no nags) from 'having' to maintain a positive rate of climb of at least a few hundred feet per minute, to the currently assigned FL060.  This is useful if my DP/FMC says to cross a certain waypoint at FL040 somewhere within the 40nm terminal airspace.  Now RC won't nag you while you level-off prior to and while crossing your FL040 FMC waypoint.  Then you would restart your climb to FL060, pending any further FMC altitude restrictions, but don't go any higher until RC clears you.  Regardless of this option, once your cross the 40nm terminal airspace boundary, you must maintain at least a minimum rate of climb to your next assigned FL, otherwise you'll get penalized.

 

No Alt Rest is not a 'free pass' (golden cheat) to climb straight to your filed FL of 370, for example.  But I do agree, JD could've labeled the option a bit better way back in the day.

Share this post


Link to post
Share on other sites

Thanks jordan for clearing that up :)

 

Now if i want to fly my own SID with my ngx fmc do i have to make my waypoint beyond 30nm and ATC won't give me any instructions is that right?

Oh also i'm using PFPX to i have to include my SID in my plan for RC or do i have to leave it out?

Share this post


Link to post
Share on other sites

When flight-planning, I also use PFPX and I had used FSBuild for many, many years as well.  I always leave my SID and STARS out of my exported FPs.  I try to find a "common" DP waypoint, regardless of runway or distance, and use it as my first exported FP waypoint.  But, I have to manually type in any/all 'common' DP waypoints in the PFPX FP editor I want to export as part of the FP.  This way RC and Flightsim Flight Keeper both know about a few of my DP waypoints.  So if my SID has 5 waypoints and waypoints 3, 4 & 5 are common to all departures in the direction I'm going, I will remove the SID while flight-planning in PFPX and manually type in waypoints 3, 4, and 5.  Then do the same for my STAR, find common waypoints to about a30 or 40nm from my destination then remove the STAR and type in those common STAR waypoints by hand.  I then export the FP.  Now in the FMC, I chose the exported FP (which only contains 'common' SID/STAR waypoints.  Then I chose the Rwy and full DP in the FMC and it will tie straight into the start of my FP (clear any duplicate waypoints on the LEGS page).  Then do the same for the arrival, select the STAR and arrival rwy, then clear the duplicate waypoints from the last few LEGS pages.

 

This way, my 'generic' FP works with multiple runways for both RC and FSFK, and I can get the FMC to still use the actual/desired SID and STAR.

Share this post


Link to post
Share on other sites

LOL, sorry - I know it's a bit confusing, but it's a work-around that has served me well over the years.

 

PFPX is currently designed NOT to export the SID & STAR portion of any FP - and, PDMG won't import any SID/STAR portion of a FP into the FMC (it'll strip it) during the 'load route'.  So...  I manually include any/all desired SID/STAR waypoints by typing in those waypoints by hand into the PFPX FP editor.  Some SIDs and STARs are extremely long and to have the a FP start 100 or 200nm away because the SID gets striped on export and/or FMC import, is not desirable.  Nor is ending an exported FP a long distance from the destination (because the STAR gets stripped).  This is why manually include some of the SID/STAR waypoints - to get my FP closer to the departure and arrival airports.

Share this post


Link to post
Share on other sites

Right i see thats alot of work still thats the reason i left behind PFE lol

 

Hmm is there not another way i can fly my SID freely like having the waypoint outside 30nm from the airport thats what it says in the manual?

Share this post


Link to post
Share on other sites

If you first waypoint is outside 30 nm you can choose any of the three options on the controller tab. RC will default to No Departure Procedure giving you altitudes and vectors and monitoring you. The other two give you no vectors and you choose whether to have RC monitor your climb to the initial altitude or not.

 

If you first waypoint is with 30 nm it assumes you are following a published procedure (No Dep Proc is grayed out) you navigate on your own to cross those waypoints (in the RC plan) within 30 nm with or without RC commanding/monitoring  altitudes. To get more flexibility use the NOTAMS option.

Share this post


Link to post
Share on other sites

Got it ronzie thanks guys!!!

 

I was thinking about using the NOTAMS then RC will not give you and initial alt for takeoff is that correct and you have to contact centre when back on track is that right?

Share this post


Link to post
Share on other sites

With NOTAMS for departure (or arrival) RC becomes advisory. It will still issue commands but will not hold you to them within the zones it is offered. In the case of departure after you declare enroute then the flexibility is gone.

 

For the arrival phase NOTAMS does not loosen the crossing restriction altitudes at 40 nm out from destination.

Share this post


Link to post
Share on other sites

For the arrival phase NOTAMS does not loosen the crossing restriction altitudes at 40 nm out from destination

 

It does if you respond Ctl-6 "Unable to comply" (available with NOTAMS checked, but not with Otto handling comms). Then your told, "do the best can" and I follow the rest of my VNAV descent, picture perfect, every time.  :rolleyes:

Share this post


Link to post
Share on other sites

How do i set it up for the PM to set my transponder?

Also after i get clearance i can no longer hear WX reports? I'm tuned to the ATIS FREQ but nothing happens!

Share this post


Link to post
Share on other sites

Just finished that flight and ATIS didn't tuned even though i had the freq tuned?

 

PFE i could have ATIS 200 nm out

Share this post


Link to post
Share on other sites

PM does not set the transponder, only comms. PM when handed controls gives up all control on approach.

 

You need to request ATIS via the RC menus. However, if you use Active Sky with FSX that ATIS will be incorrect for weather. See pinned topic.

 

Did you tune ATIS on COM1? That is all RC handles.

 

In RC you can request Leave ATC frequency for weather during most phases.

 

ai is not generated that far out (200nm) in FS so runway selection could be meaningless as weather is not the only consideration for runway choice.

Share this post


Link to post
Share on other sites

Ok i'll set it manually once i get it on clearance!

 

Yeh tuned ATIS on comm1 i was trying to play it but got nothing? On PFE i can tune in ATIS and hear it fine...

 

Leaving radar freq for wx report - is that dest report ?

Share this post


Link to post
Share on other sites

 

 


Leaving radar freq for wx report - is that dest report ?

 

If you are close enough, yes.

Share this post


Link to post
Share on other sites

It would be great to have RC weather report at like 100 nm or something just prior to descend!

 

Because in RW pilots have already squared away there RWY and STAR in the FMC and conducted the app brief.

 

But it seems like in RC you have to do it at 50nm and then your work load goes out the roof lol

 

You shouldn't be doing all that while approaching the terminal area.

Where is this pinned topic about ASN and RC

Share this post


Link to post
Share on other sites

I have a question,

 

I'm using a SID with a DP, No Alt Rest. ATC clears me to alt 5000 now my SID has an alt rest. of 6000! Can i climb above 5000 to my SID alt and then hold till 30nm when ATC takes over?

Share this post


Link to post
Share on other sites

From the manual:

 

"No Altitude Restr
Clearance Delivery will assign an initial altitude, and Departure will keep you climbing. However, some published DPs include altitude restrictions. They may be AOA (at or above), AT, or AOB (at or below) altitude instructions. If you see your DP might cause you to remain level at an altitude for some period or until a certain DME, this is the DP feature to use. Use this checkbox if you do not want the RC controller pestering you for not maintaining a continuous rate of climb to your assigned altitude. There will be no lateral “watch-dogging”, there will be no vertical “watch-dogging” from RC until you are at or beyond 30 miles from the departure field."

 

To go above though at 30 nm out you may have to use the NOTAMS feature so RC remains advisory until you declare on-course. Not sure.

Share this post


Link to post
Share on other sites

Yeh thats fine but what i'm saying is, is it fine to climb above ATC initial clearance 5000 to my SID alt 6000?

 

I have to say this is the one for me i have had 8 flights all perfect. Very good product, never goes wrong!

 

I have another question or query lol when i setup my STAR ATC has me turning off my STAR route and when i do come to selecting VIS app i'm way off my STAR slightly to continue it, so i just opt for vectors.

 

Is this normal by the way what else can i do to get around that?

Share this post


Link to post
Share on other sites

Without NOTAMS I'm not sure. 5,000 was the initial altitude and by your 6,000 crossing waypoint RC might have delivered a higher clearance to get there by that time.

 

Do you have a link to that SID? I'd like to see it.

Share this post


Link to post
Share on other sites

It looks like in this case GOSSAM might be on the edge of the 30 nm radius of the RC departure zone with the crossing at 6000 feet.

 

The default RC altitude variation is 200 feet so that will not cover it. I'd turn on NOTAMS if you wish to fly the SID as published so you can climb to 6000 in time.

 

You also are choosing the Without alt. restr. option but which is OK but I am not sure if that allows you to climb above the initial altitude assignment. Do a short trip and try it without NOTAMS. I would use NOTAMS, though, because of the tight turns required and you may need a little relaxing of the departure horizontal limitation of 2 miles to get waypoint credit in RC.

 

Sorry I can't answer directly.

 

By the time you use the can't comply response and get acknowledged it might make it more complex so if necessary I would opt for NOTAMS.

 

Try it without NOTAMS going above the initial altitude of 5000 to make 6,000 by GOSSAM and let us know if RC complains.

 

Thanks.

Share this post


Link to post
Share on other sites

Hi ronzie RC isn't complaining to me. its just i'm not sure if i should climb above 5000 to my SID ALT 6000

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this