Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Intercepting ILS speed

Featured Replies

What speed do you intercept with POSKY PSS 777-200 merge to insure it doesn't lose too much altitude then has to regains so climbs to much etc etc etc, does the speed affect ILS LOC capture? With or without landing gear down and what flap settings? If you use PSS flaps or POSKY flaps section in the merge does it affect the ILS or overall performance of the aircraft, eg at low speed the flap sections of PSS or POSKY may affect the speed and throttle setting etc...Cheers.

The speed will depend on your landing weight, and I think the angle should be +2.5 for -500fpm (I think that's the usual ILS descend rate). So you got to set your speed accordingly. But PSS has the FMS, which should calculate that correctly for you.Landing gear usually comes out when you intercept glideslope and I believe above 2500ft.What flap depends on what speed you choose for landing, also a thing you can set in FMS in the 777.And you should use PSS characteristics (flaps, engine, etc) within the merge, my experience with merges was always halfway, that is why I am not using them. Only contact points, lights and such from the POSKY...

You should fly a speed according to your current flap setting. Different speeds are given for different sets of flaps (due to the lift variation flaps make). Since you have FMS (and you're flying a complex add-on), the speed tape on your 777 should have "speed bugs", which give you information on the speed to fly on which flap setting. Try to use the speed information on the speed tape so you don't come in too fast.As for the landing gear bit, on the MD-80, you usually lower the gear when the GS needle is one dot (or half a dot) above glide slope and once you set landing flaps you perform the landing checklist.

Ed Ocampo
Staff Reviewer
AVSIM Online
[email protected]

pilot.gif
Fly DC Jets

Depending on the aircraft you typically go into your final landing configuration about 7 miles out from the threshold. Some approaches have an outer marker at this point. It is at this point that if ATC is giving you speeds above your landing speed for expediting traffic that you can dictate your landing speed and slow down. RC will not do this so not to worry but AI tend to land fast. Some pilots will wait until about five miles out before dropping gear.The turbo-prop or jet airliners typically like to have gear down with intended flaps so maximum drag is available at this point to keep turbine engines spooled up in case a go-around is needed. This decreases the delay in getting up to maximum take-off power.Maybe some version of RC will say maintain 180 knots until the outer marker (or distance from the threshold).

  • Author

Thx for the feedback! Do we maintain an altitude before establishing or should we be descending to establish, ie intercept LOC while still descending to the given ATC altitude?Cheers

Thx for the feedback! Do we maintain an altitude before establishing or should we be descending to establish, ie intercept LOC while still descending to the given ATC altitude?Cheers
Maintain altitude ,and be at an altitude that puts you below the Glideslope. Then intercept the Localizer first, get established on the Localizer , then grab the glideslope.So you want to do this far enough out so to space out the distance between grabbing the localizer then the glideslope. I'm usually about 3000 ftabove the airport elevation and 13 nm or more.For the Localizer intercept speed stay under 200 kts, and intercept at a 30 degree angle or less and you should be fine (set flaps accordingly).The FMC calculated speed mentioned is actually the approach speed (or Vref) which is the speed you fly when you are fully established and configuredon the approach. You can be higher than that speed on initial Localizer intercept especially if you intercept the localizer earlier like 15-20 nm out. ATCmay also require you to fly a speed higher than the FMC approach speed to maintain spacing until you reach the Final approach Fix.Regards.Ernie.
ea_avsim_sig.jpg
Thx for the feedback! Do we maintain an altitude before establishing or should we be descending to establish, ie intercept LOC while still descending to the given ATC altitude?Cheers
If under ATC instructions you will normally be in level flight when instructed to fly a intercept heading, although it is possible you will still be descending. At the point of LOC intercept and following that G/S capture, you should be in level flight. If using A/P you will ant to be in ALT HLD and HDG SEL, with LOC armed. When LOC captured press APP which arms the G/S.Speed will depend on ATC instructions and a/c weight, but in a 737 I usually aim for 180 KIAS when on intercept and 160 KIAS when G/S captured. Go to VREF+ speed and landing config between 7-4 miles outPeter

Peter Schluter

One additional caution specifically for FS default scenery is that the LOC/ILS properties out of the box have their backcourse enabled. If both ends of a runway share the same frequency in most cases you will see the incorrect LOC/ILS until about a degree or two off center line. Insure you are receiving the correct code and don't arm LOC or APP until you verify it. You can disable the backcourse transmission in these instances with AFCAD or better yet ADE9X.I watch the course asnd GS (if present) indicators and use HDG SEL to turn inbound on the LOC and after ident is established turn on APP. This especially avoids a false glide slope from the incorrect navaid.Regarding approach navigation be aware that sometimes due to terrain radar blocking you will be given vectors to an appropriate IAF (Initial Approach Fix) and then be cleared to navigate on your own according to the published procedure following altitude and heading guidance from this.

  • Author

Ok, cheers thx for the feedback. Why i'm asking is because in the POSKY PSS merge when it goes to establish, the plane establishes but while turning it loses altitude. Then it tries to get back to the set altitude by climbing but climbs too much etc and after a series of these it gets to the altitude and gets onto the Glideslope. It's really fustrating. Does this ever happen to your planes? This happens when i am at level flight and intercepting. I have done alot of flights with the merge (done ILS approaches too) and this almost always happens. So if i descend while i intercept and maybe set a higher speed and intercept with less of an angle maybe the ILS will work fine?

Ok, cheers thx for the feedback. Why i'm asking is because in the POSKY PSS merge when it goes to establish, the plane establishes but while turning it loses altitude. Then it tries to get back to the set altitude by climbing but climbs too much etc and after a series of these it gets to the altitude and gets onto the Glideslope. It's really fustrating.
Hi, this is caused by the (apparantly crappy) flight model.When intercepting the G/S you should fly level at the altitude published on the approach chart.Not entirely true... If it is a CDFA approach (Constant Descent Final Approach) you intercept the G/S during descent.But it requires a good planning.In a 737 I usually fly these speeds but will do for 777 too (flap setting may vary):Initial Approach : 210-230kts depening on weight (Clean config)Vectors to final : 180kts, flaps 5Established on Loc, 1 dot above G/S : 160kts, gear down, flaps 15At O/M or 1.500ft AGL : Vapp + Landing flaps EDIT:I uploaded the ILS profile for a 777:777-ILSProfile.gif

Location: Vleuten, The Netherlands, 17.3dme SPL 108.40 | Simulator: FS2024
System: AMD 7800X3D - Gigabyte X670 - RTX 4090 - 64GB DDR5 - 2 x 2TB SSD - 32" 1440p Display - Windows 11 Pro

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.