Narrative:

A BE36/G was flashing at me sector 32/31 from sector 22/21. Routing shr.V86.rap..fsd. The aircraft was level at 9;000 ft. I called the sector 22 controller before taking the handoff requesting the BE36 climb to 11;000 ft to comply with the MEA on V86. The MEA on V86 went to 11;100 ft/10;000 ft GPS/*9;300 MOCA. The BE36 was a /G aircraft. The sector 22 controller agreed to accomplish this so I took the handoff. The pilot never came over on the radio because he was too low to reach me. I then noticed that the aircraft was not climbing fast enough for me to ensure the MEA on the airway and he was more than 22 miles from the rap NAVAID so the MOCA was not applicable. I then called the controller back and requested that he send the BE36 direct to rap because the mia was only 9;300 ft along his route of flight. The controller was agitated that I made the request and then decided to argue the need of the new routing. The BE36 was in my airspace; not on my frequency; and popping in and out of radar. I then proceeded to tell the sector 22/21 controller that he could deal with it and he needed to ship him to rca approach when they took the handoff and then I hung up the line. Recommendation; there needs to be several things done to resolve this situation and to help prevent another one. There needs to be better radar and radio communications west and northwest of rap. It is a bad area for both and makes our job increasingly difficult. There needs to be some clarification as to what is the correct way to handle the situation via altitude and routing. There needs to be some clarity on the definitions of mia and the use of the MOCA; no point did I feel that the BE36 and its passengers were in danger of running into the hills but this is an issue of protecting my ticket.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZDV Controller described a below MIA/MVA event and the disagreement between controllers involved with regard to routing and procedure; the reporter suggesting that improved Radio/RADAR coverage would help prevent future events.

Narrative: A BE36/G was flashing at me Sector 32/31 from Sector 22/21. Routing SHR.V86.RAP..FSD. The aircraft was level at 9;000 FT. I called the Sector 22 Controller before taking the handoff requesting the BE36 climb to 11;000 FT to comply with the MEA on V86. The MEA on V86 went to 11;100 FT/10;000 FT GPS/*9;300 MOCA. The BE36 was a /G aircraft. The Sector 22 Controller agreed to accomplish this so I took the handoff. The pilot never came over on the radio because he was too low to reach me. I then noticed that the aircraft was not climbing fast enough for me to ensure the MEA on the airway and he was more than 22 miles from the RAP NAVAID so the MOCA was not applicable. I then called the Controller back and requested that he send the BE36 direct to RAP because the MIA was only 9;300 FT along his route of flight. The Controller was agitated that I made the request and then decided to argue the need of the new routing. The BE36 was in my airspace; not on my frequency; and popping in and out of RADAR. I then proceeded to tell the Sector 22/21 Controller that he could deal with it and he needed to ship him to RCA Approach when they took the handoff and then I hung up the line. Recommendation; there needs to be several things done to resolve this situation and to help prevent another one. There needs to be better RADAR and radio communications west and northwest of RAP. It is a bad area for both and makes our job increasingly difficult. There needs to be some clarification as to what is the correct way to handle the situation via altitude and routing. There needs to be some clarity on the definitions of MIA and the use of the MOCA; no point did I feel that the BE36 and its passengers were in danger of running into the hills but this is an issue of protecting my ticket.

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