sundog
Well-Known Member
plus if i have to hear u say "maintain 2,200 until established on the localizer, cleared ILS runway 13R approach" one more time.
noo, it's ME that is fumbling through the entire approach clearance into kbfi every time.
plus if i have to hear u say "maintain 2,200 until established on the localizer, cleared ILS runway 13R approach" one more time.
I've also been chewed out by a pilot (rightly so) for issuing him an old altimeter. The altimeter was six hours old and I didn't notice. Fortunately the pilot did.
Taylor , your on the $ 99.9% of the time. While training students in VFR weather , its appropriate to teach the FAR/AIM phraseology , but in the real world , doing approaches , in busy airports down to minimums with tired pilots ,when the controllers are busy , we just click the mic. Now if its headings , altitudes etc , now thats different. You have to be able to distinguish between the two...................
I gotta also disagree with this one. I will *occasionally* double-click the mic in response, but only as a reply to unimportant transmissions from ATC like "nice job, thanks for the help". If it's in any way related to flight operations, the minimum I'll respond with is my callsign--and I try to see how often I can get away with that alone. But I always read back significant elements like headings, altitudes, etc, or to simple instructions with "wilco".Taylor , your on the $ 99.9% of the time. While training students in VFR weather , its appropriate to teach the FAR/AIM phraseology , but in the real world , doing approaches , in busy airports down to minimums with tired pilots ,when the controllers are busy , we just click the mic. Now if its headings , altitudes etc , now thats different. You have to be able to distinguish between the two...................
In this case your altimeter is overreading and you are lower than actually indicated. Bad news.Case in point. On the way to PHL(tropical storm Hanna passed by), I got ATIS, Altimeter was 2972. By the time, we got into PHL approach, it was 2942. That might not a lot difference in altitude. It could mean you can or can't made it to the runway.
On the topic of altimeter settings, a question I've always had. If I'm on V16 heading towards PSP VOR westbound, when I am handed off to a new LA Center controller, I'm given an altimeter setting for Palm Springs, which I acknowledge. Later on in the hour, still flying to PSP, I hear another pilot check on and is given a new altimeter setting for Palm Springs. This is a debate I've had, do I change my altimeter setting to reflect the new setting given to the other pilot? One of the arguments I've heard is to not update because ATC is providing seperation based off of what your transponder is reporting, so if the altimeter setting varies a few hundred feet, ATC won't be expecting that change, and it messes up their seperation. But then the other side of the debate is that you always update to the current altimeter setting. I can imagine what the answer is, but i'd like to hear it from a controller themselves.
Not based off of what they're reading on your Mode C readout?Not a controller but....WHA? Never heard that. Dial in the current setting so you're at the correct altitude; ATC's providing seperation based on where(altitude and location) they're expecting you to be.
Not based off of what they're reading on your Mode C readout?