Air carrier pushed back, has APU problem. Blocks taxiway while solving.

Attributes
ACN	181917
Time
Date	199106
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : las
State Reference	NV
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	ground : preflight ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 130 flight time total : 6000 flight time type : 130
ASRS Report	181917
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : less severe non adherence : far non adherence : clearance non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

After pushback from gate, aircraft engines were being started when APU shut down during start. Had electrical xfer from APU to batteries to engine gen all uncommanded. Called maintenance for help in clearing all faults. We thought we were clear of all traffic (not blocking txwys). We were not monitoring ground control when company called to inform us that ground was trying to contact us. Ground informed us that we were blocked traffic. After clearing maintenance items, we started taxi to runway after receiving clearance from ground. Approximately half-way to runway we needed to return to the gate. The captain informed company via radio and then I believe that he also called ground control. Upon returning to the gate area ground control asked us to call them on the phone. At the gate area we were in the a position that we were blocking several taxiing aircraft due to taxiway closures. This whole incident could have been avoided by much better crew communication. The captain-first officer communication had broken down in the cockpit due to both very new to complex aircraft, captain's way of operating in cockpit and first officer (me) being at the point of letting the captain run over him.

Original NASA ASRS Text

Title: ACR PUSHED BACK, HAS APU PROBLEM. BLOCKS TXWY WHILE SOLVING.

Narrative: AFTER PUSHBACK FROM GATE, ACFT ENGS WERE BEING STARTED WHEN APU SHUT DOWN DURING START. HAD ELECTRICAL XFER FROM APU TO BATTERIES TO ENG GEN ALL UNCOMMANDED. CALLED MAINT FOR HELP IN CLRING ALL FAULTS. WE THOUGHT WE WERE CLR OF ALL TFC (NOT BLOCKING TXWYS). WE WERE NOT MONITORING GND CTL WHEN COMPANY CALLED TO INFORM US THAT GND WAS TRYING TO CONTACT US. GND INFORMED US THAT WE WERE BLOCKED TFC. AFTER CLRING MAINT ITEMS, WE STARTED TAXI TO RWY AFTER RECEIVING CLRNC FROM GND. APPROX HALF-WAY TO RWY WE NEEDED TO RETURN TO THE GATE. THE CAPT INFORMED COMPANY VIA RADIO AND THEN I BELIEVE THAT HE ALSO CALLED GND CTL. UPON RETURNING TO THE GATE AREA GND CTL ASKED US TO CALL THEM ON THE PHONE. AT THE GATE AREA WE WERE IN THE A POS THAT WE WERE BLOCKING SEVERAL TAXIING ACFT DUE TO TXWY CLOSURES. THIS WHOLE INCIDENT COULD HAVE BEEN AVOIDED BY MUCH BETTER CREW COM. THE CAPT-F/O COM HAD BROKEN DOWN IN THE COCKPIT DUE TO BOTH VERY NEW TO COMPLEX ACFT, CAPT'S WAY OF OPERATING IN COCKPIT AND F/O (ME) BEING AT THE POINT OF LETTING THE CAPT RUN OVER HIM.

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