PDA

View Full Version : Airspace management questions


Tuno
May 31st 07, 04:43 PM
1) I have been unable to find any kind of description of the USFIF
database (linked on the Worldwide Turnpoint Exchange web page as the
root source of Special Use Airspace (SUA) files). At this point I've
nearly given up but if anyone has any source of info they could share,
I'd most appreciate it.

In particular, something that would describe ...

2) the meaning of an airspace's effective time of "0000-1500Z++
DAILY". This is the EFF_TIMES value for a fairly new SUA near the US/
Mexico border with the SUAS_IDENT="TFR60199(1)" (there is also
"TFR60199(2)") and TYPE='T' (Temporary Reserved Airspace).

The identifier suggests it is a TFR, but I cannot find it listed with
other TFRs on other aviation web sites. I guess some TFRs are more
temporary than others.

3) The aforementioned USFIF database does not contain international
country boundaries. Since Mexico (and, I assume, Canada) are
prohibited (little 'p') airspace for US contest pilots, Winscore flags
flights that cross those boundaries. Where does it (Winscore) get its
boundary information? (My guess is one of John Leibacher's products; I
know he gets international border info from a CIA database.)

4) For that matter, where do SeeYou/Naviter and LX Navigation get
their airspace information for their respective databases? (I note
that SeeYou's latest airspace database for the USA is 2006, where all
other supported countries are 2007.)

-ted/2NO

Tuno
June 3rd 07, 04:52 AM
Keep away from children. Use only as directed. Wear appropriate
protection ...

http://www.asa-soaring.org/files/usfif2sua.pdf
http://www.asa-soaring.org/files/usfif2sua.exe

2KA
June 6th 07, 12:05 AM
I can offer no help on your questions above, but it may help to
examine the output of AIRSPACE.EXE. Of course that program no longer
works with unmodified Edition 9 USFIF files, but I have had success
running AIRSPACE.EXE by making a simple substitution on the values on
in the Shap column in BNDRY.TXT. I used a text editor to change
<TAB>B<TAB> to <TAB>H<TAB> in that file, and now AIRSPACE seems to
work OK. Evidently "B" is a new value that appears in the newer
editions that is not supported by AIRSPACE.EXE.

2KA

Google