![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
On Nov 28, 5:08 am, "Steven P. McNicoll"
wrote: "Dan" wrote in message ... That's one way to look at it. However fortunately in this case the weather was clear and there were probably minimal safety issues. If pilots give ATC some slack when needed, hopefully they'll be nice when the pilots mess up. He did eventually get the clearance straightened out. Nobody's perfect, and as long as we all realize and learn from mistakes, I don't see why there's a need to be anal about it. It's a two-way street. Why does ATC need some slack in this case? Ground control knew he was IFR, that controller issued an IFR clearance and taxi instructions to the OP. Presumably the ground controller passes a flight strip to the local controller on all departures that shows the aircraft to be IFR or VFR. This is about as basic as it gets in ATC, there's no excuse for this error and certainly no excuse for compounding it by asking the OP to squawk VFR after departure. Agreed, ATC completely screwed up. My point was only this - suppose you bust an altitude because you were distracted, etc. If it didn't cause a loss of seperation, would you rather the controller said, "please check your altitude" or "please call this number when you land to discuss FAA administrative action." In this scenario, the tables were turned. Let's treat ATC how we would like to be treated. Nobody is perfect all of the time. It's just a question of how to handle things when someone does occasionally screw up. --Dan |
#2
|
|||
|
|||
![]() "Dan" wrote in message ... Agreed, ATC completely screwed up. My point was only this - suppose you bust an altitude because you were distracted, etc. If it didn't cause a loss of seperation, would you rather the controller said, "please check your altitude" or "please call this number when you land to discuss FAA administrative action." I'd rather the former, and that tends to be the case where no loss of separation has ocurred. In this scenario, the tables were turned. Let's treat ATC how we would like to be treated. Nobody is perfect all of the time. It's just a question of how to handle things when someone does occasionally screw up. I don't have an issue with the initial error, the controller not knowing the guy was IFR. I have an issue with the controller trying to cover up that error. |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
CAI 302 Utility program confusion | Frank[_1_] | Soaring | 1 | March 30th 07 03:57 AM |
Confusion about when it's my navigation, and when it's ATC | Mxsmanic | Piloting | 258 | January 18th 07 11:52 PM |
Confusion about when it's my navigation, and when it's ATC | Mxsmanic | Instrument Flight Rules | 332 | January 18th 07 11:52 PM |
Confusion Plus | Kevin Berlyn | Home Built | 1 | March 6th 05 06:40 AM |
confusion | G.A. Seguin | Soaring | 0 | July 14th 04 12:08 AM |