B747-400 Captain reported multiple EICAS messages during climb. Flight returned and landed uneventfully at the departure airport.
Synopsis
B747-400 Captain reported multiple EICAS messages during climb. Flight returned and landed uneventfully at the departure airport.
Narrative
On this flight I was acting as PM with an FO acting as PF and two FO's in the observer seats. During taxi out several EICAS messages flashed on the upper EICAS; however they cleared before I could see what they were. We decided to continue operating normally. After rotation several EICAS messages displayed. I recall seeing CABIN ALT AUTO; BATT DISCH MAIN; and the other crewmembers told me they also saw an ANTISKID and BRAKE LIMITER message. All of these messages were intermittent with the exception of CABIN ALT AUTO. I asked our third seat FO to pull up the CABIBN ALT AUTO QRH while I requested a level off at 8000 feet from ATC. We followed the QRH procedure; which included an instruction to not climb to higher altitudes. I advised ATC that we had a pressurization problem and would need to stay at 8000 feet and requested either vectors or holding while we worked it out. The PF took the radios and focused on flying the plane while I reviewed the QRH with the other FO's and contacted the company via satphone. Dispatch connected us with MX; and the agreed with our conclusion that it would be best to return to ZZZ. They did not have any recommendations as to whether it would be best to jettison fuel; burn fuel; or land overweight. We discussed it and decide to increase our drag while we prepared to return to ZZZ; and then see how much fuel was remaining and make our decision. We selected flaps 5; gear down; and descended to 5000 feet. We also increased speed; and as thrust increased received a BLD 4 EICAS message. It cleared after one or two seconds as the thrust stabilized. We decided to burn off fuel and as soon as we reached our landing weight we proceeded inbound for an ILS to XX R. Landing and taxi-in were uneventful. I briefed maintenance and wrote up the problem in the aircraft log. MX was not able to correct the issue before we ran out of duty day and we returned to rest. At this time I do not know what specific maintenance issue caused all of these failures. A number of status messages appeared during and after the flight; including a ELEC BCU 2 and CAPT XFR BUS; maybe a failure in one of those could have caused the other issues. ATC was very helpful; providing us exactly what we needed; and the rest of the crew did a great job working together to make a plan and turn the plane around. Outside of finding the cause of the maintenance problems and preventing it in the future I don't have a lot of suggestions for next time. I was fortunate to have 3 skilled professionals on the crew with me; everyone worked together well resulting in a safe outcome to the flight.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.