ZLC controller reports of another less experienced controller issuing a clearance to an aircraft bel...

Narrative:

As I was taking over for another cpc; less than five years of experience [as a] controller; I was witness to him issuing a clearance to this aircraft off the ground. The mia in the area is 140. The controller issued 120 direct to ffu. I sat back and let him finish the briefing. I asked him how the 120 altitude clearance will work. His reply was something to the effect of the departure procedure. I took over the position and I began to research where the obstacle departure clearance is for the airport. I was only able to quickly find the departure procedure. The pilot came off the ground; I radar identified and queried if the pilot was able to maintain his own terrain and obstacle clearance through 140. The pilot stated he was so I issued the climb to 140. The pilot later stated 140 would be too high for his airplane. I told him I was unable to allow the IFR clearance due to terrain and suggested a VFR bearing due west to get in terrain that would allow IFR flight at a lower altitude. The pilot seemed to like the idea and I asked if there was any issue of cloud avoidance with the plan we were executing. At the appropriate altitude; I was then able to issue an IFR clearance. Worth mentioning; the pilot originally filed 100; which is well below mia altitudes along his route. Published obstacle departure clearance for such mountainous terrain.

Original NASA ASRS Text

Title: ZLC Controller reports of another less experienced Controller issuing a clearance to an aircraft below a useable altitude. The ZLC Controller then took over the position and rectified the situation.

Narrative: As I was taking over for another CPC; less than five years of experience [as a] controller; I was witness to him issuing a clearance to this aircraft off the ground. The MIA in the area is 140. The controller issued 120 direct to FFU. I sat back and let him finish the briefing. I asked him how the 120 altitude clearance will work. His reply was something to the effect of the departure procedure. I took over the position and I began to research where the obstacle departure clearance is for the airport. I was only able to quickly find the departure procedure. The pilot came off the ground; I radar identified and queried if the pilot was able to maintain his own terrain and obstacle clearance through 140. The pilot stated he was so I issued the climb to 140. The pilot later stated 140 would be too high for his airplane. I told him I was unable to allow the IFR clearance due to terrain and suggested a VFR bearing due west to get in terrain that would allow IFR flight at a lower altitude. The pilot seemed to like the idea and I asked if there was any issue of cloud avoidance with the plan we were executing. At the appropriate altitude; I was then able to issue an IFR clearance. Worth mentioning; the pilot originally filed 100; which is well below MIA altitudes along his route. Published obstacle departure clearance for such mountainous terrain.

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.

Attributes
ACN	1232768
Time
Date	201501
Local Time Of Day	1201-1800
Place
Locale Reference	ZLC.ARTCC
State Reference	UT
Environment
Light	Night
Aircraft 1
Make Model Name	Small Aircraft
Flight Phase	Initial Climb
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 5
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT

ZLC controller reports of another less experienced controller issuing a clearance to an aircraft below a useable altitude. The ZLC controller then took over the position and rectified the situation.