Crash of an Airbus A330-203 off Fernando de Noronha: 228 killed

Date & Time: Jun 1, 2009 at 0014 LT
Type of aircraft:
Operator:
Registration:
F-GZCP
Flight Phase:
Survivors:
No
Schedule:
Rio de Janeiro – Paris
MSN:
660
YOM:
2005
Flight number:
AF447
Country:
Crew on board:
12
Crew fatalities:
Pax on board:
216
Pax fatalities:
Other fatalities:
Total fatalities:
228
Captain / Total flying hours:
6547
Captain / Total hours on type:
4479.00
Copilot / Total flying hours:
2936
Copilot / Total hours on type:
807
Aircraft flight hours:
18870
Aircraft flight cycles:
2644
Circumstances:
On Sunday 31 May 2009, the Airbus A330-203 registered F-GZCP operated by Air France was programmed to perform scheduled flight AF 447 between Rio de Janeiro-Galeão and Paris Charles de Gaulle. Twelve crew members (3 flight crew, 9 cabin crew) and 216 passengers were on board. The departure was planned for 22 h 00. At around 22 h 10, the crew was cleared to start up engines and leave the stand. Takeoff took place at 22 h 29. The Captain was Pilot Not Flying (PNF); one of the copilots was Pilot Flying (PF). At the start of the Cockpit Voice Recorder (CVR) recording, shortly after midnight, the aeroplane was in cruise at flight level 350. Autopilot 2 and auto-thrust were engaged. Auto fuel transfer in the “trim tank” was carried out during the climb. The flight was calm. At 1 h 35, the aeroplane arrived at INTOL point and the crew left the Recife frequency to change to HF communication with the Atlántico Oceanic control centre. A SELCAL test was successfully carried out, but attempts to establish an ADS-C connection with DAKAR Oceanic failed. Shortly afterwards, the co-pilot modified the scale on his Navigation Display (ND) from 320 NM to 160 NM and noted “…a thing straight ahead”. The Captain confirmed and the crew again discussed the fact that the high temperature meant that they could not climb to flight level 370. At 1 h 45, the aeroplane entered a slightly turbulent zone, just before SALPU point. Note: At about 0 h 30 the crew had received information from the OCC about the presence of a convective zone linked to the inter-tropical convergence zone (ITCZ) between SALPU and TASIL. The crew dimmed the lighting in the cockpit and switched on the lights “to see”. The co-pilot noted that they were “entering the cloud layer” and that it would have been good to be able to climb. A few minutes later, the turbulence increased slightly in strength. Shortly after 1 h 52, the turbulence stopped. The co-pilot again drew the Captain’s attention to the REC MAX value, which had then reached flight level (FL) 375. A short time later, the Captain woke the second co-pilot and said “[…] he’s going to take my place”. At around 2 h 00, after leaving his seat, the Captain attended the briefing between the two co-pilots, during which the PF (seated on the right) said specifically that “well the little bit of turbulence that you just saw we should find the same ahead we’re in the cloud layer unfortunately we can’t climb much for the moment because the temperature is falling more slowly than forecast” and that “the logon with DAKAR failed”. Then the Captain left the cockpit. The aeroplane approached the ORARO point. It was flying at flight level 350 and at Mach 0.82. The pitch attitude was about 2.5 degrees. The weight and balance of the aeroplane were around 205 tonnes and 29%. The two copilots again discussed the temperature and the REC MAX. The turbulence increased slightly. At 2 h 06, the PF called the cabin crew, telling them that “in two minutes we ought to be in an area where it will start moving about a bit more than now you’ll have to watch out there” and he added “I’ll call you when we’re out of it”. At around 2 h 08, the PNF proposed “go to the left a bit […]”. The HDG mode was activated and the selected heading decreased by about 12 degrees in relation to the route. The PNF changed the gain adjustment on his weather radar to maximum, after noticing that it was in calibrated mode. The crew decided to reduce the speed to about Mach 0.8 and engine de-icing was turned on. At 2 h 10 min 05, the autopilot then the auto-thrust disconnected and the PF said “I have the controls”. The aeroplane began to roll to the right and the PF made a nose-up and left input. The stall warning triggered briefly twice in a row. The recorded parameters showed a sharp fall from about 275 kt to 60 kt in the speed displayed on the left primary flight display (PFD), then a few moments later in the speed displayed on the integrated standby instrument system (ISIS). The flight control law reconfigured from normal to alternate. The Flight Directors (FD) were not disconnected by the crew, but the crossbars disappeared. Note: Only the speeds displayed on the left side and on the ISIS are recorded on the FDR; the speed displayed on the right side is not recorded. At 2 h 10 min 16, the PNF said “we’ve lost the speeds ” then “alternate law protections”. The PF made rapid and high amplitude roll control inputs, more or less from stop to stop. He also made a nose-up input that increased the aeroplane’s pitch attitude up to 11° in ten seconds. Between 2 h 10 min 18 and 2 h 10 min 25, the PNF read out the ECAM messages in a disorganized manner. He mentioned the loss of autothrust and the reconfiguration to alternate law. The thrust lock function was deactivated. The PNF called out and turned on the wing anti-icing. The PNF said that the aeroplane was climbing and asked the PF several times to descend. The latter then made several nose-down inputs that resulted in a reduction in the pitch attitude and the vertical speed. The aeroplane was then at about 37,000 ft and continued to climb. At about 2 h 10 min 36, the speed displayed on the left side became valid again and was then 223 kt; the ISIS speed was still erroneous. The aeroplane had lost about 50 kt since the autopilot disconnection and the beginning of the climb. The speed displayed on the left side was incorrect for 29 seconds. At 2 h 10 min 47, the thrust controls were pulled back slightly to 2/3 of the IDLE/CLB notch (85% of N1). Two seconds later, the pitch attitude came back to a little above 6°, the roll was controlled and the angle of attack was slightly less than 5°. The aeroplane’s pitch attitude increased progressively beyond 10 degrees and the plane started to climb. From 2 h 10 min 50, the PNF called the Captain several times. At 2 h 10 min 51, the stall warning triggered again, in a continuous manner. The thrust levers were positioned in the TO/GA detent and the PF made nose-up inputs. The recorded angle of attack, of around 6 degrees at the triggering of the stall warning, continued to increase. The trimmable horizontal stabilizer (THS) began a nose-up movement and moved from 3 to 13 degrees pitch-up in about 1 minute and remained in the latter position until the end of the flight. Around fifteen seconds later, the ADR3 being selected on the right side PFD, the speed on the PF side became valid again at the same time as that displayed on the ISIS. It was then at 185kt and the three displayed airspeeds were consistent. The PF continued to make nose-up inputs. The aeroplane’s altitude reached its maximum of about 38,000 ft; its pitch attitude and angle of attack were 16 degrees. At 2 h 11 min 37, the PNF said “controls to the left”, took over priority without any callout and continued to handle the aeroplane. The PF almost immediately took back priority without any callout and continued piloting. At around 2 h 11 min 42, the Captain re-entered the cockpit. During the following seconds, all of the recorded speeds became invalid and the stall warning stopped, after having sounded continuously for 54 seconds. The altitude was then about 35,000 ft, the angle of attack exceeded 40 degrees and the vertical speed was about -10,000 ft/min. The aeroplane’s pitch attitude did not exceed 15 degrees and the engines’ N1’s were close to 100%. The aeroplane was subject to roll oscillations to the right that sometimes reached 40 degrees. The PF made an input on the side-stick to the left stop and nose-up, which lasted about 30 seconds. At 2 h 12 min 02, the PF said, “I have no more displays”, and the PNF “we have no valid indications”. At that moment, the thrust levers were in the IDLE detent and the engines’ N1’s were at 55%. Around fifteen seconds later, the PF made pitch-down inputs. In the following moments, the angle of attack decreased, the speeds became valid again and the stall warning triggered again. At 2 h 13 min 32, the PF said, “[we’re going to arrive] at level one hundred”. About fifteen seconds later, simultaneous inputs by both pilots on the side-sticks were recorded and the PF said, “go ahead you have the controls”. The angle of attack, when it was valid, always remained above 35 degrees. From 2 h 14 min 17, the Ground Proximity Warning System (GPWS) “sink rate” and then “pull up” warnings sounded. The recordings stopped at 2 h 14 min 28. The last recorded values were a vertical speed of -10,912 ft/min, a ground speed of 107 kt, pitch attitude of 16.2 degrees nose-up, roll angle of 5.3 degrees left and a magnetic heading of 270 degrees. No emergency message was transmitted by the crew. The wreckage was found at a depth of 3,900 metres on 2 April 2011 at about 6.5 NM on the radial 019 from the last position transmitted by the aeroplane. Both CVR and DFDR were found 23 months after the accident, in May 2011 at a depth of 3,900 metres. The final report was published in July 2012.
Probable cause:
The obstruction of the Pitot probes by ice crystals during cruise was a phenomenon that was known but misunderstood by the aviation community at the time of the accident. From an operational perspective, the total loss of airspeed information that resulted from this was a failure that was classified in the safety model. After initial reactions that depend upon basic airmanship, it was expected that it would be rapidly diagnosed by pilots and managed where necessary by precautionary measures on the pitch attitude and the thrust, as indicated in the associated procedure. The occurrence of the failure in the context of flight in cruise completely surprised the pilots of flight AF 447. The apparent difficulties with aeroplane handling at high altitude in turbulence led to excessive handling inputs in roll and a sharp nose-up input by the PF. The destabilization that resulted from the climbing flight path and the evolution in the pitch attitude and vertical speed was added to the erroneous airspeed indications and ECAM messages, which did not help with the diagnosis. The crew, progressively becoming de-structured, likely never understood that it was faced with a 'simple' loss of three sources of airspeed information. In the minute that followed the autopilot disconnection, the failure of the attempts to understand the situation and the de-structuring of crew cooperation fed on each other until the total loss of cognitive control of the situation. The underlying behavioral hypotheses in classifying the loss of airspeed information as 'major' were not validated in the context of this accident. Confirmation of this classification thus supposes additional work on operational feedback that would enable improvements, where required, in crew training, the ergonomics of information supplied to them and the design of procedures. The aeroplane went into a sustained stall, signaled by the stall warning and strong buffet. Despite these persistent symptoms, the crew never understood that they were stalling and consequently never applied a recovery manoeuvre. The combination of the ergonomics of the warning design, the conditions in which airline pilots are trained and exposed to stalls during their professional training and the process of recurrent training does not generate the expected behavior in any acceptable reliable way. In its current form, recognizing the stall warning, even associated with buffet, supposes that the crew accords a minimum level of 'legitimacy' to it. This then supposes sufficient previous experience of stalls, a minimum of cognitive availability and understanding of the situation, knowledge of the aeroplane (and its protection modes) and its flight physics. An examination of the current training for airline pilots does not, in general, provide convincing indications of the building and maintenance of the associated skills. More generally, the double failure of the planned procedural responses shows the limits of the current safety model. When crew action is expected, it is always supposed that they will be capable of initial control of the flight path and of a rapid diagnosis that will allow them to identify the correct entry in the dictionary of procedures. A crew can be faced with an unexpected situation leading to a momentary but profound loss of comprehension. If, in this case, the supposed capacity for initial mastery and then diagnosis is lost, the safety model is then in 'common failure mode'. During this event, the initial inability to master the flight path also made it impossible to understand the situation and to access the planned solution.
Thus, the accident resulted from the following succession of events:
- Temporary inconsistency between the airspeed measurements, likely following the obstruction of the Pitot probes by ice crystals that, in particular, caused the autopilot disconnection and the reconfiguration to alternate law;
- Inappropriate control inputs that destabilized the flight path;
- The lack of any link by the crew between the loss of indicated speeds called out and the appropriate procedure;
- The late identification by the PNF of the deviation from the flight path and the insufficient correction applied by the PF;
- The crew not identifying the approach to stall, their lack of immediate response and the exit from the flight envelope;
- The crew’s failure to diagnose the stall situation and consequently a lack of inputs that would have made it possible to recover from it.
These events can be explained by a combination of the following factors:
- The feedback mechanisms on the part of all those involved that made it impossible:
* To identify the repeated non-application of the loss of airspeed information procedure and to remedy this,
* To ensure that the risk model for crews in cruise included icing of the Pitot probes and its consequences;
- The absence of any training, at high altitude, in manual aeroplane handling and in the procedure for 'Vol avec IAS douteuse';
- Task-sharing that was weakened by:
* Incomprehension of the situation when the autopilot disconnection occurred,
* Poor management of the startle effect that generated a highly charged emotional factor for the two copilots;
- The lack of a clear display in the cockpit of the airspeed inconsistencies identified by the computers;
- The crew not taking into account the stall warning, which could have been due to:
* A failure to identify the aural warning, due to low exposure time in training to stall phenomena, stall warnings and buffet,
* The appearance at the beginning of the event of transient warnings that could be considered as spurious,
* The absence of any visual information to confirm the approach-to-stall after the loss of the limit speeds,
* The possible confusion with an overspeed situation in which buffet is also considered as a symptom,
* Flight Director indications that may led the crew to believe that their actions were appropriate, even though they were not,
* The difficulty in recognizing and understanding the implications of a reconfiguration in alternate law with no angle of attack protection.
Final Report:

Crash of a Beechcraft 350 Super King Air in Porto Seguro: 14 killed

Date & Time: May 22, 2009 at 2053 LT
Registration:
PR-MOZ
Flight Type:
Survivors:
No
Schedule:
São Paulo – Porto Seguro
MSN:
FL-237
YOM:
1999
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
14
Captain / Total flying hours:
20000
Captain / Total hours on type:
5000.00
Copilot / Total flying hours:
357
Copilot / Total hours on type:
107
Circumstances:
The twin engine aircraft departed São Paulo-Congonhas Airport at 1831LT on a private flight to Porto Seguro, carrying 12 passengers and two pilots, among them the Brazilian Businessman Roger Wright, his wife, children and grandchildren. On approach to Porto Seguro-Terravista Golf Club Airport, the crew encountered poor weather conditions and the visibility was low due to the night. On final approach to runway 15, the aircraft impacted trees located 900 metres from the runway threshold. The aircraft continued for about 700 metres then struck others trees and crashed 200 metres short of runway, bursting into flames. The aircraft was totally destroyed and all 14 occupants were killed.
Probable cause:
The crew's decision to continue the approach in poor weather conditions following a high motivation to land at destination.
The following contributing factors were identified:
- The crew failed to follow the published procedures,
- The crew did not take the bad weather conditions into consideration and took the decision to land,
- Limited visibility due to rain falls and night,
- Weather conditions affected the perception of the pilots who suffered a loss of situational awareness,
- Poor judgment of the situation and flight conditions on part of the crew,
- The crew continued the approach under VFR mode in IMC conditions,
- The crew carried out an improvised VFR approach via a GPS system,
- Excessive approach speed,
- Poor crew coordination,
- Lack of crew discipline.
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante off Santo Antônio: 24 killed

Date & Time: Feb 7, 2009 at 1324 LT
Operator:
Registration:
PT-SEA
Survivors:
Yes
Schedule:
Coari - Manaus
MSN:
110-352
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
26
Pax fatalities:
Other fatalities:
Total fatalities:
24
Captain / Total flying hours:
18870
Captain / Total hours on type:
7795.00
Copilot / Total flying hours:
1011
Copilot / Total hours on type:
635
Aircraft flight hours:
12686
Circumstances:
The twin engine aircraft departed Coari Airport at 1240LT on a charter flight to Manaus-Eduardo Gomes Airport, carrying 26 passengers and two pilots. About 30 minutes into the flight, while cruising at FL115, the crew informed ATC that the left engine failed and elected to divert to the unused Manacapuru Airfield. While approaching runway 08, the aircraft rolled to the left to an angle of 30° then crashed in the Rio Manacapuru. 24 people were killed while 4 passengers were slightly injured.
Probable cause:
The following factors were identified:
- At takeoff from Coari Airport, the total weight of the aircraft was 6,414 kg, which means 744 kg over the MTOW,
- On board were 26 passengers including 8 children while the aircraft was certified for 19 passengers,
- The left engine fuel pump was completely burnt during the accident but it could not be determined if it failed during the flight or not,
- The crew was not sufficiently trained for emergency situations,
- Poor work organisation,
- Lack of supervision from the operator concerning crew's decisions before and during flights,
- Poor crew coordination,
- Lack of crew communication,
- Non compliance with management techniques,
- Incomplete execution of the actions provided by the emergency checklist.
Final Report:

Crash of a Beechcraft 200 Super King Air in Recife: 2 killed

Date & Time: Nov 23, 2008 at 1115 LT
Operator:
Registration:
PT-OSR
Survivors:
Yes
Site:
Schedule:
Teresina - Recife
MSN:
BB-784
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
10000
Circumstances:
Following an uneventful flight from Teresina, the crew started the approach to Recife-Guararapes Airport runway 18. On final, both engines failed simultaneously. The aircraft stalled and crashed in a residential area located 5 km from the runway threshold. A passenger and a pilot were killed while eight others occupants were injured. There were no victims on the ground while the aircraft was destroyed.
Probable cause:
Double engine failure caused by a fuel exhaustion. The following contributing factors were identified:
- Poor flight planning,
- The crew failed to add sufficient fuel prior to departure from Teresina Airport,
- The fuel quantity was insufficient for the required distance,
- The crew failed to follow the published procedures,
- Overconfidence from the crew,
- Poor organisational culture on part of the operator,
- Lack of discipline and poor judgment on part of the crew,
- Lack of supervision.
Final Report:

Crash of a Beechcraft 100 King Air in Bauru: 1 killed

Date & Time: Oct 12, 2008
Type of aircraft:
Registration:
N525ZS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bauru – Sorocaba
MSN:
B-66
YOM:
1971
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Shortly after takeoff from Bauru Airport, the twin engine aircraft encountered difficulties to maintain a positive rate of climb. It then descended until it impacted ground about 5 km from the airport. The pilot, sole on board, was killed. He was supposed to deliver the aircraft at Sorocaba Airport.

Crash of a Beechcraft BeechJet 400A in São José dos Campos

Date & Time: Jul 15, 2008 at 1130 LT
Type of aircraft:
Operator:
Registration:
PT-WHF
Flight Type:
Survivors:
Yes
Schedule:
São Paulo - São José dos Campos
MSN:
RK-82
YOM:
1994
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4300
Captain / Total hours on type:
2811.00
Copilot / Total flying hours:
540
Copilot / Total hours on type:
35
Circumstances:
The crew departed São Paulo-Congonhas Airport on a positioning flight to São José dos Campos. While descending to São José dos Campos, the captain led the controls to the copilot who was still under instruction. On final, the aircraft was too high on the glide. The captain took over controls but his reaction was excessive. The aircraft suddenly rolled to the right, causing the right wing to struck the ground few dozen metres short of runway 15 threshold. The aircraft landed and came to rest on the main runway. Both pilots evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
The captain did not conduct a preflight briefing and then improvised during the descent by deciding to leave the controls to the copilot while he was still under instruction.
The following contributing factors were identified:
- The copilot who was pilot-in-command on final was in his initial training process,
- The captain authorized the copilot to be the PIC while he was still under initial training,
- The captain was not qualified to operate as an instructor,
- The captain did not make any simulator training for more than two years,
- The copilot had never completed any simulator training since the beginning of his training,
- Lack of crew coordination,
- Poor judgment on part of the captain.
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante in Coari

Date & Time: Apr 21, 2008 at 1500 LT
Operator:
Registration:
PT-OCV
Survivors:
Yes
Schedule:
Manaus – Carauari
MSN:
110-359
YOM:
1981
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
16442
Captain / Total hours on type:
2519.00
Copilot / Total flying hours:
1132
Copilot / Total hours on type:
364
Circumstances:
The twin engine aircraft departed Manaus-Eduardo Gomes Airport on a flight to Carauari, carrying 15 passengers and two pilots. About 50 minutes into the flight, while cruising at an altitude of 8,500 feet, the right engine failed. The crew elected several times to restart it but without success. After the crew informed ATC about his situation, he was cleared to divert to Coari Airport located about 37 km from his position. Because the aircraft was overloaded and one engine was inoperative, the crew was approaching Coari Airport runway 28 with a speed higher than the reference speed. The aircraft landed too far down the runway, about 700 metres past the runway 28 threshold (runway 28 is 1,600 metres long). After touchdown, directional control was lost. The airplane veered off runway to the left and while contacting a drainage ditch, the undercarriage were torn off and the aircraft came to rest 20 metres further. All 17 occupants were evacuated, among them nine were injured. The aircraft was damaged beyond repair.
Probable cause:
The failure of the right engine was the result of the failure of the fuel pump due to poor maintenance and a possible use beyond prescribed limits. The presence of iron oxide inside and outside the fuel pump as well as the lack of cleanliness of the internal components indicates a probable lack of maintenance. When the right engine stopped running, the generator No. 1 was then responsible for powering the aircraft's electrical system. As the latter was not in good working order, the primary generator could not withstand the overload and ceased to function, leaving only the battery to power the entire electrical system. To maintain power to critical systems, the crew would have had to select the backup power system. Since after the engine stopped, there was no monitoring of the electrical system, the pilots only realized the failure of the electrical system when they attempted to extend the landing gears. The emergency hydraulic system was then used to lower the gears, after which the crew did not return the system selection valve to the 'normal' position, resulting in the brakes and the steering systems to be inoperative after landing. The chain of failures may be associated with not reading the checklist when performing procedures after the engine failure.
The following contributing factors were identified:
- Poor flight preparation,
- The crew failed to follow the SOP's, and took the decision to initiate the flight with an aircraft that was overloaded by 503 kilos,
- When the emergency situation presented itself to the crew, they failed to follow the checklist,
- On an organizational level, the company did not have an effective personnel training system in place, so that the crew did not have sufficient skills to respond to emergency situations,
- Because the aircraft was overloaded and that one engine was inoperative, the crew was forced to complete the approach with a speed higher than the reference speed,
- An improper use of the controls allowed the aircraft to land 700 meters past the runway 28 threshold, reducing the landing distance available,
- The crew focused their attention on the failure of the right engine and did not identify the failure of the electrical system, which delayed their tasks assignment, all made worse by the failure to comply with the checklist,
- The operations cleared the crew to start the flight despite the fact that the aircraft was overloaded on takeoff based on weight and balance documents,
- The crew did not prepare the flight according to published procedures and did not consider the total weight of the aircraft in relation to the number of passengers on board and the volume of fuelin the tanks, which resulted in an aircraft to be overloaded by 503 kilos and contributed to the failure of the right engine,
- A lack of maintenance on the part of the operator.
Final Report:

Crash of an Embraer EMB-820C Carajá in Lençóis: 2 killed

Date & Time: Mar 31, 2008 at 0630 LT
Operator:
Registration:
PT-VCI
Flight Type:
Survivors:
No
Schedule:
Salvador – Lençóis
MSN:
820-144
YOM:
1986
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
25000
Captain / Total hours on type:
1769.00
Copilot / Total flying hours:
750
Copilot / Total hours on type:
195
Aircraft flight hours:
7293
Circumstances:
The twin engine aircraft departed Salvador Airport at 0525LT on a cargo flight to Lençóis, carrying two pilots and a load of bank documents. On final approach to Lençóis Airport, the crew encountered limited visibility due to marginal weather conditions. The captain decided to continue the approach and completed a turn to the left when the aircraft crashed 2 km from the runway threshold, bursting into flames. The aircraft was totally destroyed and both pilots were killed.
Probable cause:
The decision of the captain to continue the approach under VFR mode in IMC conditions to an airport that was not suitable for IFR operations. The following contributing factors were identified:
- The lack of ground references may have contributed to the commander's spatial disorientation,
- Although the weather conditions made it impossible to land under VFR conditions, the captain insisted on landing, neglecting IFR procedures,
- The captain ignored the copilot's advice and continued with the approach procedure,
- The captain put the aircraft in an attitude that caused it to stall,
- Poor judgment on part of the captain,
- Despite the implementation of a CRM program, the operator was unable to identify that the captain was violating the published procedures.
Final Report:

Crash of a Learjet 35A in Campo de Marte: 8 killed

Date & Time: Nov 4, 2007 at 1410 LT
Type of aircraft:
Operator:
Registration:
PT-OVC
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Campo de Marte - Rio de Janeiro
MSN:
35A-399
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
10049
Captain / Total hours on type:
3749.00
Copilot / Total flying hours:
643
Copilot / Total hours on type:
125
Aircraft flight hours:
10583
Circumstances:
The aircraft was returning to its base in Rio de Janeiro-Santos Dumont following an ambulance flight to Campo de Marte AFB. Shortly after takeoff from runway 30, while climbing to an altitude of 1,400 feet, the aircraft rolled to the right to an angle of 90° then entered an uncontrolled descent and crashed onto several houses located on Bernardino de Sena Street, bursting into flames. Both pilots as well as six people on the ground were killed. Six others people were seriously injured.
Probable cause:
A possible loss of control during initial climb consecutive to a fuel imbalance. The following contributing factors were identified:
- Crew fatigue,
- Non-compliance with published procedures,
- Poor distribution of tasks prior to the flight and during the initial climb,
- Overconfidence on part of the crew,
- Poor flight preparation,
- Loss of situational awareness,
- Incorrect application of controls,
- The crew failed to follow the pre-takeoff checklist.
Final Report:

Crash of a Beechcraft 60 Duke in Silvânia: 2 killed

Date & Time: Sep 17, 2007 at 1340 LT
Type of aircraft:
Operator:
Registration:
PT-OOH
Flight Phase:
Survivors:
No
Schedule:
Montes Claros – Goiânia
MSN:
P-27
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1000
Captain / Total hours on type:
85.00
Circumstances:
The twin engine aircraft departed Montes Claros Airport at 1200LT on a flight to Goiânia, carrying one passenger and one pilot. As he started the descent to Goiânia Airport, the pilot reported the failure of the left engine and requested the permission to proceed with a direct approach to runway 32 despite the runway 14 was in use. Few seconds later, the right engine failed as well. The pilote reduced his altitude and attempted an emergency landing when the aircraft crashed in an open field located near Silvânia, about 50 km east of Goiânia Airport. On impact, the fixing points of the seat belts broke away, causing both occupants to impact the instrument panel. The aircraft was severely damaged and both occupants were killed.
Probable cause:
Failure of both engines in flight due to fuel exhaustion. The following contributing factors were identified:
- Poor judgment on the part of the pilot who considered that the quantity of fuel present in the tanks before departure was sufficient, which was not the case,
- Poor flight planning on part of the pilot who miscalculated the fuel consumption,
- The pilot failed to follow the procedures related to fuel policy.
Final Report: