Crash of a Cessna C-98A Grand Caravan near Bom Jardim da Serra: 8 killed

Date & Time: Aug 2, 2011 at 1327 LT
Type of aircraft:
Operator:
Registration:
2735
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Porto Alegre - Rio de Janeiro
MSN:
208B-2130
YOM:
2009
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The single engine aircraft departed Canoas AFB in Porto Alegre at 1145LT on a flight to Rio de Janeiro-Galeão Airport, carrying six officers and two pilots on behalf of the 5th Air Transport Squadron. While cruising over the State of Santa Catarina, the crew encountered limited visibility due to poor weather conditions when the aircraft impacted a mountain near Bom Jardim da Serra. The aircraft disintegrated on impact and all 8 occupants were killed.

Crash of a Cessna 207 Skywagon near Port Vila

Date & Time: Aug 1, 2011 at 1700 LT
Operator:
Registration:
YJ-FLY
Flight Phase:
Survivors:
Yes
Schedule:
Whitegrass - Port Vila
MSN:
207-0362
YOM:
1976
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft was performing a taxi flight from Whitegrass Airport located on Tannu Island, to Port Vila, with six passengers and a pilot on board. While approaching Efate Island, the pilot encountered poor weather conditions with heavy rain falls and attempted an emergency landing in the garden of the Lagon Resort, south of Port Vila. On touchdown, the airplane lost its nose gear and left main gear, cartwheeled and came to rest, broken in two. All occupants were slightly injured and the aircraft was damaged beyond repair.

Crash of a Boeing 747-48EF in the East China Sea: 2 killed

Date & Time: Jul 28, 2011 at 0411 LT
Type of aircraft:
Operator:
Registration:
HL7604
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Seoul - Shanghai
MSN:
29907/1370
YOM:
2006
Flight number:
OZ991
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
14123
Captain / Total hours on type:
6896.00
Copilot / Total flying hours:
5211
Copilot / Total hours on type:
492
Aircraft flight hours:
28752
Aircraft flight cycles:
4799
Circumstances:
On 28 July 2011, about 04:11 Korean Standard Time), Asiana Airlines flight 991, a B747-400F airplane, HL7604 (hereafter referred to as AAR991), a scheduled cargo flight from Incheon, Republic of Korea, to Shanghai, China, crashed into the international waters about 130 km west of Jeju International Airport (hereafter referred to as Jeju Airport after the flight crew reported a cargo fire to SHI ACC near a reporting point SADLI on airway A593 about 03:54 and attempted to divert to Jeju Airport. Due to the crash impact and fire, the captain and the first officer (FO) were fatally injured, the aircraft was destroyed, and the cargo shipments were damaged, incapable of being recovered, or washed away. AAR991 was a scheduled international cargo flight operated at night under the instrument flight rule in accordance with the Aviation Act of the Republic of Korea and the Convention on International Civil Aviation. The captain and the FO showed up at the flight crew ready room of Asiana Airlines in Incheon International Airport (hereafter referred to as Incheon Airport) an hour before the scheduled time of departure) and signed the "show-up log," respectively. The line mechanic stated that on 28 July, about 02:00, the flight crew arrived at the airplane and that the captain performed the ramp inspection. The loadmaster stated that about 02:15, under the guidance with him, the captain inspected the loaded status of dangerous goods and other shipments in the main deck cargo compartment. The transcript) of ATC radio communications shows that at 03:04:28, AAR991 took off from runway 15L in Incheon Airport. From this moment, the captain) took control of radio communications. At 03:05:48, AAR991 made initial contact with Seoul Area Control Center (SEL ACC) after takeoff and was instructed to climb to 34,000 ft and fly direct to MALPA. At 03:12:19, the flight crew were advised to contact Incheon Area Control Center (ICN ACC). At 03:12:35, AAR991 was climbing to 34,000 ft on a permitted route when it made initial contact with ICN ACC, and at 03:13:05, was allowed to fly direct to NIRAT. At 03:26:05, ICN ACC instructed AAR991 to change its radio frequency to 124.52 MHz. From this moment, the FO mainly assumed control of radio communications, but the captain also occasionally made communication. At 03:26:21, the crew were instructed to fly direct to SADLI, and at 03:50:46, ICN ACC advised AAR991 to contact SHI ACC on frequency 134.0 MHz. At 03:51:15, AAR991 stated that it was maintaining at 34,000 ft and flying direct to SADLI when it made initial contact with SHI ACC. At 03:52:39, SHI ACC instructed AAR991, "AAR991 radar contact, off-set 5 miles right of track," and the flight crew carried out this instruction at 03:52:51. The Aircraft Communications Addressing and Reporting System (ACARS) messages) received by the ground station were as follows: about 03:53, "EQUIPMENT SMOKE," "EQUIP COOLING," and "CGO DET 11 MN DK"; and about 03:54, "CGO DET 6 MN DK" and "CGO DET 10 MN DK." At 03:54:23, the FO stated, "Shanghai control, Shanghai control, AAR991 request emergency descent, emergency, declare emergency due to fire main deck. Request descent, and descent to one-zero thousand." At 03:54:37, SHI ACC gave AAR991 a descent clearance and instructed it to turn at its discretion, and the FO acknowledged this instruction. The radar data of ICN ACC shows that AAR991 started descending at 03:54:59. At 03:55:08, the FO requested a diversion to Jeju Airport, stating "We have fire main deck, AAR991, return to Jeju AAR991," and SHI ACC approved the request. At 03:58:03, SHI ACC instructed AAR991 to maintain 10,000 ft, however, followed by no response from AAR991. At 03:58:25, SHI ACC requested KAL886 flying near AAR991 to relay any information from AAR991 to SHI ACC. KAL886 stated that AAR991 was descending to 10,000 ft and flying direct to Jeju. According to the radar data of ICN ACC, AAR991 was flying at 16,000 ft at a ground speed of 452 kt on a heading of 345°. At 03:59:13, AAR991 requested a radar vector to Jeju. At 03:59:50, SHI ACC instructed AAR991 to fly heading 045, and AAR991 acknowledged this instruction. At 03:59:26, according to the ATC transcript, the sound of the FO's breathing through an oxygen mask was recorded four times when he communicated with SHI ACC. The last ACARS messages received by the ground station about 04:00 are as follows: "YAW DAMPER UPR," "RUD RATIO DUAL," and "FLAPS CONTROL." At 04:00:23, SHI ACC instructed AAR991 to contact ICN ACC on 124.52 MHz for a radar vector to Jeju, however, AAR991 stated that it was unable to contact on this frequency. Consequently, SHI ACC instructed the crew to monitor frequency 134.0 MHz. The radar data of ICN ACC shows that at 04:01:43, AAR991 was flying at 8,200 ft at a ground speed of 404 kt on a heading of 033°, and after this, AAR991's altitude, ground speed, and heading changed inconsistently. At 04:02:00, SHI ACC instructed AAR991 to contact Fukuoka Area Control Center (FUK ACC) on 133.6 MHz. At 04:02:10, the FO stated, "AAR991" and 12 seconds later, added, "Fukuoka AAR991 mayday mayday mayday, we have cargo fire, request direct to Jeju please," followed by no response from FUK ACC. At 04:03:01, the FO called SHI ACC and stated that it was unable to contact FUK ACC. Consequently, SHI ACC instructed AAR991 to pass information to KAL886 and let KAL886 relay the information to FUK ACC and ICN ACC. At 04:03:01, the flight track data of the Incheon radar shows that AAR991's transponder code in Mode 3/A was set to 7700 from 6353 when the aircraft was flying at 8,500 ft at a ground speed of 410 kt on a heading of 027°. At 04:03:24, KAL886 advised AAR991 that it would relay its message to ICN ACC, and the FO stated, "Yes, now direct Jeju heading 030." KAL886 informed AAR991 that SHI ACC gave it heading 045, and the FO acknowledged this instruction. At 04:04:14, SHI ACC instructed KAL886 to use another transmitter to contact ICN ACC on 124.52 MHz, to request heading to Jeju from its present position, and to report back to SHI ACC. Regarding this, KAL886 gave an affirmative response. At 04:05:30, the captain called KAL886, and KAL886 responded, "Relay from Incheon Control, from Incheon Control, maintain heading 060, radar vector for final, and you may descend to 7,000 ft." At 04:05:52, KAL886 again relayed the message, "Maintain heading 060, radar vector for final, and descend to 7,000 ft," followed by the captain's response, "Descend 7,000 ft." Beginning 04:06:25, the captain called "Korean Air" twice. At 04:06:30, KAL886 responded, "Stand by, stand by," followed by the captain's statement at 04:06:32, "Ah… we are now that rudder control is not working and seems to be fired… (jamming)." At 04:06:41, SHI ACC instructed KAL886 to contact ICN ACC on 124.52 MHz, and at 04:07:16, instructed AAR991 to try contacting KAL886 on 124.52 MHz, followed by the captain's acknowledgement. At 04:07:34, the captain stated, "We have to open the hatch, hatch." Subsequently, KAL886 instructed AAR991 to change its frequency to ICN ACC frequency 124.52 MHz. At 04:08:52, ICN ACC instructed KAL886 to relay the message to AAR991 that JEJ APP established radar contact with AAR991 and that AAR991 should contact JEJ APP on 121.2 MHz. At 04:09:08, KAL886 relayed this message to AAR991. At 04:09:47, the captain said to JEJ ACC, "Rudder control… flight control, all are not working." The FO said to JEJ ACC, "Did you contact? Uh… do you contact us?" and JEJ ACC responded, "AAR991… yes, I can hear you." At 04:10:06, the FO stated, "We have heavy vibration on the airplane, may need to make an emergency landing, emergency ditching," and JEJ ACC responded, "Yes, say again, please." He stated, "Altitude control is not available due to heavy vibration, going to ditch… ah." At 04:10:26, JEJ ACC asked AAR991, "Can you make approach to Jeju?" and subsequently, tried to contact AAR991 three times, however, followed by no response from AAR991. The aircraft crashed in the East China Sea and both pilots were killed. Debris were found about 130 km west of Jeju.
Probable cause:
The Aviation and Railway Accident Investigation Board (ARAIB) determines the cause of this accident as follows:
A fire developed on or near the pallets containing dangerous goods but no physical evidence of the cause of the fire was found. The fire rapidly escalated into a large uncontained fire, and this caused some portions of the fuselage to separate from the aircraft in midair, thereby resulting in the crash.
Contributing Factors:
1. Flammable materials like photo-resist (Class 3) were loaded in position ML, and flammable materials like paint, photo-resist, corrosive liquid, and lithium-ion batteries (Class 9) were loaded on one pallet in position PR.
2. It was difficult to contain a large scale of fire only by the fire suppression system of a Class E cargo compartment that was not equipped with an active fire suppression system.
Final Report:

Crash of a De Havilland DHC-2 Beaver near Buss Lakes: 5 killed

Date & Time: Jun 30, 2011 at 1111 LT
Type of aircraft:
Registration:
C-GUJX
Flight Phase:
Survivors:
No
Schedule:
Buss Lakes - Southend
MSN:
1132
YOM:
1958
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
4023
Captain / Total hours on type:
3664.00
Aircraft flight hours:
12746
Circumstances:
The Lawrence Bay Airways Ltd. float-equipped de Havilland DHC-2 (registration C-GUJX, serial number 1132) departed from a lake adjacent to a remote fishing cabin near Buss Lakes for a day visual flight rules flight to Southend, Saskatchewan, about 37 nautical miles (nm) southeast. There were 4 passengers and 1 pilot onboard. The aircraft crashed along the shoreline of another lake located about 2 nm southeast of its point of departure. The impact was severe and the 5 occupants were killed on impact. The emergency locator transmitter activated, and the aircraft was found partially submerged in shallow water with the right wing tip resting on the shore. There was no post-crash fire. The accident occurred during daylight hours at about 1111 Central Standard Time.
Probable cause:
Findings as to Causes and Contributing Factors:
While manoeuvring at low level, the aircraft's critical angle of attack was likely exceeded and the aircraft stalled. The stall occurred at an altitude from which recovery was not possible.
Other Findings:
The separation of the propeller blade tip likely resulted from impact forces.
The investigation could not determine whether the fuel pressure warning light was illuminated prior to the accident.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain near Zaraza

Date & Time: Jun 16, 2011 at 0950 LT
Operator:
Registration:
YV1394
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Maracay - Puerto Ordaz
MSN:
31-7405135
YOM:
1974
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Maracay on a cargo flight to Puerto Ordaz, carrying one pilot, one passenger and some bank documents. While in cruising altitude, the pilot informed ATC about smoke in the cockpit and elected to divert to the nearest airport. Eventually, he attempted an emergency landing in an open field located some 20 km east from Zaraza. After touchdown, the aircraft rolled for few dozen metres before coming to rest, bursting into flames. While both occupants escaped uninjured, the aircraft was totally destroyed by fire.
Probable cause:
During a flight of transport of values, in the phase of cruise, a smoke emergency appeared in the cockpit, that when not being able to be controlled, derived in a landing of emergency by precaution in a nonprepared field, which resulted without apparent damages to the aircraft, triggering later a fire and the almost total destruction of the same, due, very probably, to an electrical failure that originated the fire.

Mishap of a Beechcraft A100 King Air in Blountville

Date & Time: Jun 15, 2011 at 1405 LT
Type of aircraft:
Operator:
Registration:
N15L
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bridgewater - Wichita
MSN:
B-212
YOM:
1974
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4837
Captain / Total hours on type:
87.00
Copilot / Total flying hours:
900
Copilot / Total hours on type:
2
Aircraft flight hours:
16170
Circumstances:
The airplane was flying in instrument meteorological conditions at flight level 200 (about 20,000 feet), and a large area of thunderstorm activity was located to the northwest. About 20 miles from the thunderstorm activity, the airplane began to encounter moderate turbulence and severe icing conditions. The pilot deviated to the south; however, the turbulence increased, and the airplane entered an uncommanded left roll and dive. The autopilot disengaged, and the pilot's attitude indicator dropped. The pilot leveled the airplane at an altitude of 8,000 feet and landed without further incident. Subsequent examination revealed that one-third of the outboard left elevator separated in flight and that the empennage was substantially damaged. Meteorological and radar data revealed the airplane entered an area of rapidly intensifying convective activity, which developed along the airplane's flight path, and likely encountered convectively-induced turbulence with a high probability of significant icing. The effect of icing conditions on the initiation of the upset could not be determined; however, airframe structural icing adversely affects an airplane's performance and can result in a loss of control.
Probable cause:
An encounter with convectively-induced turbulence and icing, which resulted in an in-flight upset and a loss of airplane control.
Final Report:

Crash of a Pilatus PC-12/45 in Faridabad: 10 killed

Date & Time: May 25, 2011 at 2243 LT
Type of aircraft:
Operator:
Registration:
VT-ACF
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Patna - New Delhi
MSN:
632
YOM:
2005
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
1521
Captain / Total hours on type:
1300.00
Copilot / Total flying hours:
300
Copilot / Total hours on type:
70
Aircraft flight hours:
1483
Circumstances:
M/s Air Charter Services Pvt Ltd. offered their aircraft VT-ACF for operating medical evacuation flight to pick one critically ill patient from Patna on 25/05/2011. The Aircraft took off from Delhi to Patna with two crew members, two doctors and one male nurse. The Flight to Patna was uneventful. The Air Ambulance along with patient and one attendant took off from Patna at 20:31:58 IST, the aircraft during arrival to land at Delhi crashed near Faridabad on a Radial of 145 degree and distance of 15.2 nm at 22:42:32 IST. Aircraft reached Patna at 18:31 IST. Flight Plan for the flight from Patna to Delhi was filed with the ATC at Patna via W45-LLK-R594 at FL260, planned ETD being 22:00 hours IST and EET of 2hours for a planned ETA at VIDP being 24:00 hours IST. The crew took self-briefing of the weather and same “Self Briefing” was recorded on the flight plan submitted at ATC Patna. The passenger manifest submitted at Patna indicated a total of 2 crew and 5 passengers inclusive of the patient. Weather at Patna at the time of departure was 3000m visibility with Haze. Total fuel on board for departure at Delhi was 1516 lts. The preflight/transit inspection of the aircraft at Patna was carried out by the crew as per laid down guidelines. The crew requested for startup at 20:21 IST from Patna ATC and reported airborne at 20:33:43 IST. The aircraft climbed and maintained FL 260 for cruise. On handover from Varanasi Area Control (Radar), the aircraft came in contact with Delhi Area Control (East) Radar at 21:53:40 IST at 120.9 MHz. At 21:53:40 IST aircraft was identified on Radar by squawking code 3313. At 22:02:05 IST the crew requested for left deviation of 10° due to weather, the same was approved by the RSR controller. At 22:05:04 IST the crew informed that they have a critical patient on board and requested for priority landing and ambulance on arrival. The same was approved by the RSR controller. The aircraft was handed over to Approach Control on 126.35 MHz at 22:28:03 IST. At 22:28:18 IST VT-ACF contacted TAR (Terminal Approach Radar) on 126.35 MHz and it was maintaining FL160. At 22:32:22 IST, VT-ACF was asked to continue heading to DPN (VOR) and was cleared to descend to FL110. At 22:36:34 IST, the TAR controller informed VT-ACF about weather on HDG 330°, the crew replied in “Affirmative” and requested for left heading. At 22:38:12 IST, TAR controller gave aircraft left heading 285° which was copied by the aircraft. The aircraft started turning left, passing heading 289, it climbed from FL125 to FL141. At 22:40:32 IST the TAR controller gave 3 calls to VT-ACF. At 22:40:43 IST aircraft transmitted a feeble call “Into bad weather”, at that instance the aircraft had climbed FL 146.Thereafter the aircraft was seen turning right in a very tight turn at a low radar ground speed and loosing height rapidly from FL146 to FL 016. Again at 22:41:32 IST TAR controller gave call to VT-ACF, aircraft transmitted a feeble call “Into bad weather. Thereafter the controller gave repeated calls on both 126.35 MHz and also 121.5 MHz, before the blip on radar became static on a radial of 145 degree at 15.2 nm from DPN VOR at 22:42:32 IST. All attempts to raise contact with the aircraft failed. The TAR controller then informed the duty WSO and also the ATC Tower. At 22:50:00 IST, the tower informed the WSO that they have got a call from the City Fire Brigade confirming that an aircraft has crashed near Faridabad in a congested residential area known as Parvatia Colony. After the accident, local residents of the area and police tried to put off the fire and extricate the bodies from the wreckage of the aircraft.
Probable cause:
The probable cause of the accident could be attributed to departure of the aircraft from controlled flight due to an external weather related phenomenon, mishandling of controls, spatial disorientation or a combination of the three.
Final Report:

Crash of a Saab 340A near Prahuaniyeu: 22 killed

Date & Time: May 18, 2011 at 2050 LT
Type of aircraft:
Operator:
Registration:
LV-CEJ
Flight Phase:
Survivors:
No
Schedule:
Rosario – Córdoba – Mendoza – Neuquén – Comodoro Rivadavia
MSN:
25
YOM:
1985
Flight number:
OSL5428
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
22
Captain / Total flying hours:
6133
Captain / Total hours on type:
2187.00
Copilot / Total flying hours:
1342
Copilot / Total hours on type:
288
Aircraft flight hours:
41422
Aircraft flight cycles:
44477
Circumstances:
On 18 May 2011, the pilot in command (PIC) and the crew - composed of the copilot (COP) and cabin crew members (CCM) - initiated the flight OSL5428 from Rosario International Airport (ROS) in the province of Santa Fe at 20:35, the final destination being the Comodoro Rivadavia International Airport (CRD), in the province of Chubut. The flight had scheduled intermediate stopovers at Córdoba International Airport (COR), Mendoza (MDZ), and Neuquén (NQN), according to the company's plans. The company designated aircraft Saab 340A, with registration number LV-CEJ, for the flight. After having made the intermediate stopovers in Córdoba (COR) and Mendoza (MDZ), the pilot landed the aircraft at the airport in Neuquén at 22:20. After refuelling and carrying out the planned dispatch, the crew and 19 passengers (18 adults and one minor) on board, prepared to make the last leg of the flight OSL5428, from Neuquén Airport (NQN) to the final destination: Comodoro Rivadavia International Airport (CRD). The flight took off at 23:05. After the take-off, the aircraft started to climb AWY T 105, to reach FL190, in accordance with the flight plan. After flying for 24 minutes, the pilot levelled the aircraft at 17,800 feet, and remained at this level for approximately 9 minutes. Due to the fact that the meteorological conditions at this level caused icing, the technical crew descended to FL (flight level) 140. Shifting to FL140 took five minutes. During this stage of the flight the icing conditions steadily worsened. By the time the aircraft had reached FL140, the icing conditions were severe. The aircraft flew for approximately two minutes with a straight and level flight attitude, increasing the accumulation of ice. Then the aircraft completely lost lift, which resulted in a loss of control, and the subsequent entry into abnormal flight attitude. The aircraft plunged towards the earth and impacted the ground, which resulted in a fire. Everyone on board perished and the aircraft was destroyed. The accident happened at night under IMC conditions.
Probable cause:
During a commercial, domestic passenger flight, while cruising, the crew lost control of the aircraft, which uncontrollably impacted the ground due to severe ice formation caused by the following factors:
- Entering an area with icing conditions without adequately monitoring the warning signals from the external environment (temperature, cloudiness, precipitation and ice accumulation) or the internal (speed, angle of attack), which allowed for prolonged operations in icing conditions to take place.
- Receiving a forecast for slight icing - given that the aircraft encountered sever icing conditions - which led to a lack of understanding regarding the specific meteorological danger.
- Inadequately evaluating the risks, which led to mitigating measures such as adequate briefing (distribution of tasks in the cockpit, review of the de-icing systems, limitations, use of power, use of autopilot, diversion strategy etc.) not being adopted.
- Levels of stress increasing, due to operations not having the expected effects, which led the crew to lose focus on other issues.
- Icing conditions that surpassed the aircraft's ice protection systems, which were certified for the aircraft (FAR 25 Appendix C).
- Inadequate use of speed, by maintaining the speed close to stall speed during flight in icing conditions.
- Inadequate use of the autopilot, by not selecting the IAS mode when flying in icing conditions.
- Partially carrying out the procedures established in the Flight Manual and the Operations Manual, when entering into areas with severe icing conditions.
- Realizing late that the aircraft had started to stall, because the buffeting that foretells a stall was confused with the vibrations that signify ice contamination on the propellers.
- Activation of the Stick Shaker and Stall Warning at a lower speed than expected in icing conditions.
- Using a stall recovery technique which prioritized the reduction of the angle of attack at the expense of altitude loss, and which was inappropriate for the flight conditions.
- The aileron flight controls reacting in an unusual manner when the aircraft lost control, probably due to the accumulation of ice in the surfaces of these, which made it impossible for the aircraft to recover. The increasingly stressful situation of the crew, which affected its operational decision-making.
Final Report:

Crash of a PZL-Mielec AN-2R in Sofyevka

Date & Time: May 17, 2011 at 1915 LT
Type of aircraft:
Operator:
Registration:
RA-68122
Flight Phase:
Survivors:
Yes
MSN:
1G195-27
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Circumstances:
The pilot, sole on board, was performing a crop spraying flight when the engine lost power. He elected to make an emergency landing in a field 2 kilometers from Sofyevka, in the Stavropol krai. Upon touchdown, the aircraft rolled over and came to rest upside down, bursting into flames. The pilot escaped uninjured while the aircraft was partially destroyed by fire. The wreck was evacuated and disposed away before the arrival of the accident investigation commission. Therefore, it was not possible to the MAK to determine the cause of the engine failure. As the pilot did not have any valid licence for this kind of aircraft, this PZL-Mielec AN-2R built on 11FEB1982 did not have a valid Certificate of Airworthiness. It had a double registration: FLA-34906 and RA-68122 which was the official one present in the Russian Civil Aviation registry.
Probable cause:
Engine failure in flight for undetermined reasons.
Final Report:

Crash of a Grumman S-2T Tracker in Bahía Blanca

Date & Time: Apr 20, 2011
Type of aircraft:
Operator:
Registration:
0701/2-AS-22
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bahía Blanca - Bahía Blanca
MSN:
298
YOM:
1957
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a training flight on this Tracker delivered to the Armada Argentina in 1978. While flying in the vicinity of the Bahía Blanca-Comandante Espora Airport, the crew encountered unknown technical problems and was forced to attempt an emergency landing in an open field. While both pilots escaped with minor injuries, the aircraft was damaged beyond repair.