Narrative:

Aircraft was dispatched with MEL [for an] engine generator systems (idg; gcb) rh inoperative; requiring use of APU to power right side electrics. Although the procedures applicable to this MEL were thoroughly briefed; after pushback first officer (first officer) inadvertently selected APU to off per habituated normal procedures. Captain caught it almost immediately and returned the APU switch to run. The APU continued it's normal shutdown cycle because the switch was not placed to start then run. Although the MEL was completely understood and briefed; neither pilot caught that the APU had shutdown because they thought they had intervened in time by returning the APU switch to run. As well; during taxi out to the runway; no EICAS or panel lights alert that the affected electrics are not being powered by the APU nor that the APU has shutdown. The only way to ensure that the affected electrics are being powered by the APU is to verify prior to takeoff that the APU run light is illuminated. No existing procedures guarantee nor mandate that this critical action is accomplished.during initial power application for [takeoff (to)]; both utility busses auto load shed as a result of the right side electrics being unpowered. Aircraft speed never exceeded 10 knots and a slow speed reject was performed with the aircraft being taxied off the runway to an unoccupied taxiway. Corrective actions were taken by restoring the APU and a normal to followed.inadequate systems training and reinforcement of systems knowledge; operational application; during initial training. The brevity of systems training and lack of operational application does not provide crews with an adequate back-stop of experience when faced with non-normal situations.additionally; during preflight no preliminary west&B was delivered to the aircraft. The final west&B was delivered approximately 3 minutes prior to scheduled pushback. The lateness of the west&B created a feeling of being rushed; which ultimately led to the first officer habituating to normal after takeoff procedures.standardize procedures for operations with MEL's. Although the after start checklist includes recall and the pilot handbook (phb) discusses unexpected EICAS messages; it was insufficient in this instance to prevent the event as the two EICAS messages encountered were anticipated and expected. If recall were placed earlier in the checklist; in this case prior to APU; the expected EICAS messages; and then appropriate follow-on action (APU on versus shutdown); would have been more easily facilitated. Additionally; procedures requiring crews with MEL's to discuss EICAS messages prior to calling for the after start checklist could help alleviate this kind of event.in addition; the MEL should be modified to include an additional operations step.prior to taking the runway for takeoff; ensure APU run light is illuminated

Google
 

Original NASA ASRS Text

Title: A B767 flight crew rejected the takeoff due to EICAS warnings resulting from mistakenly shutting down the APU after dispatching with a generator inop.

Narrative: Aircraft was dispatched with MEL [for an] Engine generator systems (IDG; GCB) RH INOP; requiring use of APU to power right side electrics. Although the procedures applicable to this MEL were thoroughly briefed; after pushback First Officer (FO) inadvertently selected APU to off per habituated normal procedures. Captain caught it almost immediately and returned the APU switch to RUN. The APU continued it's normal shutdown cycle because the switch was not placed to START then RUN. Although the MEL was completely understood and briefed; neither pilot caught that the APU had shutdown because they thought they had intervened in time by returning the APU switch to RUN. As well; during taxi out to the runway; no EICAS or panel lights alert that the affected electrics are not being powered by the APU nor that the APU has shutdown. The only way to ensure that the affected electrics are being powered by the APU is to verify PRIOR to takeoff that the APU RUN light is illuminated. No existing procedures guarantee nor mandate that this critical action is accomplished.During initial power application for [Takeoff (TO)]; both Utility busses auto load shed as a result of the right side electrics being unpowered. Aircraft speed never exceeded 10 knots and a slow speed reject was performed with the aircraft being taxied off the runway to an unoccupied taxiway. Corrective actions were taken by restoring the APU and a normal TO followed.Inadequate systems training and reinforcement of systems knowledge; operational application; during initial training. The brevity of systems training and lack of operational application does not provide crews with an adequate back-stop of experience when faced with non-normal situations.Additionally; during preflight no preliminary W&B was delivered to the aircraft. The Final W&B was delivered approximately 3 minutes prior to scheduled pushback. The lateness of the W&B created a feeling of being rushed; which ultimately led to the FO habituating to normal after takeoff procedures.Standardize procedures for operations with MEL's. Although the After Start Checklist includes RECALL and the Pilot Handbook (PHB) discusses unexpected EICAS messages; it was insufficient in this instance to prevent the event as the two EICAS messages encountered were anticipated and expected. If RECALL were placed earlier in the checklist; in this case prior to APU; the expected EICAS messages; and then appropriate follow-on action (APU on versus shutdown); would have been more easily facilitated. Additionally; procedures requiring crews with MEL's to discuss EICAS messages prior to calling for the After Start Checklist could help alleviate this kind of event.In addition; the MEL should be modified to include an additional Operations step.PRIOR TO TAKING THE RUNWAY FOR TAKEOFF; ENSURE APU RUN LIGHT IS ILLUMINATED

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