 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Nct controller reports of an aircraft that requested a 360 turn. The controller used the term 'proceed as requested.' the aircraft did and while halfway through the turn the pilot requested to rejoin the flight plan and climb to a higher than assigned block altitude. Controller again used the term; 'proceed as requested;' but forgot to restate the altitude to maintain. Aircraft climbed through uncoordinated airspace leading to an airspace violation by the nct controller.
| Attributes | |
| ACN | 1280786 |
| Time | |
| Date | 201507 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | NCT.TRACON |
| State Reference | CA |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | UAV - Unpiloted Aerial Vehicle |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (mon) 1 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance |
Narrative:
Aircraft X [a uav] departed bab and began a normal climb out to FL190 on their filed route of flight. As aircraft X was leaving approximately 140 the pilot requested a left 360. I responded with 'proceed as requested' and restated to maintain FL190. As aircraft X was about halfway into the unplanned turn the pilot asked if they could rejoin their filed route of flight and climb to FL510 block FL590. I responded with 'proceed as requested' and did not restate the altitude to maintain. At that point aircraft X rejoined the filed route of flight and began a climb into ZOA airspace without coordination or communications transfer as the aircraft X pilot missed the frequency change.I failed to restate the altitude to maintain on the second 'proceed as requested' instruction. Additionally I will refrain from using 'proceed as requested' with IFR aircraft as it can lead to confusion. I don't usually use that phraseology with IFR aircraft; but I felt that the pilot was a little confused and that giving them less complicated instructions would be more expeditious. In this case it led to confusion with the altitude and an airspace violation occurred.
Original NASA ASRS Text
Title: NCT Controller reports of an aircraft that requested a 360 turn. The Controller used the term 'Proceed as requested.' The aircraft did and while halfway through the turn the pilot requested to rejoin the flight plan and climb to a higher than assigned block altitude. Controller again used the term; 'Proceed as requested;' but forgot to restate the altitude to maintain. Aircraft climbed through uncoordinated airspace leading to an airspace violation by the NCT Controller.
Narrative: Aircraft X [a UAV] departed BAB and began a normal climb out to FL190 on their filed route of flight. As Aircraft X was leaving approximately 140 the pilot requested a left 360. I responded with 'Proceed as requested' and restated to maintain FL190. As Aircraft X was about halfway into the unplanned turn the pilot asked if they could rejoin their filed route of flight and climb to FL510 block FL590. I responded with 'Proceed as requested' and did not restate the altitude to maintain. At that point Aircraft X rejoined the filed route of flight and began a climb into ZOA airspace without coordination or communications transfer as the Aircraft X pilot missed the frequency change.I failed to restate the altitude to maintain on the second 'Proceed as requested' instruction. Additionally I will refrain from using 'Proceed as requested' with IFR aircraft as it can lead to confusion. I don't usually use that phraseology with IFR aircraft; but I felt that the pilot was a little confused and that giving them less complicated instructions would be more expeditious. In this case it led to confusion with the altitude and an airspace violation occurred.
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.