Narrative:

ATC asked if our routing was tvc J522 yyz. We said 'yes' and then were told we were so of the arwy and to turn left heading 070 to avoid a hot military area. (This ATC assigned airspace was unknown to the crew until the next day because the department of defense, for security reasons, will not allow it to be depicted on navigation charts). We then were cleared 'direct au sable (asp) J552.' I programmed 'direct asp' in the mcdu and selected 'managed navigation' on the flight management panel (fmp). I then line selected asp and entered 'J522/yyz' and inserted. The scratch pas showed 'arwy mismatch'. Thinking I made a programming error, I tried again; same outcome. I suspected a clearance error and I checked the hl chart and confirmed 'asp' was not on J522. Meanwhile, valuable time and distance passed and controller gave a 160 heading to void a hot military area. (This unknown second area was not realized until a few mins later). I turned the heading bug in the direction of 160 and aircraft gave me 15 degrees angle of bank. I used this moment to correctly enter the arwy using 'tvc J522 yyz' and it appeared. ATC then asked if we were in 160 heading and we said we were coming to it after momentarily holding 110. At the same time the first officer in addition to talking to ATC and verifying programming remotely tuned tvc and displayed it in VOR mode on his navigation display (nd). At this point my nd showed the aircraft north of course and the first officer nd showed aircraft intercepting the runway right. We then turned left to proceed using the first officer nd and eventually were cleared direct alb. The next day I discussed this evolution with my employer and visited ZMP center to see their display. While there I watched the same flight proceed through the area safely because the captain added 'klant' intersection using place/bearing-place/bearing on the primary flight plan page. This was done because the aircraft data base as confirmed by me airborne and the company later, did not have 'klant' in the data base. This resulted in the following: mcdu flight plan = msp J106 crb J522 yyz roc alb gomz bos. Actual flight plan = msp J106 grb J522 tvc yyz roc alb gomz bos. The crew was unknowingly proceeding from tvc direct to yyz with the potential to enter a hot military area. As a result of the incorrect data base and ATC clearance not initially being valid at asp, we entered a hot area north of the arwy. Our secondary flight plan, which was a copy of the initial primary matched the clearance given in msp.

Related reports:

Google
 

Original NASA ASRS Text

Title: ADVTECH ACR LFT EXPERIENCES TRACK DEVIATION DUE DIFFERENCE BETWEEN FILED FLT PLAN AND THAT STORED IN ACFT FMS DATA BASE.

Narrative: ATC ASKED IF OUR RTING WAS TVC J522 YYZ. WE SAID 'YES' AND THEN WERE TOLD WE WERE SO OF THE ARWY AND TO TURN L HDG 070 TO AVOID A HOT MIL AREA. (THIS ATC ASSIGNED AIRSPACE WAS UNKNOWN TO THE CREW UNTIL THE NEXT DAY BECAUSE THE DEPT OF DEFENSE, FOR SECURITY REASONS, WILL NOT ALLOW IT TO BE DEPICTED ON NAV CHARTS). WE THEN WERE CLRED 'DIRECT AU SABLE (ASP) J552.' I PROGRAMMED 'DIRECT ASP' IN THE MCDU AND SELECTED 'MANAGED NAV' ON THE FLT MGMNT PANEL (FMP). I THEN LINE SELECTED ASP AND ENTERED 'J522/YYZ' AND INSERTED. THE SCRATCH PAS SHOWED 'ARWY MISMATCH'. THINKING I MADE A PROGRAMMING ERROR, I TRIED AGAIN; SAME OUTCOME. I SUSPECTED A CLRNC ERROR AND I CHKED THE HL CHART AND CONFIRMED 'ASP' WAS NOT ON J522. MEANWHILE, VALUABLE TIME AND DISTANCE PASSED AND CTLR GAVE A 160 HDG TO VOID A HOT MIL AREA. (THIS UNKNOWN SEC AREA WAS NOT REALIZED UNTIL A FEW MINS LATER). I TURNED THE HDG BUG IN THE DIRECTION OF 160 AND ACFT GAVE ME 15 DEGS ANGLE OF BANK. I USED THIS MOMENT TO CORRECTLY ENTER THE ARWY USING 'TVC J522 YYZ' AND IT APPEARED. ATC THEN ASKED IF WE WERE IN 160 HDG AND WE SAID WE WERE COMING TO IT AFTER MOMENTARILY HOLDING 110. AT THE SAME TIME THE F/O IN ADDITION TO TALKING TO ATC AND VERIFYING PROGRAMMING REMOTELY TUNED TVC AND DISPLAYED IT IN VOR MODE ON HIS NAV DISPLAY (ND). AT THIS POINT MY ND SHOWED THE ACFT N OF COURSE AND THE F/O ND SHOWED ACFT INTERCEPTING THE RWY R. WE THEN TURNED L TO PROCEED USING THE F/O ND AND EVENTUALLY WERE CLRED DIRECT ALB. THE NEXT DAY I DISCUSSED THIS EVOLUTION WITH MY EMPLOYER AND VISITED ZMP CTR TO SEE THEIR DISPLAY. WHILE THERE I WATCHED THE SAME FLT PROCEED THROUGH THE AREA SAFELY BECAUSE THE CAPT ADDED 'KLANT' INTXN USING PLACE/BEARING-PLACE/BEARING ON THE PRIMARY FLT PLAN PAGE. THIS WAS DONE BECAUSE THE ACFT DATA BASE AS CONFIRMED BY ME AIRBORNE AND THE COMPANY LATER, DID NOT HAVE 'KLANT' IN THE DATA BASE. THIS RESULTED IN THE FOLLOWING: MCDU FLT PLAN = MSP J106 CRB J522 YYZ ROC ALB GOMZ BOS. ACTUAL FLT PLAN = MSP J106 GRB J522 TVC YYZ ROC ALB GOMZ BOS. THE CREW WAS UNKNOWINGLY PROCEEDING FROM TVC DIRECT TO YYZ WITH THE POTENTIAL TO ENTER A HOT MIL AREA. AS A RESULT OF THE INCORRECT DATA BASE AND ATC CLRNC NOT INITIALLY BEING VALID AT ASP, WE ENTERED A HOT AREA N OF THE ARWY. OUR SECONDARY FLT PLAN, WHICH WAS A COPY OF THE INITIAL PRIMARY MATCHED THE CLRNC GIVEN IN MSP.

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.