aircraft goes upwards fastwhen using 'APP' button

[Nav]

I think I'm under the glideslope when I select APP...

satz, there's no need for guesswork. the instruments will tell you whether you're above or below it. See the first screenshot in that tute linked to in Post 4 above. The big instrument top left (the Attitude Indicator) tells you whether or not you're below the glideslope - the one below (Horizontal Situation Indicator) tells you where you are relative to the runway line.

That's in the 737 - in smaller aircraft like the Cessnas, the corresponding instrument just has crosshairs - but the principle is the same.

I suspect that what MAY be happening is that you're not getting down to the specified height in good time - and are therefore pressing 'APP' while you're still descending. So the 'descent' command is interfering with the 'approach' command, and 'something's gotta give.'

Best thing is to begin your descent in good time - remember that aeroplanes in a normal descent usually travel three miles forward for every thousand feet down - so if you're flying an airliner at 30,000 feet, for example, you should start your descent not later than 90 miles out. You should aim to be down to the specified approach height, levelled out, and approaching the glidepath at a sensible angle and at reasonable speed, not less than 10 miles out - and BEFORE you press 'APP.'

[Romflyer]

I too have experienced this issue of the autopilot racing upward when you hit the APPR button.......it has happened for me (couple of times) at CYVR Vancouver, I'm pretty sure that as mentioned above the problem is not being below the glideslope before you intercept it, in the case for CYVR, 08L and 26R both use the same ILS frequency 110.55, so when you engage the APPR above the glideslope the autopilot picks up the glideslope from the opposite runway and tries to capture it  :o
Since I figured this out a couple of years ago I always sneak up on the glidslope from level flight and fly into the glideslope from below, and I've never had the problem again  8-)

As mentioned earlier, the biggest favour you can do yourself on this topic is go read Nav's excellent tutorial.

[satz]

hi all

I'm definetely below the glideslope before activating 'APP" button.

I tried again this morning.

For example I descended to 2000 when asked to intercept the localiser (or whatever the words they say!)...  and then selected APP.

After a little while the ALT light switched off (as normal), but the ac starts climbing at 40 degrees nose up to something around 8000 feet, stalling, etc

and this is within a few miles of the airport.

I just can't work out what goes wrong.  I saved the flight before selecting "APP" so I could try it out and it happened each time.  This time I was using an add-on Kai Tak airport (The one done by the Nine Dragons team)

It really ruins a flight for me, enough to almost make me go back to 2002....(except I love the weather in 04!)

Do you think something is wrong with my install?  (btw, I installed the 9.1 official patch just after first installing the game)


Satz

[HoratioWondersocks]

Perhaps you could send a screenshot of your panel just as you are about to hit APP just after as well.You never now somebody may spot something you could be doing wrong.
PS i bet there is nothing wrong with your FS9 installation either.There is almost certainly a simple  reason for the errant behaviour you describe .When i first started to learn ILS approaches i used to have all sorts of problems with things going wrong LSZH i seem to remember caused me some grief with approaches (doesn't now)usually it was forgetting to switch from GPS to NAV and suchlike that caused much mountain eating and earth sampling.
Don't give up on FS9 you will only regret it.
cheers Andy
PS don't ask me how you take and post screenshots  i can't do it myself.Its probably easy to do though.
PPS you may want to check out Pete (fsuipc)Dowsons  site there you can download a useful little utility that automatically saves your flight at predetermined intervals this would allow you to go back to your approach and try again if you get it wrong without having to go the whole irritating process of a new flight  each time.
Andy

[Fozzer]

...also...

Make sure you are on the correct glide scope for the approved runway heading!

Some runways only have one ILS glide scope for one end only of the runway....(make sure you pick the right end)!

Other runways have a glide scope at BOTH ends of the runway....BUT only ONE ILS Frequency. One of them will be a "Back-Course" heading frequency....which often turns you round...a common confusion with "FS Navigator"!

ATIS will inform you which end of the runway is in operation.

Practice ILS approaches and landings using the Default Cessna 172 and the Default Beech Baron 58, using their excellent Bendix-King Radio Stacks*......!

Providing I contact ATIS for the latest Airport Information in advance, I have no problems in carrying out all the correct procedures when approaching the Airfield.

Paul...G-BPLF...FS 2004...FS Navigator... 8-)...!

* ......and you are having a problem with a particular Airfield layout.......!

[Nav]

[quote]I just can't work out what goes wrong.

[satz]

hi nav

the problem happens to me even at approaches to some runways at KLAX and other inbuilt airports.


Satz

[HoratioWondersocks]

Could this be  a trim problem?
What about your use of the NAv switch?you only mention selecting APP.
When i am doing an ILS approach i first enter the runway ils frequency into my NAV1 (and 2 usually)I click the little light in the radio stack for audio,when i hear the Morse identifier of the runway i turn on my NAV button(autopilot)when i am given directions to the airport i initially let  NAV   turn me onto the right course(not APP)when i am approaching and I see the vertical bar(i think it represents the rnwy hdg ...Apoogies i cant remember the name of the instrument but its the one that tells you if you are to high or low on the glidescope)when i see that bar move across until its central then I will select the APP button.
PS your trim wheel hasn't somehow got stuck in a climb position?has it
Andy