Date: 201511
Local time of day: 1201-1800
Location: MCI.Airport, MO
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class B MCI
ATC / advisory: Tower MCI
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other takeoff roll
Result: Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: After all checklists for pushback had been completed; we lost ground power on the aircraft prior to having the APU started.  So the aircraft went to battery only stand-by power for about 30 seconds.  Ground power was reconnected and the APU was started on put on the busses.  After regaining electrical power; we re-verified that all the data was still in the FMC. We rechecked the route and that all the takeoff data was still in the FMC.  There was a CDU fault that took about two minutes to clear and then everything was back up 100 percent.  We received pushback clearance and taxied to 1L at MCI.  V1 and Vr were the same (130 knots) and V2 was 135 knots.  I pushed the power up; hit the autothrottles; and asked for takeoff thrust.  My First Officer (FO) called takeoff thrust set and I re-established my hand on the thrust levers.  My FO then called 80 knots and then V1 rotate.  I thought the call came rather fast in the takeoff sequence; but at the moment I was focused on the engine instruments.  I removed my hand from the thrust levers and began my rotation.  It was at that moment that I realized we were only at about 100 knots.  The nose of the aircraft was off the ground; but we were well below the briefed speeds.  I had started my rotation based on my FO call. I kept the nose off the ground but stopped my rotation and pushed the thrust up until the aircraft felt as if it wanted to fly.  We left the ground at about 120 knots; still 15 knots below V2.  I let the aircraft accelerate to V2 and then contained a normal climb.   At this point we realized what had happened.  Due to the power loss; the V2 bug on the MCP had reset its self to 100 knots.  My FO said that when he saw it on the speed tape that he thought that the speeds I.E. V1; Vr; and V2 were all the same and called rotate.From now on; anytime I have an electric power loss on the aircraft; I am going to run the full Before Start Originating; Before Push; and Before Taxi Checklist to make sure none of these critical items have been missed or reset due to the electrical power loss.


Second narrative: We had just finished the Before Push Checklist when the Ground Crew on the ramp signaled to the Captain asking if they could pull Ground power. The Captain held up one finger for them to wait a minute as the APU had not been started. The Ground Crew proceeded to pull the Ground power and we were left on standby battery power until we could get the APU up and running. When we were able to establish power again; we checked to make sure all of our data in the FMC was correct. All of the flight plan data as well as the performance data was correct. What we failed to catch was the V2 bug on the MCP had reverted back to 100 knots.


Synopsis: A B737 flight crew reported they rotated prematurely when the FMC performance data was lost following an electrical power failure during pushback.