ZKC controller described a low altitude alert event apparently caused because of an altitude assignm...

Narrative:

I was vectoring aircraft X for a VOR approach to runway 03 at foe. I descended aircraft X to 3;000 ft since that is the minimum altitude for the approach; also thinking that was the minimum IFR altitude (mia). I observed an MSAW alert while aircraft X was descending out of 4;000 ft; immediately checked my low altitude map; and still thought the mia was 3;000 ft. After closer evaluation of the map; I found that the area where I had vectored aircraft X had a mia of 3;200 ft. At this time; aircraft X was already established on the final approach course at 3;000 ft. I never observed aircraft X descend below 3;200 ft prior to being established on the final approach course. The low altitude controller charts located above the radar scopes are very cluttered and can be difficult to obtain information from in a timely fashion. A feature available on all low altitude sector maps that displays the mia directly on the radar scope would be the best solution to prevent events of this sort. The current practice of using the controller chart to determine mia; MVA; etc.; and not having this information available to display on the radar scope is inefficient; impractical; and at times unsafe.

Original NASA ASRS Text

Title: ZKC Controller described a low altitude alert event apparently caused because of an altitude assignment below the Minimum IFR Altitude (MIA) published altitude. The reporter suggested MIA altitude information be provided on the RADAR display.

Narrative: I was vectoring Aircraft X for a VOR approach to Runway 03 at FOE. I descended Aircraft X to 3;000 FT since that is the minimum altitude for the approach; also thinking that was the Minimum IFR Altitude (MIA). I observed an MSAW alert while Aircraft X was descending out of 4;000 FT; immediately checked my low altitude map; and still thought the MIA was 3;000 FT. After closer evaluation of the map; I found that the area where I had vectored Aircraft X had a MIA of 3;200 FT. At this time; Aircraft X was already established on the final approach course at 3;000 FT. I never observed Aircraft X descend below 3;200 FT prior to being established on the final approach course. The low altitude Controller charts located above the RADAR scopes are very cluttered and can be difficult to obtain information from in a timely fashion. A feature available on all low altitude sector maps that displays the MIA directly on the RADAR scope would be the best solution to prevent events of this sort. The current practice of using the Controller chart to determine MIA; MVA; etc.; and not having this information available to display on the RADAR scope is inefficient; impractical; and at times unsafe.

Data retrieved from NASA's ASRS site as of April 2012 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	969380
Time
Date	201109
Local Time Of Day	0001-0600
Place
Locale Reference	FOE.Airport
State Reference	KS
Environment
Light	Night
Aircraft 1
Make Model Name	T6A Texan II / Harvard II (Raytheon)
Operating Under FAR Part	Part 91
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

ZKC controller described a low altitude alert event apparently caused because of an altitude assignment below the minimum IFR altitude (mia) published altitude. The reporter suggested mia altitude information be provided on the radar display.