37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 209150 |
Time | |
Date | 199205 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : dfw |
State Reference | TX |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | other personnel |
Qualification | other |
ASRS Report | 209150 |
Person 2 | |
Affiliation | company : air carrier |
Function | other personnel other |
Qualification | other other : other |
Events | |
Anomaly | non adherence : published procedure non adherence : far |
Independent Detector | other other : unspecified |
Resolutory Action | other |
Consequence | faa : investigated |
Supplementary | |
Primary Problem | Airport |
Air Traffic Incident | other |
Narrative:
It was discovered that our data base was compromised. Somehow, someone updated the computer to allow it to accept airports not listed as alternates in our flight plan data base. It appears it affected our fleet only. How many flts were dispatched with illegal alternates is anyone's guess. We dispatchers do not normally look up authorized airports in the operations specifications. The data base is supposed to be the control. I suppose in these days of automation we need to get back in the 'books.' callback conversation with reporter revealed the following information. Reporter said a dispatch analyst was updating the dispatch data base and erroneously changed some airports to approved alternates when they were in fact not approved. He said it was a human error with no ulterior motives. He said the errors have been corrected but pointed out that nothing has been done to prevent the same thing from happening again. He mentioned 2 other reports he has sent in regarding data base errors which could also happen again. His main complaint is that when errors are found, they are corrected but nothing is done to prevent a recurrence.
Original NASA ASRS Text
Title: ACR DISPATCH COMPUTER CORRUPTED WHEN DATA BASE WAS CHANGED TO AUTHORIZE CERTAIN ARPTS TO BE USED AS ALTERNATES WHEN THEY ARE REALLY ILLEGAL FOR SUCH USE.
Narrative: IT WAS DISCOVERED THAT OUR DATA BASE WAS COMPROMISED. SOMEHOW, SOMEONE UPDATED THE COMPUTER TO ALLOW IT TO ACCEPT ARPTS NOT LISTED AS ALTERNATES IN OUR FLT PLAN DATA BASE. IT APPEARS IT AFFECTED OUR FLEET ONLY. HOW MANY FLTS WERE DISPATCHED WITH ILLEGAL ALTERNATES IS ANYONE'S GUESS. WE DISPATCHERS DO NOT NORMALLY LOOK UP AUTHORIZED ARPTS IN THE OPS SPECS. THE DATA BASE IS SUPPOSED TO BE THE CTL. I SUPPOSE IN THESE DAYS OF AUTOMATION WE NEED TO GET BACK IN THE 'BOOKS.' CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO. RPTR SAID A DISPATCH ANALYST WAS UPDATING THE DISPATCH DATA BASE AND ERRONEOUSLY CHANGED SOME ARPTS TO APPROVED ALTERNATES WHEN THEY WERE IN FACT NOT APPROVED. HE SAID IT WAS A HUMAN ERROR WITH NO ULTERIOR MOTIVES. HE SAID THE ERRORS HAVE BEEN CORRECTED BUT POINTED OUT THAT NOTHING HAS BEEN DONE TO PREVENT THE SAME THING FROM HAPPENING AGAIN. HE MENTIONED 2 OTHER RPTS HE HAS SENT IN REGARDING DATA BASE ERRORS WHICH COULD ALSO HAPPEN AGAIN. HIS MAIN COMPLAINT IS THAT WHEN ERRORS ARE FOUND, THEY ARE CORRECTED BUT NOTHING IS DONE TO PREVENT A RECURRENCE.
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.