Narrative:

Seattle, wa, to ontario, ca, july time. The listing of center stored flight plans showed us filed J-5 lkv J-67 lin. After initializing our flight management system (FMS) on the ground in sea we checked that it agreed on the route with our center stored flight plan. After passing lkv southbound and established ourselves on J-67 toward lin, sea center questioned where we were going and said that their data showed us continuing on J-5 to ehf. Upon returning to dispatch office in seattle we discovered that effective july sun, the center stored route had been changed, dispatch knew it, seattle center knew it, but the flight crews had not been informed. On thur, july the flight crews received a revision, dated sun, july, with the new route in it. Suggestion to avoid this in the future: issue changes to pilots in a timely manner so we don't go flying where we are not filed, and furthermore update the data in the flight management system whenever a center stored route is changed. I realize that this is primary an in-house problem, but it sure could have been a much greater ATC problem had sea center radar been out and the controller had not detected our deviation from flight plan. Supplemental information from acn 150280. In the future when there is a question concerning flight plans I will ask for a full route clearance.

Google
 

Original NASA ASRS Text

Title: FLT CREW OF LGT ENROUTE SEA TO ONT FLIES WRONG COURSE BECAUSE THEY WERE NOT INFORMED THAT THERE HAD BEEN A CHANGED IN THE CENTER STORED FLT PLAN ROUTE.

Narrative: SEATTLE, WA, TO ONTARIO, CA, JULY TIME. THE LISTING OF CTR STORED FLT PLANS SHOWED US FILED J-5 LKV J-67 LIN. AFTER INITIALIZING OUR FLT MGMNT SYS (FMS) ON THE GND IN SEA WE CHKED THAT IT AGREED ON THE RTE WITH OUR CTR STORED FLT PLAN. AFTER PASSING LKV SBND AND ESTABLISHED OURSELVES ON J-67 TOWARD LIN, SEA CTR QUESTIONED WHERE WE WERE GOING AND SAID THAT THEIR DATA SHOWED US CONTINUING ON J-5 TO EHF. UPON RETURNING TO DISPATCH OFFICE IN SEATTLE WE DISCOVERED THAT EFFECTIVE JULY SUN, THE CTR STORED RTE HAD BEEN CHANGED, DISPATCH KNEW IT, SEATTLE CTR KNEW IT, BUT THE FLT CREWS HAD NOT BEEN INFORMED. ON THUR, JULY THE FLT CREWS RECEIVED A REVISION, DATED SUN, JULY, WITH THE NEW RTE IN IT. SUGGESTION TO AVOID THIS IN THE FUTURE: ISSUE CHANGES TO PLTS IN A TIMELY MANNER SO WE DON'T GO FLYING WHERE WE ARE NOT FILED, AND FURTHERMORE UPDATE THE DATA IN THE FLT MGMNT SYS WHENEVER A CTR STORED RTE IS CHANGED. I REALIZE THAT THIS IS PRIMARY AN IN-HOUSE PROB, BUT IT SURE COULD HAVE BEEN A MUCH GREATER ATC PROB HAD SEA CTR RADAR BEEN OUT AND THE CTLR HAD NOT DETECTED OUR DEV FROM FLT PLAN. SUPPLEMENTAL INFO FROM ACN 150280. IN THE FUTURE WHEN THERE IS A QUESTION CONCERNING FLT PLANS I WILL ASK FOR A FULL RTE CLRNC.

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.