37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 760527 |
Time | |
Date | 200710 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 135 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : takeoff roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : cfi pilot : atp |
Experience | flight time last 90 days : 130 flight time total : 16600 flight time type : 2400 |
ASRS Report | 760527 |
Events | |
Anomaly | non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : regained aircraft control flight crew : became reoriented |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
Taxi out with new construction since my last flight. Ground control advised 'taxi-slow' for unknown reason. We did. Approaching active departure runway; advised to switch to tower. Entering runway we were asked to 'taxi-fast.' appeared we would be released shortly. Our cue to starting #2. (Southeast taxi; normal to minimize excessive fuel burn -- a delay prone airport for us.) following request to 'taxi-fast' local controller asked us to come up on 122.75. He had information for us. The night before we had been delayed 1 hour due to a runway confign at our destination that shuts down departures from an on-going frustrating experience for us. This controller is sympathetic and has tried to help our cause. He was on duty the night prior during our delay. He wanted our phone number for contacting us later with further information. So; we are southeast taxiing on active (back taxiing due to construction). Pilot monitoring (captain in right seat) is off frequency and I became concerned we were off tower frequency due to his switching his communication to other radio confign. I could not see active frequency. We resolved that issue. He came back on tower frequency; tower cleared us for takeoff reaching runway end. A confusing; rushed situation with many distrs. We completed checklist; I turned around and began advancing power. Immediately I was aware something not right. Aircraft sluggish; pulling to right. Pilot monitoring (captain; right seat) noted #2 engine not running. We slowed -- a little progress (100-200 ft) advised tower we needed to reset equipment turned around; started #2 engine and reaching runway ground once again; we completed checklist again and took off uneventfully. An embarrassing scene. I have heard rumors of others in same situation; but have never experienced this before myself. Our aircraft has no annunciator/EICAS lights if engine is shut down normally or is not started in this southeast taxi confign. We modified our checklist the next day to add a confirmation of 2ND engine started to line up checklist.
Original NASA ASRS Text
Title: AN EMB135 PILOT REPORTS STARTING THE TKOF ROLL WITH AN ENG NOT STARTED BECAUSE ATC DISTRACTED THEM WITH TAXI INSTRUCTIONS AND COM INFO REQUESTS.
Narrative: TAXI OUT WITH NEW CONSTRUCTION SINCE MY LAST FLT. GND CTL ADVISED 'TAXI-SLOW' FOR UNKNOWN REASON. WE DID. APCHING ACTIVE DEP RWY; ADVISED TO SWITCH TO TWR. ENTERING RWY WE WERE ASKED TO 'TAXI-FAST.' APPEARED WE WOULD BE RELEASED SHORTLY. OUR CUE TO STARTING #2. (SE TAXI; NORMAL TO MINIMIZE EXCESSIVE FUEL BURN -- A DELAY PRONE ARPT FOR US.) FOLLOWING REQUEST TO 'TAXI-FAST' LCL CTLR ASKED US TO COME UP ON 122.75. HE HAD INFO FOR US. THE NIGHT BEFORE WE HAD BEEN DELAYED 1 HR DUE TO A RWY CONFIGN AT OUR DEST THAT SHUTS DOWN DEPS FROM AN ON-GOING FRUSTRATING EXPERIENCE FOR US. THIS CTLR IS SYMPATHETIC AND HAS TRIED TO HELP OUR CAUSE. HE WAS ON DUTY THE NIGHT PRIOR DURING OUR DELAY. HE WANTED OUR PHONE NUMBER FOR CONTACTING US LATER WITH FURTHER INFO. SO; WE ARE SE TAXIING ON ACTIVE (BACK TAXIING DUE TO CONSTRUCTION). PLT MONITORING (CAPT IN R SEAT) IS OFF FREQ AND I BECAME CONCERNED WE WERE OFF TWR FREQ DUE TO HIS SWITCHING HIS COM TO OTHER RADIO CONFIGN. I COULD NOT SEE ACTIVE FREQ. WE RESOLVED THAT ISSUE. HE CAME BACK ON TWR FREQ; TWR CLRED US FOR TKOF REACHING RWY END. A CONFUSING; RUSHED SITUATION WITH MANY DISTRS. WE COMPLETED CHKLIST; I TURNED AROUND AND BEGAN ADVANCING PWR. IMMEDIATELY I WAS AWARE SOMETHING NOT RIGHT. ACFT SLUGGISH; PULLING TO R. PLT MONITORING (CAPT; R SEAT) NOTED #2 ENG NOT RUNNING. WE SLOWED -- A LITTLE PROGRESS (100-200 FT) ADVISED TWR WE NEEDED TO RESET EQUIP TURNED AROUND; STARTED #2 ENG AND REACHING RWY GND ONCE AGAIN; WE COMPLETED CHKLIST AGAIN AND TOOK OFF UNEVENTFULLY. AN EMBARRASSING SCENE. I HAVE HEARD RUMORS OF OTHERS IN SAME SITUATION; BUT HAVE NEVER EXPERIENCED THIS BEFORE MYSELF. OUR ACFT HAS NO ANNUNCIATOR/EICAS LIGHTS IF ENG IS SHUT DOWN NORMALLY OR IS NOT STARTED IN THIS SE TAXI CONFIGN. WE MODIFIED OUR CHKLIST THE NEXT DAY TO ADD A CONFIRMATION OF 2ND ENG STARTED TO LINE UP CHKLIST.
Data retrieved from NASA's ASRS site as of January 2009 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.