 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Zan controller described airspace incursion event. Contact with an adjacent facility failed and corrective vectors were too late to avoid the adjacent facilities airspace.
| Attributes | |
| ACN | 872174 |
| Time | |
| Date | 201002 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZAN.ARTCC |
| State Reference | AK |
| Aircraft 1 | |
| Make Model Name | B747-400 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Oceanic |
| Flight Plan | IFR |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types |
Narrative:
Air carrier X was eastbound on B327 headed for czvr airspace. Air carrier X needed to be handed off to czvr. I called czvr approximately three minutes prior to the boundary on the shout line; they didn't answer (which is not entirely unusual if they are briefing or are busy but they sometimes say 'keep them coming' and call back when they have time). I waited about 45 seconds; which put the aircraft approximately two minutes 15 seconds from the boundary and tried again. Once again; no answer. I attempted contact a third time on the shout line about 20 seconds later with no luck. I hung up the shout line and told air carrier X to turn left heading 360. He was approximately 12 miles from the boundary at FL390. He didn't turn quick enough and crossed the 2.5 NM line from the czvr boarder. Air carrier X skirted the czvr boundary and proceeded deeper into zan's airspace. Czvr then contacted me via commercial line and took the multiple hand offs that I had for them. Air carrier X was then cleared back on course and contacted czvr. Causal factor is all of the lines between zan and czvr were OTS. Zan had multiple line outages with other facilities but I was the first to find this out. Recommendation; I suggest radar hand offs be set up between zan and czvr. To alleviate further instances with other facilities we should also have radar hand offs between zan and russia where we both have radar coverage.
Original NASA ASRS Text
Title: ZAN Controller described airspace incursion event. Contact with an adjacent facility failed and corrective vectors were too late to avoid the adjacent facilities airspace.
Narrative: Air Carrier X was Eastbound on B327 headed for CZVR airspace. Air Carrier X needed to be handed off to CZVR. I called CZVR approximately three minutes prior to the boundary on the shout line; they didn't answer (which is not entirely unusual if they are briefing or are busy but they sometimes say 'keep them coming' and call back when they have time). I waited about 45 seconds; which put the aircraft approximately two minutes 15 seconds from the boundary and tried again. Once again; no answer. I attempted contact a third time on the shout line about 20 seconds later with no luck. I hung up the shout line and told Air Carrier X to turn left heading 360. He was approximately 12 miles from the boundary at FL390. He didn't turn quick enough and crossed the 2.5 NM line from the CZVR boarder. Air Carrier X skirted the CZVR boundary and proceeded deeper into ZAN's airspace. CZVR then contacted me via commercial line and took the multiple hand offs that I had for them. Air Carrier X was then cleared back on course and contacted CZVR. Causal factor is all of the lines between ZAN and CZVR were OTS. ZAN had multiple line outages with other facilities but I was the first to find this out. Recommendation; I suggest RADAR hand offs be set up between ZAN and CZVR. To alleviate further instances with other facilities we should also have RADAR hand offs between ZAN and Russia where we both have RADAR coverage.
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.