 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZOA controller described an apparent false conflict alarm when an airline data block failed to drop off the operational display after the aircraft had landed; the reporter listing data link/atop anomalies as causal factors.
| Attributes | |
| ACN | 992804 |
| Time | |
| Date | 201202 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZOA.ARTCC |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 129 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
While working oceanic sector 3 I cleared air carrier Y for arrival kwa island airport. After arrival; I received arrival report from kwa base operations. Opened appropriate window; hit modify and entered arrival time. Fpea was opened for air carrier X. Atops automatically deleted flight plan for air carrier X. I was distracted by flashing orange conflict and other operations. I did not perceive disappearance of air carrier X data block. Approximately five minutes later saw air carrier Y data block still on scope. [I] re-entered arrival message using same process. This time air carrier Y disappeared from scope as expected. Air carrier X was data linked aircraft. Normal expectation is that air carrier X would have to be logged off data link prior to atop allowing controller to delete flight plan information. Recommend that arrival airport should be a necessary entry into fpea window to report arrival for aircraft. System should do a logic check on arrival airport. Data link aircraft should not be deleted out of atop until logged off data link.
Original NASA ASRS Text
Title: ZOA Controller described an apparent false conflict alarm when an Airline Data Block failed to drop off the operational display after the aircraft had landed; the reporter listing Data Link/ATOP anomalies as causal factors.
Narrative: While working Oceanic Sector 3 I cleared Air Carrier Y for arrival KWA Island Airport. After arrival; I received arrival report from KWA Base Operations. Opened appropriate window; hit modify and entered arrival time. FPEA was opened for Air Carrier X. ATOPS automatically deleted Flight Plan for Air Carrier X. I was distracted by flashing orange conflict and other operations. I did not perceive disappearance of Air Carrier X Data Block. Approximately five minutes later saw Air Carrier Y Data Block still on scope. [I] re-entered arrival message using same process. This time Air Carrier Y disappeared from scope as expected. Air Carrier X was Data Linked aircraft. Normal expectation is that Air Carrier X would have to be logged off Data Link prior to ATOP allowing controller to delete flight plan information. Recommend that arrival airport should be a necessary entry into FPEA window to report arrival for aircraft. System should do a logic check on arrival airport. Data Link aircraft should not be deleted out of ATOP until logged off Data Link.
Data retrieved from NASA's ASRS site as of July 2013 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.