37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 307750 |
Time | |
Date | 199506 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : fay |
State Reference | NC |
Altitude | msl bound lower : 4000 msl bound upper : 4000 |
Environment | |
Flight Conditions | IMC |
Light | Dawn |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other |
Route In Use | enroute : direct enroute airway : fay |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Experience | controller radar : 10 |
ASRS Report | 307750 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : unable |
Consequence | faa : investigated |
Supplementary | |
Primary Problem | Navigational Facility |
Air Traffic Incident | other |
Situations | |
Navigational Aid | Unspecified |
Narrative:
I want to establish a database for ARTS iia interface problems between fay and our adjoining approach controls, particularly those approach controls in ZJX host. Note: fay is a ZDC host. Note: this has been a problem for approximately 4 yrs. Situation: aircraft departs fay for points s-sw. Fay attempts automated handoff via ARTS iia to flo or myr approach. ARTS iia rejects handoff for whatever reason and we get 'if' (interface). This then requires a manual handoff to either flo or myr. The problem is 10 fold if we had to make an amendment to the aircraft flight plan via the fdio prior to handoff. Most controllers now work around the problem ie, use manual procedures rather than automated. Fay aus is very well aware of problem and has been unable to resolve the problem. The problem seems to stem from going from one host ZDC to another ZJX? Callback conversation with reporter revealed the following: reporter stated the problem has been ongoing for 5 yrs. The if occurs when an aircraft route or altitude is amended while in fay airspace en route to an adjoining approach control in ZJX computer area. Dss has said enter a false fix to trick the computer and the problem will be solved.
Original NASA ASRS Text
Title: ATC EQUIP PROB ARTS INTERFACE WITH ADJOINING APCH CTL FACILITIES.
Narrative: I WANT TO ESTABLISH A DATABASE FOR ARTS IIA INTERFACE PROBS BTWN FAY AND OUR ADJOINING APCH CTLS, PARTICULARLY THOSE APCH CTLS IN ZJX HOST. NOTE: FAY IS A ZDC HOST. NOTE: THIS HAS BEEN A PROB FOR APPROX 4 YRS. SITUATION: ACFT DEPARTS FAY FOR POINTS S-SW. FAY ATTEMPTS AUTOMATED HDOF VIA ARTS IIA TO FLO OR MYR APCH. ARTS IIA REJECTS HDOF FOR WHATEVER REASON AND WE GET 'IF' (INTERFACE). THIS THEN REQUIRES A MANUAL HDOF TO EITHER FLO OR MYR. THE PROB IS 10 FOLD IF WE HAD TO MAKE AN AMENDMENT TO THE ACFT FLT PLAN VIA THE FDIO PRIOR TO HDOF. MOST CTLRS NOW WORK AROUND THE PROB IE, USE MANUAL PROCS RATHER THAN AUTOMATED. FAY AUS IS VERY WELL AWARE OF PROB AND HAS BEEN UNABLE TO RESOLVE THE PROB. THE PROB SEEMS TO STEM FROM GOING FROM ONE HOST ZDC TO ANOTHER ZJX? CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: RPTR STATED THE PROB HAS BEEN ONGOING FOR 5 YRS. THE IF OCCURS WHEN AN ACFT RTE OR ALT IS AMENDED WHILE IN FAY AIRSPACE ENRTE TO AN ADJOINING APCH CTL IN ZJX COMPUTER AREA. DSS HAS SAID ENTER A FALSE FIX TO TRICK THE COMPUTER AND THE PROB WILL BE SOLVED.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.