FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Varig Flight 254

3 Sept 1989 · Near São José do Xingu, Brazil

Boeing 737-241 · Major navigational error resulting in fuel exhaustion

From São Paulo/Guarulhos–Governor André Franco Montoro International Airport (GRU) to Val de Cans/Júlio Cezar Ribeiro International Airport (BEL)

Report a problem

Event

Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
Event fatalities
12 · all aircraft and ground
Ground fatalities
Unknown
Occupants
54
Survivors
42
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
34
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline

Boeing 737-241

Flight
RG254
Aircraft type
Boeing 737
Category
Airplane · from aircraft type
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
PP-VMK
Operator
Varig
Onboard fatalities
12
Route
From São Paulo/Guarulhos–Governor André Franco Montoro International Airport (GRU)To Val de Cans/Júlio Cezar Ribeiro International Airport (BEL)

Cause areas

  • Personnel issues › Task performance
  • Personnel issues › Psychological
  • Organizational issues › Development
  • Organizational issues › Support/oversight/monitoring

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Varig Flight 254 was a scheduled domestic passenger flight from São Paulo, Brazil, to Belém, capital city of the state of Pará in the country's North Region. On 3 September 1989, the Boeing 737-200 operating this flight had several intermediate stopovers, the last being in Marabá, Pará. Prior to takeoff from Marabá, the crew entered an incorrect heading into the flight computer, flying deep into a remote area of the Amazon jungle. Attempts to reach an alternative airport were unsuccessful and the plane eventually ran out of fuel, crashing during a belly landing in the jungle 1700 km northwest of Rio de Janeiro. Of the 54 passengers and crew, 12 passengers died and many more sustained serious injuries. The survivors were rescued two days later.

Background

The flight was a scheduled service from São Paulo to Belém with stopovers in Uberaba, Uberlândia, Goiânia, Brasília, Imperatriz, Marabá, and finally Belém. The São Paulo–Belém route had an approximate duration of eight hours and 20 minutes. At 9:43, Flight 254 left Guarulhos International Airport, São Paulo, heading towards Belém. The flight crew consisted of 32-year-old Captain Cézar Augusto Padula Garcez, First Officer Nilson de Souza Zille, 29, and four flight attendants. The flight went smoothly through all the stops, and at 17:20, the crew was arranging the final preparations at Marabá Airport while the passengers were boarding.

Accident

While First Officer Zille was making an external inspection of the aircraft, Captain Garcez consulted the flight plan for the magnetic heading to Belém; the flight plan read 0270. Garcez interpreted this as 270°, but it was intended to mean 027.0°. Varig's heading notation for the flight plan was changed to four digits from three while Garcez was on vacation, and it did not explicitly specify the position for the decimal point, which was implicitly located between the last two digits. That confusion was the primary cause for the disaster, along with other minor errors. The captain, therefore, set the left-side horizontal situation indicator (HSI) to 270°, i.e. a due-west course. This heading is clearly inconsistent with a route from Marabá to Belém.

After setting the HSI, Garcez programmed the aircraft performance management system (PMS) to the distance to Belém (187 nmi). The flight plan indicated an altitude of 29000 ft (FL290), and a leg duration of 48 minutes. When co-captain Zille got to his seat, instead of checking his own flight plan to adjust his HSI – as he was required to do – he only referenced the captain's indicator and set his to match it. At 17:45, flight 254 took off from Marabá, and the autopilot steered the aircraft to a heading of 270° away. When Garcez believed the aircraft to be close to the destination, he attempted to use his VHF radio to communicate with the Belém tower. Failing to do so directly, he used another Varig airliner operating flight RG266, as a radio relay to talk to Belém Airport. When Garcez managed to establish communications with Belém, he requested descent clearance, and received it. Upon performing his descent, the captain found it very odd that he could not recognize any of the characteristic geographical features of the Belém area (such as the Marajó Island and the Amazon River estuary), and even asked the tower controller if the city was without electricity. In 1989, Belém airport still had no radar, so the controller informed Flight 254 that it was the only one in its airspace, and gave it landing clearance.

After the PMS started indicating negative distance to its destination, Captain Garcez decided to execute a 180° turn and locate Belém visually. He also descended the aircraft to 4000 ft and reduced its speed to 200 kn. Reluctant to use the HF radio to request help, the captain decided to take visual reference from a river he located below the plane, believing it to be the Amazon. The river was actually the Xingu, which runs chiefly south-north, while the Amazon runs west-east.

At that time, the flight had already taken 30 minutes longer than scheduled, and the passengers were getting anxious. When First Officer Zille finally noticed their initial mistake, the captain and he decided, after checking their navigation charts, to make contact with Santarém airport, believing it to be the closest airport, and made an almost 180° turn, now establishing a 350° magnetic course. After some calculations, Garcez realized that the aircraft did not have the necessary fuel to reach Santarém, and he started heading south again (along the now properly identified Xingu River). Finally, he decided to contact Marabá airport again, to find his location. The radio frequency of Goiânia's locator was the same as Marabá's, and Garcez mistakenly tuned to Goiânia, located about 675 nmi south of Marabá. The captain was already nervous, and he failed to notice that the tuned locator's Morse code identifier was not consistent with Marabá's beacon.

At 20:05, Belém Center called Flight 254 again, demanding a report. The captain stated that he had a 170° magnetic heading to Marabá (in reality it was Goiânia), and that he was receiving a bearing from the Carajás beacon (which actually was the Barra do Garças beacon). Garcez was perplexed when Belém informed him that the Carajás beacon had been shut down since 19:30, and the center decided to illuminate the Carajás runway in an attempt to facilitate Flight 254's orientation. Realizing that he would not have enough fuel to reach Belém, the captain decided to head for Carajás Airport, which would have been the correct decision if he had not mistaken Goiânia for Marabá. Another opportunity to solve the situation was missed around 20:30, when the flight passed within 100 nmi of the Serra do Cachimbo Air Force Base, a very large airfield, which the 737 could have successfully reached.

After that, the forced landing of the aircraft into the rainforest in the north of Mato Grosso became inevitable. At the time, no written procedures were available for such an emergency situation. Garcez and Zille decided to fly at 8000 ft until they ran out of fuel, thus avoiding a possible explosion upon landing, and with the engines on, they would still have hydraulic power to command the aircraft's ailerons and flaps. They also decided to keep the plane flying slightly above stall speed, which in this case was around 150 kn. During their descent, they spotted very few lights through the jungle, coming from the houses of farms that had electrical generators. At 20:40, Garcez informed the Belém center that he would be making a forced landing over the jungle. A few minutes later, when he had 15 minutes left of fuel, Garcez informed his passengers of the situation. When around 100 kg of fuel were remaining, the left engine stopped. The right engine ran for a further two minutes, and then stopped, as well.

Even after shutdown, the engines were still windmilling due to the passage of the air through them. This gave the airplane some rudimentary and unreliable hydraulic control. Garcez commanded the lowering of the flaps, which only moved to position two (around 10°) due to the failing hydraulic system. With the batteries discharged, the plane had no electrical power and the only four instruments working in the cockpit were the artificial horizon, altimeter, airspeed indicator, and vertical speed indicator. The only things the crew could see on the horizon were faint light spots due to distant forest burnings, and at 21:06, local time, the plane crash-landed over treetops that extended over 50 m above ground.

The deceleration due to the crash was such that passengers without fastened seatbelts were flung to the front of the airplane, and some seats detached from the floor, also racing forward. When the aircraft fell through the foliage, two thick trees tore away both wings, and caused a severe torsion of the fuselage, which contributed to more seats detaching, and to the collapsing of the false roof over the passengers' heads. After its speed slowed to about 35 kn, the aircraft ran for little more than 30 m and stopped, lying on its right side.

Investigation and cause

Causes

Upon investigation, the crash was found to have been caused primarily by negligence on the part of the flight crew. Customary investigations showed that the aircraft was in perfect condition for the flight, and that its mandatory periodic inspections had been properly conducted. The main factor for the accident was concluded to be an error in reading the correct heading from the flight plan by the commander, compounded by the co-pilot copying the setting from the commander's panel instead of checking the flight plan. The fact that plan course 0270 actually asked for 027.0 degrees was due to the Varig standardization of flight planning for all its fleet, but only aircraft equipped with an inertial navigation system (INS) actually used headings with decimals. Despite the pilots having been told about this peculiarity in the airline's training program, the value expressed in the flight plan 0270 was interpreted by the commander as 270° (he was on vacation during the change of standard). This misinterpretation changed the general direction from north-northeast (27.0°) to west (270°). The Boeing 737 was not equipped with INS, using only automatic direction finders and VHF omnidirectional range.

Months after the accident, the flight plan Varig 254 used was shown to 21 pilots of major airlines in the world during a test conducted by the International Federation of Air Line Pilots' Associations. No fewer than 15 pilots committed the same mistake that the Flight 254 crew had made. After the accident, Varig installed Omega navigation systems in their aircraft.

Also, several other factors contributed to the accident:

the pilot did not realise he should be receiving a stronger VHF signal from Belém if he were nearing that airport,

he should be receiving the local radio stations from Belém instead of other distant stations at the same frequencies,

he should have checked his position and heading against the sun and geographic landmarks,

and the airline's support team in Belém did not take action upon realizing the aircraft arrival was delayed.

Captain Garcez and First Officer Zille were both sentenced to four years in prison for their roles in the accident, but this was later changed to community service.

Text from the Wikipedia article “Varig Flight 254” (revision 1367392896, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

Sources

Wikipedia article: Varig Flight 254
Article
Varig Flight 254
Revision
1367392896 · 2026-08-02 · retrieved 2026-09-18
Wikidata
Q690883
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
Where each value comes from
Record
Wikipedia article "Varig Flight 254" (page 3139386, revision 1367392896)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site
Map position
Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
airline flight number in the infobox
Fatalities
Wikipedia infobox: aircraft fatalities
Ground fatalities
not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (1)
  • Wikipedia · Facts from the Wikipedia article's infobox and coordinates, not checked against an investigation report. Independent review pending.