What happened
A VASP Boeing 727-200, registration PP-SRK, departed São Paulo bound for Fortaleza with a scheduled stop in Rio de Janeiro. On June 8, 1982, at approximately 02:25 local time, the aircraft was descending from flight level 330 toward Fortaleza. Air traffic control authorized the crew to descend to flight level 050 and required them to report crossing flight level 100.
The captain initiated the descent approximately 51 nautical miles earlier than optimal for the route profile. As the aircraft descended, it passed through flight level 090 at 55 nautical miles from Fortaleza but continued descending past the authorized limit of flight level 050 without reporting the crossing of flight level 100 as instructed. The crew appeared to be attempting a visual approach to the illuminated city below, selecting flaps for landing and setting the altitude alert to 1,500 feet, which is the visual traffic pattern altitude for Fortaleza.
At 3,800 feet, the first officer warned the captain about hills ahead, but the descent continued. The aircraft collided with a hill in the Serra da Aratanha range, 14 nautical miles from the airport, at an altitude of 1,950 feet. The impact caused a fire that completely destroyed the aircraft.
The investigation
CENIPA examined flight data recorder (FDR) and cockpit voice recorder (CVR) data, crew qualifications, maintenance records, and meteorological conditions. The weather was clear with good visibility. The DME at Fortaleza was not active, but the aircraft’s inertial navigation system allowed for precise positioning.
The investigation found that the captain had serious personal financial and family problems, though no direct evidence linked these to the accident during flight. Both crew members were medically fit and had adequate rest prior to the flight. The first officer had sufficient experience for the mission. The aircraft’s maintenance was not a contributing factor.
Analysis of the recorders showed the altitude alert sounded twice (at 5,800 feet and 2,300 feet), indicating the aircraft was significantly above its selected altitude. The crew failed to maintain the minimum safe altitude prescribed by instrument approach charts, which restricted descent to 4,500 feet between 25 and 8 nautical miles from the airport.
Findings
The accident was caused by the captain’s failure to adhere to air traffic control instructions and instrument approach procedures while attempting a visual approach at night. Contributing factors included:
- Poor descent planning, initiating descent too early.
- Loss of situational awareness due to fixation on the illuminated city below (spatial disorientation/visual illusion).
- Failure to maintain minimum safe altitude and speed restrictions below flight level 100.
- Lack of crew resource management; the first officer’s warning about terrain was ignored.
- Non-compliance with company operational procedures regarding approach discipline.
Safety action
CENIPA issued several safety recommendations:
- Pilots must prioritize navigation planning and avoid early descents that increase risk.
- Air traffic rules are mandatory for safety; compliance is compulsory.
- Airlines must enforce operational standards to ensure flight discipline.
- Captains must make decisions based on team input, not hierarchical authority alone.
- Non-operating crew members have an obligation to intervene if safety is compromised.
- Airlines should improve performance evaluation systems for instruction and operational monitoring.