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.

Doing a U-Turn after loading an approach

Featured Replies

I've been trying IFR flight plans without a runway and approach planned, and waiting for an assignment from the approach ATC.

I recall this was a problem in the past, where the plane does a U-Turn after loading the approach to go back to the last waypoint to begin the approach, rather than just intersecting it at the most convenient point.

I thought this was fixed in a recent patch, but obviously not.  Is there some way to load an approach that won't cause this behaviour?

Edited by Virtual-Chris

Not that I know of.  I had one IFR low Altitude plan try to route me back 60+ miles back because it was the last waypoint in the flight plan prior to the airport.

To mitigate that I try to choose a fix fairly close to the destination airport and insert that into the IFR flight plan.  Then once I get the approach info, I wait until I pass THAT fix until I activate the approach.  Then the circle back isn't as painful.

The only thing to eliminate it I know is to enter the approach and arrival information in the flight planner, and that's not entirely accurate given how field conditions can change over the length of a flight.

  • Author

I found this... which seems like a workaround... I don't relish having to do this on the G1000 though. 😞

 

 

 

1 hour ago, Virtual-Chris said:

I've been trying IFR flight plans without a runway and approach planned, and waiting for an assignment from the approach ATC.

I recall this was a problem in the past, where the plane does a U-Turn after loading the approach to go back to the last waypoint to begin the approach, rather than just intersecting it at the most convenient point.

I thought this was fixed in a recent patch, but obviously not.  Is there some way to load an approach that won't cause this behaviour?

This is a very well publicized problem.  The cure is to have at least one flight plan nav point left before you load and then activate the approach.  

Say you are headed to KSTP and you have the RNAV (GPS) 32 approach loaded, but not activated.   The end of your flight plan looks like this:

→ GEP →  LDASH →  FOMRU → RULDE → KSTP

LDASH is the IAF of the already loaded approach.  GEP is the last fix before that IAF.  In order to avoid the 180° turnaround, go into PROC and Activate the approach before you reach GEP.

Edited by fppilot

Frank Patton
Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; 
NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                       
"I will never put my name on a product that does not have in it the best that is in me." - John Deere

The problem is if you have no approach loaded and wait for ATC to assign you one - it's very likely you'll be past that last waypoint before ATC assigns you the approach, which means guaranteed U-turn.

Edited by marsman2020

AMD 3950X | 64GB RAM | AMD 5700XT | CH Fighterstick / Pro Throttle / Pro Pedals

Hahaha....  Wouldn't it be nice if these approaches just worked?

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 |

 

 

7 minutes ago, ryanbatcund said:

Hahaha....  Wouldn't it be nice if these approaches just worked?

Update 9....assuming they don't miss that promise and decide it was "a typo".

AMD 3950X | 64GB RAM | AMD 5700XT | CH Fighterstick / Pro Throttle / Pro Pedals

51 minutes ago, fppilot said:

This is a very well publicized problem.  The cure is to have at least one flight plan nav point left before you load and then activate the approach.  

This is why I insert a final waypoint very close to the arrival airport.  This gives ATC a chance for me to get my approach and transition information PRIOR to reaching that waypoint.  And if I don't get it until after, the U turn isn't terrible.

Edited by wthomas33065

Frank Patton
Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; 
NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                       
"I will never put my name on a product that does not have in it the best that is in me." - John Deere

  • Author
13 minutes ago, fppilot said:

Interesting, I thought I had that loaded when flying and testing this yesterday. I better double check that it's actually loading up.  Although I noted it saved my G1000 settings from previous sessions which is a good clue that it is loading (I think).  Hmm... I wonder if the mod is broken too.

Edited by Virtual-Chris

I've been using the WT G1000 for my around the world flight.  Instant U-turns upon loading the ATC-assigned approach on both Leg 1 and Leg 2.  So it may be fixed in some instances, but not in others.

Asobos flight planning code is apparently very...."fragile" (probably being generous), so we probably just need to wait for the mod makers to dig in further and rip it all out and replace it.

Edited by marsman2020

AMD 3950X | 64GB RAM | AMD 5700XT | CH Fighterstick / Pro Throttle / Pro Pedals

48 minutes ago, marsman2020 said:

I've been using the WT G1000 for my around the world flight.  Instant U-turns upon loading the ATC-assigned approach on both Leg 1 and Leg 2.  So it may be fixed in some instances, but not in others.

For the WT G1000, make sure to select "activate", not "load".   It's in their instructions but easily overlooked (as I did at first).

Hope this helps.  

3 hours ago, tyrodes said:

For the WT G1000, make sure to select "activate", not "load".   It's in their instructions but easily overlooked (as I did at first).

I flew the Baron into KAVL this afternoon with the WT G1000 mod. Not aware of the activate, not load, I did load as soon as I selected the approach.  Was 200 nm out.  Later did activate, still before the last waypoint prior to the approach procedure and the approach was flown perfectly.  I have not yet attempted waiting to activate the approach after the final waypoint.  Will try that with practice approaches, not with one at the end of a 2 1/2 hour flight.

The approach and landing were spot on.

Edited by fppilot

Frank Patton
Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; 
NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                       
"I will never put my name on a product that does not have in it the best that is in me." - John Deere

4 hours ago, tyrodes said:

For the WT G1000, make sure to select "activate", not "load".   It's in their instructions but easily overlooked (as I did at first).

Hope this helps.  

I was not aware of that, will double check the documentation.

AMD 3950X | 64GB RAM | AMD 5700XT | CH Fighterstick / Pro Throttle / Pro Pedals

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.