Walter Boyd wrote, i npart:
.......I further suspect that the controller in the original post simply doesn't realize that the rule of thumb is statue, not nautical. He should probably just be gently corrected...and I would simply ask him to measure his Class D on a TAC chart as evidence of his error.
-Walter
I just now decided to try to answer my own last-posted question, which was something like "are other ATC's mistakely using a 5 (10, or whatever) nautical mile radius as their perimeter when they're shown on FAA docs (Sectional, TAC, etc) and pilot's GPS as 5 statute miles.
So far I reached only one other (not that easy to get direct-to-control-tower phone numbers):
Klamath Falls class-D KLMT told me, as expected/hoped by-the-book, their radius is 5 statute miles, and as an aside mention that's 4.35 nautical miles.
I'll see if I can collect enough of these to make a statement about how common or rare it might be for ATC to be overreaching their airspace when believing an aircraft has entered.
I believe it's worth investigating how common this nautical-mile/statute-mile confounding of perimeter by ATC might be. If a class-C ATC were to incorectly monitor their airspace as 30 nautical miles when officially it is 30 statute miles the potential for problems would be even greater than near class-D: My iFly would be showing me a full 4 nautical miles outside their airspace .... which I'd probably view as a comfortable margin ... right at the moment ATC would be seeing me entering their airspace with neither having made radio contact nor having the required transponder. In a situation such as that, if it exists, the rule of thumb we've all agreed on here (essentially, cut yourself a mile or two of slack if you want to communicate with ATC, or just want to avoid an airspace) would be insufficient margin.
Alex