Narrative:

While working approach a medevac helicopter broadcast an initial call on my frequency. The ec-135 was a previously unidentified pop-up call; but I recognized the call sign from proposed satellite departure IFR flight plans that I had in my bay. The ec-135 had an IFR flight plan on file from ZZZ1 to ZZZ2. On his initial call the ec-135 reported that he was declaring an emergency and climbing because he had inadvertently entered IMC. I asked him to identify. I radar identified him 2 miles east of ZZZ3 and asked him his intentions. He requested to pick up the IFR flight plan that he had on file. I issued the IFR clearance including a climb to an altitude above my MVA. At that time; the ec-135 was approximately 1 NM south of my airspace boundary (in [a sector of another TRACON]) tracking northbound. I immediately attempted to coordinate with [other] sector. The controller at that sector did not answer the line and soon the ec-135 was solidly in my airspace. Due to the emergency nature of the flight I continued to handle the situation in my best judgment. Once above my MVA I began expeditious medevac handling and vectored him toward his requested destination. At that point the ec-135 terminated his emergency. ZZZ2; the ec-135's destination; is in [another sector controlled by another TRACON]; so I achieved the appropriate radar hand off/coordination required for any standard operation. Due to the medevac/emergency nature of the event I believe everyone involved handled the situation to the best of their ability.

Related reports:

Google
 

Original NASA ASRS Text

Title: TRACON Controller described an airspace infraction when a medevac helicopter encountered IMC awaiting his IFR clearance and coordination with an adjacent sector was not completed prior to issuing the IFR clearance.

Narrative: While working Approach a Medevac helicopter broadcast an initial call on my frequency. The EC-135 was a previously unidentified pop-up call; but I recognized the call sign from Proposed Satellite Departure IFR flight plans that I had in my bay. The EC-135 had an IFR flight plan on file from ZZZ1 to ZZZ2. On his initial call the EC-135 reported that he was declaring an emergency and climbing because he had inadvertently entered IMC. I asked him to IDENT. I RADAR identified him 2 miles east of ZZZ3 and asked him his intentions. He requested to pick up the IFR flight plan that he had on file. I issued the IFR clearance including a climb to an altitude above my MVA. At that time; the EC-135 was approximately 1 NM south of my airspace boundary (in [a sector of another TRACON]) tracking northbound. I immediately attempted to coordinate with [other] sector. The Controller at that sector did not answer the line and soon the EC-135 was solidly in my airspace. Due to the emergency nature of the flight I continued to handle the situation in my best judgment. Once above my MVA I began expeditious medevac handling and vectored him toward his requested destination. At that point the EC-135 terminated his emergency. ZZZ2; the EC-135's destination; is in [another sector controlled by another TRACON]; so I achieved the appropriate RADAR hand off/coordination required for any standard operation. Due to the medevac/emergency nature of the event I believe everyone involved handled the situation to the best of their ability.

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.