37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 889039 |
Time | |
Date | 201005 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZMP.ARTCC |
State Reference | MN |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types |
Narrative:
Controllers were working traffic on the direct access radar channel (darc) only en route backup surveillance (ebus) system so that en route automation modernization (eram) testing could be accomplished. Since 'darc only' has no flight plan capability; eram controllers were entering flight plans into eram so that controllers could pass that flight plan information from one controller to the next and from one facility to the next. Eram generated flight progress strips for the flights that controllers were using (after verification). I noticed the limited data block on a flight approaching my airspace from the north. I guessed it was aircraft X (I had an etms flight plan showing the flight en route from ane..mkt..oma); and since I had yet to receive a strip on the aircraft asked the eram controller if he had a flight plan on him in the eram system. He said he didn't; and went to the other area to tell its eram controller to enter the flight plan information on that flight so that it would generate a flight progress strip. While that was occurring; the limited data block entered my airspace without a hand off or other coordination. When the aircraft entered my airspace I forced up the data block onto my display. After aircraft X was over 10 miles inside my airspace an automated hand off was initiated on the flight which I accepted. Recommendation; workload on darc only is quite a bit higher for controllers as there is no flight plan capability and all hand offs must be accomplished manually. Therefore; usage of 'darc only' should be minimized. However; with eram testing; 'darc only' operations have increased. Eram testing should not affect live traffic operations to the extent it has as it degrades safety. They stopped using/testing eram on live traffic; but we now go 'darc only' so that they can accomplish eram testing. Using either system affects the safety of the air traffic system. They need to develop another testing regimen for eram that minimizes the use of 'darc only' on live traffic.
Original NASA ASRS Text
Title: ZMP controller described airspace incursion event during 'DARC Only' operations; noting this operation increases workload/complexity and another ERAM testing regimen needs to be developed.
Narrative: Controllers were working traffic on the Direct Access Radar Channel (DARC) only En Route Backup Surveillance (EBUS) system so that En Route Automation Modernization (ERAM) testing could be accomplished. Since 'DARC Only' has no flight plan capability; ERAM controllers were entering flight plans into ERAM so that controllers could pass that flight plan information from one controller to the next and from one facility to the next. ERAM generated flight progress strips for the flights that controllers were using (after verification). I noticed the limited data block on a flight approaching my airspace from the North. I guessed it was Aircraft X (I had an ETMS flight plan showing the flight en route from ANE..MKT..OMA); and since I had yet to receive a strip on the aircraft asked the ERAM controller if he had a flight plan on him in the ERAM system. He said he didn't; and went to the other area to tell its ERAM controller to enter the flight plan information on that flight so that it would generate a flight progress strip. While that was occurring; the limited data block entered my airspace without a hand off or other coordination. When the aircraft entered my airspace I forced up the data block onto my display. After Aircraft X was over 10 miles inside my airspace an automated hand off was initiated on the flight which I accepted. Recommendation; workload on DARC Only is quite a bit higher for controllers as there is no flight plan capability and all hand offs must be accomplished manually. Therefore; usage of 'DARC Only' should be minimized. However; with ERAM testing; 'DARC Only' operations have increased. ERAM testing should not affect live traffic operations to the extent it has as it degrades safety. They stopped using/testing ERAM on live traffic; but we now go 'DARC Only' so that they can accomplish ERAM testing. Using either system affects the safety of the air traffic system. They need to develop another testing regimen for ERAM that minimizes the use of 'DARC Only' on live traffic.
Data retrieved from NASA's ASRS site as of April 2012 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.