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.

LOC on A320 NEO ?

Featured Replies

As title what does it mean and when should it be used.? I have googled it but still confused. I can land perfectly ok using ILS, I struggle a bit on visual. 

LOC means localiser (which is the lateral guidance of an ILS approach). Do you mean the LOC button? It‘s used to capture the localiser, but not yet the glideslope (GS).
Use cases:
1) You‘re cleared for the LOC only, and are supposed to stay off the GS until a certain distance / waypoint. In this situation you can only use the LOC button.

2) LOC only approach (no GS available). If you use the APPR button, the A320 might fly an RNAV overlay instead of using the raw data localiser. In this case hitting LOC enables you to actually use the localiser.

3) There is a GS, but it‘s faulty / under maintanance. In this case using the GS could be potentially dangerous and therefore you can not hit the APPR button, but use the LOC button instead.

4) Some (like myself) like to first capture the LOC only and then hit APPR. It feels more natural to me and gives more control over the aircraft in certain situations.

5) When you‘re too high and need to intercepting the glideslop from above, this can lead to dangerous descents and might be hard to control if you use APPR mode (with GS armed). Instead it‘s recommended to use LOC only, descent with VS and wait until the actual GS indicator on the PFD says you‘re now at/below the GS, and only then hit the APPR button. 

That said, if you only fly offline you‘ll practically never have to use LOC, since all its use cases are induced by ATC or real life maintainance stuff.

For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.

You'd use LOC if you've been instructed to join the localizer but not cleared for the ILS approach (probably the most common case these days) or when flying a localizer back course or localizer-only approach (though these are increasingly rare given the prevalence of RNP approaches).

Edit: What @Fiorentoni said!

Edited by martinboehme

  • Author
On 2/27/2024 at 11:37 AM, Fiorentoni said:

LOC means localiser (which is the lateral guidance of an ILS approach). Do you mean the LOC button? It‘s used to capture the localiser, but not yet the glideslope (GS).
Use cases:
1) You‘re cleared for the LOC only, and are supposed to stay off the GS until a certain distance / waypoint. In this situation you can only use the LOC button.

2) LOC only approach (no GS available). If you use the APPR button, the A320 might fly an RNAV overlay instead of using the raw data localiser. In this case hitting LOC enables you to actually use the localiser.

3) There is a GS, but it‘s faulty / under maintanance. In this case using the GS could be potentially dangerous and therefore you can not hit the APPR button, but use the LOC button instead.

4) Some (like myself) like to first capture the LOC only and then hit APPR. It feels more natural to me and gives more control over the aircraft in certain situations.

5) When you‘re too high and need to intercepting the glideslop from above, this can lead to dangerous descents and might be hard to control if you use APPR mode (with GS armed). Instead it‘s recommended to use LOC only, descent with VS and wait until the actual GS indicator on the PFD says you‘re now at/below the GS, and only then hit the APPR button. 

That said, if you only fly offline you‘ll practically never have to use LOC, since all its use cases are induced by ATC or real life maintainance stuff.

Thank you so much for that infomation.

  • Author
On 2/27/2024 at 11:38 AM, martinboehme said:

You'd use LOC if you've been instructed to join the localizer but not cleared for the ILS approach (probably the most common case these days) or when flying a localizer back course or localizer-only approach (though these are increasingly rare given the prevalence of RNP approaches).

Edit: What @Fiorentoni said!

Thank you, much clearer now much appreciation for your response.

LOC is half an ILS 😄  .... the "lefty/righty bit".   GS in the "uppy/downy bit".      LOC + GS = ILS.

There are though some approaches that are LOC only, where the ground equipment includes a localizer but not a glideslope.

Bill 😎
FS2024 • Currently in 'GA mode' : A2A Comanche 2024 & Aerostar • Black Square C208, Bonanzas, Barons, TBM850, Dukes • COWS DA40 & DA42 • FSW Legacy, C24R Sierra & C414 • Echo Falco F8L • FFX HJET, Visionjet and P180 2024 • Got Friends A32 Vixxen • FSReborn Sirius TL3000, Sting S4 and Piper M500 • Flyboy Rans S6S • Skyward DA50RG • SWS Zenith CH701, RV-8, RV-10, RV-14, PC12 • Milviz C310R • Air Foil Labs Bristell B23 
TrackIR • BeyondATC • PMS GTN Payware • RealTurb • Axis & Ohs • FS Realistic Pro
9800X3D • RTX 3080 • 64GB DDR5-6000
NPPL licence holder in the UK

Also, you don't have to arm LOC for an ILS.  Just press APPR.

- Chris

Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD  | 1000 Watt Gold PSU |  Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ)

Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired

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.