37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1297637 |
Time | |
Date | 201509 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PCT.TRACON |
State Reference | VA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport |
Operating Under FAR Part | Part 135 |
Flight Phase | Cruise |
Route In Use | Airway V377 |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 9.0 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was working coordinator position. ARTCC called to handoff aircraft X. The data tag was in handoff status; but to the wrong sector. We took a point out on aircraft X instead; since the aircraft only transitions a small portion of our airspace. There is an automation problem with aircraft on this route. Aircraft X departs an airport inside of pct airspace. The aircraft then exits TRACON airspace and enters ARTCC airspace. Then the aircraft re-enters TRACON airspace for 5 miles before entering ARTCC airspace. Another issue with this route is that some ARTCC controllers assume that aircraft on this route are already being watched/pointed out to the TRACON sector. They think this because the aircraft is handed off to ARTCC from TRACON. The handoff to ARTCC comes from a different area in the TRACON.we need to fix automation so aircraft will handoff correctly. Also need to brief ARTCC that just because the aircraft originates in TRACON airspace that not all TRACON sectors are aware of that aircraft.
Original NASA ASRS Text
Title: An aircraft departs TRACON Airspace; enters ARTCC Airspace; departs ARTCC Airspace back into TRACON Airspace. Automation software does not process the flight data properly; handing off the data tag to the wrong sector. This also causes confusion for controllers as to what if any verbal coordination is required for aircraft on these type of routes. This is a common problem in ATC facilities everywhere. As of this report software developers have not been able to or have not been tasked with figuring out a remedy to processing these type of flight plans.
Narrative: I was working coordinator position. ARTCC called to handoff aircraft X. The data tag was in handoff status; but to the wrong sector. We took a point out on aircraft X instead; since the aircraft only transitions a small portion of our airspace. There is an automation problem with aircraft on this route. Aircraft X departs an airport inside of PCT airspace. The aircraft then exits TRACON airspace and enters ARTCC airspace. Then the aircraft re-enters TRACON airspace for 5 miles before entering ARTCC airspace. Another issue with this route is that some ARTCC controllers assume that aircraft on this route are already being watched/pointed out to the TRACON sector. They think this because the aircraft is handed off to ARTCC from TRACON. The handoff to ARTCC comes from a different area in the TRACON.We need to fix automation so aircraft will handoff correctly. Also need to brief ARTCC that just because the aircraft originates in TRACON airspace that not all TRACON sectors are aware of that aircraft.
Data retrieved from NASA's ASRS site 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.