F-15 questions: 1]orbit waypoint 2]ILS

[fitness88]

1] Is there a way to lock into a waypoint and prevent it from automatically cycling to the next waypoint as you approach. It would make it easier to use a specific waypoint as a reference point [ie. orbit waypoint 3]?

 

2]It seems that if I didn't pull up all the time, following the glideslope and localizer lines would consistantly fly me into the ground about 50 yards short of the runway. Is there something I am doing wrong or is this a glitch flying F-15 with ILS?

Edited November 29, 2008 by fitness88

[Rhino4]

All the ILSs are like that no matter what plane you use. Try doing an autopilot decent and you will crash 50m short of the runway even though the computer shows you still perfectly on glidescope....

 

As for the waypoint question....not that I can think of...

[Silent Warrior]

About the ILS, I noticed the autopilot likes to automatically deactivate about 50 meters (not sure on feet) off the ground, especially during landing. (In other words, you HAVE to land manually at some point.) Could this be the problem?

[fitness88]

About the ILS, I noticed the autopilot likes to automatically deactivate about 50 meters (not sure on feet) off the ground, especially during landing. (In other words, you HAVE to land manually at some point.) Could this be the problem?

 

Silent Warrior you may be partially correct. Deactivating the ILS short of the runway might work better provided you were accuately on glideslope at the point of going manual. However the ILS glideslope is taking you into the ground for a crash situation too far from the runway for ILS to be any good during an instrument landing. The issue is not serious when conditions are clear but when the weather is bad and visability is very limited [combo of low ceiling and fog on the ground] you would like to be able to count on your instruments.

Brit_Radar_Dude says:

"I already suggested in an earlier post that you try an instrument only landing challenge in near zero visibility, give it a go, it's real fun"

So how do you do it given the inaccuracy of the ILS system?

 

Thank you all for your response.

Edited November 29, 2008 by fitness88

[bear.is.flying]

Reported Problem: Autoland very rough.

 

Resolution: Autoland system not installed in aircraft.

 

For the majority of aircraft, the autopilot is disconnected at 200 ft and the approach and landing is flown manually from there. 200 ft is also called the decision altitude. If you can't see the runway, PAPI, or runway and approach lighting, then you must abort the landing.

[fitness88]

Darkmage:

It's not the actual landing capability I'm referring to, I understand that it is necessary to go manual just before touching down. The problem is with the glideslope being out of calibration and inaccurately low. I wonder if there is some consistancy with the problem that would allow for a constant addition in elevation by a couple of degrees to the GS, therefore making it more reliable and therefore being able to follow it closer to the runway?

Thank you.

Edited November 29, 2008 by fitness88

[fitness88]

ILS actually does work...

 

I spoke with a pilot friend and he advised me of a couple of things, the most important is to get on the glideslope/localizer early and stay there. It then helps to make any correction a minor one especially as you get close to the runway.

Getting the cross from the integrated flight director and the flight path marker all overlaying the cross of the ILS needles at the same time and holding it there WILL give you a perfect approach. It takes practice but I have had a few successes at it. Only once you get it perfect can you feel confortable flying in blind..not there yet.

[Ironhand]

1] Is there a way to lock into a waypoint and prevent it from automatically cycling to the next waypoint as you approach. It would make it easier to use a specific waypoint as a reference point [ie. orbit waypoint 3]?

Not that I've ever found.

 

2]It seems that if I didn't pull up all the time, following the glideslope and localizer lines would consistantly fly me into the ground about 50 yards short of the runway. Is there something I am doing wrong or is this a glitch flying F-15 with ILS?

I was going to say that, while there are issues with some of the sim's airbase ILSs, the problem you are reporting isn't one of them. But, in reading further, I see that you've figured that out. :)

 

Rich

[fitness88]

Ironhand:

I also found a way to lock onto any waypoint so that it doesn't cycle to the next waypoint as you approach. Simply change from NAV mode to any combat mode [ie. press key 3]. The NAV mode indicator will no longer appear in the lower right HUD but the waypoint will still show and will not change unless you maually change it.

Edited November 30, 2008 by fitness88

[fitness88]

followup to ILS

 

I realized what I was doing wrong with ILS landings. I was not using the aircraft datrum in conjunction with the ADI Localizer and glideslope command bars to guide me to the threshold of the runway as you should. What I was doing in error was trying to use only the ILS needles on the HUD [as the command bars] without an aircraft datrum to use as a reference point. The aircraft datrum that is on the HUD is strictly a waterline fixed parallel to the longitudinal axis of the aircraft.

Follow the ADI command bars and you will have a perfect landing every time!

Edited December 3, 2008 by fitness88

[IvanK]

I guess because the ADI bars have a refrence... the aircraft symbol. The HUD bars are not referenced to anything ! They should be referenced to either the waterline symbol or the Velocity vector I would have thought.

[fitness88]

I guess because the ADI bars have a refrence... the aircraft symbol. The HUD bars are not referenced to anything ! They should be referenced to either the waterline symbol or the Velocity vector I would have thought.

 

I couldn't agree more with you. It seemed so logical that I took it for granted that it was the velocity vector on the HUD that I was supposed to reference. All the ILS needles on the HUD do is confirm a good glide slope and localizer position once you have established it first using the ADI.

Having flown Jane's F/A18 since it was released, I got used to using the velocity vector on the HUD to reference.

Well, fly and learn.

Edited December 4, 2008 by fitness88