(USA, Arizona) Luke SATR now contained in FAA NFD

[Tuno]

As promised, the Luke SATR has appeared in the 201006 edition of the
National Flight Database.

Important note: justsoar.com morphs the NFD entry from Restricted type
Unspecified/Other to Controlled, Class D. So, to get the SATR in your
airspace file(s), you must include the "Class D" in your selections.
This transposition is done because the new Part 93 rules for this SATR
read just like Class D -- two-way radio communication is required for
entry.

Straying way off topic, the last day at Region 9 South, we had a young
pilot flying a Zuni II in his first contest who lost aileron control
at 8000' while still in the start cylinder. He took the time to
evaluate the situation carefully, and eventually landed the glider
safely at Pinal Airpark (a few miles north of El Tiro) using rudder
and elevator only. Nice work Eric!

~ted/2NO

[Andy[_1_]]

On May 17, 3:57*pm, Tuno > wrote:
> As promised, the Luke SATR has appeared in the 201006 edition of the
> National Flight Database.

I wonder if this means that Garmin will include the SATR area in the
next cycle of their databases.

The following is extracted from a Deer Valley Airport Pilot's
Association brief:

SATR Missing in GPS Database - As many of you have already found out,
the SATR does not appear in the new Garmin database updates. One of
our DVPA members queried Garmin on it not being there and following is
the Garmin response ---


“The Special Air Traffic Rule that is in effect starting 6 May 10 has
been reviewed by our standards department and we will NOT be capturing
this area in our database at this time.

This area applies to VFR acft operations only and outlines the
communication requirements that are needed within this area between
VFR operations and Luke Apch Control.

Also as you note, this doesn't fit cleanly into any existing SUA type
for ARINC.”

[Tuno]

< Also as you note, this doesn't fit cleanly into any existing SUA
type for ARINC >

Yes and no. The ARINC specification provides a "Unspecified/other"
category for restricted airspaces, under which the Luke (and other)
SATRs are described. For every rule there's going to be exceptions,
hence U/O.

The Part 93 components are going to be like that -- no doubt why they
are in Part 93. Look at the Grand Canyon airspace -- the only Class E
on the map you can't fly in.