Narrative:

An orion P3 was cleared for the localizer/DME back course 35 at koa. After vectoring the aircraft onto final and clearing it I observed it intercept and track the back course inbound. The P3 then reported established and was instructed to contact koa tower. I scanned my other traffic and when I returned to the P3's target I observed it to be east of course. I called koa tower and advised the controller and asked if the P3 was going to execute the missed approach. I was advised to standby while the controller double checked. The P3 reported the airport was not in sight and that they'd lost navigation. Koa asked me what I wanted to do and because the P3 was below my mias (minimum IFR altitude) and issued a climb to 5;000 and a heading of 330 away from the terrain. The P3 returned to my frequency and operations continued normally from here. The ambiguity of this whole event really bothers me and my performance could have been better. First; we have an aircraft off course below the mias. I rightly queried the tower and here is where I think communication broke down. Rather than have a longer discussion I felt just issuing a climb above the mia and a heading to return the aircraft to safe area was the best course of action. I failed to have the tower controller tell the P3 they were below the mia so I do not know if they ever received that warning. What I have determined is that I need to ensure that the advisory is issued next time and to take control of the situation quicker if the tower doesn't. I've reviewed this over and over and next time I will be sure that I include an instruction to the tower to issue the safety alert along with any control instructions.

Related reports:

Google
 

Original NASA ASRS Text

Title: A HCF Controller had a below MVA event with traffic on the LOC/DME BC at KOA executing a missed approach procedure turning in the wrong direction.

Narrative: An Orion P3 was cleared for the LOC/DME BC 35 at KOA. After vectoring the aircraft onto final and clearing it I observed it intercept and track the BC inbound. The P3 then reported established and was instructed to contact KOA Tower. I scanned my other traffic and when I returned to the P3's target I observed it to be east of course. I called KOA Tower and advised the Controller and asked if the P3 was going to execute the missed approach. I was advised to standby while the Controller double checked. The P3 reported the airport was not in sight and that they'd lost navigation. KOA asked me what I wanted to do and because the P3 was below my MIAs (Minimum IFR Altitude) and issued a climb to 5;000 and a heading of 330 away from the terrain. The P3 returned to my frequency and operations continued normally from here. The ambiguity of this whole event really bothers me and my performance could have been better. First; we have an aircraft off course below the MIAs. I rightly queried the Tower and here is where I think communication broke down. Rather than have a longer discussion I felt just issuing a climb above the MIA and a heading to return the aircraft to safe area was the best course of action. I failed to have the Tower Controller tell the P3 they were below the MIA so I do not know if they ever received that warning. What I have determined is that I need to ensure that the advisory is issued next time and to take control of the situation quicker if the Tower doesn't. I've reviewed this over and over and next time I will be sure that I include an instruction to the Tower to issue the safety alert along with any control instructions.

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.