Charleston to Boston (4R) Worked OK Rick

[DAVIDSTRAKA]

Thought I would thrown in the approach plate also.

 

 

Leaving Charleston

 

 

Boston Approach 4R. Everything lined up fine.

 

 

 

 

 

 

 

Not sure what the issue is. Is it the localizer, wrong freq, glideslope?

[Downwind66]

I think it is none of the above. I can fly Charleston to JFK, land there. Takeoff to Boston, ILS works fine. If I try the flight non-stop Charleston to Boston, I can pick up the localizer, the aircraft heading to Boston, never recognizes the glide scope????? And yes, not too high to miss it. 1700' just as your approach plate indicates. Frequency 110.30. I just don't know. I'll try it again soon with other aircraft.

[DAVIDSTRAKA]

I think it is none of the above. I can fly Charleston to JFK, land there. Takeoff to Boston, ILS works fine. If I try the flight non-stop Charleston to Boston, I can pick up the localizer, the aircraft heading to Boston, never recognizes the glide scope????? And yes, not too high to miss it. 1700' just as your approach plate indicates. Frequency 110.30. I just don't know. I'll try it again soon with other aircraft.

 

 

That is odd. Different aircraft do the same thing?

[flightsimg]

Thanks for that second Boston approach! I like it :):)

The trouble should come from a long flight. By the end of it your PC memory is full and can't manage the ILS entirely, I think

[Downwind66]

Gerard - That is what I am thinking. I can fly into JFK, takeoff again for the 165 mile leg eastbound and it works fine! I think my computer just runs out of breath and needs a quick stop! I just tried it again with the Boeing 767, it catches the localizer, it tracks inbound and the ball on the glide scope drops and when it should disengage the autopilot's altitude, it doesn't disengage!

 

Oh, forgot to mention. I can fly the leg from Charleston to JFK and the ILS there is fine, no Problemo!

 

Rick :cool:

Edited July 7, 2019 by Downwind66

[NMLW]

A fine approach and landing at bean town David. :cool: :cool:

[DAVIDSTRAKA]

A fine approach and landing at bean town David. :cool: :cool:

 

Thanks Larry!

[DAVIDSTRAKA]

Gerard - That is what I am thinking. I can fly into JFK, takeoff again for the 165 mile leg eastbound and it works fine! I think my computer just runs out of breath and needs a quick stop! I just tried it again with the Boeing 767, it catches the localizer, it tracks inbound and the ball on the glide scope drops and when it should disengage the autopilot's altitude, it doesn't disengage!

 

Oh, forgot to mention. I can fly the leg from Charleston to JFK and the ILS there is fine, no Problemo!

 

Rick :cool:

 

I’ve noticed that when I disengage the autopilot, I have to disengage the auto throttle separately.

[flightsimg]

Keep with my idea it's a question of PC performance. Checked numerous times that the ILS/slope let to desire at the arrival of a flight and, when checking that with a restarted FSX, things went smoothly

The other possibility with a ILS/slope troubes resides with the tuning of those values with the free airedit, if I remember well (opening the .air file for a given plane); maybe also in the .cfg

[kalizzi]

Is that a 717? I flew on board Air Tran years ago from Atlanta Hartsfield to Newark New Jersey and it was a 717. Just like a beefed up DC-9. Nice set of shots David.

[DAVIDSTRAKA]

Is that a 717? I flew on board Air Tran years ago from Atlanta Hartsfield to Newark New Jersey and it was a 717. Just like a beefed up DC-9. Nice set of shots David.

 

Yep, 717. Thanks!