Archived

This topic is now archived and is closed to further replies.

FTD1949

Approach contact problem

Recommended Posts

Hi All, I had an IFR flight from KROA to KIAD yesterday and all went well until the approach phase. After receiving what should have been a vector to intercept the glideslope I was unable to communicate with approach control because he was busy communicating with other aircraft and I couldn't get a word in edgewise because of all the communications and ended up overshooting the intercept. When I was finally able to communicate with approach I was given another vector but by the time I received it I was to high and close to make it work. Any way to break in when there is so much communication to other aircraft happening or perhaps I just should have declared a missed approach? Thanks in advanceCraigLian Li PC 65B CaseCorsair HX Series CMPSU-620HX 620W Power SupplyPlextor PX-810SA/SW-BL DVD/CDGiagabyte GA-P35-DS3RCrucial Ballistix 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500)Arctic Freezer 7 ProIntel E6850 Core 2 Duo 3.0GHz 4M shared L2 Cache @ 3.6 GHzEVGA 7950GT KO 512mb 169.21_forceware whqlSeagate Barracuda 7200.10 500GB 7200 RPM 16MB Cache SATASeagate Barracuda 7200.10 250GB 7200 RPM 16MB Cache SATAWinXP Pro SP2

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Try turning down the traffic setting, I generally don't use higher than 30 in the VoxATC settings menu.

Share this post


Link to post
Share on other sites

Thanks for the tip.CraigLian Li PC 65B CaseCorsair HX Series CMPSU-620HX 620W Power SupplyPlextor PX-810SA/SW-BL DVD/CDGiagabyte GA-P35-DS3RCrucial Ballistix 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500)Arctic Freezer 7 ProIntel E6850 Core 2 Duo 3.0GHz 4M shared L2 Cache @ 3.6 GHzEVGA 7950GT KO 512mb 169.21_forceware whqlSeagate Barracuda 7200.10 500GB 7200 RPM 16MB Cache SATASeagate Barracuda 7200.10 250GB 7200 RPM 16MB Cache SATAWinXP Pro SP2

Share this post


Link to post
Share on other sites