37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1031500 |
Time | |
Date | 201208 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Component | |
Aircraft Component | Electrical Distribution Relay |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 20000 Flight Crew Type 10500 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
We pushed back normally. Our plan was to perform a one engine taxi (right engine) to the runway and do a cross-bleed start of the left engine on the way. After start everything was normal until the APU shut down after its one minute cooldown. At that time we received the left bus off EICAS along with all the other messages that entails. One factor we had to consider was an equipment cooling message. In light of the seriousness of our problem we elected to perform a return to the gate without consulting dispatch and maintenance control. We called the gateway and told them we were taxiing back in. We started the APU again and taxied in using only the right engine. As the APU came online the left bus was again powered but the equipment cooling problem remained along with several other messages. After block-in we described the problem to dispatch and maintenance control and wrote it up in the logbook. I am concerned that had we started both engines or had we taxied with one engine and left the APU on we would not have known that the right generator would not pick up the left AC bus through the bus tie system. I wonder if other 767's might have the same issue.
Original NASA ASRS Text
Title: Following a single engine taxi out a B767-300 flight crew returned to the gate when the right engine generator failed to pick up the left AC buss when the APU was shut down; indicating a failure of the bus tie breaker.
Narrative: We pushed back normally. Our plan was to perform a one engine taxi (right engine) to the runway and do a cross-bleed start of the left engine on the way. After start everything was normal until the APU shut down after its one minute cooldown. At that time we received the L BUS OFF EICAS along with all the other messages that entails. One factor we had to consider was an equipment cooling message. In light of the seriousness of our problem we elected to perform a return to the gate without consulting Dispatch and Maintenance Control. We called the gateway and told them we were taxiing back in. We started the APU again and taxied in using only the right engine. As the APU came online the L Bus was again powered but the equipment cooling problem remained along with several other messages. After block-in we described the problem to Dispatch and Maintenance Control and wrote it up in the logbook. I am concerned that had we started both engines or had we taxied with one engine and left the APU on we would not have known that the right generator would not pick up the left AC bus through the bus tie system. I wonder if other 767's might have the same issue.
Data retrieved from NASA's ASRS site as of July 2013 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.