37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1677235 |
Time | |
Date | 201908 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | S56.TRACON |
State Reference | UT |
Aircraft 1 | |
Make Model Name | Small Transport |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X departed slc on a 340 heading climbing to 100. I acknowledged his check on but did not climb him out of 100. His routing was a little strange; so I asked my hand-off to coordinate direct rks and 150; while I checked the asd-X to ensure that there was not conflicting traffic behind him and that the coordinated altitude would work. In the meantime I had another controlled come sit down next to me and said they were going to take the position; and several other aircraft checked on. When I returned to aircraft X to give the new routing and altitude; I saw that he was quickly climbing out of 102; and I mistakenly assumed that I had already given him the 150 altitude; so I did not also include that in the instruction. Aircraft X quickly continued the climb to 106; and I started giving the briefing. As I began the briefing I saw that aircraft X was descending again; and I instructed them to expedite the climb to 150 and turned them away from terrain; but they did not respond. I issued a low altitude alert and instructed them that they were about to enter a higher MVA and advised them to expedite the climb through 120. This time they read back the instruction and started the climb. They entered an 110 MVA at 102; and I again issued the heading away from higher terrain; which they did read back. The aircraft quickly climbed out of the MVA and was turned back on course. I need to make sure to reissue instructions when I'm not 100% certain they received them; just to be on the safe side.
Original NASA ASRS Text
Title: S56 Controller reported unsure of climb clearance resulting in aircraft entering a higher MVA.
Narrative: Aircraft X departed SLC on a 340 heading climbing to 100. I acknowledged his check on but did not climb him out of 100. His routing was a little strange; so I asked my hand-off to coordinate direct RKS and 150; while I checked the ASD-X to ensure that there was not conflicting traffic behind him and that the coordinated altitude would work. In the meantime I had another controlled come sit down next to me and said they were going to take the position; and several other aircraft checked on. When I returned to Aircraft X to give the new routing and altitude; I saw that he was quickly climbing out of 102; and I mistakenly assumed that I had already given him the 150 altitude; so I did not also include that in the instruction. Aircraft X quickly continued the climb to 106; and I started giving the briefing. As I began the briefing I saw that Aircraft X was descending again; and I instructed them to expedite the climb to 150 and turned them away from terrain; but they did not respond. I issued a low altitude alert and instructed them that they were about to enter a higher MVA and advised them to expedite the climb through 120. This time they read back the instruction and started the climb. They entered an 110 MVA at 102; and I again issued the heading away from higher terrain; which they did read back. The aircraft quickly climbed out of the MVA and was turned back on course. I need to make sure to reissue instructions when I'm not 100% certain they received them; just to be on the safe side.
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.