37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1478053 |
Time | |
Date | 201708 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | S56.TRACON |
State Reference | UT |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID NSIGN5 |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID NSIGN5 |
Flight Plan | IFR |
Person 1 | |
Function | Departure Instructor |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Speed All Types |
Narrative:
I was performing ojti on the lake and gunnison sectors combined. This is the developmentals first positions at his first FAA facility. We had a light to moderate level of traffic; with some VFR aircraft and a few weather deviations adding to the complexity. Aircraft X departed on the nsign departure ocs transition assigned climb via 230 kts. Aircraft Y departure 3.5 in trail ekr transition assigned the same. Separation increased to about 3.78. We were working on climbing and coordinating speeds with the traffic as aircraft Y started to overtake aircraft X since aircraft X did not continue to speed up to 230 kts as assigned. As soon as the developmental was finished with the other traffic; he caught aircraft X being overtaken and sped him up to 250 kts. This caused the already slow climbing aircraft to not be able to make the next crossing restrictions which we need to get him above terrain. Aircraft X clearing the terrain became the focus. Aircraft Y was turned to the east as soon as his climb rate indicated he would clear the terrain; however separation had decreased to 2.6 miles. At this point my main focus is aircraft X. Tower can give us aircraft less than 3 if the routes diverge if they get visual separation on the ground; this is indicated on the strip. However; the developmental was not using strips since we are not required to. We are used to seeing this kind of proximity on a daily basis; I did not notice the separation decrease since the main focus was on aircraft X's climb. Aircraft X advised us he could not make the crossing restriction. As aircraft X made the eastbound turn on the departure I realized he would not make the MVA and issued a turn to the northwest away from terrain. Aircraft X just barely entered the 11000 MVA climbing through 10600. Aircraft X speeds were deleted to expedite the climb; however he increased his speeds further by 20 knots and swung wider than anticipated. I definitely should have turned him off the departure earlier. However; we use judgment to start the east turn prior to clearing the MVA; we don't use crossing restrictions; at that point even a slow underperforming [aircraft type] will clear 11000 out of 9800 at that point with an expeditious climb. As far as turning aircraft X earlier; next time if there is any doubt I'll take him off the departure. When these unexpected situations happen on this sector; and aircraft then continue to not operate as expected; there are very little outs. We need to get above 12000 to turn east; the downwind is descending to 11000 about 6 miles west of us. Getting visual separating is technically an 'out' but does not increase the safety situation. It is still up to us to fix something. Visual off the ground; though not used here; puts aircraft in very close proximity with little outs when something goes wrong and increased workload greatly. It also leads us to a point that we expect visual separation with less than three miles. The fact they put it on the strip doesn't help since we are not required to use strips and the expectation to when aircraft are departed 1.5 in trail is too difficult to keep up with. I suggest we get all departures 3 in trail. Then if we see separation collapsing we don't have to scramble to get or verify visual separation. This procedure has caused multiple safety situations throughout the years.
Original NASA ASRS Text
Title: S56 TRACON Controller reported a loss of separation due to a slower speed aircraft in front of a faster departure.
Narrative: I was performing OJTI on the Lake and Gunnison sectors combined. This is the Developmentals first positions at his first FAA facility. We had a light to moderate level of traffic; with some VFR aircraft and a few weather deviations adding to the complexity. Aircraft X departed on the NSIGN departure OCS transition assigned climb via 230 kts. Aircraft Y departure 3.5 in trail EKR transition assigned the same. Separation increased to about 3.78. We were working on climbing and coordinating speeds with the traffic as Aircraft Y started to overtake Aircraft X since Aircraft X did not continue to speed up to 230 kts as assigned. As soon as the Developmental was finished with the other traffic; he caught Aircraft X being overtaken and sped him up to 250 kts. This caused the already slow climbing aircraft to not be able to make the next crossing restrictions which we need to get him above terrain. Aircraft X clearing the terrain became the focus. Aircraft Y was turned to the east as soon as his climb rate indicated he would clear the terrain; however separation had decreased to 2.6 miles. At this point my main focus is Aircraft X. Tower can give us aircraft less than 3 if the routes diverge if they get visual separation on the ground; this is indicated on the strip. However; the Developmental was not using strips since we are not required to. We are used to seeing this kind of proximity on a daily basis; I did not notice the separation decrease since the main focus was on Aircraft X's climb. Aircraft X advised us he could not make the crossing restriction. As Aircraft X made the eastbound turn on the departure I realized he would not make the MVA and issued a turn to the northwest away from terrain. Aircraft X just barely entered the 11000 MVA climbing through 10600. Aircraft X speeds were deleted to expedite the climb; however he increased his speeds further by 20 knots and swung wider than anticipated. I definitely should have turned him off the departure earlier. However; we use judgment to start the east turn prior to clearing the MVA; we don't use crossing restrictions; at that point even a slow underperforming [aircraft type] will clear 11000 out of 9800 at that point with an expeditious climb. As far as turning Aircraft X earlier; next time if there is any doubt I'll take him off the departure. When these unexpected situations happen on this sector; and aircraft then continue to not operate as expected; there are very little outs. We need to get above 12000 to turn east; the downwind is descending to 11000 about 6 miles west of us. Getting visual separating is technically an 'out' but does not increase the safety situation. It is still up to us to fix something. Visual off the ground; though not used here; puts aircraft in very close proximity with little outs when something goes wrong and increased workload greatly. It also leads us to a point that we expect visual separation with less than three miles. The fact they put it on the strip doesn't help since we are not required to use strips and the expectation to when aircraft are departed 1.5 in trail is too difficult to keep up with. I suggest we get all departures 3 in trail. Then if we see separation collapsing we don't have to scramble to get or verify visual separation. This procedure has caused multiple safety situations throughout the years.
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.