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.

Handoff to approach fails

Featured Replies

This problem is specific to a flight from KSBN to KORD. I've tried via DEERE and CGT at various atltudes between 10,000 and 14,000 with the same results. Have duplicated this four times now. Here's what happens:I hand off comms to Otto before takeoff. I do this every flight. At cruise altitude, still under initial departure control, Otto leaves freq. for weather. Shortly after we come back from weather, Departure instructs us to contact Approach on 128.45. The radio frequency changes, and then all comms stop. Otto does *not* check in. Approach does not issue any instructions. Comms just stop. I can totally abandon my flight plan, change altitude and even land with no further comment from approach.If you need files to shoot this, please give me the exact procedure as I'm not familiar with debuggin files in RC.Thanks!-MJL

_____________________________

 

  • Commercial Member
This problem is specific to a flight from KSBN to KORD. I've tried via DEERE and CGT at various atltudes between 10,000 and 14,000 with the same results. Have duplicated this four times now. Here's what happens:I hand off comms to Otto before takeoff. I do this every flight. At cruise altitude, still under initial departure control, Otto leaves freq. for weather. Shortly after we come back from weather, Departure instructs us to contact Approach on 128.45. The radio frequency changes, and then all comms stop. Otto does *not* check in. Approach does not issue any instructions. Comms just stop. I can totally abandon my flight plan, change altitude and even land with no further comment from approach.If you need files to shoot this, please give me the exact procedure as I'm not familiar with debuggin files in RC.Thanks!-MJL
since you can duplicate this, make a log, instructions pinned to the top of the forum. then zip it up (zip only please), and send it to me.jd

From the manual:"Give the aircraft to the co-pilot and allow him/her to fly us onto final. You handle the radios in Approach airspace. Otto will not execute the controller‟s clearances, until you have acknowledged that clearance."You need to take the comms before reaching 40 nm out (approach jurisdiction) and insure there are no messages to ack. An RC ATC transmission not acknowledged will stall it.See if that helps.In addition, be sure you have met your crossing restriction of 11,000 or 10,000 feet at about 40 nm out from KORD. If not you'll get delay vectors forever until you are at the requested altitude.

Hi ronzie,"You need to take the comms before reaching 40 nm out (approach jurisdiction)".I always give the comms (not the plane) to Otto somewhere during descent and leave them with him for the rest of the flight.Otto will ack frequency changes, change frequencies and and contact Approach - Tower - Ground without problems.Of course, Otto will not execute the controller's instructions, but he is acknowledging those instructions.I suspect -MJL's problem is something else.Andreas

Regards,

Andreas Gutzwiller

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.