Is this a plotting error or do these airspace restrictions really not track with the overlaying airspace?
Just browsing https://www.1800wxbrief.com/Website/interactiveMap and noticed this NOTAM for an airshow coming up in a couple days
It's not shown to be concentric with the airport's class D
This TFR is defined as a 5NM radius based on a point defined on a radial from the CRG VOR
As a standard class D airspace is a little less than 5nm radius so I suppose KNIP is probably non-standard so that would explain it being slightly smaller
But why not just define the TFR based on the Class D...or at least the class D's center point?
(seems like it would just be easier and generally safer to NOTAM the KNIP airspace but up to the higher altitude)
OR
Is it?...and this is just sloppy plotting error?
I've noticed this before with TFR's so I've been curious about the logic or lack thereof for a while now.
on skyvector it looks like this...pretty much the same
Just browsing https://www.1800wxbrief.com/Website/interactiveMap and noticed this NOTAM for an airshow coming up in a couple days
It's not shown to be concentric with the airport's class D
This TFR is defined as a 5NM radius based on a point defined on a radial from the CRG VOR
As a standard class D airspace is a little less than 5nm radius so I suppose KNIP is probably non-standard so that would explain it being slightly smaller
But why not just define the TFR based on the Class D...or at least the class D's center point?
(seems like it would just be easier and generally safer to NOTAM the KNIP airspace but up to the higher altitude)
OR
Is it?...and this is just sloppy plotting error?
I've noticed this before with TFR's so I've been curious about the logic or lack thereof for a while now.
on skyvector it looks like this...pretty much the same