Hey Guys-I've had this happen several times and can't seem to see a common thread to the problem. I'll have everything set up for an approach, with the proper speed per the FMC, gear down, flaps down, both A/Ps on, and I'll be coming down the glideslope like I'm on a rail. Then, the sim will seem to "jump" or "wiggle" and the next thing I know the plane is climbing away (or remaining at a constant altitude)from the glideslope and the approach has disconnected. Manual takeover is then initiated.This doesn't happen all the time, so I can't seem to figure out what is going on. Any ideas?On a different problem, I was flying from Houston (KIAH) to Austin (KAUS) with everything except landing runway set up on the FMS. When I was assigned a landing runway, I went to the Arrival page for Austin to set up the runway and, while they (all the runways) were all listed, when I went to select the assigned runway I received a "Program Error" message in the scratchpad area. That is exactly what it said. No runway was selectable. I could still get speed references for the various flap settings at landing, all other pages seemed to be OK, but I couldn't select the runway. What's up with this?I'm sure there must be "operator error" in here somewhere!Thanks-Mike Smith

I had exactly the same occurence last night flying from LEST - EGKK (SAntiago - Gatwick).I resolved the problem by going to the rte page and reselecting EGKK as the destination, then all the runways and stars were available again.... very strange.

I also had this problem, but it occured after having saved a flightplan with FS Build in the PMDG .rte format. So practically I alreadu had the departure and landing runway selected upon activating the flight plan from the COROUTE voice in the FMC.As I approached my destination I decide to change the landing runway and that's when I got the Program Error in the scratch pad everytime I selected the arrival page.Maybe it has something to do with loading saved flightplans that already include dep/arr runways. Don't know for sure though.Regards,Bjorn

Mike,Did you get an answer to your issue about the ILS approach "disconnecting"?....I'm doing a search because I'm having a similar problem with APP disconnecting about 10 miles out, and I can't re-establish it and end up flying over the theshold at about 1000 feet!CheersTim

Tim, What exactly do you mean when you say that APP disconects??[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/forum/betaimg.jpgAMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

Randy,Firstly a disclaimer. I take full responsibility for this being my lack of knowledge.I'm setting myself up for an approach a la default a/c and following ATC IFR commands, the glideslope comes "alive" and I click on the APP button. (I still havent' figured out the value of the VOR/LOC button but that's a story for another day).The plane follows the ILS until I'm about 5 miles out, then I notice in a mad panic the height isn't dropping, and the APP is no longer lit. In the ensuing mess, I've flown over the threshold at about 1000ft.I've experimented with CMD A and B both pressed, but am finding that things disconnect without me noticing and re-establishing them in the time left is not working.....I went searching for answers (impressed?) and came across a help sheet from August last year that I'll have a crack at tonight, and see where things go.Whilst you're here though, there's a comment on it that says:"Set the Inbound Course on the MCP"Does this refer to the CRS button on the left? If so, I fail to understand what value this button has. It seemed redundant in the default a/c, and doesn't seem to affect the autoflight system on the occasional successful landing I have had.The fun and games continue, and what fun it is!CheersTim