37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 777315 |
Time | |
Date | 200803 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sea.airport |
State Reference | WA |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : s46.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : initial |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 238 flight time type : 14000 |
ASRS Report | 777315 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 56 flight time type : 56 |
ASRS Report | 777099 |
Events | |
Anomaly | non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance flight crew : returned to intended or assigned course |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
Pre departure clearance received by first officer (first trip after IOE). Clearance was verbatim as filed on our release except mountain 5 departure listed after clearance. There were no minuses (-) or pluses (+) in the clearance. First officer read the clearance as runway heading to 9000 ft. I did not check the pre departure clearance due to last min passenger issues. I did ask if there was a SID and he said no. On departure; when handed to departure control; I stated we were on runway heading climbing to 9000 ft. Passing about 6 DME departure asked if we had been given a SID; then gave us a turn and asked if we had received an electronic clearance. He said it seemed to be a problem with the pre departure clearance's and did not seem too concerned. I am not sure if I am required to check the pre departure clearance myself but could easily incorporate it into my FMC route check. I think our clearance should have been input as a SID departure on our release; not as a flight plan exactly as on our release followed by a SID with no plus or minus to indicate a change. The clearance by itself looked like a vector departure. I intended to keep the release but cannot find it now. Basically; we failed to see the additional clearance items. If I had looked at the pre departure clearance I would have known we were doing the mountain 5. I have not flown with a new guy in a long; long time and should have known to verify everything. Also; when handed to departure; I stated runway heading to 9000 ft and expected to be corrected if this was not our clearance. Supplemental information from acn 777099: received pre departure clearance. The pre departure clearance routing matched the release exactly. After reading the pre departure clearance I ensured the proper routing on route page 2 as well as the legs page of the FMC. Upon completion of the before start checklist; I briefed the captain on the routing that I had put into the FMC; and we checked to ensure it was correct. Start; taxi and takeoff were normal. No distrs; pressures; etc. Passing approximately 7000 ft the controller asked us if we were in our turn; to which the captain responded negative; we are runway heading to 10000 ft. The controller then told us to come left to 070 degrees; we had been cleared for the mountain 5 departure. He told us we could sort it out later. Upon rechking the pre departure clearance; I realized that I failed to recognize below the shorthand text of the routing; the words 'mountain 5 departure.' even though I read both pages of the pre departure clearance; somehow I missed that important note. I know that if the mountain 5 departure was abbreviated in the shorthand text of the routing on the pre departure clearance; I would not have missed it. The captain called seattle departure control after arriving and they expressed no concern about the event. It was my mistake and I learned a great lesson about using pre departure clearance's. If the pre departure clearance routing shorthand contained all routing information or if the mountain 5 departure addition contained minus or plus; it would have clued me in that the pre departure clearance was different from the 01 route and the release. All that said; I still should not have missed this.
Original NASA ASRS Text
Title: FLT CREW REPORTS MISSING SID CHANGE TO MOUNTAIN 5 ON PDC; AND HAS TRACK DEV DEPARTING SEA.
Narrative: PDC RECEIVED BY FO (FIRST TRIP AFTER IOE). CLRNC WAS VERBATIM AS FILED ON OUR RELEASE EXCEPT MOUNTAIN 5 DEP LISTED AFTER CLRNC. THERE WERE NO MINUSES (-) OR PLUSES (+) IN THE CLRNC. FO READ THE CLRNC AS RWY HDG TO 9000 FT. I DID NOT CHK THE PDC DUE TO LAST MIN PAX ISSUES. I DID ASK IF THERE WAS A SID AND HE SAID NO. ON DEP; WHEN HANDED TO DEP CTL; I STATED WE WERE ON RWY HDG CLBING TO 9000 FT. PASSING ABOUT 6 DME DEP ASKED IF WE HAD BEEN GIVEN A SID; THEN GAVE US A TURN AND ASKED IF WE HAD RECEIVED AN ELECTRONIC CLRNC. HE SAID IT SEEMED TO BE A PROB WITH THE PDC'S AND DID NOT SEEM TOO CONCERNED. I AM NOT SURE IF I AM REQUIRED TO CHK THE PDC MYSELF BUT COULD EASILY INCORPORATE IT INTO MY FMC RTE CHK. I THINK OUR CLRNC SHOULD HAVE BEEN INPUT AS A SID DEP ON OUR RELEASE; NOT AS A FLT PLAN EXACTLY AS ON OUR RELEASE FOLLOWED BY A SID WITH NO PLUS OR MINUS TO INDICATE A CHANGE. THE CLRNC BY ITSELF LOOKED LIKE A VECTOR DEP. I INTENDED TO KEEP THE RELEASE BUT CANNOT FIND IT NOW. BASICALLY; WE FAILED TO SEE THE ADDITIONAL CLRNC ITEMS. IF I HAD LOOKED AT THE PDC I WOULD HAVE KNOWN WE WERE DOING THE MOUNTAIN 5. I HAVE NOT FLOWN WITH A NEW GUY IN A LONG; LONG TIME AND SHOULD HAVE KNOWN TO VERIFY EVERYTHING. ALSO; WHEN HANDED TO DEP; I STATED RWY HDG TO 9000 FT AND EXPECTED TO BE CORRECTED IF THIS WAS NOT OUR CLRNC. SUPPLEMENTAL INFO FROM ACN 777099: RECEIVED PDC. THE PDC ROUTING MATCHED THE RELEASE EXACTLY. AFTER READING THE PDC I ENSURED THE PROPER ROUTING ON RTE PAGE 2 AS WELL AS THE LEGS PAGE OF THE FMC. UPON COMPLETION OF THE BEFORE START CHKLIST; I BRIEFED THE CAPT ON THE ROUTING THAT I HAD PUT INTO THE FMC; AND WE CHKED TO ENSURE IT WAS CORRECT. START; TAXI AND TKOF WERE NORMAL. NO DISTRS; PRESSURES; ETC. PASSING APPROX 7000 FT THE CTLR ASKED US IF WE WERE IN OUR TURN; TO WHICH THE CAPT RESPONDED NEGATIVE; WE ARE RWY HDG TO 10000 FT. THE CTLR THEN TOLD US TO COME L TO 070 DEGS; WE HAD BEEN CLRED FOR THE MOUNTAIN 5 DEP. HE TOLD US WE COULD SORT IT OUT LATER. UPON RECHKING THE PDC; I REALIZED THAT I FAILED TO RECOGNIZE BELOW THE SHORTHAND TEXT OF THE ROUTING; THE WORDS 'MOUNTAIN 5 DEP.' EVEN THOUGH I READ BOTH PAGES OF THE PDC; SOMEHOW I MISSED THAT IMPORTANT NOTE. I KNOW THAT IF THE MOUNTAIN 5 DEP WAS ABBREVIATED IN THE SHORTHAND TEXT OF THE ROUTING ON THE PDC; I WOULD NOT HAVE MISSED IT. THE CAPT CALLED SEATTLE DEP CTL AFTER ARRIVING AND THEY EXPRESSED NO CONCERN ABOUT THE EVENT. IT WAS MY MISTAKE AND I LEARNED A GREAT LESSON ABOUT USING PDC'S. IF THE PDC ROUTING SHORTHAND CONTAINED ALL ROUTING INFO OR IF THE MOUNTAIN 5 DEP ADDITION CONTAINED MINUS OR PLUS; IT WOULD HAVE CLUED ME IN THAT THE PDC WAS DIFFERENT FROM THE 01 RTE AND THE RELEASE. ALL THAT SAID; I STILL SHOULD NOT HAVE MISSED THIS.
Data retrieved from NASA's ASRS site as of May 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.