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.

Incorrect Ground Assignment @ KMCO

Featured Replies

May have found another bug.  Just landed in Orlando and was handed off to ground on 121.7.  Attempted to contact ground and was told to check frequency.  The info button has 121.8 listed for that airport.  After tuning to that frequency I was able to get taxi instructions to the gate.

 

As an extra bit of information - I just tried to file a new flight plan - when trying to contact clearance they are telling me to immediately try and contact ground.

Chris DeGroat  

XP11 | MSFS

i9 12900k | 32GB DDR5 RAM | 2TB Samsung EVO SSD (1TB x 2 in RAID 0) | MSI RTX 3090 | Reverb G2 | RealSimGear TBM900 Panel with Yoko+ TQ6+ & TM TPR Pedals

  • Commercial Member

Chris, 121.7 is Ground for KISM. 

I just tried the Clear of Active call at KMCO and was given 121.8.  Not sure what happened on your flight.  ClrDel also works on 134.7 at KMCO.

 

You might try connecting and disconnecting between flights or legs of flights - after each full stop landing.  This will clear the many variables floating around that might get P2A confused.  If you still have trouble, turn P2A off and back on.

 

Regards,

Dave

  • Author

Chris, 121.7 is Ground for KISM. 

I just tried the Clear of Active call at KMCO and was given 121.8.  Not sure what happened on your flight.  ClrDel also works on 134.7 at KMCO.

 

You might try connecting and disconnecting between flights or legs of flights - after each full stop landing.  This will clear the many variables floating around that might get P2A confused.  If you still have trouble, turn P2A off and back on.

 

Regards,

Dave

Thats actually what I did that cleared the second issue.  First issue Im not sure why it insisted on 121.7 instead of 121.8 after landing. After reloading it gave the correct ground frequency for the departure flow.

Chris DeGroat  

XP11 | MSFS

i9 12900k | 32GB DDR5 RAM | 2TB Samsung EVO SSD (1TB x 2 in RAID 0) | MSI RTX 3090 | Reverb G2 | RealSimGear TBM900 Panel with Yoko+ TQ6+ & TM TPR Pedals

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.