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.

Problem at KSRQ

Featured Replies

Hi,After more than 100 successful flights using RC4, I encountered a problem on my last flight. I was going from KEYW to KSRQ with an intermediate point of RSW, flying the Dreamfleet A36. All was normal with Approach telling me to expect an approach to runway 32 and directing me to descend to 2000 ft and a heading of 320. I expected an intercept heading, but received no further instructions. Staying with the last ATC heading took me approximately 3.5 miles SW of the airport. I waited until I was at least 5 miles past the airport, then requested a visual. RC4 responded immediately to contact tower and the last of the flight was normal (for a visual approach).Is this a known problem for this airport/runway? I did not run a logfile as I did not expect the problem. The airport and scenery are default. I was running ASV6.5 for weather, FSNAV (not using the FMC), and was using the autopilot only for heading and altitude.Dale

Dale

  • Commercial Member

if it was a near straight in approach, you're not going to get a vector to the locailzer. just an intercept to the localizer. you have to turn on the localizer yourselfif you think there is a problem, follow the directions on the top of the forum, duplicate the problem, and send me the .logbe sure to click debug before loading the .plnjd

  • Author

>if it was a near straight in approach, you're not going to>get a vector to the locailzer. just an intercept to the>localizer. you have to turn on the localizer yourself>>if you think there is a problem, follow the directions on the>top of the forum, duplicate the problem, and send me the .log>>be sure to click debug before loading the .pln>>jdPerhaps this is a silly question, but what is the difference between a vector to the localizer and an intercept to the localizer?I tried the flight again, with the log file enabled. Naturally, this time it worked perfectly. I tried to keep everything the same, but the weather was updated. On the first run KSRQ winds were 040@4, and on the second, 030@8. Both times Runway 32 was active. What confused me was that on the first attempt, RC4 never cleared me for the approach, so I continued to follow the assigned heading, which was about 3 miles West of the localizer course.Well, if I can't duplicate it, there's not much that can be done, and I can't rule out that I may have done something that caused the problem. Thanks for taking the time to answer so quickly.Dale

Dale

  • Commercial Member

if the localizer is say, 360 degrees, depending on which way you are coming in (left base or right base) it will tell you to fly 330 or 30a 30 degree intercept. when you get to the point where the airport, and hopefully the runway is a bearing of 360 degrees, then you turn to 360jd

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.