B737 flight crew reported burning odor in the cabin during climbout. Diverted and landed uneventfully.
Synopsis
B737 flight crew reported burning odor in the cabin during climbout. Diverted and landed uneventfully.
Narrative
Climbing through approximately 21;000 ft we received a call from the flight attendants (FM). The FM told us that there was a very strong electrical burning smell in the cabin. There was no smoke and they could not identify the source. The smell was not present on the flight deck. I transferred the aircraft controls and normal ATC radio communications to the FO so that I could start managing the situation. We requested priority handling and told ATC we needed to return to ZZZ immediately. I sent an ACARS diversion report to dispatch and began preparing for the quick air return to ZZZ. I talked to the FM again and she said the smell was still present; but was not as strong and there was still no smoke present. I gave her a briefing for the air return. I did not run the Smoke Fire Fumes checklist because the air return was happening so fast and I didn't want to delay getting on the ground; and also the smell was dissipating. The aircraft controls were transferred back to me for the approach and landing. After landing; AARF reported no abnormal indications on the outside of the aircraft and the FM said that although the smell was still present in the cabin she believed it to be safe to taxi the gate. After arrival at the gate we deplaned normally and ARFF personnel made their way on board for an assessment. ARFF personnel then reported that they found no evidence of a fire. We filed forms for the electrical burning smell and an overweight landing and also verbally briefed station maintenance personnel. I then briefed the dispatcher and flight operations together on the phone.
Second reporter narrative
We were climbing through FL210 when the FA called; and said she smelled a very strong; electrical type of burning smell which was getting worse. We leveled our climb; notified ATC that we were returning to ZZZ.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.