A B757-200 DISPATCHER; USING HIS COMPANY'S APPROVED SOFTWARE; WAS UNABLE TO COME UP WITH THE SAME FLT PLAN THAT WAS ISSUED BY LAS CLRNC DELIVERY.
Synopsis
A B757-200 DISPATCHER; USING HIS COMPANY'S APPROVED SOFTWARE; WAS UNABLE TO COME UP WITH THE SAME FLT PLAN THAT WAS ISSUED BY LAS CLRNC DELIVERY.
Narrative
WHILE PLANNING A FLT FROM LAS-ORD; FILED LAS.AACES2.DVC.J146.GLD.J192.PWE..IRK.BDF3.ORD. CAPT RECEIVED AN ATC REROUTE AFTER PUSHBACK OF LAS.AACES2.BCE.J100.EKR..BFF.J94.DBQ..JVL..ORD. I TRIED TO RUN FLT PLAN USING COMPANY SOFTWARE BY RUNNING A RTE OVER BFF ONLY; BUT NOT IGNORING DEP/ARR. THE SOFTWARE BUILT LAS.AACCES2.J100.EKR.J116.FAF.J94.DBQ..JVL..ORD. I THEN TRIED TO BUILD IT IGNORING DEP/ARR AND ENTERING RTE BCE.J100.EKR..BFF.J94.JVL. THE SOFTWARE PRODUCED LAS.AACES2.BCE.J100.EKR.J116.FQF..BFF.J94.DBQ..JVL..ORD. I THEN ATTEMPTED TO RUN IT A THIRD TIME; ENTERING RTE AND SOFTWARE STILL PRODUCED LAS.AACES2.BCE.J100.EKR.J116.FQF..BFF.J94.DBQ..JVL..ORD. I EVENTUALLY HAD TO RUN A FORWARD FLT PLAN WHICH DOES NOT CHK DRIFTDOWN. THIS HAS A MAJOR IMPACT ON BOTH SAFETY AND DISPATCHER WORKLOAD; WHICH COULD LEAD TO FURTHER SAFETY ISSUES. DISPATCHER HAS ONLY 2 OPTIONS. USE THE FORWARD FLT PLANNING SYS AND CHK DRIFTDOWN MANUALLY; OR HAVE THE FIC BUILD A RTE; BOTH OF WHICH ARE TIME CONSUMING AND CAN CAUSE LENGTHY UNNEEDED DELAYS. IN THIS INSTANCE; ACFT WAS VERY LIGHT AND I COULD QUICKLY VERIFY DRIFTDOWN. I ALSO HAD THE CREW CHK DRIFTDOWN NUMBERS. CURRENT FLT PLANNING IS EXTREMELY INEFFICIENT AND POTENTIALLY UNSAFE.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.