Welcome, Guest. Please login or register.
Did you miss your activation email?
December 09, 2016, 02:15:42 PM
Home Help Login Register      
News: No coverage in your area? If you are near your local airport contact us to learn about becoming a volunteer

+  LiveATC Discussion Forums
|-+  Recent Posts
Pages: 1 ... 3 4 [5] 6 7 ... 10

 41 
 on: November 29, 2016, 01:29:54 PM 
Started by GeoffSM1 - Last post by GeoffSM1
High wind speeds and wind sheer creating difficulties at Amsterdam (Runway 18R) on
20 November. Unfortunately, a somewhat noisy feed.
Given the conditions, is it not a little a little disturbing that the controller did not give a wind sheer warning to every pilot? What is more, unless my ears are deceiving me, the pilot of the first aircraft gave wind sheer as the reason for going round and yet, when specifically asked about wind sheer by another pilot shortly afterwards, the controller replied that no wind sheer had been reported.

 42 
 on: November 29, 2016, 10:12:49 AM 
Started by JetScan1 - Last post by JetScan1
Quote
Same with traffic out of Jacksonville and Miami Center areas off the Florida coast, here ARINC is using 130.70 to assign HF frequencies now. I haven't tried yet but you will probably hear this on the San Juan feed.

Just checked the San Juan LiveATC radio and it appears 130.70 is no longer covered on this feed. Anyone in Florida able to hear the ARINC operator on 130.70 ?

JS

 43 
 on: November 28, 2016, 08:43:25 PM 
Started by helimedic - Last post by helimedic
The YPJT feed will be down due to hardware issues with my Raspberry Pi which is likely a board fault.

I am away on business for 2 weeks and will have a look at a fix ASAP.

Helimedic.

 44 
 on: November 28, 2016, 12:15:02 PM 
Started by JetScan1 - Last post by JetScan1


There appears to be some sort of reception issue with this feed. The ARINC operator on 129.90 is coming through very strong but the transmissions are always broken up or getting clipped and unreadable. No problem with aircraft reception though, they are coming through okay even at far distances. So it doesn't sound like an antenna problem ? Are the operator transmissions so strong that they are overmodulating the radio ? Checking the archives its been like that for a few weeks now, prior to this reception was okay.

FYI for those interested, New York ARINC appears to have expanded their VHF coverage so that you will now hear the operator on 129.90 assigning HF frequencies for traffic routing via OXANA.ZZTOP and SAUCR.ONGOT on the JFK/LGA feed (if it was working). Prior to this HF frequencies were assigned by New York Center on 126.025 on these routes.

Same with traffic out of Jacksonville and Miami Center areas off the Florida coast, here ARINC is using 130.70 to assign HF frequencies now. I haven't tried yet but you will probably hear this on the San Juan feed. 


JS

 45 
 on: November 28, 2016, 08:59:06 AM 
Started by RonR - Last post by JetScan1
Ron,

Quote
JFK1 is locked on 128.675 right now.

Thanks for that. During that time 128.675 was simulcasting with 133.500 and 125.925

However I pulled up some more ZNY-JOBOC archive from yesterday and starting at 2120Z they did split off 128.675 into a separate sector. It was used in the corridor working NYC area arrivals/departures from what sounded like FL240 to up to FL300. With 133.500 (combined with 125.925) working FL310 and above.

First time I've heard that, will keep an eye on it. Any chance you could take 128.675 off your #1 radio and put it on the #3 so it's with 133.500 ? Would make it easier to cross-check, and you would hear the controller in that area when they are combined.

JS

 46 
 on: November 27, 2016, 11:53:34 PM 
Started by oktalist - Last post by ftlurker
The pilot initially requests vectors back to Dallas Love, but a few seconds later in the recording he formally declares an emergency and requests immediate vectors back to Fort Worth (for the extra runway length).  I think the pilot only realized the issue because there is no ILS approach to 13L at DFW. It feels like this could have been a lot worse than it was. Not an insignificant miss by ATC. If they had given him 13R he might have executed an approach on 13R at Love Field.

Nothing personal, the protocols are designed so that both sides make sure comms are clear and confirmed.

I agree with your interpretation of how this happened. And yet, as I listen again and again, everyone followed protocol. Which is what scary!  it was just that during readback, the field was mentioned only intermittently and when it was mentioned it was overlooked by a busy crew or ATC.

Whoa! This is one that the ATC/FAA/NTSB should review to avoid this happening again.



 47 
 on: November 27, 2016, 07:58:06 PM 
Started by RonR - Last post by RonR
Sure no problem....JFK1 is locked on 128.675 right now. Sorry it took a while to get back to you...

Sent from my SGH-M919 using Tapatalk


 48 
 on: November 27, 2016, 05:23:55 PM 
Started by RonR - Last post by JetScan1
Ron,

Quote
Have you ever heard ZNY split up the ZNY 133.5 sector?

No I've never heard them split it before (2 different controllers). I pulled up the archives between 2000Z-2059Z and it did sound they were using both frequencies in the sector, but the sector was not split (same controller on both frequencies) from what I could tell. Any chance you could isolate 128.675 on one of your radios for a bit to help figure out what's going on ?  

 49 
 on: November 27, 2016, 04:36:34 PM 
Started by RonR - Last post by RonR
No problem Jet...

Have you ever heard ZNY split up the ZNY 133.5 sector?  That's what seems to be going on right now.  133.5 and 128.675 are both in use in this sector... 

 50 
 on: November 27, 2016, 11:45:38 AM 
Started by RonR - Last post by JetScan1
Quote
for anyone interested, ZNY is using 128.675 again

Thanks for the update Ron. I've also heard 121.12 used as a backup for 133.50, and a few weeks ago they were briefly using 121.125 as a sub for 132.17.

Pages: 1 ... 3 4 [5] 6 7 ... 10


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!