HDG TRACK DEV BY A B757 FLT CREW WHEN THEIR ASSIGNED CLRNC WAS THOUGHT TO BE THE MCCRN2 DEP VERSUS THE ATC ASSUMED IDALE2 DEP FROM LAS; NV.

Date: 2003-10 · Aircraft: B757-200 · Phase: climb

Anomalies: deviation-altitude-undershoot|deviation-altitude-crossing-restriction-not-met|deviation-track-heading-all-types|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-clearance

Synopsis

HDG TRACK DEV BY A B757 FLT CREW WHEN THEIR ASSIGNED CLRNC WAS THOUGHT TO BE THE MCCRN2 DEP VERSUS THE ATC ASSUMED IDALE2 DEP FROM LAS; NV.

Narrative

WE WERE FLYING THE DEP AND DEP CTL ASKED IF WE WERE DIRECT SHEAD YET. WE ANSWERED THAT WE WERE ON THE SID AND ANTICIPATING A VECTOR. CTLR ASKED IF WE WERE FLYING THE IDALE 2 DEP. WE TOLD HIM NO; THAT WE WERE ASSIGNED THE MCCRN2.LAS DEP. HE ASKED IF THAT WAS ASSIGNED AND WE REPLIED IN THE AFFIRMATIVE. HE CLRED US BTY AND AS FILED. WE THEN REALIZED THAT WE BOTH MISSED THE REVISED SEGMENT ON THE PDC. ENRTE TO SFO; ZLA ASKED US TO CALL LAS TRACON ON THE GND IN SFO. DURING THE CALL; WE ADMITTED WE MISSED THE CLRNC CHANGE. HE TOLD US THAT REQUIRED SEPARATION WAS NEVER VIOLATED. HE ALSO TOLD US THAT THIS HAPPENED REGULARLY AND THAT THEY WRE TRYING TO GET COMPANY TO FILE THE RNAV DEP AS STANDARD ROUTING. HE THANKED US FOR OUR CANDOR AND SAID IT WAS A DEAD ISSUE. THE CAPT AND I WERE BOTH CALLED AT XA30 FOR AN XD30 RPT. WE BOTH HAD LESS THAN 4 HRS SLEEP PRIOR TO TKOF FROM DEN TO LAS ON THE FIRST LEG. THIS WAS THE MAIN CONTRIBUTING FACTOR AS I FELT EXTREMELY TIRED AND FATIGUED ALL DAY LONG AND IN FACT FOUND MYSELF MISSING LITTLE THINGS. YOU CANNOT PLAN PROPER REST ON RESERVE WHEN A CALL CAN COME AT ANY TIME DAY OR NIGHT WITH AN ASSIGNMENT TO FLY. REQUIRED REST IS NOT ADDRESSING WHAT IT WAS DESIGNED TO DO. CREW SCHEDULING IS USING THE LOOSE RULES TO FIT THEIR NEEDS; NOT THE NEEDS OF THE PLTS TO GET PROPER REST. DURING THE DEP BRIEFING; WE BOTH USED THE (NON RNAV SID) NOTE ON THE FPF TO CONFIRM THE PROPER DEP ROUTING. WE BOTH SHOULD HAVE RECOGNIZED OUR FATIGUE EARLIER AND USED SLOWER MORE DELIBERATE BRIEFINGS TO AVOID THE MISTAKES WE MADE. THIS IS THE SECOND TIME IN THE LAST 2 MONTHS THAT I HAVE EXPERIENCED A FATIGUE INCIDENT; ALTHOUGH THE FIRST DID NOT RESULT IN A COMPANY RPT. IT IS EASY TO SAY THAT PLTS SHOULD NOT FLY WHEN FATIGUED; BUT THE CONDITION IS SO INSIDIOUS THAT IT IS EASILY MISSED. I EXPECT THESE INCIDENTS TO CONTINUE AND INCREASE SYS-WIDE AND HOPE SOMEONE TAKES NOTICE AND ADDRESSES THE ROOT CAUSES.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.