Welcome, Guest. Please login or register.
Did you miss your activation email?
July 31, 2015, 11:33:48 PM
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 4 ... 10

 11 
 on: Today at 07:24:23 AM 
Started by 777lrf - Last post by 777lrf
Thanks for the report 777lrf! I heard it too on my end a few days ago and restarted the PC. Been having network issues and the reboot cleared it up.
Chananya thanks for relaying the message to me! Smiley
Ken




Thank you for the feed! Appreciate it. It's been down today but I am sure you are going to bring it back up when you are able.

Wondering if you are planning on expanding into RJAA tower/ground? Or do you live too far away?

 12 
 on: July 30, 2015, 10:44:32 PM 
Started by herrtodd - Last post by w0x0f
This CBS article is rubbish.  The video is slightly better.  The pilot and controller did not "argue."  The controller did not "scold" the pilot. 

The pilot called while holding in center airspace to find out what was going on.  The controller explained what was going on and gave the pilot his options, one of which was to declare an emergency.  The controller added for informational purposes that Allegiant was given due notice of the airport closure.  The flight was an hour late and missed the window.

I was rather surprised to learn that there were 2 management pilots flying this aircraft.  One was the VP of Operations, who is an alleged advocate of operating with minimum fuel, and the other was Director of Flight Safety and Quality Assurance.  Expect some sort of shake up in the ranks.

http://www.reviewjournal.com/news/las-vegas/allegiant-air-execs-controls-flight-landed-low-fuel

 13 
 on: July 30, 2015, 03:28:21 PM 
Started by MochaHagotdi - Last post by VictorAtienza94
All of the interim waypoints along J42 are right near an ARTCC boundary

Exactly, BUT telling/reading the route for an aircraft is absolutely unnecessary.

It is okay for the system to read it and recognize it but if you're clearing an aircraft a re-route you can just read the short version smiley smiley

 14 
 on: July 30, 2015, 02:47:34 PM 
Started by MochaHagotdi - Last post by Brad G.
I guess is kinda due to sector limits or something... huh huh
Very plausible. IIRC, back in HOST days, someone said the computers wouldn't behave well when a FP crossed an ARTCC with no points in/near the ARTCC it could recognize. All of the interim waypoints along J42 are right near an ARTCC boundary (e.g. they are fixes likely depicted/known for both ARTCC's enroute computers/scopes).

If so.. gotta love 1970s technology causing lengthier-than-needed in-air IFR clearances now in 2015.  rolleyes

 15 
 on: July 30, 2015, 02:04:08 PM 
Started by MochaHagotdi - Last post by tyketto
Really makes me wonder what flight strip Center was looking at as compared to what the cab and TRACON had, especially given that the new routing doesn't appear to have been followed. Sure sounds like somebody dropped the ball given Center's initial (and subsequent?) confusion.

The only thing I can think of for this was the metering for the weather delay that the NY area is having. KEWR and KJFK both have 2 hour 15 minute delays coming in and out.

Looking at the preferred IFR routes from the FAA (page 401), the preferred route for KLAX-KEWR is SID DAG J100 0BH J10 IOW J60 JOT J146 GIJ J554 CRL J584 SLT FQM–STAR

So giving them the reroute would have to pretty much be for weather, which they probably were rerouted again after DRK, which turns out to be the case.

BL.

Quote
Random question... why the heck would you read out "MEM.J42.BNA.J42.BKW.J42.GVE" rather than "MEM.J42.GVE" ?

good question. No real need for that type of read out on the clearance.

BL.

 16 
 on: July 30, 2015, 01:20:10 PM 
Started by MochaHagotdi - Last post by VictorAtienza94
Random question... why the heck would you read out "MEM.J42.BNA.J42.BKW.J42.GVE" rather than "MEM.J42.GVE" ?

I've been asking that myself for years...

I guess is kinda due to sector limits or something... huh huh


 17 
 on: July 30, 2015, 12:11:52 PM 
Started by MochaHagotdi - Last post by Brad G.
Really makes me wonder what flight strip Center was looking at as compared to what the cab and TRACON had, especially given that the new routing doesn't appear to have been followed. Sure sounds like somebody dropped the ball given Center's initial (and subsequent?) confusion.

Random question... why the heck would you read out "MEM.J42.BNA.J42.BKW.J42.GVE" rather than "MEM.J42.GVE" ?

 18 
 on: July 29, 2015, 06:56:15 PM 
Started by MochaHagotdi - Last post by Flyingnut
Looks like the "new" routing is not valid anymore, because the aircraft is currently over SE Minnesota right now. 

Marty

 19 
 on: July 29, 2015, 06:42:07 PM 
Started by MochaHagotdi - Last post by MochaHagotdi
Caught this gem while listening to the ZLA 04/13/21 feed earlier this afternoon. VRD166 was climbing out on the LOOP7 departure out of KLAX. Center inquired whether VRD was direct TRM (Thermal VOR) or not. This in turn opened Pandora's box for a full (re)route clearance...

https://flightaware.com/live/flight/VRD166/history/20150729/1935Z/KLAX/KEWR

Original routing: LOOP7 DAG J100 LAS KD54U TXC OVR DSM EVOTE NELLS KEEHO J584 SLT FQM3

New Routing: HOLTZ9.TRM..PKE..DRK.J6.IRW..FSM..MEM.J42.BNA.J42.BKW.J42.GVE.PHLB03

 20 
 on: July 29, 2015, 03:23:54 PM 
Started by herrtodd - Last post by hb7
The CBS post doesn't list credit for the source of the clip: http://www.cbsnews.com/news/allegiant-air-pilot-pleads-atc-make-emergency-landing-closed-airport/  sad

Pages: 1 [2] 3 4 ... 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!