Narrative:

There have been 2 occasions at ZJX in the last week when the facility's host computer malfunctioned. The ZJX host computer incurred several aborts and start-overs caused by an invalid address. This occurrence was from a known problem that has been around for 10 yrs. This computer failure caused the facility to fall back onto the back-up system darc. While in darc, manual entries/actions normally performed automatically by the computer were required. These actions overwhelmed the controllers at ZJX created unsafe sits and jeopardized the flying public. The system was restored and no actions by facility management have been taken to inform the users (controllers) the nature of the 'known situation' that created the failure. If the users don't know what caused the problem, how can they prevent it from occurring again? 1 day later, around XA00, the host computer failed again. Once again, this overwhelmed the controllers. I was working the data position at R66. I was unable to perform the many tasks that were required of me. I know for a fact that I violated the airspace of several sectors in ZTL's airspace and in ZJX's airspace by allowing aircraft to enter their airspace without their approval or knowledge. 24 hours after this event, the cause is still unknown and is being investigated. During the course of both of these events, the traffic destined to travel in and through the ZJX airspace was not stopped or slowed down. No attempt by the tmu was made to adjust the flow of traffic. These actions further overwhelmed the controllers operating the system and jeopardized the flying public by placing them in an unsafe situation that had become unmanageable. Callback conversation with reporter revealed the following information: reporter stated he did not know what the exact problem was, nor has asked for maintenance/management incident failure clarification, but has 'moved on.' reporter stated that the equipment is old, the problem is 'known' by all and believes it is specific to ZJX.

Google
 

Original NASA ASRS Text

Title: ZJX CTLR ADVISES OF 2 HOST COMPUTER FAILURES WITHIN A 24 HR PERIOD ALLEGEDLY CAUSED BY SOME 'KNOWN' PROB.

Narrative: THERE HAVE BEEN 2 OCCASIONS AT ZJX IN THE LAST WK WHEN THE FACILITY'S HOST COMPUTER MALFUNCTIONED. THE ZJX HOST COMPUTER INCURRED SEVERAL ABORTS AND START-OVERS CAUSED BY AN INVALID ADDRESS. THIS OCCURRENCE WAS FROM A KNOWN PROB THAT HAS BEEN AROUND FOR 10 YRS. THIS COMPUTER FAILURE CAUSED THE FACILITY TO FALL BACK ONTO THE BACK-UP SYS DARC. WHILE IN DARC, MANUAL ENTRIES/ACTIONS NORMALLY PERFORMED AUTOMATICALLY BY THE COMPUTER WERE REQUIRED. THESE ACTIONS OVERWHELMED THE CTLRS AT ZJX CREATED UNSAFE SITS AND JEOPARDIZED THE FLYING PUBLIC. THE SYS WAS RESTORED AND NO ACTIONS BY FACILITY MGMNT HAVE BEEN TAKEN TO INFORM THE USERS (CTLRS) THE NATURE OF THE 'KNOWN SIT' THAT CREATED THE FAILURE. IF THE USERS DON'T KNOW WHAT CAUSED THE PROB, HOW CAN THEY PREVENT IT FROM OCCURRING AGAIN? 1 DAY LATER, AROUND XA00, THE HOST COMPUTER FAILED AGAIN. ONCE AGAIN, THIS OVERWHELMED THE CTLRS. I WAS WORKING THE DATA POS AT R66. I WAS UNABLE TO PERFORM THE MANY TASKS THAT WERE REQUIRED OF ME. I KNOW FOR A FACT THAT I VIOLATED THE AIRSPACE OF SEVERAL SECTORS IN ZTL'S AIRSPACE AND IN ZJX'S AIRSPACE BY ALLOWING ACFT TO ENTER THEIR AIRSPACE WITHOUT THEIR APPROVAL OR KNOWLEDGE. 24 HRS AFTER THIS EVENT, THE CAUSE IS STILL UNKNOWN AND IS BEING INVESTIGATED. DURING THE COURSE OF BOTH OF THESE EVENTS, THE TFC DESTINED TO TRAVEL IN AND THROUGH THE ZJX AIRSPACE WAS NOT STOPPED OR SLOWED DOWN. NO ATTEMPT BY THE TMU WAS MADE TO ADJUST THE FLOW OF TFC. THESE ACTIONS FURTHER OVERWHELMED THE CTLRS OPERATING THE SYS AND JEOPARDIZED THE FLYING PUBLIC BY PLACING THEM IN AN UNSAFE SIT THAT HAD BECOME UNMANAGEABLE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED HE DID NOT KNOW WHAT THE EXACT PROB WAS, NOR HAS ASKED FOR MAINT/MGMNT INCIDENT FAILURE CLARIFICATION, BUT HAS 'MOVED ON.' RPTR STATED THAT THE EQUIP IS OLD, THE PROB IS 'KNOWN' BY ALL AND BELIEVES IT IS SPECIFIC TO ZJX.

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.