Welcome, Guest. Please login or register.
Did you miss your activation email?
March 01, 2015, 03:30:36 AM
Home Help Login Register      
News: LiveATC.net Flyers Released!  Please click here to download & print a copy and be sure to post at an airport near you!

+  LiveATC Discussion Forums
|-+  Recent Posts
Pages: [1] 2 3 ... 10

 1 
 on: February 28, 2015, 03:20:06 PM 
Started by mperry - Last post by mperry
What radios are you using?


Sent from my iPhone using Tapatalk

 2 
 on: February 28, 2015, 01:00:03 PM 
Started by mperry - Last post by JetScan1
dave,

You've got 3 separate feeds ...

KMCO Departure (East)
KMCO Departure (West)
KMCO Departure (East/West)

Are these 3 feeds using 2 radios with the East/West crosswired together ? Or are you using 3 separate radios here ?

 3 
 on: February 28, 2015, 12:50:33 PM 
Started by mperry - Last post by JetScan1
Quote
But the receivers used on this feed (which will not change) are not capable of turning delay off.

That would be a problem as they seem to simulcast quite a bit even when the respective sector is closed, and as they don't use those extra sectors that often it would screw up the feeds the rest of the time. In that case probably better to leave it the way it is.

Adding 128.375 to replace 125.550 on the "KMCO Arrival (West)" feed would be good though. For the amount of time they actually use the west arrival final 123.850 (not very often) but seem to simulcast with the very busy 127.750 a lot, maybe it would be better to remove 123.850 from the radio ? You wouldn't get coverage of 123.850 the few times they open it but it would open up the busy high arrivals sectors from getting blocked by the 127.750 controller simulcasting on 123.850.

Of course the best solution would be a couple more radio's (I can donate funds). Anyway just minor points, it's a great setup with good overall coverage (except the missing and very busy 128.375).

 4 
 on: February 28, 2015, 12:33:29 PM 
Started by mperry - Last post by dave
I do monitor these threads.  smiley. Since I run this feed I can review the changes.  But the receivers used on this feed (which will not change) are not capable of turning delay off. 

 5 
 on: February 28, 2015, 12:17:17 PM 
Started by mperry - Last post by JetScan1
Quote
Does anyone know what the DISNEY/OVIDO is for example.

The DISNEY Sector, 119.400, basically covers the southern area of the TRACON from at and below 4500/5500 feet (varies). Works arrivals and departures into Kissimmee (ISM) and some arrivals into Orlando Executive (ORL) as well as transient aircraft at/below 4500/5500 feet.

The OVIDO Sector, 119.775, is only open when traffic is busy and handles the airspace around Orlando Executive (ORL).

When the OVIDO sector is closed this portion of airspace is controlled by the North Satellite Sector, 121.100, which basically covers the northern part of the TRACON from at and below 5500 feet. Primarily Sanford (SFB) arrivals and departures and some or all ORL arrivals and departures (varies).

If Dave is reading this.

From what I've heard it seems at times even when the OVIDO sector is closed the controller will simulcast on 119.775 and 121.100. So what ends up happening on the DISNEY/OVIDO feed is you will hear the same controller as you do on 121.100 blocking out a lot of the DISNEY 119.400 traffic. Perhaps a more logical setup might be to include the OVIDO sector with the North Satellite feed and take it off the DISNEY feed ?

Also it appears that 125.550 has been replaced by 128.375, so on the West Arrival feed it would make more sense to cover only 128.375 and 134.050. I also notice that 123.850 is also on this radio. As the controller often simulcasts on 127.750 and 123.850 when its closed it would seem to me to make more sense to put 123.850 on the 127.750 radio. As long as there was NOT a delay function set as it would screw things up most of the time. 

 6 
 on: February 28, 2015, 11:34:18 AM 
Started by JAYLUGO21 - Last post by mperry
If you live that close get a scanner, you can more likely hear more, plus maybe you can help out when the other feed has to be removed for a few days.


Sent from my iPhone using Tapatalk

 7 
 on: February 28, 2015, 11:28:11 AM 
Started by mperry - Last post by mperry
Does anyone know what the  DISNEY/OVIDO is for example.


Sent from my iPhone using Tapatalk

 8 
 on: February 27, 2015, 05:53:14 PM 
Started by les187 - Last post by swa4678
If they were close enough to require any sudden sort of maneuver, it's almost a sure bet they'd have to be with tower by that point. Do you have a date and time and/or tail number (or scheduled air carrier flight number) for this as well?

 9 
 on: February 27, 2015, 03:57:18 PM 
Started by les187 - Last post by les187
I'm a journalist trying to track down audio of a specific incident.  I don't know which actual feed to listen to in the archives.  The incident apparently involved a pilot being within sight of the runway when he had to pull up suddenly because another plane was still on the runway. I'm trying to figure out which air traffic recording I would listen to for any sort of communication about this?  The airport is IAH, I just an not sure which specific IAH feed is appropriate?  Thanks in advance for advice!

 10 
 on: February 27, 2015, 01:08:24 PM 
Started by RonR - Last post by RonR
Interesting article on Americas Air Traffic Control System.  Thought I'd pass it on...

http://www.wired.com/2015/02/air-traffic-control/

Pages: [1] 2 3 ... 10


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!