B737 flight crew reported a return to gate during pushback due to a Hazmat configuration issue. The Hazmat issue was corrected by adding ballast around the Hazmat allowing the flight to depart safely.
Synopsis
B737 flight crew reported a return to gate during pushback due to a Hazmat configuration issue. The Hazmat issue was corrected by adding ballast around the Hazmat allowing the flight to depart safely.
Narrative
After brakes set; at the end of pushback; the push crew informed CA (Captain) they wanted to reposition us for an aircraft pushback off of Gate Y. The Ramp controller did not give us direction to reposition for another aircraft push. CA informed push crew Ramp Controller had not cleared us that; and that disconnecting at the position behind Gate X was acceptable. Push back crew made no mention of returning to gate; or issue with Dangerous Goods. After disconnect with engines running; and ready to taxi; Ramp Controller was contacted for taxi clearance. We were informed to contact company Ops. Upon reaching Ops; we were informed there was a load situation with our Dangerous Goods; and that we needed to return to gate. A Final Dangerous Goods Summary had been received and acknowledged in chocks; prior to initial brake release. At this point; the aircraft had not moved from the position where the push crew disconnected. Ground crew was not in position to facilitate returning to gate. After the ground crew appeared to huddle and brief; they repositioned to receive the aircraft. The aircraft returned immediately back to gate we departed from (Gate X). After engine shutdown; DG (Dangerous Goods) load issue was resolved; and CA confirmed no change to DG was made; but that ballast was added around DG. Final Weight Manifest was received after second pushback; taxi; and takeoff were normal. Remainder of flight was uneventful. During flight an ACARS message was received to contact Operations Control. After engine shutdown; CA contacted Operations Control as requested and verbally debriefed.
Second reporter narrative
[Report narrative contained no additional information.]
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.