mtsu_av8er
Well-Known Member
If you are flying for a company that gets your flight plans through the PDC, then at ORD, metering is the initial contact.
Ah-ha! Now, that makes sense . . . thanks!
If you are flying for a company that gets your flight plans through the PDC, then at ORD, metering is the initial contact.
I always say I have the current info on ground also. Heres a question for the group. The other day I pull up to the non-movement line and call ground for taxi with the current info. It was near the top of the hour so it had just changed. I was "cleared to taxi and advise when you have XXXX." Me and my student taxi to the runup area, and I just switched to ATIS freq before the runup to get the current. Being a class D airport I guess I was in the wrong to not request a frequency change in the runup area. Anyway we taxied to the hold short gave tower the info and so on. Out of the runup area we don't have to say anything else to ground so I just told tower when we were number 1 & we had XXXX. I told my student that it was a oops on my part, and they should always request a freq change to be safe and by the book. Two way communictation and all.....or am I just being to anal? :dunno:
Shouldn't need to talk to ground anymore in the runup area. From what you describe, it was a normal changeover to local point anyway.
I always say I have the current info on ground also. Heres a question for the group. The other day I pull up to the non-movement line and call ground for taxi with the current info. It was near the top of the hour so it had just changed. I was "cleared to taxi and advise when you have XXXX." Me and my student taxi to the runup area, and I just switched to ATIS freq before the runup to get the current. Being a class D airport I guess I was in the wrong to not request a frequency change in the runup area. Anyway we taxied to the hold short gave tower the info and so on. Out of the runup area we don't have to say anything else to ground so I just told tower when we were number 1 & we had XXXX. I told my student that it was a oops on my part, and they should always request a freq change to be safe and by the book. Two way communictation and all.....or am I just being to anal? :dunno:
This is what controllers are responsible for:
From the Good Book 7110.65 Chapter 3, Section 9
Section 9. Departure Procedures and Separation
3-9-1. DEPARTURE INFORMATION Provide current departure information, as appropriate, to departing aircraft.
a. Departure information contained in the ATIS broadcast may be omitted if the pilot states the appropriate ATIS code.
b. Issue departure information by including the following:
1. Runway in use. (May be omitted if pilot states “have the numbers.”)
2. Surface wind from direct readout dial, wind shear detection system, or automated weather observing system information display. (May be omitted if pilot states “have the numbers.”)
3. Altimeter setting. (May be omitted if pilot states “have the numbers.”)
Don't worry Tower Flowers, the Center guy has you covered on a chapter we don't even use in the Z's.
I don't if I've already given it to Clearance Delivery.
(basic 5 w's...you're cracking me up dood. Wait. I'm too old to say "dood".)
Get in the habit of telling the ground controller of the ATIS code because it is their responsibility to ensure that you have the proper ATIS, not clearance delivery.
:yeahthat: At DPA, if you don't tell CD you have information XX they will query you."advise on INITIAL contact you have _____"
So if there is a CD, I give the letter to them and not ground, however, if there is only a ground control, then they are my initial contact so they would get the code.
Same deal with approach/tower considerations.
:yeahthat: At DPA, if you don't tell CD you have information XX they will query you.