On Tue, 25 Oct 2005 10:55:40 GMT, "Steven P. McNicoll"
wrote:


"Nathan Young" wrote in message


Upon initial contact from the aircraft, the controller, should be able
to key the N-number into a database and see if there is a flightplan
available. In this manner, each controller would have access to each
flightplan, but only as they need it.


Only as they need it? How does the computer know what controller needs
access to the flight plan at any moment?

It would not have to know that, it is a reply/request based system.
The controller (client) would type in an N-number (the request), and
the server replies with flightplans on file for that N-number.

Security and redudancy issues aside, I could have something like this
running on SQL and webconfigured in less than a week.

But those are rather important issues.

Yes, they are. My point was not to replace the current ATC system
with something I hack together in 1 week.

What am I missing? I am eager to learn how the current system works.
What do you want to know?

I know so little about the current system, that I do not know where to
begin. Do you have a link to documents or websites which would
explain how FSS and ATC enter, share, and track flightplans - ideally
in a few pages, not a 400page technical document?

However, I will start with a few questions:

1. If I file an IFR with 1800WXBrief, what happens to that
information? Does it go to a nationwide database? From discussion
the in this thread, I gather it only is sent to controllers
responsible for the departure airport, or perhaps controllers for
nearby airspaces.

2. How does ATC communicate with adjacent Center/Approach facilities?
Is this a leased phone line arrangement? Do you dial a number or just
pick up the appropriate phone for each location?

3. When a facility hands off to another facility how does the info on
the strip get from the first controller to the 2nd?

If any Chicago area controllers are lurking and are interested in
providing a tour to your facility - feel free to email.

Nathan