37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 266646 |
Time | |
Date | 199403 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : sfo |
State Reference | CA |
Altitude | agl bound lower : 0 agl bound upper : 0 msl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zny |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 153 flight time total : 7004 flight time type : 2400 |
ASRS Report | 266646 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation Intra Facility Coordination Failure |
Narrative:
The incident occurred during push back at sfo with an FAA air safety inspector on the jump seat performing a no- notice line check. Both the ATIS and predep clearance stated that metering should be contacted for pushback clearance. Chart pages for sfo were reviewed and no special instructions for pushback/taxi were found. Metering was contacted and told air carrier X ready for pushback. Both pilots understood the response as, 'cleared to push, monitor ground, they will contact you.' the FAA inspector later stated he heard our call to metering, but did not hear metering's response. The pushback was begun and as the aircraft was brought to a stop, ground control contacted us and informed us they had not cleared us to pushback. We informed them metering had approved the pushback and they told us to report ready for taxi. During the taxi to runway 10, numerous radio calls were monitored between ground and other aircraft that indicated there was considerable confusion between metering, aircraft, and ground control. This was my first trip to sfo (other than as an engineer several yrs ago) and the captain had limited experience at sfo. I believe the resultant incident resulted from 3 main reasons: 1) lack of written guidance in charts regarding actual pushback scenario. 2) metering terminology. 3) lack of a standardized procedure in the ATC system regarding handoffs from metering to ground control and who actually controls pushbacks. (I.e., at iah, metering approves pushbacks and turns you over the ground for taxiing. At ord, ramp control approves pushbacks and metering turns you over to ground for taxi.) this situation will occur again unless a standardized procedure for pushback/taxi when metering is involved is developed and published. Additionally, where multiple contacts are required, specific guidance should be published in the charts. Callback conversation with reporter revealed the following information: pps at sfo stated they do not have a metering position at sfo. Metering to the runway is done by the gate hold position. When an aircraft is released gate hold will tell the aircraft to monitor ground controller. Gate hold position phraseology does not use the word pushback to illuminate pilot interpretation that a pushback is approved.
Original NASA ASRS Text
Title: ACR X NON ADHERENCE TO ATC INSTRUCTION PUSHED BACK FROM GATE WITHOUT CLRNC.
Narrative: THE INCIDENT OCCURRED DURING PUSH BACK AT SFO WITH AN FAA AIR SAFETY INSPECTOR ON THE JUMP SEAT PERFORMING A NO- NOTICE LINE CHK. BOTH THE ATIS AND PREDEP CLRNC STATED THAT METERING SHOULD BE CONTACTED FOR PUSHBACK CLRNC. CHART PAGES FOR SFO WERE REVIEWED AND NO SPECIAL INSTRUCTIONS FOR PUSHBACK/TAXI WERE FOUND. METERING WAS CONTACTED AND TOLD ACR X READY FOR PUSHBACK. BOTH PLTS UNDERSTOOD THE RESPONSE AS, 'CLRED TO PUSH, MONITOR GND, THEY WILL CONTACT YOU.' THE FAA INSPECTOR LATER STATED HE HEARD OUR CALL TO METERING, BUT DID NOT HEAR METERING'S RESPONSE. THE PUSHBACK WAS BEGUN AND AS THE ACFT WAS BROUGHT TO A STOP, GND CTL CONTACTED US AND INFORMED US THEY HAD NOT CLRED US TO PUSHBACK. WE INFORMED THEM METERING HAD APPROVED THE PUSHBACK AND THEY TOLD US TO RPT READY FOR TAXI. DURING THE TAXI TO RWY 10, NUMEROUS RADIO CALLS WERE MONITORED BTWN GND AND OTHER ACFT THAT INDICATED THERE WAS CONSIDERABLE CONFUSION BTWN METERING, ACFT, AND GND CTL. THIS WAS MY FIRST TRIP TO SFO (OTHER THAN AS AN ENGINEER SEVERAL YRS AGO) AND THE CAPT HAD LIMITED EXPERIENCE AT SFO. I BELIEVE THE RESULTANT INCIDENT RESULTED FROM 3 MAIN REASONS: 1) LACK OF WRITTEN GUIDANCE IN CHARTS REGARDING ACTUAL PUSHBACK SCENARIO. 2) METERING TERMINOLOGY. 3) LACK OF A STANDARDIZED PROC IN THE ATC SYS REGARDING HDOFS FROM METERING TO GND CTL AND WHO ACTUALLY CTLS PUSHBACKS. (I.E., AT IAH, METERING APPROVES PUSHBACKS AND TURNS YOU OVER THE GND FOR TAXIING. AT ORD, RAMP CTL APPROVES PUSHBACKS AND METERING TURNS YOU OVER TO GND FOR TAXI.) THIS SIT WILL OCCUR AGAIN UNLESS A STANDARDIZED PROC FOR PUSHBACK/TAXI WHEN METERING IS INVOLVED IS DEVELOPED AND PUBLISHED. ADDITIONALLY, WHERE MULTIPLE CONTACTS ARE REQUIRED, SPECIFIC GUIDANCE SHOULD BE PUBLISHED IN THE CHARTS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: PPS AT SFO STATED THEY DO NOT HAVE A METERING POS AT SFO. METERING TO THE RWY IS DONE BY THE GATE HOLD POS. WHEN AN ACFT IS RELEASED GATE HOLD WILL TELL THE ACFT TO MONITOR GND CTLR. GATE HOLD POS PHRASEOLOGY DOES NOT USE THE WORD PUSHBACK TO ILLUMINATE PLT INTERP THAT A PUSHBACK IS APPROVED.
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.