xc tool.

Hi All,

As a long time lurker I have learning and gained much from this group,
now hopefully I can contribute some. I have written a tool that you may
find useful. It came about because my wife did not like me asking her
to lookup freq. and airport info while flying together. I'm a newly
minted ppasel and would rather fly than have my head down looking for
information. The tool takes a from and to airport code and will
calculate all airports and navaids along the path of the flight and
print the basic information about them. It takes a 20nm path for
airports and a 50nm path for navaids. They are presented in the order
that they will be encountered. You can give it a try he

http://arion.doit.wisc.edu/cgi-bin/flightplan.cgi
username/password is guest/guest

Questions, comments or suggestion are welcome.

Todd Neidinger

remove the no and spam from the return email address.

"Todd Neidinger" wrote in message
...
Hi All,

As a long time lurker I have learning and gained much from this group,
now hopefully I can contribute some. I have written a tool that you may
find useful. It came about because my wife did not like me asking her
to lookup freq. and airport info while flying together. I'm a newly
minted ppasel and would rather fly than have my head down looking for
information. The tool takes a from and to airport code and will
calculate all airports and navaids along the path of the flight and
print the basic information about them. It takes a 20nm path for
airports and a 50nm path for navaids. They are presented in the order
that they will be encountered. You can give it a try he

http://arion.doit.wisc.edu/cgi-bin/flightplan.cgi
username/password is guest/guest

Questions, comments or suggestion are welcome.

Wow! What do you use for a database?

Allen


Todd Neidinger

remove the no and spam from the return email address.

Todd Neidinger wrote:

Questions, comments or suggestion are welcome.

Not bad at all. Because of the need to get around the Washington ADIZ, I would like
to see this accept one optional waypoint, but it's very nice as it is. I can always
break my flight plans into two separate legs (as I do now).

Thanks.

George Patterson
In Idaho, tossing a rattlesnake into a crowded room is felony assault.
In Tennessee, it's evangelism.

Thanks Todd!

On Wed, 21 Jul 2004 11:33:34 -0500, Todd Neidinger wrote:

http://arion.doit.wisc.edu/cgi-bin/flightplan.cgi
username/password is guest/guest

Awesome job Todd. This one is a keeper!!!

Allen

"Todd Neidinger" wrote in message
...
Hi All,


http://arion.doit.wisc.edu/cgi-bin/flightplan.cgi
username/password is guest/guest

Questions, comments or suggestion are welcome.


Nice.

Question/Issue: I put in HPN-UCA and it gave a distance of 168 NM but
Airnav gives a distance of 145.3 NM (the Garmin 530 simulator gives 145
also).

Well, I'm impressed. Going on a 700nm cross country Friday morning
and will have to take this print out with me.
Good job.


Scott D.


On Wed, 21 Jul 2004 11:33:34 -0500, Todd Neidinger
wrote:

Hi All,

As a long time lurker I have learning and gained much from this group,
now hopefully I can contribute some. I have written a tool that you may
find useful. It came about because my wife did not like me asking her
to lookup freq. and airport info while flying together. I'm a newly
minted ppasel and would rather fly than have my head down looking for
information. The tool takes a from and to airport code and will
calculate all airports and navaids along the path of the flight and
print the basic information about them. It takes a 20nm path for
airports and a 50nm path for navaids. They are presented in the order
that they will be encountered. You can give it a try he

http://arion.doit.wisc.edu/cgi-bin/flightplan.cgi
username/password is guest/guest

Questions, comments or suggestion are welcome.

Todd Neidinger

remove the no and spam from the return email address.

Nice program, Todd.


"Todd Neidinger" wrote in message
...
Hi All,

As a long time lurker I have learning and gained much from this group,
now hopefully I can contribute some. I have written a tool that you may
find useful. It came about because my wife did not like me asking her
to lookup freq. and airport info while flying together. I'm a newly
minted ppasel and would rather fly than have my head down looking for
information. The tool takes a from and to airport code and will
calculate all airports and navaids along the path of the flight and
print the basic information about them. It takes a 20nm path for
airports and a 50nm path for navaids. They are presented in the order
that they will be encountered. You can give it a try he

http://arion.doit.wisc.edu/cgi-bin/flightplan.cgi
username/password is guest/guest

Questions, comments or suggestion are welcome.

Todd Neidinger

remove the no and spam from the return email address.

http://arion.doit.wisc.edu/cgi-bin/flightplan.cgi
username/password is guest/guest

That's awesome!

Here are some suggestions that came to mind:

Can you add the little morse code identifiers for the navaids? After
all, we should all be identifying our navaids, right?

On the front page, you could add a few more user options for what to
show or not show... like a box to check if you want NDB's (if your plane
is so equipped), and a box to check if you want runway lights (if you're
flying at night). Another spacesaver might be: to check whether CTAF
and Unicom are the same frequency, and to list them together as
CTAF/Unicom if they are. Same with CTAF/Runway lights and Tower/Runway
lights, which are often the same.

--Kath