 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Boi TRACON controller reported insufficient spacing caused an aircraft to be vectored off the RNAV approach into a higher MVA.
| Attributes | |
| ACN | 1470468 |
| Time | |
| Date | 201708 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | BOI.TRACON |
| State Reference | ID |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Other RNAV Z Runway 28L |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
An aircraft was on the RNAV Y approach. I vectored and used speed control to put aircraft X behind the aircraft on the RNAV Z approach. I failed to anticipate the compression caused by the aircraft on the RNAV Y slowing and the arc of the approach cutting the corner and did not provide enough space. Aircraft X was on the arc portion of the RNAV approach below the MVA (minimum vectoring altitude) and I had to cancel their approach clearance and vector and climb them to resolve the separation with the aircraft on the RNAV Y.I told aircraft X to cancel approach clearance and fly heading 100 and maintain 7000 feet. He read it back and I said 'correction turn left hand turn heading 280 maintain 7000.' another aircraft checked on and I told them to stand by and went back to aircraft X who was showing in a full right turn to continue the right turn because left at that point was worse for terrain than keeping the right turn going. He said 'we are already established in the left hand turn is this going to work?' I told him 'no delay climb to 7100' which is the MVA. He clipped the lower right hand edge of that MVA climbing through 6700 feet.sequencing the RNAV rnp approach is difficult. I will not try to do that again without building in more space. I think my heading change caused the pilot to turn the wrong direction making a bad situation worse.
Original NASA ASRS Text
Title: BOI TRACON Controller reported insufficient spacing caused an aircraft to be vectored off the RNAV Approach into a higher MVA.
Narrative: An aircraft was on the RNAV Y approach. I vectored and used speed control to put Aircraft X behind the aircraft on the RNAV Z approach. I failed to anticipate the compression caused by the aircraft on the RNAV Y slowing and the arc of the approach cutting the corner and did not provide enough space. Aircraft X was on the arc portion of the RNAV approach below the MVA (Minimum Vectoring Altitude) and I had to cancel their approach clearance and vector and climb them to resolve the separation with the aircraft on the RNAV Y.I told Aircraft X to cancel approach clearance and fly heading 100 and maintain 7000 feet. He read it back and I said 'correction turn left hand turn heading 280 maintain 7000.' Another aircraft checked on and I told them to stand by and went back to Aircraft X who was showing in a full right turn to continue the right turn because left at that point was worse for terrain than keeping the right turn going. He said 'we are already established in the left hand turn is this going to work?' I told him 'no delay climb to 7100' which is the MVA. He clipped the lower right hand edge of that MVA climbing through 6700 feet.Sequencing the RNAV RNP approach is difficult. I will not try to do that again without building in more space. I think my heading change caused the pilot to turn the wrong direction making a bad situation worse.
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.