Narrative:

After taking off on runway xxr; about 300-500 ft we got loud static in both the captain's headset and first officer's headset. Couldn't understand what the tower was giving us. Had to ask again and told him we are having static in our headsets; hard to understand. I was trying to find the problem so we can hear. We finally understood to switch to departure but very hard to understand at that point with departure; and not sure if we got everything from ATC. I switch to speaker at that time and ask again. I could hear them a lot better; but still had static in the speaker. At least we could understand them. During this time; I made sure the observer's headset wasn't plugged in and changed out headsets. Then asked the first officer to change headsets to see if that would help. That didn't work at all and we were still getting static. The static would go away but come back within 1 min or less as loud as when we took off. At that point I contacted maintenance control to see if there was something we could do. They said the only way we can fix it; is if we came back. I made the decision to return to ZZZ because we couldn't communication between each other very well without our headset; and if going into ZZZ1 that had thunderstorm in the area upon our arrival; just didn't feel safe without them. At FL270 we told ATC that we are having headset problem; and would like to return to ZZZ. At that point we had to burn off fuel for landing; so we went to a holding pattern. After holding in 4 different places due to thunderstorms and avoiding them; we went through one cloud that looked fine but we got a strong sulfur smell in the flight deck. We didn't see any flash of lightning and continued. Few mins later the lights in the cabin went out and the emergency lights came on. That point flight attendant called and asked what went wrong. He told us it's completely dark in the cabin and just the emergency lights came on. I cycled the emergency lights and took about 15 seconds for the main cabin lights to come back on and the emergency lights to go out. I decided at that point I felt that if the lights went out in the cabin; I didn't want to take the chance that we could have an electrical problem up in the flight deck; and could have a safety issue. So I contacted dispatch with the problem and told them we are declaring an emergency; with an overweight landing. He told us ok and land less than 360 FPM. I told ATC about the problem and declared an emergency. We asked for longest runway and have the fire trucks there just in case. We got runway xxr and had no further problem until landing. We got a very strong electrical smell in the flight deck. We did have the fire truck look around the aircraft before returning to the gate. Also noting that we don't know if we missed any calls from ATC with our problem; but did have at one time that we leveled off and ATC told us we were cleared up to an altitude. After talking to the maintenance gentleman; he told us it could have been a problem with the outside jack; and something stuck in it to cause this problem.

Google
 

Original NASA ASRS Text

Title: E145 FLT CREW RETURNS TO DEP ARPT WHEN STATIC IN VHF COM AND THUNDERSTORMS MAKE IT IMPOSSIBLE TO CONTINUE TO DESTINATION.

Narrative: AFTER TAKING OFF ON RWY XXR; ABOUT 300-500 FT WE GOT LOUD STATIC IN BOTH THE CAPT'S HEADSET AND FO'S HEADSET. COULDN'T UNDERSTAND WHAT THE TWR WAS GIVING US. HAD TO ASK AGAIN AND TOLD HIM WE ARE HAVING STATIC IN OUR HEADSETS; HARD TO UNDERSTAND. I WAS TRYING TO FIND THE PROB SO WE CAN HEAR. WE FINALLY UNDERSTOOD TO SWITCH TO DEP BUT VERY HARD TO UNDERSTAND AT THAT POINT WITH DEP; AND NOT SURE IF WE GOT EVERYTHING FROM ATC. I SWITCH TO SPEAKER AT THAT TIME AND ASK AGAIN. I COULD HEAR THEM A LOT BETTER; BUT STILL HAD STATIC IN THE SPEAKER. AT LEAST WE COULD UNDERSTAND THEM. DURING THIS TIME; I MADE SURE THE OBSERVER'S HEADSET WASN'T PLUGGED IN AND CHANGED OUT HEADSETS. THEN ASKED THE FO TO CHANGE HEADSETS TO SEE IF THAT WOULD HELP. THAT DIDN'T WORK AT ALL AND WE WERE STILL GETTING STATIC. THE STATIC WOULD GO AWAY BUT COME BACK WITHIN 1 MIN OR LESS AS LOUD AS WHEN WE TOOK OFF. AT THAT POINT I CONTACTED MAINT CTL TO SEE IF THERE WAS SOMETHING WE COULD DO. THEY SAID THE ONLY WAY WE CAN FIX IT; IS IF WE CAME BACK. I MADE THE DECISION TO RETURN TO ZZZ BECAUSE WE COULDN'T COM BTWN EACH OTHER VERY WELL WITHOUT OUR HEADSET; AND IF GOING INTO ZZZ1 THAT HAD TSTM IN THE AREA UPON OUR ARR; JUST DIDN'T FEEL SAFE WITHOUT THEM. AT FL270 WE TOLD ATC THAT WE ARE HAVING HEADSET PROB; AND WOULD LIKE TO RETURN TO ZZZ. AT THAT POINT WE HAD TO BURN OFF FUEL FOR LNDG; SO WE WENT TO A HOLDING PATTERN. AFTER HOLDING IN 4 DIFFERENT PLACES DUE TO TSTMS AND AVOIDING THEM; WE WENT THROUGH ONE CLOUD THAT LOOKED FINE BUT WE GOT A STRONG SULFUR SMELL IN THE FLT DECK. WE DIDN'T SEE ANY FLASH OF LIGHTNING AND CONTINUED. FEW MINS LATER THE LIGHTS IN THE CABIN WENT OUT AND THE EMER LIGHTS CAME ON. THAT POINT FLT ATTENDANT CALLED AND ASKED WHAT WENT WRONG. HE TOLD US IT'S COMPLETELY DARK IN THE CABIN AND JUST THE EMER LIGHTS CAME ON. I CYCLED THE EMER LIGHTS AND TOOK ABOUT 15 SECONDS FOR THE MAIN CABIN LIGHTS TO COME BACK ON AND THE EMER LIGHTS TO GO OUT. I DECIDED AT THAT POINT I FELT THAT IF THE LIGHTS WENT OUT IN THE CABIN; I DIDN'T WANT TO TAKE THE CHANCE THAT WE COULD HAVE AN ELECTRICAL PROB UP IN THE FLT DECK; AND COULD HAVE A SAFETY ISSUE. SO I CONTACTED DISPATCH WITH THE PROB AND TOLD THEM WE ARE DECLARING AN EMER; WITH AN OVERWT LNDG. HE TOLD US OK AND LAND LESS THAN 360 FPM. I TOLD ATC ABOUT THE PROB AND DECLARED AN EMER. WE ASKED FOR LONGEST RWY AND HAVE THE FIRE TRUCKS THERE JUST IN CASE. WE GOT RWY XXR AND HAD NO FURTHER PROB UNTIL LNDG. WE GOT A VERY STRONG ELECTRICAL SMELL IN THE FLT DECK. WE DID HAVE THE FIRE TRUCK LOOK AROUND THE ACFT BEFORE RETURNING TO THE GATE. ALSO NOTING THAT WE DON'T KNOW IF WE MISSED ANY CALLS FROM ATC WITH OUR PROB; BUT DID HAVE AT ONE TIME THAT WE LEVELED OFF AND ATC TOLD US WE WERE CLRED UP TO AN ALT. AFTER TALKING TO THE MAINT GENTLEMAN; HE TOLD US IT COULD HAVE BEEN A PROB WITH THE OUTSIDE JACK; AND SOMETHING STUCK IN IT TO CAUSE THIS PROB.

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