An MD80 rejected takeoff due to #2 engine slow to make takeoff power, second attempt normal.

Attributes
ACN	369463
Time
Date	199705
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ont
State Reference	CA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : luk
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 180 flight time total : 4000 flight time type : 600
ASRS Report	369463
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	other flight crewa other other : unspecified cockpit
Resolutory Action	aircraft : equipment problem dissipated
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

On may/fri/97, the captain and I were cleared for takeoff on runway 26R at ontario airport, ca. Upon advancing the throttles for takeoff power the right engine spooled up much slower than the left engine. While we waited for the right engine to spool up, valuable runway was being used up, as we commenced a rolling takeoff. When the right engine spooled, the captain decided to exit the runway and taxi back for another takeoff at the beginning of the runway. The captain and I thought it was the best action to commence the takeoff at the beginning of the runway, and exit the runway when we did, because of the valuable runway behind us and the aircraft engines were not spooled up to maximum takeoff power. Looking back on this whole incident I would do things differently. After discontinuing the takeoff we should have returned to the gate and have maintenance look on the engine before proceeding for another takeoff. Also, my attitude to always looking for reasons to continue has been greatly affected by this incident. The second takeoff was normal and the journey to our destination was uneventful. However, the captain did write up the condition affecting the right engine when we arrived to our destination, at the request of the engine mechanic upon speaking with him.

Original NASA ASRS Text

Title: AN MD80 REJECTED TKOF DUE TO #2 ENG SLOW TO MAKE TKOF PWR, SECOND ATTEMPT NORMAL.

Narrative: ON MAY/FRI/97, THE CAPT AND I WERE CLRED FOR TKOF ON RWY 26R AT ONTARIO ARPT, CA. UPON ADVANCING THE THROTTLES FOR TKOF PWR THE R ENG SPOOLED UP MUCH SLOWER THAN THE L ENG. WHILE WE WAITED FOR THE R ENG TO SPOOL UP, VALUABLE RWY WAS BEING USED UP, AS WE COMMENCED A ROLLING TKOF. WHEN THE R ENG SPOOLED, THE CAPT DECIDED TO EXIT THE RWY AND TAXI BACK FOR ANOTHER TKOF AT THE BEGINNING OF THE RWY. THE CAPT AND I THOUGHT IT WAS THE BEST ACTION TO COMMENCE THE TKOF AT THE BEGINNING OF THE RWY, AND EXIT THE RWY WHEN WE DID, BECAUSE OF THE VALUABLE RWY BEHIND US AND THE ACFT ENGS WERE NOT SPOOLED UP TO MAX TKOF PWR. LOOKING BACK ON THIS WHOLE INCIDENT I WOULD DO THINGS DIFFERENTLY. AFTER DISCONTINUING THE TKOF WE SHOULD HAVE RETURNED TO THE GATE AND HAVE MAINT LOOK ON THE ENG BEFORE PROCEEDING FOR ANOTHER TKOF. ALSO, MY ATTITUDE TO ALWAYS LOOKING FOR REASONS TO CONTINUE HAS BEEN GREATLY AFFECTED BY THIS INCIDENT. THE SECOND TKOF WAS NORMAL AND THE JOURNEY TO OUR DEST WAS UNEVENTFUL. HOWEVER, THE CAPT DID WRITE UP THE CONDITION AFFECTING THE R ENG WHEN WE ARRIVED TO OUR DEST, AT THE REQUEST OF THE ENG MECH UPON SPEAKING WITH 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.