37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1338686 |
Time | |
Date | 201603 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Environment | |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Developmental |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 0 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Procedural FAR Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
I had turned aircraft X for spacing to las. When I turned him back to the southeast I thought there would be enough room to clear the nellis airspace; but a combination of the aircraft groundspeed and being a [large transport]; the aircraft didn't turn quick enough to stay clear of nellis airspace. There was a large amount of frequency congestion due to moderate turbulence and light to moderate chop; and ride reports. The winds were also strong out of the west. The volume or complexity was average but the frequency congestion and reports were constant. When I thought the aircraft may come close to the nellis airspace I had the D side call nellis and point him out. They said traffic observed but to keep him clear. I gave the aircraft a south heading to try to steer him farther away but it was already too late and he went a few miles inside the airspace. I approximate that I turned the aircraft 18 or 20 miles west of the airspace and he still entered. It's kind of embarrassing to me because I thought it was enough time to turn back.I talked with some people in the area and they said this has happened in the past and suggested using a fix to the northwest to ensure the aircraft won't go into nellis. Giving the aircraft direct tezum direct bty should have kept him clear or I should have vectored him sooner and used a larger buffer.
Original NASA ASRS Text
Title: ZOA Controller reported turning an aircraft 20 miles away from another facilities airspace and doing a point out. The aircraft entered the airspace and the reporter was told to keep the aircraft out of the airspace. Controller reported others have this same problem
Narrative: I had turned Aircraft X for spacing to LAS. When I turned him back to the southeast I thought there would be enough room to clear the Nellis airspace; but a combination of the aircraft groundspeed and being a [large transport]; the aircraft didn't turn quick enough to stay clear of Nellis airspace. There was a large amount of frequency congestion due to moderate turbulence and light to moderate chop; and ride reports. The winds were also strong out of the west. The volume or complexity was average but the frequency congestion and reports were constant. When I thought the aircraft may come close to the Nellis airspace I had the D side call Nellis and point him out. They said traffic observed but to keep him clear. I gave the aircraft a south heading to try to steer him farther away but it was already too late and he went a few miles inside the airspace. I approximate that I turned the aircraft 18 or 20 miles west of the airspace and he still entered. It's kind of embarrassing to me because I thought it was enough time to turn back.I talked with some people in the area and they said this has happened in the past and suggested using a fix to the northwest to ensure the aircraft won't go into Nellis. Giving the aircraft direct TEZUM direct BTY should have kept him clear or I should have vectored him sooner and used a larger buffer.
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.