From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: *** X-Spam-Status: No, score=3.4 required=5.0 tests=BAYES_50,INVALID_DATE, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Newsgroups: comp.lang.ada Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!pmafire!mica.inel.gov!wdo From: wdo@INEL.GOV (william d orr) Subject: Re: Copenhagen Air Traffic Control System Message-ID: <1991Jun25.175213.24762@inel.gov> Sender: news@inel.gov Reply-To: wdo@deary.UUCP (william d orr) Organization: Idaho National Engineering Laboratory, Idaho Falls, Idaho References: <3347@sparko.gwu.edu> <1991Jun24.134926.11913@sctc.com> <3359@sparko.gwu.edu> Date: Tue, 25 Jun 91 17:52:13 GMT List-Id: >>mfeldman@seas.gwu.edu (Michael Feldman) writes: >> > >I hope it was clear that my "bottom line" was sarcastic. I find myself >wondering how the Europeans managed to develop a working, installed ATC >system in Ada while the FAA system just drags along. The European airports >seem progressively to be adopting versions of the Thomson system. Taken as >a whole, European air traffic is not signficantly less voluminous than >American traffic - Paris, London, Amsterdam, and Frankfurt are _very_ >busy places, and they'd all fit into the American East. > >A recent posting expressed concern that the FAA system will never be >completed. What's holding it up? Maybe we should just adopt the European >system (if it were politically possible, which I'm sure it's not). >Can anybody enlighten us here? Where are we going wrong? > >Mike Mike I am not defending the FAA system on this but there are several fundamental differences between stateside air traffic control and that in Europe. The system that the FAA is envisioning will reduce the number of enroute air traffic control centers (now called ARTCC) by at least a factor of 3. With each Area Control Facility not only handling the traffic of 2 to 5 ARTCC enroute facilities but also the terminal traffic of almost all terminal facilities as well. The goal here is to allow the ACF to also replace most terminal Radar Approach Control facilites as well. To meet this goal will require a lot more than just new software but also implem entation of new technology in data links directly to airborne aircraft control systems to replace verbal commands that are now given to pilots by radio. Add to this new software to automate such critcal elements as aircraft separation by altitude, airspeed and automated sequencing of aircraft in the terminal area and you have a monumental task for any computer system in any language. Compare our environment to that of Europe and you see the ICAO air traffic control structure to be quite simialar but still different. In ICAO most countries have few enroute facilities to interface (often only one or two) vs the many we have in the states. So the enroute air traffic structure tends to be more similar to terminal to terminal air traffic using enroute procedures than the system we use where several to many enroute facilities will handle most enroute aircraft. I also have no idea whether the current air traffic control upgrades in Europe are also combining enroute and terminal facilities as our National Airspace Plan intends to do. I suspect not. After 20 years as an air traffic controller in our military both stateside and overseas, I see the NAS plan to be a logical but very ambitious plan. Perhaps the NAS plan may be a little too abitious even though it's implementation has slipped from the year 2000 to at least 2010. I hope these details are enlightening and wish to add my belief that both the US and ICAO systems are needed and I am very glad that they are under way Bill ========== long legal disclaimer follows, press n to skip =========== Neither the United States Government or the Idaho National Engineering Laboratory or any of their employees, makes any warranty, whatsoever, implied, or assumes any legal liability or responsibility regarding any information, disclosed, or represents that its use would not infringe privately owned rights. No specific reference constitutes or implies endorsement, recommendation, or favoring by the United States Government or the Idaho National Engineering Laboratory. The views and opinions expressed herein do not necessarily reflect those of the United States Government or the Idaho National Engineering Laboratory, and shall not be used for advertising or product endorsement purposes.