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.

Maybe I'm not understanding the app hold button?

Featured Replies

 

One other "fine point:" After you press Approach, some aircraft will start to descend on the glideslope even if they are not yet lined up with the runway

There is a specific option in the PMDG NGX in the aircraft settings that allows you to "allow" or "deny" this particular behavior.

 

In general I never arm approach before arming and capturing the localizer. Its just a good habit in my mind, and if I'm on a precision approach and I don't have the time or attention to deal with separately monitoring LOC capture then G/S capture, I figure I'm doing something wrong with my approach because by the time you're at this point you shouldn't have much left to organize. If you're too high or too fast then you screwed up about 15 to 20 nm farther back. Thats my opinion though. With the NGX though I do use FS2Crew which makes the workload much more manageable and realistic. For those who opt for the cowboy, do it all yourself approach (which is admirable in its own way ;) ) I can see things being a bit more hectic.

 

 

As for the specific procedure mentioned by OP -

ATC says approach 15 miles from the marker fly heading X

When ATC says this does it mean maintain current heading and when 15 DME turn to the assigned heading? I'm just curious since I'm not an expert on correct ATC nomenclature.

  • Replies 36
  • Views 11k
  • Created
  • Last Reply

Top Posters In This Topic

I've never used APP hold before a few days ago, and have only a vague understanding of what it does.

 

Just fly the test flight step-by-step to "see" the ILS work and what the switches do. Let us know which step you don't understand.

 

Dave

I know the gps/nav switch has been mentioned already but here's what I'm guessing happened ...

 

You were on a flight plan, navigating with GPS, and they cleared you for the approach.  You forgot to swap to NAV and did or didn't have the ILS freq tuned in.

 

I'm also curious to know what happened...

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

As for the specific procedure mentioned by OP -

 

Quote

 

ATC says approach 15 miles from the marker fly heading X

 

 

When ATC says this does it mean maintain current heading and when 15 DME turn to the assigned heading? I'm just curious since I'm not an expert on correct ATC nomenclature.

 

 

Not sure I've heard this particular formulation in FS X ATC, but I would guess "15 miles from the marker" is for pilot's information, and the heading would be the intercept heading for getting to the extended runway line.  I don't think it would imply "maintain current heading" until a certain point.  I think it means turn to heading x right now.  I'm more used to "fly xxx, cleared for the approach, contact tower on [freq." or something to that effect. 

 

Mike

 

                    bUmq4nJ.jpg?2

 

  • Author

I did the flight, and the only thing that happens is I come down rather hard, I waited until I was more or less crossing the runway before hitting APP, and it worked like a charm, thank you for all the help.

Congratulations - I think :unsure: .  Do you mean that you captured the approach as expected and you waited until you crossed the end of the runway to disengage?  Remember that you should disengage at minimums so you can be prepared to go around if needed and otherwise get youself into a landing configuration - try to touch down at something significantly less than 500 fpm (I shoot for ~ 100 fpm - easier in the Baron 58 than a 737-800).  If you let the autopilot take you all the way down you will be descending at a rate of ~ 500 fpm (Cessna 172) to 800+ fpm (large commercial carriers).  Ouch!

Dan

Legacy Virtual Airline

Legacy Aviation Knowledge Academy

 

Windows 10, i7 3770 3.9 GHz, 16 GB DDR3 RAM, NVIDIA 1070 ti, 42" 1080p widescreen / P3D v5, P3D v4, FSX with Acceleration, FSX-SE / TrackIR-5

  • Author

Ahh, ok, I figured I was doing something wrong, yes, I waited until the proper time to engage the ils, but let it take me all the way down, that is where I failed this time. :)

Congratulations! Now you see how the system works. Just don't forget step 10.

ATC will bring you lower and closer.

Have Fun
Dave

  • Author

Thanks again for all your help. I wish I had thought of asking around when I was first starting out :).

  • Author

New issue... I tried another airport to be sure I understand what Im doing. Now the aircraft hits the GS,, and everything works perfectly, except, the aircraft doesn't start descent. Seems like every time I learn to do one thing, I do something that I've always done right, wrong. I don't know what I could be doing wrong, because it is the same things I was doing at the other airport. Autopilot should be on? Including Alt Hold?

Be sure you're capturing the glide slope from BELOW (the little balls (HSI) or bar (NAV1) would be up high)

 

Also be sure it really is an ILS and not a localizer...  because loc only approaches exist too.

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

  • Author

Does it say in FSX if it is Loc only and not ILS?

What airport and what Ry ?

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

  • Author

Hang on let me look again. KJAX, runway 25. Edit I do use Navigraph, could there be an issue here?

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.