Avianca Flight 52, Boeing 707 near New York (1990): fuel state phraseology and fuel planning case study

1. Planned into a busy system. The flight departed Medellin for JFK with the fuel figures and planning recorded in the aircraft paperwork that the NTSB later examined. The report found evidence of roughly 78,000 to 82,000 lb aboard depending on which record was used, and noted Boeing guidance that low-fuel operations required care, especially if vectoring delays or a missed approach were possible.

2. Arrival delays built up. Because of poor weather in the northeastern United States, ATC held the aircraft three times for a total of about 1 hour 17 minutes.

3. The crew asked for priority, not an emergency. While holding at CAMRN, after an EFC of 2105, the first officer said, “I think we need priority.” When asked how long they could hold, he replied they could hold about five minutes, and later said Boston had been the alternate but they could not do that because they would run out of fuel.

4. The crew seems to have believed ATC understood more than ATC actually did. The NTSB cited cockpit conversation beginning about 2109:21 suggesting the crew believed they were being accommodated with priority handling.

5. First approach to JFK. The flight was vectored for the ILS to runway 22L at JFK. During the approach, the report says windshear, fatigue and stress were factors in the unsuccessful completion of the first approach.

6. Missed approach, but still no explicit emergency call. After the approach was discontinued, the captain said, “tell them we are in emergency.” The first officer then transmitted that they would try once again and were “running out of fuel,” but did not use the word “emergency.”

7. Vectors away from the airport. After handoff back to approach, the first officer again said, “we’re running out of fuel sir” while acknowledging climb instructions. The controller responded with headings and altitude, not emergency handling, because the urgency had not been clearly conveyed.

8. Fuel exhaustion. Less than 3 minutes after the final exchange in which the first officer still had not clearly declared an emergency, the engines began flaming out. The aircraft lost power on all four engines and crashed about 16 miles from JFK.

…the captain advised the first officer, “tell them we are in emergency.” […] He did not use the word “emergency,” as instructed by the captain, and therefore did not communicate the urgency of the situation.

NTSB final report, section 2.3.

1. Tight fuel margin. The NTSB found the crew did not adequately manage fuel for a complex arrival with weather, holding, and the possibility of a missed approach. The break point for a pilot is before departure and again en route: fuel must be planned and then re-planned against actual delays.

2. Holding accumulation. ATC held the flight three times for about 1 hour 17 minutes total. When delay starts to consume options, the pilot has to move from hoping for a normal sequence to asking clearly for what is needed.

3. Ambiguous phraseology. The first officer asked for “priority” and later said they were running out of fuel, but the NTSB found controllers did not understand that an emergency existed. The break point here is communications training: if you need emergency handling, say “emergency” or “MAYDAY,” not a softer phrase.

4. Assumed understanding. The captain asked whether ATC had been told they did not have fuel, and the first officer replied that he had already advised them. The NTSB found the first officer incorrectly assumed his request for priority had been understood as a request for emergency handling. The break point is closed-loop cockpit communication: do not assume your message was understood unless the response shows it.

5. Missed approach exposure. The report says the crew failed to consider that they could not allow a missed approach. A go-around is normal in training, but it is never free, it costs fuel, workload, and time.

6. Too late for recovery. After the missed approach, the first officer still said only that they were “running out of fuel sir,” and later “we just running out of fuel.” Less than 3 minutes after that last call the engines began flaming out. The break point had passed: by then the aircraft needed immediate, unmistakable priority.

1. Declare the emergency plainly. If you need immediate help, use the word your training gives you: “MAYDAY” for distress, or at the very least “emergency” in plain English. Avianca 52 shows that “priority” and “running out of fuel” may not produce the handling you think they will.

2. Understand minimum fuel versus emergency fuel. “Minimum fuel” is not the same as an emergency declaration. It tells ATC you cannot accept undue delay, but if the situation has become unsafe or you need priority now, declare the emergency clearly.

3. Plan fuel for the real arrival, not the ideal one. Your fuel plan has to include the possibility of vectors, holding, one approach, and a go-around if the rules or your operation require it. The NTSB highlighted exactly this point by citing both the long delays and Boeing’s warning to add fuel if vectoring or a go-around might happen.

4. Re-plan in flight as conditions change. Good planning is not finished at engine start. When the delays grow, ask early: can I still continue safely, should I divert, and what words do I need to use so ATC understands my limits?

5. Close the loop in the cockpit and on the radio. The captain believed ATC had been told about the fuel emergency, but the NTSB found the message had not been passed in clear emergency terms. In any cockpit, even a training aircraft with one pilot and one instructor, the important question is not “did I say something,” but “did the other side understand it?”

• National Transportation Safety Board: Avianca, The Airline of Colombia, Boeing 707-321B, HK 2016, Fuel Exhaustion, Cove Neck, New York, January 25, 1990, NTSB/AAR-91/04, adopted 30 April 1991
• National Transportation Safety Board: Investigation DCA90MA019, accessed 6 November 2026