True, the poor kid was clueless, but the controller was NOT helping the situation. Still I can kinda see why he got ticked
Another argument for georeferenced airport diagrams!
True, the poor kid was clueless, but the controller was NOT helping the situation. Still I can kinda see why he got ticked
What do you guys think about controllers in training? They make mistakes too... we shake our heads and smile and move on ;-) although, i have to admit, i seem to make mistakes more often than they do!
is there a time when a controller has absolutely nothing to do? I know there are slow times b/c I've heard them strike up short conversations with pilots, but is there ever a time when you're just staring at a screen with nothing to do?
is there a time when a controller has absolutely nothing to do? I know there are slow times b/c I've heard them strike up short conversations with pilots, but is there ever a time when you're just staring at a screen with nothing to do?
Yes especially the one cranky guy I dealt with when I was a student pilot. He yelled at me one time after I told him that I was a student pilot telling me "I don't care if you are a student pilot". What a jerk.
When the student clearly has no clue what he is doing and freakin derails...I can see how even the most patient controller can get upset.
...And they know who the student pilots are without being told. They see the same tail numbers all the time.
I did this twice at KFRG and went to KCDW instead, not as busy and not as many students :wink2: but there are controllers "in training" which sometimes makes student pilot's life not as dull
Many of us experienced pilots fly those same airplanes. I hope they can tell I have some experience!
Someday I would like to meet the controllers at my Home Base and shake their hand and tell them thanks for all their hard work.
You ought to write a book or something!Pay absolutely no attention to the controller's tone of voice. Controllers have a book of phraseology that they MUST follow, while pilots can use whatever phraseology they want to use...we have no such guidance. Suggestions, yes, requirements, no.
Just listen to what a controller says without reading anything into how it is said, and do not hesitate to ask for a repeat or say "I don't understand what you want me to do." That removes the handcuffs from the controller who can then use plain English without risking his/her job.
From their handbook:
"This order prescribes air traffic control procedures and phraseology for use by personnel providing air traffic control services. Controllers are required to be familiar with the provisions of this order that pertain to their operational responsibilities and to exercise their best judgment if they encounter situations not covered by it."
Bob Gardner
For my visits to Phoenix, I started using GEU instead of DVT when the lines of student pilots waiting to take off at the latter started to get ridiculously long. Never a wait, and I found out later that it's actually more convenient for my relatives who live in the area.
No worries, the controller can tell from your transmissions.
As you can tell from Gucci's second YT link: http://www.youtube.com/watch?v=sTZcViXWIB4
I've seen a bunch.
I've been cleared to land while on the taxiway. I've been cleared for takeoff with someone between me and the hold short line. I've been told to turn base while on a taxiway. The big one was when a controller unintentionally gave me taxi clearance and then called a possible PD when I taxied (it resolved fairly simply and just how it should have).
The first time I made an IFR departure from SQL, the departure instructions were far more complex than I had ever gotten before, and what I wrote down when I copied the clearance turned out to be too cryptic once I got in the air.
This happened yesterday after I touched down:
Tower: "Cessna three three foxtrot, I'll call your base."
Me: "Cessna three three foxtrot is on the landing rollout."
Tower: Correction, Cessna six charlie sierra, I'll call your base."
[Acknowledgement from six charlie sierra]
Tower: "Cessna three three foxtrot, contact ground, thanks!"
You ought to write a book or something!
As a VFR pilot, I'm curious what complexity they threw at you. The DP looks pretty simple -- 30 not authorized, 12 straight out to SJC VOR.
I doubt that the published DP ever gets used. (I've never heard the one for Palo Alto being used.)
Transcribed later from LiveATC:
"[Tail number], San Carlos Ground, cleared to the Half Moon Bay Airport. On departure, fly runway heading until past the diamond-shaped waterway. Then turn right heading 120. Keep your turn within two miles of the airport, for radar vectors to Woodside, direct Tails, direct. Maintain VFR conditions at or below 1,100 until crossing the Oakland 165 radial. Then climb and maintain 2,100. Expect 5,000 five minutes after departure. Norcal Departure Control frequency 135.65. [Squawk code]."
I think the ceiling was about 1,300. Runway 30 was in use.
I know. It's sitting right in front of me. Going to browse it tonight after dinner.I've got it sitting in my bookcase right now.
. I'm glad the published DP always gets used at FRG. Turn right or left heading XXX, maintain 3000. Easy.I doubt that the published DP ever gets used. (I've never heard the one for Palo Alto being used.)
Transcribed later from LiveATC:
"[Tail number], San Carlos Ground, cleared to the Half Moon Bay Airport. On departure, fly runway heading until past the diamond-shaped waterway. Then turn right heading 120. Keep your turn within two miles of the airport, for radar vectors to Woodside, direct Tails, direct. Maintain VFR conditions at or below 1,100 until crossing the Oakland 165 radial. Then climb and maintain 2,100. Expect 5,000 five minutes after departure. Norcal Departure Control frequency 135.65. [Squawk code]."
I think the ceiling was about 1,300. Runway 30 was in use.
I'm in west Texas, but if you ever plan an NHL game at Jobbing.com or NFL game ... that's the field to land. Lineman are lazy there (you're on your own for parking et al), but the counter girl(s) really went out of their way for us.
I worked 30-years for CAA/FAA in the technical side in towers, flight service stations, three different ARTCC facilities, and RAPCON. I am a private pilot also.
The thing that I find not good in tower communications (comments are re towers only) is that there is a tendency to speak at a machine gun rate. That really makes understanding more difficult, particularly when at an unfamiliar airport where things are different. Fast speech does not make a controller a 'hot shot', it makes him/her less professional in my view. In years in ARTCC I have never heard this rapid fire speech, it seems only at towers. Its done far, far, too often, even when there is no need to rush things. I have encountered this at towered airports when I was the only plane in the area.
I know this rant won't help much, but it needs to be said.
UND does a lot of training for chinese and middle eastern carriers. The students can be a bit of a challenge at times. I admire the patience the controllers in Grand Forks and Fargo have with the flood of students. But as mentioned earlier, students create 'movements' and 'movements' justify staffing. So if one of the chinese kids needs a bit of extra controller attention, it helps to maintain the traffic volume that keeps it a FAA tower.
So how do controllers keep track of tail numbers with aircraft in their airspace? Do they write them down or are they able to label the targets on their radar screens with tail number electronically. I really need to visit a tower.
So how do controllers keep track of tail numbers with aircraft in their airspace? Do they write them down or are they able to label the targets on their radar screens with tail number electronically. I really need to visit a tower.
So how do controllers keep track of tail numbers with aircraft in their airspace? Do they write them down or are they able to label the targets on their radar screens with tail number electronically. I really need to visit a tower.