Hi Guys - long time no (need to) speak ^_^

 

My last four flights have all ben subject to "missed crossing restriction" and subsequent diversions...

 

The very last flight EGSS - LEAL...about 80 miles out on descent and currently at FL140...given instruction "descend FL120 - I need you level in 30 miles or less"...

 

This time adopted the attitude of a Stuka and pointed the nose down at 3000 fpm - reached FL120 very quickly.

 

After some time, maybe 5 - 10 mins, was informed that I had missed my crossing restriction and was then vecotored away from heading 193 to 095 - a very long way almost to the coast of Ibiza :excl:

 

Then vectored back to LEAL and a landing...

 

After many years of successful RC4 I am reluctant to castigate the software and the only changes made to the system have been the installation of ASNext - its removal and installation of the current update FSX_B5410.

 

Any observations and comments welcome.

 

Still the best add-on and the ONLY one I would not be without :rolleyes:

 

Ken

 

 

Ken,

 

You need to be at the assigned FL 40 miles from the destination airport. If you have a CDU use the FIX option to create a waypoint 41 miles out and then use the arc on the ND as a guide for the required descent rate.

 

You can further enhance this by entering the assigned speed/FL against that waypoint and in VNAV mode the aircraft will do all the hard work for you.

 

Of course, flying in Europe means different transition altitudes and for LEAL it's around 6,000ft. So when you're cleared down to FL120 you should still be on STD pressure, not QNH.

 

ASN won't be a factor. I use it myself.

Don't forget the altitude communications rule to help remember correct altimeter pressure setting:

 

If you are commanded to go to a flight level use standard pressure of 29.92 in or 1013 mb else use the surface pressure as stated by RC controllers for altitudes commanded in feet.

 

Since you were commanded to a flight level, I can't see why ASN would have a part in this since you would be set to the standard pressure. ASN does not couple to your altimeter setting, does it?

 

Make sure you are not using the FS B key to set the altimeter as it is hard coded to a transition altitude of 18,000 feet globally (it is the FAA jurisdiction TA). The RC controller page shows the transition altitude established in its database for each airport. At LEAL it is 6,000 feet. This might be different than current charts.

 

Make sure in descent that you don't go below the commanded altitude in a hasty maneuver. The command stated level flight,not at or below.

Hi Guys ~~~ thanks for your inout to this strange one!

 

On each of these flights I have been at Std pressure of 1013 after passing transition height on departure...

 

I do not use the "B" key at all - I adjust pressure via my GF-46 module (very satisfying!). On each of these flights I have been level at the stated altitude within the 30-miles instructed.

 

As stated - never had these issues previously - maybe I will try the "Unable" option next time and see where that takes me.

 

I really did not suspect ASN - but after a removal and reinstallation you never know

 

Will let you know what progress I make.

 

Ken

It has happened again

 

 

 

LEAL - LEBL (Iberian Tour for Fly UK VA)

 

Set up at LEAL - fuel set, Flt PLn set, WX check on ASN - QNH 1002, Wx brief on RC4 - QNH 1002 which means ASN is talking to RC4 and FSX...set Altimeter at 1002 - note elevation at LEAL is 141 feet amsl (correct according to FSCv9.5.1).

 

Take off... at transition altitude set Std Alt 1013.2 - climb to cruise alt FL250 ~~~ start descent ~~~ at 14,000 feet "Descend FL120 - level in 30 mls or less"...

 

At 67 miles out start descent at 2,000 fpm...reach 12,000 at 62 miles out so well inside the 30 mile requirement.

 

At 39 miles out "Missed crossing restriction - fly heading 095..."

 

At no time have I found the option "Unable"...as detailed in the manual...tried buttons 9, 0 etc.

 

This appears to be a verbal instruction only - on my system.

 

As you will see on your AdvDisp, you have the option to accept or deny these restrictions. If
you acknowledge the restriction, you bought it. Meet it. If you choose “Unable”, the
controller will issue alternate instructions.

 

After flying a very long time on 095 (only a few miles from Palma, Majorca) I cancelled IFR and hand flew the rest of the way.

 

Don't know if this might be relevant - but - in the FSC GPS module that I display on-screen there is a discrepancy when over water for the Altitude and alt AGL

 

For example - at 12,000 feet over the Med, AGL is showing 11,722 feet (-278) - at 4,000 feet still over water, AGL is 3,660 feet (-340)

 

I have checked the options in FSC and see Above Sea Level only enabled. I am pretty sure that over sea I used to have the same altitude reading prior to this recent spate of events!

 

Can't think of anything else...  this is the fifth consecutive flight where this has happened - never before!

 

The good news is that ASN was rock steady throughout - the fiddler has left the building

 

This is a real challenge...

 

Ken

Ken,

 

What aircraft are you flying? Does it have a CDU?

 

On the panel do you have a knob for adjusting altimeter pressure that also incorporates a STD button?

 

What has recently changed on your system that might be the cause of these problems? New aircraft perhaps?

 

I'm sure you meant FL120, not 12,000ft. There is a difference. :wink:

Ray ~~~ aircraft is a freeware POSKY 737-700 with the default FSX-737-800 panel.

 

I use a rack of GF modules and Pressure is adjusted via these - all alterations are reflected in the panel MFD when made. So, yes, Std pressure is confirmed in the GF module and also the MFD.

 

Yes, I meant FL120 (just indicating altitude numbers in the GF- MCPPRO)...

 

The only change has been the ASN uninstall (per instructions) and the installation of the update FSX_B5410.

 

Have just repeated the last flight - after updating the RC database (just in case!).

 

Exactly the same...instructed to descend from cruise FL250 to FL190 then FL120 within 30 miles.

Descent rate set at 2000 fpm - started this descent at 68 miles out - reached FL120 at 46 miles out...

 

At 39 miles out "missed crossing..."

 

The previous flight was a descent from FL140 to FL120 ~~~ this time FL190 to FL120 ~~~ but still achieved well within the 30 mile limit!

 

I also do not see any option to "unable" :wub:

I aborted the flight :angry:

 

My RC4 is v4.3.3845 which has worked flawlessly for years and which I recommend to all and sundry.

 

Maybe I should reinstall RC... :huh:

 

Appreciate your input B)

 

Ken :blush:

Hi!

 

Can confirm I also have had this issue once, after a clean install of FSX and latest version of ASN. I just ignored the instruction to turn, and not long time there after RC was giving me a heading towards the field and transfered me to APP. But have made a couple of flights after that, also to the same airport, and having no problem, so really have no clue what was causing this. The only thing that was a little special at that time was that the actual QNH was very low, around 970 mbrs.

 

By the way, the "unable" option is only there when you flying props I think.

 

Regards 

Johnny

Ken,

 

Two things spring to mind...

 

1) You have changed the default deviation settings specifically the altitude of 300ft. If it was less you might think you're at the right FL but not receive credit for it. Change it to 300 if it's different.

 

2) The altimeter is not set to STD pressure. The best way to check this is to use FSUIPC to display the actual pressure in FS. Read this message in very long thread with someone having the same problem. http://forum.avsim.net/topic/449882-not-at-assigned-altitude/#entry3063311

 

Let me know how you get on. It will be something very simple.

 

 

Don't know if this might be relevant - but - in the FSC GPS module that I display on-screen there is a discrepancy when over water for the Altitude and alt AGL wacko.png

For example - at 12,000 feet over the Med, AGL is showing 11,722 feet (-278) - at 4,000 feet still over water, AGL is 3,660 feet (-340)

I have checked the options in FSC and see Above Sea Level only enabled. I am pretty sure that over sea I used to have the same altitude reading prior to this recent spate of events!

 

When you are flying in an FL zone, the AGL will be different than with your altimeter set to standard pressure. If you are in an FL zone below 18,000 feet and you via ctrl-z bring it up on the FS display, it will show your QNH, I believe. I don't think the FS altitude display (ctrl-z) respects your altimeter setting - not sure.

 

The thread Ray refers to has an fsuipc debug setting that will show a multiple of what the altimeter pressure is set at in the FS title bar.

 

Your reading AGL difference in FSC at FL120 is typical difference between surface pressure altimeter (QNH) and standard pressure.

 

A test you might run is to fly FS with the clear weather theme, ASN off. That sets your surface pressure to 29.92/1013, You can then check against your FSC AGL reading over water at FL120 and at 4,000 feet. I would hope that FSC recognizes sea level over water and not the ground layer under it in its terrain database.

Ray ~~~ still a work in progress...

 

I did have different deviation settings in RC: altitude was at 500 ft which I had set due to the ups and downs caused by REX weather engine.

 

I have now changed back to the default "300" as I am now using ASNext.

 

I have checked the sim on ground at start-up which is at LeedsBradford - alt 680ft.

When I boot-up then switch on the avionics the altimeter is showing 1000mb / 29.53" with 680 feet on the display.

 

Pressing the button assigned to STD changes the setting to 1013.2mb / 29.2" with an altitude of 1080 ft so it would seem that the buttons are working as they should.

 

I also set the FSUIPC Logging Tab as you described - it says that up to four items can be displayed...

 

I already had an entry for checking the virtual memory (just in case!).

Entering your details (OK) did not display on the bar - not even after re-booting FSX.

I deleted my previous entry and substituted yours and the number came up as 16002 which is as near as makes no difference the 1000mb as shown on my GF unit and the panel.

 

I have not yet made a flight to check possible variations at altitude but I suspect that will not be an issue (?).

 

The aircraft I am using - almost every flight - is a POSKY 737-700 with panel aliased to the default 737-800.

 

I have used this configuration for a few years and everything worked fine!

 

I do note that my FSUIPC is behind the times at v4.931 so I will update that today.

 

Nothing else to report but will stay in touch.

Many thanks for your input...do not wish to oustay my welcome

 

Ken

I did have different deviation settings in RC: altitude was at 500 ft which I had set due to the ups and downs caused by REX weather engine.I have now changed back to the default "300" as I am now using ASNext.

 

That's fine. If anything 500 would be more tolerant of any altitude discrepancy. We can disregard that as a possible cause.

 

I have checked the sim on ground at start-up which is at LeedsBradford - alt 680ft. When I boot-up then switch on the avionics the altimeter is showing 1000mb / 29.53" with 680 feet on the display. Pressing the button assigned to STD changes the setting to 1013.2mb / 29.2" with an altitude of 1080 ft so it would seem that the buttons are working as they should.

 

 

Can you please monitor that offset when you press STD (airborne or not) and confirm that when divided by 16 it returns 1013.25? That remains the most likely reason you're getting yelled at for not being at the correct FL.

 

I also set the FSUIPC Logging Tab as you described - it says that up to four items can be displayed...

I deleted my previous entry and substituted yours and the number came up as 16002 which is as near as makes no difference the 1000mb as shown on my GF unit and the panel.

 

 

I think it needs exclusive access so you have to temporarily disable other logging requests. 16002/16 is 1000.125 so that looks okay.

 

I have not yet made a flight to check possible variations at altitude but I suspect that will not be an issue (?).

 

 

That is the 64 million dollar question. I've lost count of the number of flights I've taken with RC and the 40 mile / FL110 or FL120 rule is always okay with me so I'm struggling to understand why you're getting this problem now.

 

 

The aircraft I am using - almost every flight - is a POSKY 737-700 with panel aliased to the default 737-800. I have used this configuration for a few years and everything worked fine!

 

 

But have you been having the problem with RC for years too? Or are you a new user? Because you don't have a FMC with that aircraft you have no way of entering a waypoint 40 miles from the arrival airport. In the RC display the second line should show how far you are from the airport once you contact Approach. Does that show you to be 40 miles away?

 

Can you supply a flight plan that results in this problem? I'll see how I get on. I'd like to get to the bottom of this not just for you but for others who might have the same problem. The help I gave to the other user never resolved the problem so I felt like I had wasted my time with him.

Sorted :wub:

 

First I will respond to your questions above...

 

When I press STD on either the panel or my GF module it does return 1013.2 ~~~

 

I have been using RC for years (7 or 8) - never had any issues (apart from learning not to change altimeter when first told and wait for "descend TO **** feet")

 

The RC display shows 40 miles then at 39 came the words

 

Only been experiencing this issue for a few days...

 

So...I deleted the aircraft - rebooted the PC - installed the aircraft again ~~ same.

 

Installed FSUIPC (update) 4.938f ~~~ same.

 

Stern measures...recovered a back-up of RC from my "vaults" ~~~ took ages...

 

But it all works again  

 

Now ~~~ I made this last trial flight with ASN disabled but at FSX start-up it still showed Alt as 1000mb but at correct height (141) at LEAL.

 

I would have thought that with NO weather the standard 1013.2 would have been showing???

 

On running RC and taking the WX brief he also told me QNH 1000...

 

I am wondering if saving a flight for start-up with Std QNH set at 1013.2 at 680 feet at LBA would be a safe bet although I have not been able to set that up as yet - can't seem to make it work (is ASN still making the rules here despite being "disabled"?

 

Your comments most welcome but thanks anyway for your assistance and patience :blush:

 

Ken

Ken,

 

I'm pleased you believe the problem is resolved but I'm mystified what caused it in the first place.

 

When you load a previously saved flight it may contains weather. The easiest way to check is to examine the weather details in FSX and especially what pressure is set. Don't assume it's 1013.2.

 

When you said "When I press STD on either the panel or my GF module it does return 1013.2 ~~~" how are you checking that? From the altimeter reading or by reading the offset and dividing it by 16? I'd be happier if you did the latter so I know what is set 'internally' in FSX.

 

Strange that you've only recently been having this problem. What has changed to cause it?

 

I often load FSX using a saved flight. I then load ASN and once the weather has been loaded start RC, load a plan and tune in the ATIS. I then set the altimeter using the QNH in that broadcast. What was previously set in the saved flight is overwritten. Once cleared to a FL I hit STD and only change back to QNH when cleared to an altitude. Sounds like you are doing the same.

 

Do your test flight. One in the UK would be a good test with pressure currently around 1035hPa. That will result in a big difference between QNH and STD pressure.

I make sure the default flight and my saved parked flights in FS9 are set to the clear weather theme. I use AS6.5 and it requires that. I see the correct airport surface altitude with the altimeter set to standard pressure. If you look at the fsuipc.log in your modules folder it will state when the clear all weather command is sent to fsuipc. (I use the default Baron as the standard complex aircraft for the default flight which initializes the FS various environment engines even when the menus are displayed, again showed by the fsuipc.log. Often add-ons like my FS9 PMDG 737NG series state to load the Cessna first before loading the B737. This default flight is also what get first loaded when you create a flight so that is another reason to set it up that way. This avoids having to manually load a flight prior to your desired aircraft. It should be an FS default complex aircraft used.) When AS is activated it then sets up the correct weather for your departure. (In FS9 after AS completes writing the weather I need to command Refresh AI to reset ai patterns for the new written weather which also refreshes the RC ATIS report. In FSX incrementing the time by one minute will do this.)

 

Also remember in the FS setup to disable FS dynamic weather progression when using AS so they do not conflict.

 

Regarding ATIS especially for arrival, by default fsuipc4 recognizes if AS (in the FSX environment) is used. It then uses the expected AS arrival METAR read from AS. It does not affect the AS influenced destination weather, just the RC ATIS report. This is necessary because of the Global weather requirement imposed by SimConnect with DWC enabled. Please see the pinned topic on this. One of our beta testers worked with Pete Dowson on this. He also uses the destination weather lock to avoid the destination weather changing due to the weather at your aircraft position and has had better stability of ai patterns at destination with RC assigning the correct matching runway.

 

I mention this because you may see a variation between other pressure reporting and what RC reports for destination. This does not apply to your enroute/cruise phase but I thought it might apply to your mentioning differences close to your destination airport.