Narrative:

We received a message from navigation data that a tape load was being performed. After the tape load was completed; we received another navigation data message stating the load is complete and that if any flight plans required to be refilled the dispatcher needed to enter frc in the remarks line of the release. Due to schedule disruptions flights were operating 60 to 75 minutes late and 6 to 8 flight plans calculated after the tape load ended. I started to receive reject messages from the ATC computer on several fights due to the fact that the host computer did not recognize some of the new SID's that had been filed on these flights. Apparently our tape load was premature and did not coincide with the host computer navigation update. Therefore the flight plans were rejected. This occurred for three flights I was working. I called navigation data to find out what they could do to fix the problem. My attempts to build temporary routes were unsuccessful since our computer did not recognize our old SID's. Dispatch desk worked real hard to get new routes built for me and I was able to refile correct flight plans. All this upheaval occurred during a schedule disruption and a nationwide security threat with all my flights needing information and instruction with regard to threat levels and required responses. I certainly didn't need added confusion that easily could have caused improper flight plan filings; possible gross navigation errors or worse. When I asked one of the navigation data specialists why the tape load was done so early; his response was; 'we always do tape loads at this time.' I recall that this same situation occurred several years ago and the procedure was to have navigation data check with the center manager prior to initiating a tape load to avoid additional confusion during schedule disruption. Also; why do we prematurely change our navigation database so much earlier than the ATC computer and not expect to have these kinds of problems? I reviewed my flights for navigation errors and did not find any on the flight plans but a repeat of this situation is unacceptable.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier Dispatcher reports the company NAV data base being updated prior to the effective time causing many flight plans to be rejected by the ATC computer.

Narrative: We received a message from NAV data that a tape load was being performed. After the tape load was completed; we received another NAV data message stating the load is complete and that if any flight plans required to be refilled the Dispatcher needed to enter FRC in the remarks line of the release. Due to schedule disruptions flights were operating 60 to 75 minutes late and 6 to 8 flight plans calculated after the tape load ended. I started to receive reject messages from the ATC computer on several fights due to the fact that the host computer did not recognize some of the new SID's that had been filed on these flights. Apparently our tape load was premature and did not coincide with the host computer NAV update. Therefore the flight plans were rejected. This occurred for three flights I was working. I called NAV data to find out what they could do to fix the problem. My attempts to build temporary routes were unsuccessful since our computer did not recognize our old SID's. Dispatch desk worked real hard to get new routes built for me and I was able to refile correct flight plans. All this upheaval occurred during a schedule disruption and a nationwide security threat with all my flights needing information and instruction with regard to threat levels and required responses. I certainly didn't need added confusion that easily could have caused improper flight plan filings; possible gross navigation errors or worse. When I asked one of the NAV data specialists why the tape load was done so early; his response was; 'we always do tape loads at this time.' I recall that this same situation occurred several years ago and the procedure was to have NAV data check with the Center Manager prior to initiating a tape load to avoid additional confusion during schedule disruption. Also; why do we prematurely change our NAV database so much earlier than the ATC computer and not expect to have these kinds of problems? I reviewed my flights for NAV errors and did not find any on the flight plans but a repeat of this situation is unacceptable.

Data retrieved from NASA's ASRS site as of April 2012 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.