37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1013268 |
Time | |
Date | 201205 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | SAN.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 84 Flight Crew Type 16600 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown |
Narrative:
Our APU was deferred inoperative so a crossbleed start was required. The first officer told ground we needed to start one engine at the gate and then would crossbleed start the other after pushback. Ground said; 'cleared to start one at the gate; cleared to push on to taxiway bravo; and cleared to crossbleed start the other engine once on taxiway bravo.'we started one at the gate; pushed to taxiway bravo; cleared off the ground crew; and did a crossbleed start the other engine. We called for taxi and a different ground controller cleared us to taxi to runway 27 on bravo and asked us if we were going to crossbleed start during taxi.we replied; 'no. We have already started the engine.' ground said to crossbleed start; we should be perfectly aligned with the taxiway; parallel with the runway. I estimate that there was a 20 degree angle between our aircraft alignment and the taxiway. We said that we understood for future starts and taxied to the runway. We heard ground control call an airport vehicle to check the area where we had done our start; but had no further contact on the matter from ground or tower.I haven't done many crossbleed starts but I plan to talk with ground or ramp control to determine if there are particular procedures for the airport. The first ground controller could have been more specific about our start on taxiway bravo.
Original NASA ASRS Text
Title: After performing a crossbleed start of their second engine after pushback onto Bravo taxiway per clearance from Ground Control the flight crew of a B737-300 was informed by a new Ground Controller that they were improperly aligned on the taxiway when they performed the start and that an airport vehicle was enroute to check the area for any blast damage.
Narrative: Our APU was deferred inoperative so a crossbleed start was required. The First Officer told Ground we needed to start one engine at the gate and then would crossbleed start the other after pushback. Ground said; 'Cleared to start one at the gate; cleared to push on to Taxiway Bravo; and cleared to crossbleed start the other engine once on Taxiway Bravo.'We started one at the gate; pushed to Taxiway Bravo; cleared off the Ground Crew; and did a crossbleed start the other engine. We called for taxi and a different Ground Controller cleared us to taxi to Runway 27 on Bravo and asked us if we were going to crossbleed start during taxi.We replied; 'No. We have already started the engine.' Ground said to crossbleed start; we should be perfectly aligned with the taxiway; parallel with the runway. I estimate that there was a 20 degree angle between our aircraft alignment and the taxiway. We said that we understood for future starts and taxied to the runway. We heard Ground Control call an airport vehicle to check the area where we had done our start; but had no further contact on the matter from Ground or Tower.I haven't done many crossbleed starts but I plan to talk with Ground or Ramp Control to determine if there are particular procedures for the airport. The first Ground Controller could have been more specific about our start on Taxiway Bravo.
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.