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.

Radio shadow?

Featured Replies

I planned a short hop from KBOS to KACK today and ran into a "thing" that might be a bug or a feature depending on the reply to this post. :()While planning the hop I accidently set the cruise altitude to 1000 feet rather than 10000 feet. As I started the flight I was surprised as ATC cleared me to 1000 feet after take off with no "expect FLxxx within YY minutes...etc" to follow (I didn't yet realise the mistake I made in filing the flight plan). After take off I turned to my assigned heading and climbed to 1000 feet while waiting to get handed to departure. Nothing happened. There I was, a foggy day in Boston, licking the roof tops and keeping a close eye for antennas and scy scrapers heading my way. There was no options available in the menu apart from "Main menu - 0" so I couldn't ask for a higher altitude or abort the departure.After more than 5 minutes of this, still waiting for that hand-off (well de-routed from my filed plan) I decided my passengers safety had precedence over ATC so I initiated a climb to 3000 feet. Then, at ~2000' KBOS TWR suddenly contacted me and immediately handed me off to departure (who, of course, gave me a hard time for not staying at my assigned altitude *rolls eyes*).Just to make sure, I re-flew the same plan again with the exact same result.I now have two questions:Firstly, shouldn't RC reject flight plans that clearly doesn't follow departure limitations? Granted, that info is likely not available in the FS2004 database (or is it?) so I can see the problem if it doesn't.Secondly, was the getting-handed-off while climbing just a coincidence or did I simply enter "radio shadow" efter my take off so that TWR couldn't reach me?Thanks for a great product btw.

-----------------------------------------------------

i7 920 @ 3.6 GHz; 6Gb DDR3; Windows 7 Ultimate x64; Sim disk=300Gb 10,000rpm (VelociRaptor); OS disk=300Gb 7,200rpm

Radeon HD 4870 X2; Audigy 2 ZS; Dual monitors=24" Dell Widescreen (TFT) & 19" BenQ (TFT)

FSX Acceleration

Hi there,I think the hand off to departure occurs at a certain height above the airport which you never reached with a cruise altitude of 1000 feet.They are a mean bunch the RC controllers. I'll bet all the sympathy you'll get from them is: you filed it, you fly it :-lolI've done the same myself ;-)All the best,John

  • Author

Hehe, well it WAS a silly mistake and I suppose your suggestion is more likely than implementing a compex radio shadow (would be extremely cool tho).However, shouldn't there ALWAYS be some sort of option available to the pilot? I might want to declare an emergency as one of my engines decides to call it a day just after take off or something...Regards

-----------------------------------------------------

i7 920 @ 3.6 GHz; 6Gb DDR3; Windows 7 Ultimate x64; Sim disk=300Gb 10,000rpm (VelociRaptor); OS disk=300Gb 7,200rpm

Radeon HD 4870 X2; Audigy 2 ZS; Dual monitors=24" Dell Widescreen (TFT) & 19" BenQ (TFT)

FSX Acceleration

But your Thrust Reduction and Accel Height would be greater than a 1000ft AGL anyway right? ;o)Subs

  • Author

>But your Thrust Reduction and Accel Height would be greater>than a 1000ft AGL anyway right? ;o)>>SubsNot in a single piston.

-----------------------------------------------------

i7 920 @ 3.6 GHz; 6Gb DDR3; Windows 7 Ultimate x64; Sim disk=300Gb 10,000rpm (VelociRaptor); OS disk=300Gb 7,200rpm

Radeon HD 4870 X2; Audigy 2 ZS; Dual monitors=24" Dell Widescreen (TFT) & 19" BenQ (TFT)

FSX Acceleration

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.