37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1252635 |
Time | |
Date | 201504 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (mon) 6 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Las 15 miles in trail; sequencing aircraft X behind aircraft Y. Aircraft X was filed cabab.viksn.Q162.bty. To get the necessary miles in trail the aircraft X was turned 20L for spacing. When he was over J92 he was turned back lidat bty rest of route unchanged. 30 seconds later I re-verified with the aircraft that he was already in the turn southbound to stay away from the nellis complex; he assured me he was. I then asked the d-side (newly certified today) if nellis was watching; he replied yes nellis is watching him; which I interpreted as point out approved which I later learned that was not the case. The aircraft ended up approximately 3 miles in nellis' airspace before making the complete turn southbound. 3 months ago aircraft started filing routes similar to aircraft X; whether it was over kenno or viksn/Q162. This routing puts the aircraft a few miles closer to the boundary of joshua approach which when we need to sequence causes a harder turn to the north to get the necessary miles in trail. Then once they are turned back on course a much harder turn to attempt to keep them out of the nellis ranges. These routings have led to multiple violations to joshua approach as well; especially with airbus [aircraft] when they make the turns early. In this situation and many others we need to re-evaluate these routings.in the future I would turn the aircraft earlier and keep in the mind the speed difference especially with a large tailwind out of the southwest.
Original NASA ASRS Text
Title: ZOA Controller reports of an aircraft that is slow in turning and ends up in another facilities airspace leading to an airspace violation. Controller states this aircraft turned like an Airbus even though it was a different company.
Narrative: LAS 15 miles in trail; sequencing Aircraft X behind Aircraft Y. Aircraft X was filed CABAB.VIKSN.Q162.BTY. To get the necessary miles in trail the Aircraft X was turned 20L for spacing. When he was over J92 he was turned back LIDAT BTY rest of route unchanged. 30 seconds later I re-verified with the aircraft that he was already in the turn southbound to stay away from the Nellis Complex; he assured me he was. I then asked the D-side (Newly certified today) if Nellis was watching; he replied yes Nellis is watching him; which I interpreted as point out approved which I later learned that was not the case. The aircraft ended up approximately 3 miles in Nellis' airspace before making the complete turn Southbound. 3 months ago aircraft started filing routes similar to Aircraft X; whether it was over KENNO or VIKSN/Q162. This routing puts the aircraft a few miles closer to the boundary of Joshua approach which when we need to sequence causes a harder turn to the North to get the necessary miles in trail. Then once they are turned back on course a much harder turn to attempt to keep them out of the Nellis ranges. These routings have led to multiple violations to Joshua Approach as well; especially with Airbus [aircraft] when they make the turns early. In this situation and many others we need to re-evaluate these routings.In the future I would turn the aircraft earlier and keep in the mind the speed difference especially with a large tailwind out of the southwest.
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.