37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1254550 |
Time | |
Date | 201503 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZLA.ARTCC |
State Reference | CA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Small Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Other Holding Pattern |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Other Holding Pattern |
Flight Plan | VFR |
Person 1 | |
Function | Enroute |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5.5 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
I took the sector from another controller. Aircraft X was already in the airspace and orbiting near emt at 14;500. At that altitude in that area is far from ideal as the loop departure aircraft are to cross a fix koopp that is very near emt at or above 15;000 so most aircraft that are flying the loop departure are at or very near 14;500 in the same vicinity as aircraft X. It had been coordinated with sct to have the loop departures off of klax stopped at 14;000 until further notice (ufn) which provided some margin of safety. But on occasion when I climbed aircraft higher when I thought aircraft X was proceeding in a direction in its orbit that would keep the aircraft safety separated laterally; the two aircraft would get much closer either by altitude and/or laterally than I had expected. At some point during my session at sector 18 another same outfit aircraft departed riv (aircraft Y). Once I had communications with the aircraft I asked for their intentions. The pilot told me that they were heading to the same area as aircraft X and would be orbiting at 15;000. I explained to him what impact that would have for my outbound traffic and I asked if he would consider operating at a higher altitude (16;500 or above) or a lower altitude (12;500 or below). He told me that they had to operate above 12;500 so as not to be seen by the target of interest and he said he would orbit at 16;500 for as long as he could. I further queried him about their procedure and asked if it would be possible to coordinate their intentions with ZLA before departure. He told me that they do coordinate with riv tower and sct as soon as they are wheels up. However; that information was never forward on to ZLA.this was not the first time that sector 18 (and more specifically I) has worked an aircraft X & Y flight at that altitude in that area that was also an impact to the departures off of lax.I think that ZLA and possibly sct should coordinate a meeting with the department that operates the aircraft X & Y flights to allow both sides a better understanding of what each is doing and the impact that the flights. I realize that they have little control of the predictability of their flights and their timing and location; but if there was a dialogue opened between the entities involved it would help allow us to provide a better; safer service to them and it would allow them to know the drastic impact that their flight can have on the efficiency and safety of the NAS operations in that area.
Original NASA ASRS Text
Title: A Los Angeles Center (ZLA) Controller describes a situation where an aircraft is circling on a mission and is in constant conflict due to altitude and position.
Narrative: I took the sector from another controller. Aircraft X was already in the airspace and orbiting near EMT at 14;500. At that altitude in that area is far from ideal as the LOOP departure aircraft are to cross a fix KOOPP that is very near EMT at or above 15;000 so most aircraft that are flying the LOOP departure are at or very near 14;500 in the same vicinity as Aircraft X. It had been coordinated with SCT to have the LOOP departures off of KLAX stopped at 14;000 Until Further Notice (UFN) which provided some margin of safety. But on occasion when I climbed aircraft higher when I thought Aircraft X was proceeding in a direction in its orbit that would keep the aircraft safety separated laterally; the two aircraft would get much closer either by altitude and/or laterally than I had expected. At some point during my session at Sector 18 another same outfit aircraft departed RIV (Aircraft Y). Once I had communications with the aircraft I asked for their intentions. The pilot told me that they were heading to the same area as Aircraft X and would be orbiting at 15;000. I explained to him what impact that would have for my outbound traffic and I asked if he would consider operating at a higher altitude (16;500 or above) or a lower altitude (12;500 or below). He told me that they had to operate above 12;500 so as not to be seen by the target of interest and he said he would orbit at 16;500 for as long as he could. I further queried him about their procedure and asked if it would be possible to coordinate their intentions with ZLA before departure. He told me that they do coordinate with RIV tower and SCT as soon as they are wheels up. However; that information was never forward on to ZLA.This was not the first time that Sector 18 (and more specifically I) has worked an Aircraft X & Y flight at that altitude in that area that was also an impact to the departures off of LAX.I think that ZLA and possibly SCT should coordinate a meeting with the department that operates the Aircraft X & Y flights to allow both sides a better understanding of what each is doing and the impact that the flights. I realize that they have little control of the predictability of their flights and their timing and location; but if there was a dialogue opened between the entities involved it would help allow us to provide a better; safer service to them and it would allow them to know the drastic impact that their flight can have on the efficiency and safety of the NAS operations in that area.
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.