2014 Santos Cessna Citation accident

Santos

Location of Santos within Brazil

The Cessna Citation 560 XLS+ had taken off from Santos Dumont Airport, Rio de Janeiro, en route to Santos Air Force Base. Due to poor weather at the destination, the first landing attempt was abandoned, and contact was lost at 9:23 am local time. Around 10:00 am, the aircraft crashed into a densely-populated area of the Boqueirão neighbourhood in central Santos, damaging several buildings.[2]

Apart from Eduardo Campos, on board the aircraft were a pilot and a co-pilot, a reporter, a photographer and two of Mr. Campos' campaign aides; no-one survived.[3] Two people on the ground were killed and twelve more were injured.[4][5][6]

Brazil's Aeronautical Accidents Investigation and Prevention Center performed the investigation into the accident. The report identified several factors that contributed to the accident.

Despite an annual maintenance inspection on 14 February 2014 which found that all maintenance was up-to-date, the aircraft's cockpit voice recorder had been inoperable since January 2013.[7]^:140 By law, the aircraft could only fly without a functioning CVR if maintenance on it was scheduled within 15 days, or 30 in exceptional circumstances.[7]^:140 The final report on the accident noted that the pilots' schedule complied with legal duty time and rest requirements, but that "expert examination of voice, speech and language parameters on the day of the accident...indicated...fatigue and somnolence on the part of the copilot in his communications with the ATS units."[7]^:141

The conditions at Santos Dumont Airport had deteriorated since the last meteorological report the pilots had received. The ceiling was 300 feet (91 m) below the safe ceiling for a circle-to-land approach, but allowed an approach using the ECHO 1 route.[7]^:143 Despite informing air traffic control that they would use the ECHO 1 approach to Runway 35, the aircraft was far to the right of the ECHO 1 approach. After reviewing other approaches the captain had made using the flight management system on visual approaches, the investigators hypothesized that the captain was using a visual approach, aided by the FMS, with the intention of joining the ECHO 1 trajectory on final approach. The report notes that the captain used a similar approach in previous landings and that "it is possible that the captain’s experience of landing in runways of other countries with precarious infrastructure conditions, in addition to his mistaken assumption of the real meteorological conditions in the aerodrome, may have contributed to his feeling safe upon adopting such procedure."[7]^:144 However, such an approach, which saved five minutes, was not permissible in the meteorological conditions at the time of the crash, when aircraft could only use instrument only (IFR) approaches.[7]^:144

The reason for abandoning the approach is unknown. Since the meteorological conditions were close to the minimum permitted for an IFR approach, the aircraft would need to approach close to the ECHO 1 approach trajectory. On the aircraft's improper approach, the investigation noted that there was a low probability that the aircraft could have stabilized its approach in order to land safely.[7]^:146 With a wet runway and if the aircraft crossed the threshold at the reference speed, the aircraft would have a 385-metre (1,263 ft) safety margin to land on the wet runway. There was a 2 kn (3.7 km/h) tailwind at the time of the attempted landing. Additionally, a non-directional radio beacon (NDB) just before the runway (RR NDB) was non-functional on the day of the accident. Because the aircraft did not follow the ECHO 1 approach, it did not pass the only NDB available for determining the missed approach point, which was SAT NDB. The report concluded that "the fact that the crew did not follow the profile of the ECHO 1 [approach], along with their difficulty stabilizing the aircraft on a final approach, and the tail wind component condition may have contributed to their decision to discontinue the approach."[7]^:147

The proper missed approach procedure was to make a left turn at the missed approach point—the RR NDB, which was inoperable, or one minute and fifteen seconds past SAT NDB, which the aircraft didn't cross—and climb to 4,000 feet (1,200 m). However, the pilots made a low pass over the runway and began a gentle left turn at the end of the runway. Witnesses state that the aircraft made a low pass over the port before disappearing into the clouds.[7]^:147 On this trajectory, the aircraft made a "tight" turn, with a bank angle up to 60° and g-force up to 2.0 G.[7]^:148 The investigation hypothesized that the pilots were flying manually, therefore leading to a large workload for the pilot-in-command. The missed approach procedure required a significant amount of work that had to be performed in a short time. Investigators noted that "[t]he captain’s personal characteristics, indicating a person with a more impositive and confident posture, in opposition to the more passive posture of the copilot, in addition to the more limited knowledge of the equipment on the part of the latter and the possibility that he (the copilot) was fatigued, may also have hindered the dynamics of the crew in the management of the flight."[7]^:148 Investigators believe the combination of the meteorological conditions, the effect of the high g-forces on the pilots' sense of spatial perception, and that the pilot-in-command would have been rapidly switching his focus between the instrument panel and exterior caused "incapacitating" spatial disorientation, which led to an "abnormal attitude."[7]^:148

The aircraft did not respond to multiple calls from air traffic control after initiating the missed approach, suggesting the pilots were under a heavy workload managing the aircraft. Two images of the aircraft from different cameras moments before the crash show the aircraft at 35° (± 5°) and 22.4° dive angles.[7]^:149–50 The report notes that "the aircraft could only have reached such speed and fly that trajectory[] if it had climbed considerably"[7]^:149 after entering the clouds and that, in normal conditions, the pilots would not have deliberately placed the aircraft in such a steep dive.[7]^:149

Of fracture surfaces examined, none showed signs of fatigue but were caused by stress overload at the moment of impact. There was no abnormality with engine function in the moments before the crash and no evidence of failure of any aircraft system.[7]^:150

It also emerged that the on-board cockpit voice recorder did not record any of the conversations during the flight before it crashed.[8] Unlike bigger airplanes, the Citation Excel was not required by regulations to have a flight data recorder.[9]

• List of fatalities from aviation accidents