Narrative:

I was working all the satellite sectors. I had a fairly decent amount of traffic and there was considerable frequency congestion. I released the aircraft via the automated rundown list. The aircraft was a south-bound jet. Initial instructions from tower are normally a 050 heading and a climb to 2;000 ft. The aircraft departed and he appeared much farther south than I had anticipated him being. I was dealing with many other priority transmissions. I heard an aircraft say shallow turn to zero five zero. I can't remember if I radar identified the aircraft; but as soon as I registered that the plane was far too shallow to avoid the 2;200 ft. MVA (minimum vectoring altitude) he was nearing; I turned the plane to a 030 heading for the climb. I was just trying to remain west of the depicted obstacle at that point because there were no safe altitudes I could climb to for crossing traffic. I had 2 VFR aircraft at 2;500 ft. And an IFR aircraft at 3;000 ft.; 4;000 ft.; and 5;000 ft. That were all a factor. As soon as I had divergence with my traffic that was a factor; I issued a climb. Tower should assure that aircraft are turning to avoid the MVA. I don't feel we have the space available to not use 3;000 ft. In that area for other aircraft inbound just to ensure that those releases can make that turn. Weather was not an issue. The subsequent vectors the aircraft received were made quickly so I'm not sure why a shallow turn was being used. Had the plane come off correctly I would have been able to climb him in front of the VFR arrivals instead of holding underneath. I am also unaware if tower instructed the shallow turn due to a left downwind aircraft I had given them at 2;500 ft. But it's a possibility.

Google
 

Original NASA ASRS Text

Title: A TRACON Departure Controller reported a departing aircraft made an unusually shallow turn on departure and flew below the Minimum Vectoring Altitude.

Narrative: I was working all the satellite sectors. I had a fairly decent amount of traffic and there was considerable frequency congestion. I released the aircraft via the automated rundown list. The aircraft was a south-bound jet. Initial instructions from tower are normally a 050 heading and a climb to 2;000 ft. The aircraft departed and he appeared much farther south than I had anticipated him being. I was dealing with many other priority transmissions. I heard an aircraft say shallow turn to zero five zero. I can't remember if I radar Identified the aircraft; but as soon as I registered that the plane was far too shallow to avoid the 2;200 ft. MVA (Minimum Vectoring Altitude) he was nearing; I turned the plane to a 030 heading for the climb. I was just trying to remain west of the depicted obstacle at that point because there were no safe altitudes I could climb to for crossing traffic. I had 2 VFR aircraft at 2;500 ft. and an IFR aircraft at 3;000 ft.; 4;000 ft.; and 5;000 ft. that were all a factor. As soon as I had divergence with my traffic that was a factor; I issued a climb. Tower should assure that aircraft are turning to avoid the MVA. I don't feel we have the space available to not use 3;000 ft. in that area for other aircraft inbound just to ensure that those releases can make that turn. Weather was not an issue. The subsequent vectors the aircraft received were made quickly so I'm not sure why a shallow turn was being used. Had the plane come off correctly I would have been able to climb him in front of the VFR arrivals instead of holding underneath. I am also unaware if tower instructed the shallow turn due to a left downwind aircraft I had given them at 2;500 ft. but it's a possibility.

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.