Redesigning Air Traffic Control
<P>Redesigning Air Traffic Control</P><P>**** Hidden Message *****</P> 1<BR>1<BR>Redesigning Air Traffic Control<BR>Workshop Session 1:<BR>Airspace, Procedures, and Flight Plans<BR>September 21, 2000<BR>Michelle Eshow<BR>NASA Ames Research Center<BR><A href="mailto:meshow@lcs.mit.edu">meshow@lcs.mit.edu</A> / <A href="mailto:meshow@arc.nasa.gov">meshow@arc.nasa.gov</A><BR>2<BR>Outline<BR>u Motivation for ATC R&D<BR>u ATC Structure, Facilities<BR>u Airspace<BR>u Controller Roles and Responsibilities<BR>u Delay Causes<BR>u Flight Plans and Route Processing<BR>u Challenges of Automation for ATC<BR>2<BR>3<BR>Motivation for ATC Automation R&D<BR>u ATC system is already beyond its capacity. But FAA<BR>predicts that by 2010 the number of passengers will rise<BR>59%, to 1 billion/year. Nothing on the drawing board<BR>will handle this increase. (NY Times, 09/05/00)<BR>u ATC system is very complex and hard to understand,<BR>analyze, or quantify, which makes it interesting!<BR>u Current level of automation is rudimentary compared<BR>with other systems (eg, aircraft flight control systems)<BR>u Application of usable automation to ATC is required to<BR>meet air travel demands<BR>4<BR>National Airspace System<BR>u Handles: 63,000,000 Tower Assisted Operations<BR>u Carries: 544,000,000 Passengers<BR>u Over: 537,000,000,000 Revenue Passenger Miles<BR>u Using: 18,700 Air Carrier A/C<BR>F 170,000 General Aviation A/C<BR>u Supported by: 639,000 Pilots<BR>F 651,000 Non-pilots<BR>u Burning: 18,000,000,000 Gallons of Fuel<BR>u Generating: $87,000,000,000 Revenues<BR>u Producing: $5,300,000,000 Profit<BR>u In Spite of: $3,500,000,000 in Delays<BR>3<BR>5<BR>FAA Statistics<BR>u Employs: 48,000 People<BR>u Including: 17,000 Air Traffic Controllers<BR>u Operating: 21 Centers<BR>F 194 TRACONs<BR>F 476 Towers<BR>F 1 Command Center<BR>u Costing: $9,200,000,000 Annual Outlay<BR>6<BR>Functions of Air Traffic Management<BR>u Air Traffic Control:<BR>u Efficiently manage traffic flow<BR>u Provide flight information (weather, facility)<BR>u Initiate search and rescue operations<BR>Maintain legal separation among aircraft<BR>4<BR>7<BR>ATC Basics<BR>u Airline flights are under positive control at all times<BR>u Control is effected by voice via radio<BR>u Control is handed off from one controller/facility to<BR>another as flight proceeds across boundaries<BR>F controller directs pilot to speak to next facility on a different<BR>radio frequency<BR>u Communications include:<BR>F speed, heading, altitude instructions (vectors)<BR>F notification of other aircraft<BR>F which course or runway to expect<BR>F contact next facility on new frequency<BR>8<BR>ATM Tactical Information Architecture<BR>Future Controller<BR>Airline<BR>Dispatch<BR>AOC<BR>Active Controller<BR>Host Computer and ATC Information Network<BR>Flight Crew<BR>Voice<BR>ACARS<BR>Flight Plan<BR>OAG<BR>Flight Plan<BR>Voice<BR>DA’s<BR>Procedures<BR>Flight Strips, Flight Information Object<BR>Slide courtesy of Prof. J. Hansman<BR>5<BR>9<BR>ATC Facilities<BR>u Surface (“Ground”)<BR>F taxiways<BR>u Local Control (“Tower”)<BR>F surface to ~5 nm out, 2500 ft altitude<BR>u Terminal Area Control/TRACON (“Approach” or<BR>“Departure”)<BR>F to ~40 nm from airport, ~15K ft altitude (inverted wedding cake)<BR>u En-Route Control/ARTCC (“Center”)<BR>F between, above TRACONs and everything above 18K ft<BR>u Flow Control/ATC Systems Command Center<BR>F centralized planning for national flow control (does not directly<BR>control flights)<BR>10<BR>Air Traffic Control System<BR>ATCT ATCT<BR>ARTCC<BR>(Center)<BR>TRACON TRACON<BR>TMU<BR>6<BR>11<BR>US Airspace Sector Structure<BR>Slide courtesy of Prof. J. Hansman<BR>12<BR>Air Route Traffic Control Center (ARTCC)<BR>A facility established to provide air traffic control service to aircraft operating on IFR<BR>flight plans within controlled airspace and principally during the en route phase of<BR>flight. At some airports not served by an Approach Control facility, the ARTCC<BR>provides limited approach control service. When equipment capabilities and controller<BR>workload permit, certain advisory/assistance services may be provided to VFR aircraft.<BR>Air Traffic Control Manual Order 7110.65<BR>Pilot/Controller Glossary<BR>Seattle<BR>ZSE<BR>Oakland<BR>ZOA<BR>Los Angeles<BR>ZLA<BR>Salt Lake City<BR>ZLC<BR>Minneapolis<BR>ZMP<BR>Denver<BR>ZDV<BR>Albuquerque<BR>ZAB<BR>Kansas City<BR>ZKC<BR>Ft. Worth<BR>ZFW<BR>Houston<BR>ZHU<BR>Chicago<BR>ZAU<BR>Memphis<BR>ZME<BR>Atlanta<BR>ZTL<BR>Indianapolis<BR>ZID<BR>Jacksonville<BR>ZJX<BR>Miami<BR>ZMA<BR>Washington<BR>ZDC<BR>Cleveland<BR>ZOB<BR>New York<BR>ZNY<BR>Boston<BR>ZBW<BR>Anchorage<BR>ZAN<BR>Honolulu CERAP<BR>ZHN<BR>Guam CERAP<BR>ZUA<BR>San Juan CERAP<BR>ZSU<BR>21 ARTCCs<BR>3 CERAPs (combined Center RAPCONs)<BR>7<BR>13<BR>Airspace Orientation<BR>FL 230 & Below<BR>Fort Worth ARTCC<BR>18 Low Altitude Sectors<BR>14<BR>Airspace Orientation<BR>FL 240 & Above<BR>Fort Worth ARTCC<BR>15 High Altitude Sectors<BR>LBB<BR>MAF<BR>8<BR>15<BR>Super High Sectors<BR>High Sectors<BR>Low Sectors<BR>Approach<BR>Control<BR>FL350 and above<BR>FL240 to FL330<BR>VFR TWR<BR>or<BR>Uncontrolled<BR>FL230 and below<BR>16<BR>TRACON Video Map<BR>9<BR>17<BR>TRACON SECTOR<BR>DELEGATED AIRSPACE<BR>TRACON Sector Delegated Airspace<BR>18<BR>Special Use Airspace<BR>u Alert Area<BR>u Air Traffic Control<BR>Assigned Airspace<BR>u Controlled Firing Area<BR>u Military Operating Area<BR>u Prohibited Area<BR>u Restricted Area<BR>u Warning Area<BR>10<BR>19<BR>Possum Specialty<BR>Glen Rose Specialty<BR>Bowie<BR>Specialty<BR>Cedar Creek<BR>Specialty<BR>Quitman<BR>Specialty<BR>Bonham<BR>Specialty<BR>Frisco<BR>Specialty<BR>Facility Organization<BR>Fort Worth ARTCC<BR>7 Areas of Specialization<BR>20<BR>Center Controllers<BR>u Each sector has a team of 1 to 3 controllers assigned<BR>F safely and efficiently move traffic along their planned routes<BR>F merge, setup flights for delivery to next facility<BR>F must get/give permission to hand-off/receive aircraft<BR>u In quiet periods, contiguous sectors may be combined<BR>u Each Area has an Area Supervisor<BR>u In Traffic Management Unit, Traffic Management<BR>Coordinators make strategic decisions about flows<BR>F eg, based on weather and available runways, set TRACON<BR>arrival rates (aircraft/hour)<BR>F coordinate flow parameters with adjacent facilities<BR>11<BR>21<BR>ARTCC ATC Positions<BR>RADAR or<BR>“R” Position<BR>Assistant<BR>or ATA<BR>Position<BR>Radar Associate or<BR>“D” Position<BR>Hand-off/<BR>Tracker<BR>Position<BR>u Teamwork<BR>u Flexibility<BR>u Technique<BR>22<BR>Sector Workstation<BR>12<BR>23<BR>Traffic Management Unit<BR>(with CTAS)<BR>24<BR>Display System Replacement (DSR)<BR>Console<BR>13<BR>25<BR>En Route Full Data Block<BR>AAL278<BR>330C<BR>068 500<BR>Position Symbol<BR>Beacon Target<BR>Aircraft<BR>Identification<BR>Ground Speed<BR>Mode ‘C’ Altitude<BR>X100<BR>Leader Line<BR>Computer<BR>Identification<BR>Number<BR>Vector Line<BR>Histories<BR>26<BR>Radar Targets/Symbols<BR>u Flat track<BR>u Free track<BR>u Coast track<BR>u Primary target<BR>u Secondary target<BR>F Correlated target<BR>F Non-correlated target<BR>*<BR>#<BR>(Radar updates every 10-12 seconds)<BR>14<BR>27<BR>Center Radar Display<BR>CO 123<BR>350C<BR>B757 310<BR>Slide courtesy of Prof. J. Hansman<BR>28<BR>Example Scenario<BR>DFW Airport<BR>Arrival Meter Fix<BR>DFW Arrivals<BR>DFW Departures<BR>Overflights in Cruise<BR>flight plan<BR>routes<BR>En Route Sector Boundaries<BR>TRACON Boundary<BR>15<BR>29<BR>ATM Functional Structure<BR>Aircraft Aircraft State<BR>Guidance and<BR>Navigation<BR>AC State<BR>Sensor<BR>Sector<BR>Traffic<BR>Control<BR>Traffic<BR>Sensor<BR>Vectors<BR>Clearances<BR>Sector<BR>Traffic<BR>Planning<BR>National<BR>Flow<BR>Planning<BR>Approved<BR>Flight<BR>Plans<BR>Approved<BR>Handoffs<BR>Desired<BR>Sector<BR>Loads<BR>Clearance<BR>Requests<BR>Other Aircraft<BR>States<BR>Flight<BR>Planning<BR>Weather<BR>Flight<BR>Schedule<BR>Filed<BR>Flight<BR>Plans<BR>Negotiate<BR>Handoffs<BR>Schedule of<BR>Capacities<BR>hrs - day 5-20 min 5 min < 5 min<BR>Facility<BR>Flow<BR>Planning<BR>hrs<BR>Execution - Tactical Level<BR>Planning - Strategic Level<BR>Airline CFMU TMU D-side R-side<BR>Pilot<BR>Planned<BR>Flow<BR>Rates<BR>Clearance<BR>Requests<BR>Measurement<BR>Real State<BR>Plan/Intent<BR>Requests<BR>AOC<BR>Efficiency Throughput<BR>Increasing Criticality Level<BR>Safety<BR>Slide courtesy of Prof. J. Hansman<BR>30<BR>SF Bay Area - East Flow<BR>Slide courtesy of Prof. J. Hansman<BR>16<BR>31<BR>SF Bay Area - West Flow<BR>Slide courtesy of Prof. J. Hansman<BR>32<BR>Capacity Limit Factors<BR>u Airport Capacity<BR>F Runways<BR>F Gates<BR>F Landside Limits<BR>F Weather<BR>u Airspace Capacity<BR>F Airspace Design<BR>F Controller Workload<BR>u Demand<BR>F Peak Demand<BR>F Hub & Spoke Networks<BR>u Environmental Limits<BR>F Noise (relates to Airport)<BR>F Emissions (local, Ozone, NOX, CO2)<BR>Slide courtesy of Prof. J. Hansman<BR>17<BR>33<BR>Schedule Factors<BR>u Peak Demand/Capacity issue driven by airline Hub and Spoke<BR>scheduling behavior<BR>F Peak demand often exceeds airport IFR capacity (VFR/IFR<BR>Limits)<BR>F Depend on bank spreading and lulls to recover<BR>F Hub and Spoke amplifies delay<BR>u Hub and spoke is an efficient network<BR>F Supports weak demand markets<BR>u Schedules driven by competitive/market factors<BR>F Operations respond to marketing<BR>F Trend to more frequent services, smaller aircraft<BR>F Ratchet behavior<BR>F Impact of regional jets<BR>u Ultimately, airlines will schedule rationally<BR>F To delay tolerance of the market (delay homeostasis)<BR>u Limited federal or local mechanisms to regulate schedule<BR>Slide courtesy of Prof. J. Hansman<BR>34<BR>Flight Plans<BR>u Flight plans<BR>F initially filed by airline<BR>F give intent of aircraft (route, altitude, take-off time)<BR>F are amended to reflect controller clearance changes<BR>F are printed for each sector 20-30 mins before aircraft arrives<BR>F printed strips arranged next to radar display in rough eta order<BR>F serve as a physical reminder about aircraft<BR>F controllers write clearances by hand on strips<BR>F strips can be physically handed off along with aircraft<BR>F flight plans critical to trajectory prediction by automation tools<BR>18<BR>35<BR>Flight Plan Fields<BR>Field Definition Example<BR>Flight id Airline + flight no AAL108<BR>Computer id Host id number 817<BR>Aircraft Type/Equipment T/B757/G<BR>Beacon code Radar transponder id 0245<BR>Cruise altitude Cleared altitude/100 370<BR>True airspeed knots 280<BR>Departure fix Origination SFO<BR>Coordination fix Where aircraft will<BR>appear in this Center<BR>TXO<BR>Coordination time Time at which it will<BR>appear, GMT<BR>1335<BR>Status Type of flight plan Proposed<BR>Route See following<BR>36<BR>Flight Progress Strips<BR>En Route<BR>AAL278 1<BR>T/B722/R<BR>T468 G500<BR>21<BR>068 09<BR>TXK<BR>1930<BR>330 DFW.\.TXK LIT J6<BR>HVQ LDN JASEN1<BR>IAD<BR>LIT o AAL278 SPL FLT<BR>19<BR>45<BR>6262<BR>*ZTL<BR>Type<BR>aircraft<BR>Aircraft Identification<BR>Number of times flight plan has been amended<BR>Type Equipment<BR>Filed<BR>true airspeed<BR>Ground<BR>speed<BR>Computer Identification<BR>Sector<BR>number<BR>Strip<BR>number<BR>Estimated Time at fix<BR>Fix posting for<BR>Sector 21<BR>Altitude<BR>Coordination<BR>fix time<BR>Previous fix<BR>Coordination Symbol to<BR>adjacent ATC facility<BR>Beacon code<BR>Route of flight<BR>Remarks section<BR>u Control Symbology<BR>u Red/Black Strip Marking<BR>TCAS<BR>Equipped<BR>19<BR>Standard Instrument Departure (SID) 37<BR>(Pilots hard copy)<BR>38<BR>Highways of the Sky (Airways)<BR>DFW<BR>LIT<BR>MEM CHA<BR>SPA<BR>GSO<BR>IAD<BR>J66<BR>J66<BR>J118<BR>J118<BR>J14<BR>J14<BR>(Direct)<BR>Jet Routes<BR>FL180<BR>Victor Routes<BR>FL180<BR>V124<BR>20<BR>39<BR>Standard Terminal Arrival Route<BR>IAD<BR>Depart HDG 190<BR>Expect RV to Final<BR>Turbojets expect clearance to<BR>Cross at 11,000’ at 250kts<BR>HVQ<BR>07<BR>2<BR>BKW<BR>095<BR>DILNN<BR>FINKS<BR>07<BR>9<BR>R-259 AML<BR>LDN<BR>R-206<BR>JASEN<BR>GILBY R-<BR>300<BR>DOCCS<BR>“AAL278, Reduce speed to<BR>TWO ONE ZERO, Contact<BR>Dulles Approach ONE TWO<BR>ZERO POINT FOUR FIVE.”<BR>“AAL278, Reducing<BR>and switching,<BR>Good Day.”<BR>Requested Route<BR>Turbojets Expect<BR>Clearance to<BR>Cross at FL240<BR>Jasen One Arrival<BR>Charleston Transition<BR>40<BR>Flight Plan Routes<BR>u Helpful hints<BR>DFW.DALL5.TXK..LIT.J131.PXV.J29.JHW.J82.ALB.GDM2.BOS<BR>F 4 letters + 1 number: SID or STAR (TRACON route)<BR>F 3 letters: waypoint (also indicates VOR nav aid)<BR>F J + number: jet route (V + number: victor/vfr route)<BR>F “..” separates 2 like elements (ABC..DEF)<BR>F “.” separates 2 un-like elements (ABC.J52)<BR>u Some variations:<BR>u Other waypoint types:<BR>F lat/long, x/y, radial/distance:<BR>47N/121W, 437/248, DFW300040<BR>SJC./.TXO..SJT.CUGAR6.IAH<BR>Will enter ZFW at TXO; don’t need to see earlier part of route<BR>21<BR>41<BR>Domain Challenges of ATC<BR>Automation<BR>u Control techniques very different for different facilities<BR>(Center, TRACON, Tower…)<BR>u Even among same-type facilities, procedures vary<BR>widely (Chicago Center vs Ft. Worth Center)<BR>u Airspace description data not always easily parsed<BR>u Electronic system outputs do not always reflect reality<BR>u Every rule has exceptions<BR>u Difficult/costly to change procedures at the moment<BR>new tools are introduced (need fallback position)<BR>u Lots of politics among FAA, unions, airlines... 看看,啥东东 DDDDDDDDDDDDDDDDDDDDDDDDDDDDD
页:
[1]

