We would have to say that this particular accident was a breakdown in
communications in three ways-

First there was a storm coming up from the Southwest similar to Noel
hitting the Northeast over this past weekend. JFK was landing on the
22's . We were a PAA flight approaching from the Southwest
with a BOS alternate . This was a Sunday night if memory serves and we
held over ACY for a one 1 hour plus on our 10 mile legs. Avianca began
making comments about fuel, fuel. , no response from New York. This
was the second breakdown, non-standard communication about their fuel
situation, ATC needed to hear "Crit fuel, or fuel emergency" in order
to get a response sometimes, we were stacked right above them . We
attempted to communicate that an aircraft holding above us might have
a possible fuel problem however that notion was acknowledged and we
were facing a fuel problem of our own, or how long can we hold here
before screwing to BOS we asked the dispatcher? (We had worked this
out previuosly since the Bornman software at the time could not).

Finally getting routed for the ILS 22 at JFK the ceiling had dropped
and the wind picked up, Avianca missed the approach
right in front of us so we were like "Jeez" how low can you go with a
****ty ride like this since, an ordinary approach in 100 and 1/2
usually gives a fairly calm wind condition and a decent. At any rate
we landed no worries however 002 crashed behind us. Avianca's
off-airport landing closed JFK for an hour or so, we did however get
to Boston.

There is a fourth part to this: Do not crash in John McEnroe's
driveway.




n Fri, 02 Nov 2007 02:56:33 GMT, "Mike Isaksen"
wrote:


"Ned" wrote in message ...
Ten Plane Crashes That Changed Aviation
Popular Mechanics David Noland October 13, 2007


I would include the Avianca (ran out of gas) crash in Long Island, NY in the
list. Seems like there was a major rework to the ARTCC traffic desks, and an
explosion of procedural "gate holds", to prevent extended enroute holds.
That's my walkaway from that event.