I fly from KHWY just outside the world's safest airspace, the misguided SFRA. Inadvertent entry in to which will bring the wrath of the forces of darkness. :'( That said is it possible to increase the visability of the boundary depiction on SV? Currently it is a pale yellow and easy to miss.
DC SFRA
- Thread starter RV711AC
- Start date
dabear
New Member
Welcome to HWY. 
- Joined
- Mar 23, 2005
- Messages
- 13,226
Improving the visibility of the SFRA airspaces is something we have planned for the next software release.
Carl_Froehlich
Active Member
- Joined
- Aug 22, 2007
- Messages
- 324
Glad to see I am not the only person to get tripped up on the "almost invisible dim/thin yellow SFRA line". Luckily I had the SFRA boundary on the Garmin 396 (temporary mount for WX until the ADSB receiver come out). So - no Blackhawks for me that day.
The new bright/bold orange line you use for restricted areas works well - perhaps just use this for the SFRA.
The new bright/bold orange line you use for restricted areas works well - perhaps just use this for the SFRA.
- Joined
- Mar 23, 2005
- Messages
- 13,226
Just some background here:
The issue is that a "SFRA" or an "FRZ" are not ICAO understood airspace types. For this reason, in the data we get from the FAA, which is in the international ARINC-424 format, both the SFRA and FRZ are listed with a restricted airspace type of U: "Unspecified or Unknown". Given no obvious "correct" way to display an unknown airspace type we chose the yellow ticks. So we can't create a unique display for SFRA's since all we know is that's it's "unknown".
It appears Jeppesen doesn't even include the SFRA or FRZ in their data.
If you can get the FAA to change the designation in their data to "restricted" or "prohibited" then we'll show it like you want. Good luck with that!
The issue is that a "SFRA" or an "FRZ" are not ICAO understood airspace types. For this reason, in the data we get from the FAA, which is in the international ARINC-424 format, both the SFRA and FRZ are listed with a restricted airspace type of U: "Unspecified or Unknown". Given no obvious "correct" way to display an unknown airspace type we chose the yellow ticks. So we can't create a unique display for SFRA's since all we know is that's it's "unknown".
It appears Jeppesen doesn't even include the SFRA or FRZ in their data.
If you can get the FAA to change the designation in their data to "restricted" or "prohibited" then we'll show it like you want. Good luck with that!
- Joined
- Mar 23, 2005
- Messages
- 13,226
Here is a file that will make "unknown" areas look like restricted areas, orange with ticks. For those of you near the SFRA, can you try this out and let us know if it's reasonable? Any opinions about different colors or patterns are appreciated.
This also makes warning areas in general more visible (more orange color, more dense ticks than the old thin yellow ticks)
This also makes warning areas in general more visible (more orange color, more dense ticks than the old thin yellow ticks)
Carl_Froehlich
Active Member
- Joined
- Aug 22, 2007
- Messages
- 324
The "SRFR_WARNING_UPDATE" is just a text document. Is installing this the same as any other update?
Carl_Froehlich
Active Member
- Joined
- Aug 22, 2007
- Messages
- 324
Just loaded 5.0. Much better SFRA visibility.
Carl_Froehlich
Active Member
- Joined
- Aug 22, 2007
- Messages
- 324
DC SFRA and ADSB.
Now flying with the Dynon ADSB and 5.0 software. All is good but another tweak on the ADSB TFR display would be nice for us guys flying near DC. While you all have fixed the SFRA display from the faint dotted yellow line to now using the same bold line like a Restricted Area, the next problem to tackle is the "do not exceed 230 knot" area around DC. Right now the ADSB shades the entire 60 nm radius circle, making the map inside the circle harder to see. Recommend just having the outside 60nm radius ring displayed to solve the issue.
The Garmin 396/496 XM weather set up had this exact same problem - the whole circle being shaded. Their fix was to have an outside ring but then a set of faint dotted lines covering the inside of the circle. This worked, but for anyone flying here all we care about are the boundaries. We know what is inside the boundaries and to not piss off the Blackhawks.
Now flying with the Dynon ADSB and 5.0 software. All is good but another tweak on the ADSB TFR display would be nice for us guys flying near DC. While you all have fixed the SFRA display from the faint dotted yellow line to now using the same bold line like a Restricted Area, the next problem to tackle is the "do not exceed 230 knot" area around DC. Right now the ADSB shades the entire 60 nm radius circle, making the map inside the circle harder to see. Recommend just having the outside 60nm radius ring displayed to solve the issue.
The Garmin 396/496 XM weather set up had this exact same problem - the whole circle being shaded. Their fix was to have an outside ring but then a set of faint dotted lines covering the inside of the circle. This worked, but for anyone flying here all we care about are the boundaries. We know what is inside the boundaries and to not piss off the Blackhawks.
Thanks for the note. We'll put it on the list to consider.
Carl_Froehlich
Active Member
- Joined
- Aug 22, 2007
- Messages
- 324
Any updates to fixing the "just a big red blob" for the DC SFRA display? The red blob makes it very hard to use the moving map when flying into the SFRA. This fix is needed both for the SFRA as well as the outer 60nm radius "do not exceed 230 knots" area.
We have some ideas on how we can go about this, but, it's not likely to get in to our next software update, unfortunately.
Carl_Froehlich
Active Member
- Joined
- Aug 22, 2007
- Messages
- 324
Pinging again so that this does not get forgotten. It is very distracting to have the display pop all red shortly after takeoff from Dogwood (VA42).
RVDan
I love flying!
I have just started flying my Skyview system and am based near the SFRA (KFDK) I agree that the 60nm ring is a problem. The first problem is the lack of ability to distinguish the speed limited ring from the actual SFRA restricted airspace. The second problem comes when looking at ADS-B Nexrad. the red obscures the WX depictions. The third is that is also obscures terrain. Given the size of the SFRA. This is a real problem when trying to use the NEXRAD data or Terrain in the vicinity of the SFRA.
Wile you might think we Flat landers don't need terrain so much around the SFRA, the terrain does vary by 2000 ft inside the 60nm ring.
So add my vote for a fix on this problem ASAP.
It is interesting to note that some systems allow the user to select the transparency of the TFR overlays . That would solve the WX and terrain problems
Dan
Wile you might think we Flat landers don't need terrain so much around the SFRA, the terrain does vary by 2000 ft inside the 60nm ring.
So add my vote for a fix on this problem ASAP.
It is interesting to note that some systems allow the user to select the transparency of the TFR overlays . That would solve the WX and terrain problems
Dan
- Joined
- Mar 23, 2005
- Messages
- 13,226
You can actually edit the shading and color of the TFRs in SkyView. You have to edit a file on a computer, but it's not hard. We can help you if that's useful.
The issue is this will change it for ALL TFR's. The FAA sends the DC stuff just like any other "Temporary" flight restriction. So the fire TFR in CA will have the same change.
You can also turn them off right inside the user interface inside SkyView. It's an option to tun them off while you are inside the area and turn them on when you fly out.
We do still hope to make all this better eventually, or you could
The issue is this will change it for ALL TFR's. The FAA sends the DC stuff just like any other "Temporary" flight restriction. So the fire TFR in CA will have the same change.
You can also turn them off right inside the user interface inside SkyView. It's an option to tun them off while you are inside the area and turn them on when you fly out.
We do still hope to make all this better eventually, or you could
dabear
New Member
Editing the shading or turning off TFRs doesn't help when flying in the DC SFRA. Shading still covers airports, intersections, towers, altitudes (class B), etc. Removing TFRs means you don't know where the speed ring, SFRA, or FRZ is. Neither is a good option.
I flew in it the SFRA other day and had problems because I didn't know where the FRZ and the SFRA boundaries were located. I frequently fly in the SFRA.
I flew in it the SFRA other day and had problems because I didn't know where the FRZ and the SFRA boundaries were located. I frequently fly in the SFRA.
- Joined
- Mar 23, 2005
- Messages
- 13,226
I think we are getting some things confused.
1) The SFRA is in the aviation database and you don't need ADS-B to see it. As mentioned earlier in this thread, which started out before we had ADS-B, it's an "unknown" airspace. It shows up as orange with ticks, and has no interior shading. I'm no expert on DC's airspace but there is a large ring and a smaller one inside depicted so I think everything you want is there. Unless you turn off UNKNOWN airspaces, you will see this. We do not consider this a TFR because it is not marked as so.
2) If, and only if you have ADS-B, you will also get TFR's. These will show up in red with red shading inside. You have options for these:
A) Turn them off. This will not affect #1 and you will still see the orange outline. You can do this right in SkyView's menus.
B) Edit the file to reduce or even eliminate the shading, change the color, etc. You can turn off the shading and retain the outline if you want. This requires editing a file with a PC. Again, this will not change #1.
A or B will do this for all TFR's. Sorry, but the FAA doesn't transmit anything special for the DC TFR's, they just call them a TFR like all others. Due to that there isn't a perfect path for us to do something special with the DC TFR (and that's what it is to us) without a lot of work. It's on our list, like a thousand (literally) other things.
1) The SFRA is in the aviation database and you don't need ADS-B to see it. As mentioned earlier in this thread, which started out before we had ADS-B, it's an "unknown" airspace. It shows up as orange with ticks, and has no interior shading. I'm no expert on DC's airspace but there is a large ring and a smaller one inside depicted so I think everything you want is there. Unless you turn off UNKNOWN airspaces, you will see this. We do not consider this a TFR because it is not marked as so.
2) If, and only if you have ADS-B, you will also get TFR's. These will show up in red with red shading inside. You have options for these:
A) Turn them off. This will not affect #1 and you will still see the orange outline. You can do this right in SkyView's menus.
B) Edit the file to reduce or even eliminate the shading, change the color, etc. You can turn off the shading and retain the outline if you want. This requires editing a file with a PC. Again, this will not change #1.
A or B will do this for all TFR's. Sorry, but the FAA doesn't transmit anything special for the DC TFR's, they just call them a TFR like all others. Due to that there isn't a perfect path for us to do something special with the DC TFR (and that's what it is to us) without a lot of work. It's on our list, like a thousand (literally) other things.
RVDan
I love flying!
I" ll get some screen shots of what we see if that helps. I think that the other issue that was brought up is the FRZ which is well inside the SFRA and requires the pilot to have their name on a cleared list to fly inside. Even though you can get cleared into the SFRA, the FRZ may be off limits. Essentially the SFRA is where they will chase you down, the FRZ is where they shoot first and ask questions later .
And none of this coincides with the Class B airspace. There is a narrow corridor ( about 3 miles) in between the DCA class B and BWI class B, inside the SFRA and outside the FRZ that has to be clearly seen on a moving map to follow without violating someones airspace.
With the SFRA being solid red it is very difficult to see these boundaries.
I am interested in modifying the file on the computer to make this better. Called Dynon, but no one knows who I need to talk to. Could you please provide a contact?
Thanks,
Dan
T
. And none of this coincides with the Class B airspace. There is a narrow corridor ( about 3 miles) in between the DCA class B and BWI class B, inside the SFRA and outside the FRZ that has to be clearly seen on a moving map to follow without violating someones airspace.
With the SFRA being solid red it is very difficult to see these boundaries.
I am interested in modifying the file on the computer to make this better. Called Dynon, but no one knows who I need to talk to. Could you please provide a contact?
Thanks,
Dan
T