2008-03 · NASA ASRS report 777315
FLT CREW REPORTS MISSING SID CHANGE TO MOUNTAIN 5 ON PDC; AND HAS TRACK DEV DEPARTING SEA.
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.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.