37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 433256 |
Time | |
Date | 199904 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sfo.airport |
State Reference | CA |
Altitude | msl single value : 350 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B757 Undifferentiated or Other Model |
Navigation In Use | other |
Flight Phase | climbout : initial |
Route In Use | departure sid : sfo8.sfo |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 433253 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : commercial pilot : instrument |
ASRS Report | 433255 |
Events | |
Anomaly | non adherence : far non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued alert flight crew : returned to intended course flight crew : returned to original clearance |
Supplementary | |
Problem Areas | Flight Crew Human Performance Company |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Flight xx was flight planned for a gapp 3 departure from runway 1R. When the clearance was received, it included a revised segment that changed the departure to an sfo 8. The revised segment was not noticed by either pilot. Filed clearance on printer message showed gapp 3. As captain, it was my responsibility to xchk any revision. I looked directly at it, but saw only the filed clearance. My copilot was temporary duty to sfo and this was his first line trip. I was concentrating on and explaining specific items unique to sfo, including pushback onto an active taxiway, airspds and altitudes, and emergencys during and after takeoff. Additionally, the only departure prior to ours was a coast guard flight given a gapp 3. Our 350 degree departure heading was corrected by bay departure to 030 degrees. There were no departures from runway 1L and no conflicting traffic on TCASII. No conflict was reported by departure control. In my defense, I suggest that the ACARS print only the clearance as issued by ATC. That might reduce the chance of flying an incorrect SID or initial route segment. Cleared route is what we need not filed.
Original NASA ASRS Text
Title: AN ACR B757 FLC DEPARTED ON THE WRONG SID, BUT THE ALERT DEP CTLR CORRECTED THEM.
Narrative: FLT XX WAS FLT PLANNED FOR A GAPP 3 DEP FROM RWY 1R. WHEN THE CLRNC WAS RECEIVED, IT INCLUDED A REVISED SEGMENT THAT CHANGED THE DEP TO AN SFO 8. THE REVISED SEGMENT WAS NOT NOTICED BY EITHER PLT. FILED CLRNC ON PRINTER MESSAGE SHOWED GAPP 3. AS CAPT, IT WAS MY RESPONSIBILITY TO XCHK ANY REVISION. I LOOKED DIRECTLY AT IT, BUT SAW ONLY THE FILED CLRNC. MY COPLT WAS TEMPORARY DUTY TO SFO AND THIS WAS HIS FIRST LINE TRIP. I WAS CONCENTRATING ON AND EXPLAINING SPECIFIC ITEMS UNIQUE TO SFO, INCLUDING PUSHBACK ONTO AN ACTIVE TXWY, AIRSPDS AND ALTS, AND EMERS DURING AND AFTER TKOF. ADDITIONALLY, THE ONLY DEP PRIOR TO OURS WAS A COAST GUARD FLT GIVEN A GAPP 3. OUR 350 DEG DEP HDG WAS CORRECTED BY BAY DEP TO 030 DEGS. THERE WERE NO DEPS FROM RWY 1L AND NO CONFLICTING TFC ON TCASII. NO CONFLICT WAS RPTED BY DEP CTL. IN MY DEFENSE, I SUGGEST THAT THE ACARS PRINT ONLY THE CLRNC AS ISSUED BY ATC. THAT MIGHT REDUCE THE CHANCE OF FLYING AN INCORRECT SID OR INITIAL RTE SEGMENT. CLRED RTE IS WHAT WE NEED NOT FILED.
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.