Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Wesley Miles

Pages: 1 ... 4 5 [6] 7 8
76
I should specify: as long as the aircraft is flying IAW LOAs/NAS route/altitude by the time comms are transferred, I believe there to be no issue.

77
We interpret that to mean changes to NAS information... ie route, altitude, etc.  Which is why you get the "Handoff Status" error when trying to make an FDIO ammendment to an aircraft in h/o status.  Also why you have to coordinate any changes to NAS info after a handoff has been accepted.  Pretty sure this excludes maneuvers in your airspace, under your control.

This is interesting... I'll have to ask around and see what the consensus is at my facility.  If we're "doing it wrong", it may be a regional thing seeing as how variations of this happen many times each week (even with the Center).  Just had one today with ROC vectoring a guy after I accepted the handoff.

Edit: I can even remember a few times at the academy when I've had to vector after a handoff. Mind = blown.  Time for bed.

78
Yikes!!! I believe we have a difference of opinion here!  :D  Maybe your LOAs specify differently, but even  if the next sector takes the flash, the aircraft is still your control while in your airspace. I can give a guy a 360° turn after the next sector took the flash, and still be legal if he's in my airspace.

 For example: I start the handoff on a departure passing 3000. The center takes the flash at 4000.  I  still have control to vector the guy out of the gate, or around traffic, or stop his climb below traffic, as long as he's still in my airspace.

And on that logic, it's not uncommon for me to take a handoff 20 miles outside my airspace and not talk to the plane until 5 out. Maybe they had traffic, maybe the controller needed him for some reason. It's not my concern. I only care that I'm talking to him by my boundary, and when I do talk to him he has no conflicts.

 Do you guys do something differently?

79
If you follow the .65 5-4, you should not initiate a handoff until you are free of conflicts.

I disagree.  You need to ensure potential airspace violations and traffic conflicts are resolved prior to communications transfer.  It's not necessary to withhold a handoff until all conflicts are resolved.  The flashing does not indicate there are no conflicts, but rather the communications transfer.

As far as transferring communications right after the handoff has been accepted, that's just to the "extent possible", and not a requirement.  Otherwise I and nearly every radar controller I coordinate with break the rule every day.   :o

80
Absolutely Dhruv!  That's generally a good rule when talking about any radar position.  Starting the flash to the next controller as soon as possible makes your job easier and may help the receiving controller by allowing them time to plan their action, or simply aiding their situational awareness.

When the handoff has been accomplished, transfer communications as soon as you no longer need them.  If you can avoid last-minute coordination, why wait?

81
News / Re: New ZDV DATM Selected
« on: October 11, 2015, 04:39:01 PM »
Congrats Adam!

82
Zach,

We're implementing something similar at ZKC, but it's strictly for Class D's directly under Center airspace, where RADAR coverage isn't to the ground, and simulating those towers being "VFR Towers" without a DBRITE, R-ACD, etc.  

One-in-one-out is a method of non-radar separation.  It is used at uncontrolled airports, and Class D's where- as you said- the tower doesn't have a radar display, and/or the overlying facility doesn't have radar to the ground.

83
NOTAMs / Appropriate Controller Information
« on: November 21, 2014, 07:11:13 PM »
Reposted at ZKC as soon as I seen it.

84
General Discussion / Flight Watch Update?
« on: August 20, 2014, 06:52:15 PM »
Ever see the movie Jumanji?  Best not to touch it.  

85
The Control Room Floor / "Descend Via"
« on: November 08, 2013, 04:04:08 PM »
Thanks everyone for your input... I think that was a good discussion!  I agree Brad/Tim... this topic is pretty much closed with that.

86
The Control Room Floor / "Descend Via"
« on: November 03, 2013, 09:19:23 AM »
If I remember correctly, he was at ZBW.  Met him through VATSIM a few months ago but can't remember his name now.

87
The Control Room Floor / "Descend Via"
« on: November 02, 2013, 10:19:29 PM »
Who here issues "Descend Via" instructions to aircraft on an RNAV STAR working a CTR position?  I spoke with a real world CTR controller recently who told me ARTCC's are not authorized to use that phraseology-- that it's reserved only for TRACONs (with the exception of ZAB... I believe).  Has anyone else heard this?  If so, where is the documentation?

When looking at 7110.65 4-5-7... it's pretty evident to me that "Descend Via" can be issued by either ENROUTE or TERMINAL.  I know there was a notice (N JO 7110.584) which added "Climb Via", then another notice which cancelled that (N JO 7110.597)... but neither appear to affect "Descend Via" which provides provisions for both Terminal and Enroute.

Thoughts?

88
General Discussion / Again?
« on: August 20, 2013, 07:57:45 PM »
100 points to Dhruv!  

89
General Discussion / Again?
« on: August 20, 2013, 06:05:12 PM »
Here at VATUSA, we figure your loss of access is enough notification!  We always like to avoid confrontation, whenever possible. Problem is solved from your end!

100-points to the person who gets the reference!  

90
The Control Room Floor / VRC/Sector files
« on: August 11, 2013, 01:40:00 PM »
Doug,

I'm giving you the same reply I sent via email... hopefully in the future we can consolidate communications to one venue.    

As Rick explained, the extracted files are .sct2 .pof and .txt files.  Please confirm you are not trying to actually "open" these files in Windows Explorer.  That will result in errors as Windows doesn't know how to open .sct2 or .pof files.

Quote from: Rick Rump
Upon loading VRC: File>Open Sector File
Settings>General - Browse for POF and Alias file

This should work, if it does not, we'll have to figure something else out.

Pages: 1 ... 4 5 [6] 7 8