Digital airspace data question -- any FAA data gurus out there?

[Tuno]

I have a software project that uses the FAA NACO (charting office)'s
National Flight Database (NFD) as a source for controlled and
restrictive airspace data. It works great, BUT ...

The Controlled Airspace (UC records) only include classes B, C and
D ...

The Restrictive Airspace (UR records) include all the Alert/Danger/MOA/
Prohibited/Restricted/etc zones I expect to see ...

.... but NONE of the above include the Class E no-fly zones over the
Grand Canyon that are described in FAR 93.305.

Are the Grand Canyon no-fly zones considered temporary?

Are they described anywhere outside of FAR 93.305?

-ted

[Larry Dighera]

On Sat, 22 Dec 2007 09:30:17 -0800 (PST), Tuno >
wrote in
>:

>I have a software project that uses the FAA NACO (charting office)'s
>National Flight Database (NFD) as a source for controlled and
>restrictive airspace data. It works great, BUT ...
>
>The Controlled Airspace (UC records) only include classes B, C and
>D ...
>
>The Restrictive Airspace (UR records) include all the Alert/Danger/MOA/
>Prohibited/Restricted/etc zones I expect to see ...
>
>... but NONE of the above include the Class E no-fly zones over the
>Grand Canyon that are described in FAR 93.305.
>
>Are the Grand Canyon no-fly zones considered temporary?
>
>Are they described anywhere outside of FAR 93.305?
>
>-ted


As a starting point, without venturing into the FAA quagmire, I
suggest you pose your inquiry to Mr. Wally Roberts:
. He should be able to point you in the right
direction.

CC: Wally Roberts

[WJRFlyboy]

In article <dc3f4157-f7da-4668-9e41-
>, says...
> I have a software project that uses the FAA NACO (charting office)'s
> National Flight Database (NFD) as a source for controlled and
>restrictive airspace data. It works great, BUT ...

When you say "project" are you designing/coding?