ABQ Tower Local Controller reported they issued a turn and altitude restriction to a departure to avoid VFR aircraft which placed it below the Minimum Vectoring Altitude.

Date: 2023-01 · Aircraft: IAI1125 (Astra) · Phase: initial_climb

Anomalies: atc-issue-all-types|conflict-airborne-conflict|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-cftt-cfit

Synopsis

ABQ Tower Local Controller reported they issued a turn and altitude restriction to a departure to avoid VFR aircraft which placed it below the Minimum Vectoring Altitude.

Narrative

I was working Local and had received a point out from approach for two VFR overflights that had potential to conflict with our RNAV departures to the north. I accepted the point out. When an ASTR was ready to depart on the RDRNR3 departure; I felt that I had a gap to go between the two point outs and let the ASTR have the departure. After departure the plane took a very wide turn; well outside of what I was expecting; and a fast climb so I issued a turn and an altitude restriction to keep them away from the overflights. This turn misapplied our DVA procedure; correct heading but incorrect place. This turn was also exceptionally wide and the altitude was below the MVA for our rising terrain to the NE. Once the aircraft were de-conflicted I considered an approval request for higher; but I could see that the plane was clear of terrain and finally turning away from higher terrain so I decided to ship them to departure instead.I tried something and it didn't work. When I fixed it I made a different problem; and not fixing the second problem because of embarrassment was the biggest problem. I have enough experience to know why that is dangerous and; quite frankly; stupid. I have no broader recommendation beyond reminding myself that it's better to look stupid than be stupid.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.