Flight delays

[Jim Burns[_2_]]

Maybe someone with more understanding of the commercial carrier flight plan
processing system can explain what I heard on MSNBC moments ago....
Extensive flight delays are occurring at Newark, LaGuardia, and JFK due to a
computer problem in Atlanta that failed to relay flight plans to the
appropriate controlling agencies in the NYC area. The system then relayed
the flight plans to a system in Salt Lake City, which became severely
overloaded and ultimately failed.

No mention of specific airlines, so is this another Lockheed hic-up??

Jim

[xyzzy]

On Jun 8, 5:12 pm, "Jim Burns" > wrote:
> Maybe someone with more understanding of the commercial carrier flight plan
> processing system can explain what I heard on MSNBC moments ago....
> Extensive flight delays are occurring at Newark, LaGuardia, and JFK due to a
> computer problem in Atlanta that failed to relay flight plans to the
> appropriate controlling agencies in the NYC area. The system then relayed
> the flight plans to a system in Salt Lake City, which became severely
> overloaded and ultimately failed.
>
> No mention of specific airlines, so is this another Lockheed hic-up??

I also wondered if this was related to the current privatization melt-
down of FSS. They talked about difficulty getting flight plans
through, which sounds like it would be related to our current problems.

[Morgans[_2_]]

"xyzzy" > wrote

> I also wondered if this was related to the current privatization melt-
> down of FSS. They talked about difficulty getting flight plans
> through, which sounds like it would be related to our current problems.

It seems unlikely that it is _not_ in some way connected.
--
Jim in NC

[Peter Clark]

On Mon, 11 Jun 2007 19:31:58 -0400, "Morgans"
> wrote:

>
>"xyzzy" > wrote
>
>> I also wondered if this was related to the current privatization melt-
>> down of FSS. They talked about difficulty getting flight plans
>> through, which sounds like it would be related to our current problems.
>
>It seems unlikely that it is _not_ in some way connected.

I thought the airline dispatch system directly connected to the FAA
flight plan computers and thus FSS and everything FSS related has
nothing to do with them?

[sheamon]

On Jun 11, 4:37 pm, Peter Clark
> wrote:
> On Mon, 11 Jun 2007 19:31:58 -0400, "Morgans"
>
> > wrote:
>
> >"xyzzy" > wrote
>
> >> I also wondered if this was related to the current privatization melt-
> >> down of FSS. They talked about difficulty getting flight plans
> >> through, which sounds like it would be related to our current problems.
>
> >It seems unlikely that it is _not_ in some way connected.

NADIN had an outage, not the cause of Flight Service.

>From the AOPA website:

"Sometimes it's not Lockheed Martin's fault. If you had problems with
your flight plan today, it may have been due to the failure of an FAA
system. The FAA's central data switch in Atlanta - the National
Airspace Data Interchange Network (NADIN) - failed, and all operations
switched over to the Salt Lake City facility. (The NADIN transfers
flight plans from flight service stations to the host computers in the
air route traffic control centers or, if the flight is VFR, to the
appropriate flight service station for the flight's destination. IFR
clearance information is also routed through the NADIN.)

Salt Lake City became overloaded and stopped accepting new flight
plans for a while. The system was restored by afternoon but processing
slower than normal as it worked on catching up on the backlog of
flight plans."

[cwby-flyer]

On Jun 12, 5:35 pm, sheamon > wrote:

> Salt Lake City became overloaded and stopped accepting new flight
> plans for a while. The system was restored by afternoon but processing
> slower than normal as it worked on catching up on the backlog of
> flight plans."

Redundant systems are great (it's my IT job to manage one), however
they do need to be designed so that the backup sites can at least meet
normal workloads.