Narrative:

On a ferry flight from iln to phl and was cruising at FL330. Approximately 10 NM west (jst) VOR cleared via the bucks arrival (STAR) to phl. ZOB cleared the flight to cross a point 40 mi west of har VOR at FL250. As we approached jst the aircraft began to fly outbound on a different course from what my flight program showed on the long range navigation (lrn). It was at this time that I disconnected the autoplt which uses the captain's lrn information. The captain had inserted a waypoint for the crossing restr on the wrong side of har (east instead of west) and the wrong information was being displayed and used by the autoplt. It was at this time that ATC gave us a vector off the arrival and a speed restr for additional traffic sequencing. The captain was also slow in dialing up VOR frequencys to provide xrefing information and I was slow in starting my descent to make the crossing restr. I pointed out the programming error to the captain and began using my lrn for distance information. Due to a strong tailwind and having to limit our speed in the descent for sequencing, I realized we were going to miss the crossing restr. We attempted to advise ATC that we were going to be a little high, but frequency congestion prevented this. As the controller handed us off the new york ARTCC he asked us if we were going to make the restr, we informed him that we would be a little high and he chastised us for not telling him sooner. We reached FL250, 37 mi west of har missing our restr by 3 NM. Contributing factors were captain lrn programming error, along with failure to select backup information, and frequency congestion which prevented ATC notification. (No aircraft conflict was observed or reported. No evasive action required.)

Google
 

Original NASA ASRS Text

Title: ERRONEOUS WAYPOINT INFO CAUSED PLTDEV.

Narrative: ON A FERRY FLT FROM ILN TO PHL AND WAS CRUISING AT FL330. APPROX 10 NM W (JST) VOR CLRED VIA THE BUCKS ARR (STAR) TO PHL. ZOB CLRED THE FLT TO CROSS A POINT 40 MI W OF HAR VOR AT FL250. AS WE APCHED JST THE ACFT BEGAN TO FLY OUTBOUND ON A DIFFERENT COURSE FROM WHAT MY FLT PROGRAM SHOWED ON THE LONG RANGE NAV (LRN). IT WAS AT THIS TIME THAT I DISCONNECTED THE AUTOPLT WHICH USES THE CAPT'S LRN INFO. THE CAPT HAD INSERTED A WAYPOINT FOR THE XING RESTR ON THE WRONG SIDE OF HAR (E INSTEAD OF W) AND THE WRONG INFO WAS BEING DISPLAYED AND USED BY THE AUTOPLT. IT WAS AT THIS TIME THAT ATC GAVE US A VECTOR OFF THE ARR AND A SPD RESTR FOR ADDITIONAL TFC SEQUENCING. THE CAPT WAS ALSO SLOW IN DIALING UP VOR FREQS TO PROVIDE XREFING INFO AND I WAS SLOW IN STARTING MY DSCNT TO MAKE THE XING RESTR. I POINTED OUT THE PROGRAMMING ERROR TO THE CAPT AND BEGAN USING MY LRN FOR DISTANCE INFO. DUE TO A STRONG TAILWIND AND HAVING TO LIMIT OUR SPD IN THE DSCNT FOR SEQUENCING, I REALIZED WE WERE GOING TO MISS THE XING RESTR. WE ATTEMPTED TO ADVISE ATC THAT WE WERE GOING TO BE A LITTLE HIGH, BUT FREQ CONGESTION PREVENTED THIS. AS THE CTLR HANDED US OFF THE NEW YORK ARTCC HE ASKED US IF WE WERE GOING TO MAKE THE RESTR, WE INFORMED HIM THAT WE WOULD BE A LITTLE HIGH AND HE CHASTISED US FOR NOT TELLING HIM SOONER. WE REACHED FL250, 37 MI W OF HAR MISSING OUR RESTR BY 3 NM. CONTRIBUTING FACTORS WERE CAPT LRN PROGRAMMING ERROR, ALONG WITH FAILURE TO SELECT BACKUP INFO, AND FREQ CONGESTION WHICH PREVENTED ATC NOTIFICATION. (NO ACFT CONFLICT WAS OBSERVED OR RPTED. NO EVASIVE ACTION REQUIRED.)

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.