ATC question

[LewisU_Pilot]

Read this on another board.

"Appearantlly if you deviate more then 300ft from your assigned altitude, warnings automatically go off in ATC and I guess that is a really big deal.

Anyways, I hear the big deal about it is if those warnings go off at ATC for not being at the proper altitude, regardless of the lack of traffic, that it automatically gets reported to the FAA and shiat creating a bit of a mess"

Being the great instrument pilot that I am and have never had any problems with altitude. Is there any truth behind this?

 

[greygoose]

Partly true, they do report to you at 300ft. But it doesnt go to the FAA automatically. Had it happen the other day, controller fault flew into an arear were the pressure dropped dramatically from where I came from. ATC reported your 300ft off gave current altimeter setting no big deal.

 

[zbwmy]

Here at the Center you can fly all day long at +/- 299ft and we will never see it. Once you break 300ft our display shows 300ft high or low. We usually assume it is a bad altimeter setting and issue a new altimeter setting to see if that makes it go away. In flight levels we ask you to check your altitude. Unless the "snitch machine" goes off saying you came within less than 1000ft of another aircraft, no one is going to report you.

 

[FN FAL]

Being the great instrument pilot that I am and have never had any problems with altitude.

Trust in haste...regret at your leisure.

Some day you'll be flying along on a 135 flight, hit the altitude hold button to level out your climb, then get busy on some paperwork. Next thing you know, you'll get a call from center..."XYZ 9'r 9'r, say your altitude!"

It'll happen.

 

[greygoose]

Thats happened, set up the autopilot but forgot to hit the arm.

 

[Vector4fun]

"Appearantlly if you deviate more then 300ft from your assigned altitude, warnings automatically go off in ATC and I guess that is a really big deal.

Anyways, I hear the big deal about it is if those warnings go off at ATC for not being at the proper altitude, regardless of the lack of traffic, that it automatically gets reported to the FAA and shiat creating a bit of a mess"

If your mode C is off by 300' or more, we'll issue the current altimeter and ask you to check altitude. If that doesn't fix the problem, and your Mode C is really off by that amount or more, we'll ask you to turn it off. It really IS a big deal, because you could be setting off TCAS RAs for no reason. Happens when they're 200' off anyway. Then there is a form the Supes fill out for bad transponders and/or Mode C. If it's just a bit over the limit, (probaby just an adjustment to the encoder) they'll often "forget". But if it's really off, they'll do the form, and it goes to FSDO eventually I believe. Expect a FSDO-gram telling you to get it fixed.

Amazingly, I very often have to remind VFR pilots they need an accurate, operating Mode C to operate above 10K. I can authorize a temporary deviation in MY airspace, but not the next several sectors. But then again, those who don't do transponder/static system checks aren't the kind to crack the books often either...

If you really are off altitude and set off the "snitch-patch" at a Center, or cause an RA or some other conflict avoidance in a terminal environment, that will often cause a report, of course.

 

[User546]

Anyways, I hear the big deal about it is if those warnings go off at ATC for not being at the proper altitude, regardless of the lack of traffic, that it automatically gets reported to the FAA and shiat creating a bit of a mess"

I guess that COULD happen, but almost all ATC'ers are considerate and understanding enough to query "X123AB, say altitude..." And as long as you aknowledge wha altitude you SHOULD be at, and correct it quickly nothing more is ever said. I see it as a friendly reminder.