![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() "Stan Prevost" wrote in message ... Interesting. I never heard that before. So a TRACON controller cannot change a clearance without calling center to do it? It's a flight data processing issue. A terminal controller cannot amend a flight plan in the computer if the host center has auto-acquired a target on that flight. The revised clearance must then be manually coordinated. The alternative is to suspend the auto-acquire feature, which will then require the center to manually start a track on aircraft that depart from airports where the center provides approach control services. Suspending the auto-acquire is the way to go, starting a track is quick and easy and is more than made up for by the reduced manual coordination. |
#2
|
|||
|
|||
![]() "Steven P. McNicoll" wrote in message .net... "Stan Prevost" wrote in message ... Interesting. I never heard that before. So a TRACON controller cannot change a clearance without calling center to do it? It's a flight data processing issue. A terminal controller cannot amend a flight plan in the computer if the host center has auto-acquired a target on that flight. The revised clearance must then be manually coordinated. The alternative is to suspend the auto-acquire feature, which will then require the center to manually start a track on aircraft that depart from airports where the center provides approach control services. Suspending the auto-acquire is the way to go, starting a track is quick and easy and is more than made up for by the reduced manual coordination. So this becomes an issue only at a towered field using center approach control services? |
#3
|
|||
|
|||
![]() "Stan Prevost" wrote in message ... So this becomes an issue only at a towered field using center approach control services? No, it's an issue at any field using center approach control services and pop-ups in center airspace. |
#4
|
|||
|
|||
![]() "Steven P. McNicoll" wrote in message nk.net... "Stan Prevost" wrote in message ... So this becomes an issue only at a towered field using center approach control services? No, it's an issue at any field using center approach control services and pop-ups in center airspace. I don't understand. Your prior discussion was in the context of a terminal controller and center approach control, I thought. That's why I was trying to clarify that it applied to a towered field using center approach control. Can the terminal controller suspend auto-acquire? If there is not a terminal controller, does center suspend auto-acquire? Is suspending auto-acquire done on a per-acft basis? |
#5
|
|||
|
|||
![]() Stan Prevost wrote: I don't understand. Your prior discussion was in the context of a terminal controller and center approach control, I thought. That's why I was trying to clarify that it applied to a towered field using center approach control. It's affects any computer not located at a center. It does not matter what service a center provides or doesn't provide. Can the terminal controller suspend auto-acquire? Yes but this isn't ever done because I don't know when you are going to make your request. It might be 20 miles after takeoff. |
#6
|
|||
|
|||
![]() "Stan Prevost" wrote in message ... I don't understand. Your prior discussion was in the context of a terminal controller and center approach control, I thought. That's why I was trying to clarify that it applied to a towered field using center approach control. I believe you're thinking of terminal controllers as strictly tower controllers. Terminal controllers are those working in control towers and approach control facilities. What exactly were you asking when you wrote, "So this becomes an issue only at a towered field using center approach control services?" I took it to mean the auto-acquire of tracks by ARTCCs. Tracks auto-acquire wherever they happen to be if they're observed by center secondary radar when beginning their flight. Can the terminal controller suspend auto-acquire? Can the terminal controller suspend the auto-acquire of targets by the center? No, of course not. If there is not a terminal controller, does center suspend auto-acquire? No, there'd be no reason to in that case. Is suspending auto-acquire done on a per-acft basis? No, it's done center-wide. |
#7
|
|||
|
|||
![]() "Steven P. McNicoll" wrote in message link.net... "Stan Prevost" wrote in message ... I don't understand. Your prior discussion was in the context of a terminal controller and center approach control, I thought. That's why I was trying to clarify that it applied to a towered field using center approach control. I believe you're thinking of terminal controllers as strictly tower controllers. Terminal controllers are those working in control towers and approach control facilities. That's how I normally think of terminal controllers. But I thought you had excluded the approach control facilities when you used the context of fields using center approach control. Do you call center controllers "terminal controllers" when they are working approach control? That could be what I missed. What exactly were you asking when you wrote, "So this becomes an issue only at a towered field using center approach control services?" I took it to mean the auto-acquire of tracks by ARTCCs. Tracks auto-acquire wherever they happen to be if they're observed by center secondary radar when beginning their flight. I no longer think I understand anything about this discussion of under what circumstances a controller can change a flight plan. I need to find a new starting point, or just abandon it. It seems to be an obscure issue for pilots, I was just curious when it came up. Thanks. |
#8
|
|||
|
|||
![]() "Stan Prevost" wrote in message ... That's how I normally think of terminal controllers. But I thought you had excluded the approach control facilities when you used the context of fields using center approach control. I didn't use that context. This has nothing to do with flights that originate in center airspace. The problem is with flights that originate in approach airspace where center gets an auto-acquire on the aircraft. When center gets the auto-acquire approach is locked out of any further flight data processing on that flight. Do you call center controllers "terminal controllers" when they are working approach control? That could be what I missed. No. |
#9
|
|||
|
|||
![]() Stan Prevost wrote: So this becomes an issue only at a towered field using center approach control services? No it's an issue for any TRACON. All computer systems run thru the center computer. They set the paramters. Right now whenever you takeoff and tag up on the radar I lose the ability to make changes to your flightplan thru the computer. I have to call the center controller on the landline. We are in the process of having that changed with Salt Lake. Both them and us here at BIL don't like this needless coordination so we are changing it. |
#10
|
|||
|
|||
![]() "Newps" wrote in message ... No it's an issue for any TRACON. No, it's only an issue for TRACONs hosted by centers that use auto-acquire. |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Duat Graphics | Slick | Piloting | 0 | January 23rd 05 01:35 PM |
NAS and associated computer system | Newps | Instrument Flight Rules | 8 | August 12th 04 05:12 AM |
DTC DUAT | Matt Whiting | Instrument Flight Rules | 0 | June 5th 04 03:23 PM |
Picking Optimal Altitudes | O. Sami Saydjari | Instrument Flight Rules | 20 | January 8th 04 02:59 PM |