August 30, 201213 yr I am glad to hear you are starting to get a handle on your problem. I was going to try shooting some ILS approaches to to determine the best airspeed today, but I have a problem. Yesterday installed a free program from the new PCPilot Magazine disk that arrived. Ever since then, FSX locks up immediately after loading a flight. I have to do a hard reboot of the computer. I uninstalled the program, but FSX continued to lock up. After another reboot, the program reinstalled itself. After another uninstall, FSX locked up again. Looking at the files in my computer, I can't find any trace of the program left. I am currently trying to restore my computer back a week to see if that helps. I hope this works as I really don't want to reinstall FSX and all my addons all over again. Bill
August 30, 201213 yr Bill, Have you tried a system restore? I'm not totally sure it would help, but it wouldn't hurt anything. John John Wingold
August 30, 201213 yr John, can you take a screenshot when this happens? Just showing the panel, so that we can see the indications and the active mode of the AP.
August 30, 201213 yr Bill, Have you tried a system restore? I'm not totally sure it would help, but it wouldn't hurt anything. John John, I did try a system restore and it did not help. Bill
August 30, 201213 yr When the ALT light goes out, with APR on, means it has captured the GS. Airspeed should not matter at this point. Try to fly the route I did, in the 172. Bii, what was the program? This is probably getting off-topic. Dave
August 30, 201213 yr That's what I thought Dave. I have not tried it in the 172 and will try that. It will not hold in the Basler, but I can live with that by just juggling throttle and flaps. It really is not a biggie, just something I thought should work a little better. Thanks for everyone's interest/help. John John Wingold
August 30, 201213 yr The program was a demo version of FSFlyingSchoolPro. I can't say for certain it caused my problem but the CTD's did not start until after I installed it and used it yesterday. I am in the middle of running a full scan with my virus protection. Bill
August 30, 201213 yr OK CoolP, I am going to try to show what is happening (never tried this before). If all goes well, Photo 1 will show my initial pre TO settings, Photo 2 will show enroute to my waypoint (where I will begin to turn west to intercept the ILS, Photo 3 will show that turn, Photo 4 will show enroute to intercept and that is all it will take. Rest on next post. John Edit: Didn't work! Trying again: This time, if it works, the first is the intercept with the path, the second is the intercept with the glideslope, and the third is what happens then: BTW, I tried a .cfg rebuild before doing this. John John Wingold
August 31, 201213 yr John, It looks like from your screenshots that you are still making your approach too fast. You are doing 130 KIAS. The manual that comes with the Basler says to fly your approach at 100 KIAS with 1/4 flaps. Your final approach speed should be about 80 KIAS aft setting 1/2 flaps. Once the runway set full flaps but maintain 80 KIAS until touchdown. Give this a try and see if it helps. Bill
August 31, 201213 yr Thanks Bill, When I get back to it tomorrow night, I'll try to rein her in. However, when I flew the 172, it did the same thing even though I was at about 80kts when I intercepted the glideslope. John John Wingold
August 31, 201213 yr John: 1. Looks ok, the GS pointers are up (you are below GS) with APR and ALT lights on. 2. Looks ok, the GS pointers are centered (you are on GS) with ALT light out and Rate of Climb shows capture with start of decent. Agree with Bill, airspeed should be 100 kts with 1/4 flaps. 3. Looks ok, the GS pointers are a little low (you are slightly above GS) and the ROC pointer is showing a 900 ft/min decent to get to it, center the GS pointers, and slow the decent to 450 ft/min. It can't get down to it because you are too fast. In the 172. was the GS pointer up when you made the turn inbound over Bernt Chimney to itercept the LOC? Dave
August 31, 201213 yr Yes Dave, it was. That's the only thing I can't figure out. It seems that it should "lock" as it does with the heading. I have considered doing a "repair" but I don't want to mess up anything else as all seems to work except that. Maybe a line in some .cfg file is corrupt?? Thanks for your continued interest. John John Wingold
August 31, 201213 yr Thanks for posting the screens, John. Based on those, I agree with Dave. It can't get down to it because you are too fast. But I may try to flight some ILS approaches later. If I keep up the speed, I may be able to trigger the same problem. If not, then we could consider some faulty gauges, but I really think the speed is the problem. Must admit, I never flew her on the ILS so for, means with the AP having the plane. So I never saw how the AP reacts to my fuzzy flying. :lol:
August 31, 201213 yr John, I flew two attempts around KSEA. The first one being very, very fast on the approach. The AP commanded the descent as expected but the VS couldn't keep up, so I came in slightly too high. On the next run, I was more in line with the approach speeds and had the flaps out, so there was drag. With that, the AP worked fine, although aiming slightly too low now, later looking better. The last feet are yours either way, so you can correct that. In conclusion, I'd say that the approach speeds are the key, as the folks have said.
August 31, 201213 yr Yes, I agree CoolP. I had intended to try it tonight, but this 69 year old came in from work and sealed his driveway in 95 degree heat and is headed for bed. To be continued, tomorrow, I hope! Thanks for everyone's help. You are the greatest! John Wingold
Create an account or sign in to comment