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.

Final Approach

Featured Replies

Hi,I was handed off to approach at 10000 when the controller cleared me for 7000 then 2 seconds later he cleared me for 3500 feet and to intercept the localizer/glideslope, granted there was no way I could go from 10000 to 3500 in that short of time.I'm using rc31 beta. Just wondering if I did something wrong has duplicated this twice on the same flight. KHOU-KHRL.Thanks for any info.Sean

Sean,Actually, you are only cleared for the localizer intercept. This sounds like a straight-in approach. When you get the clearance to the final, you are responsible for flying the plate (that's what flying IFR is about). So you need to be slowing down and descending appropriately for your distance and altitude.Getting a straight-in approach is the best and most desired. Once lined up you have the time to do all the landing checks and speed reductions and altitude sets as needed. If need be, you can descend at 3000 fpm safely and comfortably in a jet.

Scott,Thanks for the reply, flew it a third time this morning verifying I was within the altitude constraints atc set upon me. I was only 25 miles away at 9000 feet when I was told cleared to land d/m 3100 feet. There was no way I could catch the glideslope unless I did a nose dive at 10,000 feet per minute I easily caught the localizer but was way too high on approach. I declared a missed approach and flew back around successfully.Here is the flightplan if somebody wants to verify:KHOU - Yawns - Ngp - Hrl - Khrl at fl310.Thanks,Sean

Sean,Okay, then that's probably related to the MSA.Fly it again and save a dat before contacting Approach. When JD gets back send the files to him (zipped, of course).

>Sean,>>Actually, you are only cleared for the localizer intercept. >This sounds like a straight-in approach. When you get the>clearance to the final, you are responsible for flying the>plate (that's what flying IFR is about). So you need to be>slowing down and descending appropriately for your distance>and altitude.>If need be,>you can descend at 3000 fpm safely and comfortably in a jet.Scott,I have had the above happen each time I fly the Modesto Two arrival into SFO. I am level at 10000, given a heading and new altitude of 9000. Immediately after acknowledging the descent to 9000, I am told to descend to 7000 followed immediately by the standard "xx miles from the marker, fly heading 240 intercept 28R localizer, maintain 3200 (or so) until established etc ..."So, in the process of beginning my descent out of 10000 for 9000, I am then cleared all the way down to the 3200. Yes, I could fly a 3000 fpm descent, but that is not in accordance with SOP below 10000'. ;-)-michael

Michael,Save a dat before contacting approach and save it for when JD gets back.

>Michael,>>Save a dat before contacting approach and save it for when JD>gets back.>Ok - will do. -michael

Scott,I've flown the flight 5 times now. Next time I will save a DAT file but what I noticed is right after contracting approach I was told:"Fly Heading 265 d/m 9000" about 3 sec delay then "Cleared such and such d/m 3100 fly heading 145"I will save a DAT file and send it to you.Thanks for you help,Sean

Hi,I sent a DAT file to John before contacting approach for this flight that I'm seeing the problems with.Any questions just let me know.Sean

  • Commercial Member

i found the problem, i think. the beta testers will be testing it for a couple of days, then i'll upload the new buildjd

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.