Narrative:

I arrived for duty on my shift at XA30. I was advised shortly thereafter that the host computer was scheduled to go down for maintenance at XC00. At approximately XB00 I advised the watch supervisor that XC00 was not a good time because of traffic. At XC00 the computer went down. This means no automated flight plan processing, no automated handoffs, no WX information, etc. At the time the computer went down, we were told it was not the scheduled maintenance, but that it had 'flopped.' this was very suspicious in that this type of maintenance is done generally without regard to traffic or controller workload. At the time of the 'failure,' I was working approximately 15 aircraft, with another 15 departures proposed off of atlanta. I was working 3 aircraft on approach to mcn, vectored for ILS, which required constant frequency communication. This left no time to manually pass flight plans. Supplemental information from acn 513806: the WX was IMC at some of the airports that we were providing approach control service for, so aircraft were having to be vectored for approachs also. In addition to that, the inbounds had to be called and we had to call to get the WX at the arrival airports because the automated WX reporting was lost when the computer went down.

Google
 

Original NASA ASRS Text

Title: ZTL CTLR ADDRESSES CONCERN WITH SUPVR TO DELAY MAINT TAKE-DOWN OF HOST COMPUTER ONLY TO OBSERVE THE COMPUTER FAIL WHEN CTLRS STILL HAVE TFC REQUIRING COORD COM CTL WITH OTHER ATC FACILITIES AND ACFT.

Narrative: I ARRIVED FOR DUTY ON MY SHIFT AT XA30. I WAS ADVISED SHORTLY THEREAFTER THAT THE HOST COMPUTER WAS SCHEDULED TO GO DOWN FOR MAINT AT XC00. AT APPROX XB00 I ADVISED THE WATCH SUPVR THAT XC00 WAS NOT A GOOD TIME BECAUSE OF TFC. AT XC00 THE COMPUTER WENT DOWN. THIS MEANS NO AUTOMATED FLT PLAN PROCESSING, NO AUTOMATED HDOFS, NO WX INFO, ETC. AT THE TIME THE COMPUTER WENT DOWN, WE WERE TOLD IT WAS NOT THE SCHEDULED MAINT, BUT THAT IT HAD 'FLOPPED.' THIS WAS VERY SUSPICIOUS IN THAT THIS TYPE OF MAINT IS DONE GENERALLY WITHOUT REGARD TO TFC OR CTLR WORKLOAD. AT THE TIME OF THE 'FAILURE,' I WAS WORKING APPROX 15 ACFT, WITH ANOTHER 15 DEPS PROPOSED OFF OF ATLANTA. I WAS WORKING 3 ACFT ON APCH TO MCN, VECTORED FOR ILS, WHICH REQUIRED CONSTANT FREQ COM. THIS LEFT NO TIME TO MANUALLY PASS FLT PLANS. SUPPLEMENTAL INFO FROM ACN 513806: THE WX WAS IMC AT SOME OF THE ARPTS THAT WE WERE PROVIDING APCH CTL SVC FOR, SO ACFT WERE HAVING TO BE VECTORED FOR APCHS ALSO. IN ADDITION TO THAT, THE INBOUNDS HAD TO BE CALLED AND WE HAD TO CALL TO GET THE WX AT THE ARR ARPTS BECAUSE THE AUTOMATED WX RPTING WAS LOST WHEN THE COMPUTER WENT DOWN.

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.