ZMP controller issued IFR clearance below MEA and in another facility's airspace. Operational error.

Attributes
ACN	119673
Time
Date	198908
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : sux
State Reference	IA
Altitude	msl bound lower : 3400 msl bound upper : 4000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zmp tracon : sux
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 10
ASRS Report	119673
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	conflict : ground less severe non adherence : published procedure
Independent Detector	other other : unspecified atc
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Miss Distance	horizontal : 24000 vertical : 600
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Aircraft made his first call at XXXX. I didn't catch the call sign right away. XXXX aircraft made a second call. He was broken asking if his clearance was ready from spirit lake, ia, to gri. I advised him he was broken. He asked for clearance from spirit lake to gri again. At this time a proposal was delivered to the sector by the a side. I issued a clearance from spirit lake to gri as filed, maintain 4000 based on his clearance request. He read back the clearance from spirit lake to gri maintain 4000. There was no reason for me to think he was anywhere other than 'just off of spirit lake'. In reality, he was on the sux approach boundary 45 mi southwest of spirit lake. I lost communications with the aircraft. He did change to sux approach frequency on his own at approximately XXXX zulu. By that time he had come within 600' and 4 mi of an obstruction in sux approach airspace.

Original NASA ASRS Text

Title: ZMP CTLR ISSUED IFR CLRNC BELOW MEA AND IN ANOTHER FAC'S AIRSPACE. OPERATIONAL ERROR.

Narrative: ACFT MADE HIS FIRST CALL AT XXXX. I DIDN'T CATCH THE CALL SIGN RIGHT AWAY. XXXX ACFT MADE A SECOND CALL. HE WAS BROKEN ASKING IF HIS CLRNC WAS READY FROM SPIRIT LAKE, IA, TO GRI. I ADVISED HIM HE WAS BROKEN. HE ASKED FOR CLRNC FROM SPIRIT LAKE TO GRI AGAIN. AT THIS TIME A PROPOSAL WAS DELIVERED TO THE SECTOR BY THE A SIDE. I ISSUED A CLRNC FROM SPIRIT LAKE TO GRI AS FILED, MAINTAIN 4000 BASED ON HIS CLRNC REQUEST. HE READ BACK THE CLRNC FROM SPIRIT LAKE TO GRI MAINTAIN 4000. THERE WAS NO REASON FOR ME TO THINK HE WAS ANYWHERE OTHER THAN 'JUST OFF OF SPIRIT LAKE'. IN REALITY, HE WAS ON THE SUX APCH BOUNDARY 45 MI SW OF SPIRIT LAKE. I LOST COMS WITH THE ACFT. HE DID CHANGE TO SUX APCH FREQ ON HIS OWN AT APPROX XXXX ZULU. BY THAT TIME HE HAD COME WITHIN 600' AND 4 MI OF AN OBSTRUCTION IN SUX APCH AIRSPACE.

Data retrieved from NASA's ASRS site as of August 2007 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.