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.

EDDS (Stuttgart) - ILS25 - Approach

Featured Replies

Hello experts,

i have trouble flying the mentioned approach:

spacer.png

When i come from the LBU VOR @5000 fts then i slow down and descend to LBU and turn to UNSER @4000 fts, then i can not continue the approach (Autoland). Within seconds im above the Glideslope and the aircraft stays on 4000 and flys towards the runway with 252 degrees.

@Fenix A320:  Both Autopilots on, G/S and LOC is captured, APP activated - the aircraft stays on 4000 fts.

@PMDG 737: G/S and LOC captured, both radios set to 109.9, both CMDs are on, both FDs are on, everything seems good - but as well the aircraft flys 252 degrees and stays on 4000 fts.

 

Can anybody fly this approach with autoland and explain me, what i am doing wrong there?

 

 

Regards, Jan Ast

Win 11 PC | Ryzen 7800 X3D | RTX 5080 | LG 42 C2
Cockpit 😉 | TrackIR 5 | Octavia IFR-1 | Virpil Alpha on WarBRD, Virpil CM3 Throttle, Virpil Sharka Control Panel | Honeycomb Alpha & Bravo | TM TPM Rudder

  • Replies 32
  • Views 5.8k
  • Created
  • Last Reply

If you are at 4,000 at UNSER and you are above the glideslope, the approach is wrong. Trying descending to 3500, or even 3000, as long as you are below the GS, and you should be fine. In addtion make sure you activated the approach mode on the Performance page. 

 

 

 

It may be an issue with the navdata or the scenery where the GS is set too high. You can’t descend below 4000’ until reaching UNSER according to the plate so definitely something is screwy if you’re too high this point. As bob says, maybe try a (not allowed IRL) descent before UNSER and see if that helps, but don’t get too low. The airport elevation is well above sea level, so at 3500’ you’re only actually 2400’ above the ground. 

The only thing I can think of that doesn't involve the scenery being screwy, is that you actually haven't captured the glide scope (despite thinking you have) and that you still have 4000 dialed in on the MCP. That would produce the result you describe. Are you sure the G/S is properly announciated as captured and not just armed?

 

 

Have you set your pressure correctly QNH? If your pressure is wrong, your altitude is wrong. You must approach below the glide slope for ILS mode to work.

Edited by Silicus

Most of what is said on the Internet may be the same thing they shovel on the regular basis at the local barn.

  • Author

The approach mode in the Airbus is on, yes.

Yes, pressures where right. I have flown the approach no at least 8 times with both aircraft, always the same effect.

Is it correct that in both aircraft, the final approach / autoland only starts when i approach the glideslope from below, else the aircraft stays on the 4000 fts?

That would be the only reason why both aircraft stay on their altitude, because i am already too high at UNSER with 4000 fts.

Edited by Paladin2005

Regards, Jan Ast

Win 11 PC | Ryzen 7800 X3D | RTX 5080 | LG 42 C2
Cockpit 😉 | TrackIR 5 | Octavia IFR-1 | Virpil Alpha on WarBRD, Virpil CM3 Throttle, Virpil Sharka Control Panel | Honeycomb Alpha & Bravo | TM TPM Rudder

In this approach you shoul set APPR ( Airbus ) as you approach LBU @ 4000'

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

1 minute ago, Paladin2005 said:

The approach mode in the Airbus is on, yes.

 

Is it correct that in both aircraft, the final approach / autoland only starts when i approach the glideslope from below, else the aircraft stays on the 4000 fts?

That would be the only reason why both aircraft stay on their altitude, because i am already too high at UNSER with 4000 fts.

I don't know the Airbus well enough, but in the 737 G/S should be highlighted in green on the PFD. If it's still in white then G/S is only armed but not captured. Can you verify that G/S is highlighted in green? If it is and you still won't descend then there's something screwy going on. Otherwise it simply means haven't captured the glide scope, for whatever reason.

 

 

  • Author

@andreh i will try again in the 737 and look specifically for that.

Regards, Jan Ast

Win 11 PC | Ryzen 7800 X3D | RTX 5080 | LG 42 C2
Cockpit 😉 | TrackIR 5 | Octavia IFR-1 | Virpil Alpha on WarBRD, Virpil CM3 Throttle, Virpil Sharka Control Panel | Honeycomb Alpha & Bravo | TM TPM Rudder

3 minutes ago, Paladin2005 said:

@andreh i will try again in the 737 and look specifically for that.

Good luck. Someone else also noted the baro pressure. If it's not set correctly you might actually be just a bit too high at UNSER and therefore the G/S will not capture.

 

 

According to the chart the G/S intercept point is at the 3.9DME fix at 2410ft. Sounds like you have to manually descend from 4000ft after UNSER in order to properly intercept the G/S. Try that. 

Esteban J. Aldarondo \\ CFI, CFII, MEI, Gold Seal \\ ATP \\ CL-65

System: Windows 10 Pro x64 \\ Intel i7-5930K 3.5Ghz \\ GeForce GTX 2080Ti \\ System RAM 48GB DDR4

I just tried flying the ILS R25 at EDDS in the C414AW. The autopilot intercepted the GS at UNSER at 4000ft and flew the approach without any issues. This approach has a 3 degree GS which at UNSER is right at 4000ft. Maybe there is some issue wrt the autoland type of approach which, of course, the C414AW does not do.

Al

Make sure all Assists are disabled !!

MSI Tomahawk Z790, I7-13700K, DDR5 6000mhz, MSI 4090, 3x SSD 980 PRO, Corsair 360 Liguid CPU cooler, Corsair H1200V2 power.

First of all the ordinal post is a bit confusing. Autoland is mentioned a couple of times, but the only difference between a regular ILS approach and is in autoland, once on the GS, both Autopilot switches are engaged. So the issue is that the autopilot won't lock onto the GS.  Just some ideas, is this an add on airport scenery where the GS in the scenery is not working properly?   Have you tried flying this approach with any default aircraft, and if so, does the GS work? If it does, there is something that you are not setting up correctly in the Fenix and 737. 

 

Anyway, I am on a flight now in the Fenix A 320 from LDZA to EDDS. Landing on Rwy 25 Star TEKS1W    . Will report results. 

Edited by Bobsk8

 

 

 

I just flew the approach into EDDS, intercepted GS approaching UNSER, and tracked to ;landing perfectly. 

 

 

dYki8Ot.png

 

 

 

Archived

This topic is now archived and is closed to further replies.

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.