Narrative:

Effective jul/xa/01, our marketing department started airbus A319 service to ZZZ. When I came in that night I was told to verify with these A319 crews that they had appropriate approach plates for ZZZ on board. If not, we'd facsimile them. The inbound flight landed shortly after start of my shift without incident. When I started to work up the release for the return flight next morning, I got an alert indicating A319 not authority/authorized for ZZZ. I asked my chief about this, and was told it was ok, that marketing takes care of that before putting a new service in the schedule. But that database just hadn't updated our computer data. (This was at XA45 before database or marketing were working.) I released the flight plan. (Flight actually departs after my shift.) that night when I returned, I was told that there had been an oversight in marketing and that the approval for A319 ZZZ service had not been officially approved (paperwork not completed). We had gotten a temporary approval from the FAA to operate ZZZ A319 service through the next day and that marketing should have the permanent approval by then or we'd discontinue A319 ZZZ operation until approval received. Also, I was advised that our vice president would be 'going to the top' to make sure this didn't happen again.

Google
 

Original NASA ASRS Text

Title: AN AIRLINE DISPATCHER VOICES CONCERNS RELATED TO INTERAGENCY COORD AND THE UPDATE PROBS IN THE DISPATCHER'S COMPUTERS ASSOCIATED WITH ARPT CERTIFICATION BY THE FAA FOR A RTE ARPT APPROVAL OF ZZZ, US.

Narrative: EFFECTIVE JUL/XA/01, OUR MARKETING DEPT STARTED AIRBUS A319 SVC TO ZZZ. WHEN I CAME IN THAT NIGHT I WAS TOLD TO VERIFY WITH THESE A319 CREWS THAT THEY HAD APPROPRIATE APCH PLATES FOR ZZZ ON BOARD. IF NOT, WE'D FAX THEM. THE INBOUND FLT LANDED SHORTLY AFTER START OF MY SHIFT WITHOUT INCIDENT. WHEN I STARTED TO WORK UP THE RELEASE FOR THE RETURN FLT NEXT MORNING, I GOT AN ALERT INDICATING A319 NOT AUTH FOR ZZZ. I ASKED MY CHIEF ABOUT THIS, AND WAS TOLD IT WAS OK, THAT MARKETING TAKES CARE OF THAT BEFORE PUTTING A NEW SVC IN THE SCHEDULE. BUT THAT DATABASE JUST HADN'T UPDATED OUR COMPUTER DATA. (THIS WAS AT XA45 BEFORE DATABASE OR MARKETING WERE WORKING.) I RELEASED THE FLT PLAN. (FLT ACTUALLY DEPARTS AFTER MY SHIFT.) THAT NIGHT WHEN I RETURNED, I WAS TOLD THAT THERE HAD BEEN AN OVERSIGHT IN MARKETING AND THAT THE APPROVAL FOR A319 ZZZ SVC HAD NOT BEEN OFFICIALLY APPROVED (PAPERWORK NOT COMPLETED). WE HAD GOTTEN A TEMPORARY APPROVAL FROM THE FAA TO OPERATE ZZZ A319 SVC THROUGH THE NEXT DAY AND THAT MARKETING SHOULD HAVE THE PERMANENT APPROVAL BY THEN OR WE'D DISCONTINUE A319 ZZZ OP UNTIL APPROVAL RECEIVED. ALSO, I WAS ADVISED THAT OUR VICE PRESIDENT WOULD BE 'GOING TO THE TOP' TO MAKE SURE THIS DIDN'T HAPPEN AGAIN.

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.