 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLA controller voiced concern regarding a potential conflict between a balloon operation conducted an operating transponder and a uav with less than clear altitude parameters.
| Attributes | |
| ACN | 1136290 |
| Time | |
| Date | 201312 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZLA.ARTCC |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | UAV - Unpiloted Aerial Vehicle |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Balloon |
| Flight Phase | Climb |
| Route In Use | None |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
I was working ZLA33/32 and had just also combined with ZLA34. One of the pieces of traffic that the controller working ZLA34 gave me was a uav operating 510b600. I asked the supervisor for the mission paperwork and noticed that the pre-coordinated flight plan paperwork showed that the aircraft should have been operating 510b590. As part of the briefing from sector 34; I was also told about a balloon operating above FL600. I looked at that map and noticed the flight plan was proposed to be in approximately the same location as the uav flight. I asked the supervisor to call the provided number to have the balloon flight begin a squawk so we could see the balloon location. We observed the balloon code pop up less than 8 miles from the uav. Although this did not result in a loss of separation; the potential was definitely present. The uav flight should not have been allowed to operate in an altitude not previously coordinated. In addition it is unclear if operating at 510b600 gives a uav permission to operate above FL600. The balloon flights should be required to continually squawk a code with an altitude readout for improved ATC planning.
Original NASA ASRS Text
Title: ZLA Controller voiced concern regarding a potential conflict between a balloon operation conducted an operating transponder and a UAV with less than clear altitude parameters.
Narrative: I was working ZLA33/32 and had just also combined with ZLA34. One of the pieces of traffic that the Controller working ZLA34 gave me was a UAV operating 510B600. I asked the Supervisor for the mission paperwork and noticed that the pre-coordinated flight plan paperwork showed that the aircraft should have been operating 510B590. As part of the briefing from Sector 34; I was also told about a balloon operating above FL600. I looked at that map and noticed the flight plan was proposed to be in approximately the same location as the UAV flight. I asked the Supervisor to call the provided number to have the balloon flight begin a squawk so we could see the balloon location. We observed the balloon code pop up less than 8 miles from the UAV. Although this did not result in a loss of separation; the potential was definitely present. The UAV flight should not have been allowed to operate in an altitude not previously coordinated. In addition it is unclear if operating at 510B600 gives a UAV permission to operate above FL600. The balloon flights should be required to continually squawk a code with an altitude readout for improved ATC planning.
Data retrieved from NASA's ASRS site as of July 2013 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.