TRACON controller in charge [controller in charge] reported that a developmental controller released...

Attributes
ACN	1682011
Time
Date	201909
Local Time Of Day	1801-2400
Place
Locale Reference	IKV.Airport
State Reference	IA
Environment
Flight Conditions	Marginal
Light	Night
Aircraft 1
Make Model Name	TBM 700/TBM 850
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 2
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT

Narrative:

I was working controller in charge in the TRACON; developmental released aircraft X off of runway 22 at ikv. Developmental assigned aircraft X a heading of 360 after departure due to traffic landing dsm. The developmental asked the pilot if this would comply with terrain and obstruction avoidance. The pilot answered affirmative. I told the developmental that the 360 heading was not a good idea as it will put the aircraft in a 4;000 ft. MSA during IFR/MVFR conditions. Developmental either ignored me or didn't hear apparently. Just because the pilot says he can maintain separation doesn't mean we should be assigning headings towards prominent obstructions; especially when the conditions make it impossible for them to comply. Aircraft X entered a 4;000 ft. MVA at approximately 2;800 ft. Prior to passing the altitude of the prominent obstruction. Assign headings away from obstructions for satellite airport departures when it is necessary to assign a heading.

Original NASA ASRS Text

Title: TRACON Controller in Charge [CIC] reported that a Developmental Controller released an aircraft out of a non-towered airport into airspace with a higher MVA against published procedures.

Narrative: I was working CIC in the TRACON; Developmental released Aircraft X off of Runway 22 at IKV. Developmental assigned Aircraft X a heading of 360 after departure due to traffic landing DSM. The Developmental asked the pilot if this would comply with terrain and obstruction avoidance. The pilot answered affirmative. I told the Developmental that the 360 heading was not a good idea as it will put the aircraft in a 4;000 ft. MSA during IFR/MVFR conditions. Developmental either ignored me or didn't hear apparently. Just because the pilot says he can maintain separation doesn't mean we should be assigning headings towards prominent obstructions; especially when the conditions make it impossible for them to comply. Aircraft X entered a 4;000 ft. MVA at approximately 2;800 ft. prior to passing the altitude of the prominent obstruction. Assign headings away from obstructions for satellite airport departures when it is necessary to assign a heading.

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.

TRACON controller in charge [controller in charge] reported that a developmental controller released an aircraft out of a non-towered airport into airspace with a higher MVA against published procedures.