Crash of a Comp Air CA-8 in Sorocaba: 2 killed

Date & Time: May 29, 2013 at 1540 LT
Type of aircraft:
Operator:
Registration:
PP-XLR
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Sorocaba - Jundiaí
MSN:
0204CA8
YOM:
2006
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after take off from Sorocaba Airport, while climbing, the pilot encountered technical problems and elected to return. While trying to land in a wasteland, the single engine aircraft crashed in a street and was destroyed by impact forces and a post impact fire. Both occupants were killed as a house was also destroyed.

Crash of a Learjet 60 in Valencia: 2 killed

Date & Time: May 5, 2013 at 1000 LT
Type of aircraft:
Operator:
Registration:
N119FD
Flight Type:
Survivors:
No
Site:
Schedule:
Charallave – Valencia
MSN:
60-029
YOM:
1994
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On final approach to Valencia-Arturo Michelana Airport in marginal weather conditions, the aircraft crashed in a residential area some 2,055 metres short of runway. The aircraft was totally destroyed by impact forces and a post impact fire and both pilots were killed. A building, several houses and cars were also damaged by fire.

Crash of a Raytheon 390 Premier I in South Bend: 2 killed

Date & Time: Mar 17, 2013 at 1623 LT
Type of aircraft:
Operator:
Registration:
N26DK
Survivors:
Yes
Site:
Schedule:
Tulsa - South Bend
MSN:
RB-226
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
613
Captain / Total hours on type:
171.00
Copilot / Total flying hours:
1877
Copilot / Total hours on type:
0
Aircraft flight hours:
457
Circumstances:
According to the cockpit voice recorder (CVR), during cruise flight, the unqualified pilot-rated passenger was manipulating the aircraft controls, including the engine controls, under the supervision and direction of the private pilot. After receiving a descent clearance to 3,000 feet mean sea level (msl), the pilot told the pilot-rated passenger to reduce engine power to maintain a target airspeed. The cockpit area microphone subsequently recorded the sound of both engines spooling down. The pilot recognized that the pilot-rated passenger had shutdown both engines after he retarded the engine throttles past the flight idle stops into the fuel cutoff position. Specifically, the pilot stated "you went back behind the stops and we lost power." According to air traffic control (ATC) radar track data, at the time of the dual engine shutdown, the airplane was located about 18 miles southwest of the destination airport and was descending through 6,700 feet msl. The pilot reported to the controller that the airplane had experienced a dual loss of engine power, declared an emergency, and requested radar vectors to the destination airport. As the flight approached the destination airport, the cockpit area microphone recorded a sound similar to an engine starter spooling up; however, engine power was not restored during the attempted restart. A review of the remaining CVR audio did not reveal any evidence of another attempt to restart an engine. The CVR stopped recording while the airplane was still airborne, with both engines still inoperative, while on an extended base leg to the runway. Subsequently, the controller told the pilot to go-around because the main landing gear was not extended. The accident airplane was then observed to climb and enter a right traffic pattern to make another landing approach. Witness accounts indicated that only the nose landing gear was extended during the second landing approach. The witnesses observed the airplane bounce several times on the runway before it ultimately entered a climbing right turn. The airplane was then observed to enter a nose low, rolling descent into a nearby residential community. The postaccident examinations and testing did not reveal any anomalies or failures that would have precluded normal operation of the airplane. Although the CVR did not record a successful engine restart, the pilot was able to initiate a go-around during the initial landing attempt, which implies that he was able to restart at least one engine during the initial approach. The investigation subsequently determined that only the left engine was operating at impact. Following an engine start, procedures require that the respective generator be reset to reestablish electrical power to the Essential Bus. If the Essential Bus had been restored, all aircraft systems would have operated normally. However, the battery toggle switch was observed in the Standby position at the accident site, which would have prevented the Essential Bus from receiving power regardless of whether the generator had been reset. As such, the airplane was likely operating on the Standby Bus, which would preclude the normal extension of the landing gear. However, the investigation determined that the landing gear alternate extension handle was partially extended. The observed position of the handle would have precluded the main landing gear from extending (only the nose landing gear would extend). The investigation determined that it is likely the pilot did not fully extend the handle to obtain a full landing gear deployment. Had he fully extended the landing gear, a successful single-engine landing could have been accomplished. In conclusion, the private pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls directly resulted in the inadvertent dual engine shutdown during cruise descent. Additionally, the pilot's inadequate response to the emergency, including his failure to adhere to procedures, resulted in his inability to fully restore airplane systems and ultimately resulted in a loss of airplane control.
Probable cause:
The private pilot's inadequate response to the dual engine shutdown during cruise descent, including his failure to adhere to procedures, which ultimately resulted in his failure to
maintain airplane control during a single-engine go-around. An additional cause was the pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls, which directly resulted in the inadvertent dual engine shutdown.
Final Report:

Crash of a Piper PA-31T Cheyenne II in Fort Lauderdale: 3 killed

Date & Time: Mar 15, 2013 at 1621 LT
Type of aircraft:
Registration:
N63CA
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Fort Lauderdale - Fort Lauderdale
MSN:
31-7820033
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
10000
Aircraft flight hours:
5006
Circumstances:
The multiengine airplane had not been flown for about 4 months and was being prepared for export. The pilot was attempting a local test flight after avionics upgrades had been performed. Shortly after takeoff, the pilot transmitted that he was experiencing an "emergency"; however, he did not state the nature of the emergency. The airplane was observed experiencing difficulty climbing and entered a right turn back toward the airport. It subsequently stalled, rolled right about 90 degrees, and descended. The airplane impacted several parked vehicles and came to rest inverted. A postcrash fire destroyed the airframe. Both engines were destroyed by fire and impact damage. The left propeller assembly was fire damaged, and the right propeller assembly remained attached to the gearbox, which separated from the engine. Examination of wreckage did not reveal any preimpact malfunctions. It was noted that the left engine displayed more pronounced rotational signatures than the right engine, but this difference could be attributed to the impact sequence. The left propeller assembly displayed evidence of twisting and rotational damage, and the right propeller assembly did not display any significant evidence of twisting or rotational damage indicative of operation with a difference in power. The lack of flight recorders and the condition of the wreckage precluded the gathering of additional relevant information.
Probable cause:
The pilot's failure to maintain airplane control following an emergency, the nature of which could not be determined because of crash and fire damage, which resulted in an aerodynamic stall.
Final Report:

Crash of a Fokker 50 in Goma: 7 killed

Date & Time: Mar 4, 2013 at 1744 LT
Type of aircraft:
Operator:
Registration:
9Q-CBD
Flight Type:
Survivors:
Yes
Site:
Schedule:
Kananga - Lodja - Goma
MSN:
20270
YOM:
1992
Location:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The aircraft was completing a cargo flight from Kananga to Goma with an intermediate stop in Lodja, carrying four passengers, 6 crew members and a load of various goods. On final approach to Goma Airport Runway 36, the crew encountered poor weather conditions with limited visibility due to heavy rain falls. On final, the aircraft contacted the roof of a house and crashed in the garden of a residential area, coming to rest upside down. Three passengers were seriously injured while seven other occupants were killed.

Crash of an Antonov AN-26 in Sanaa: 10 killed

Date & Time: Nov 21, 2012
Type of aircraft:
Operator:
Registration:
420
Flight Phase:
Flight Type:
Survivors:
No
Site:
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
After takeoff from Sana'a Airport, while climbing, the crew informed ATC about technical problems and elected to make an emergency landing in a wasteland. The aircraft went out of control and crashed in an abandoned market building located in the Al-Hasaba District, some 9 km south of Sanaa' Airport. All 10 occupants were killed. According to Yemen Officials, the aircraft was registered 420 but no AN-26 seems to be operated in Yemen under this registration.

Crash of a Beechcraft G18 in Taylorville: 1 killed

Date & Time: Aug 11, 2012 at 1124 LT
Type of aircraft:
Operator:
Registration:
N697Q
Flight Phase:
Survivors:
No
Site:
Schedule:
Taylorville - Taylorville
MSN:
BA-468
YOM:
1959
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1429
Captain / Total hours on type:
7.00
Aircraft flight hours:
13833
Circumstances:
The airplane was substantially damaged when it impacted terrain in a residential neighborhood in Taylorville, Illinois. The commercial pilot sustained fatal injuries. Twelve parachutists on-board the airplane exited and were not injured. No persons on the ground were injured. The airplane was registered to Barron Aviation, LLC; Perry, Missouri, and operated by Barron Aviation Private Flight Services, LLC; Hannibal, Missouri, under the provisions of 14 Code of Federal Regulations Part 91, as a sport parachuting flight. Day visual meteorological conditions prevailed and no flight plan was filed. The local flight originated from Taylorville Municipal Airport (TAZ), Taylorville, Illinois, about 1100. The airplane had climbed to an altitude of about 11,000 feet mean sea level (msl) and the parachutists were seated inside the airplane on two rear facing "straddle benches". As the airplane arrived at the planned drop location, the parachutists stood up, opened the door, and moved further aft in the airplane in preparation for their jump. Five of the parachutists were positioned hanging on to the outside of the airplane with several others standing in the door and the remainder were standing in the cabin forward of the door. Several parachutists reported that they were almost ready to jump when they heard the sounds of the airplane's stall warning system. The airplane then suddenly rolled and all twelve parachutists quickly exited the airplane. Several of those who were last to exit reported that the airplane was inverted or partially inverted as they went out the door. The pilot, seated in the left front cockpit seat, did not exit the airplane. Several witnesses reported seeing the airplane turning and descending in an inverted attitude when the airplane appeared to briefly recover, but then entered a nearly vertical dive. The airplane impacted a tree and terrain in the back yard of an occupied residence. Emergency personnel who first responded to the accident scene reported a strong smell of gasoline and ordered the evacuation of several nearby homes. There was no post impact fire.
Probable cause:
The pilot's failure to maintain adequate airspeed and use the appropriate flaps setting during sport-parachuting operations, which resulted in an aerodynamic stall/spin and a subsequent loss of control. Contributing to the accident was the pilot’s failure to follow company guidance by allowing more than four passengers in the door area during exit, which shifted the airplane’s center of gravity aft.
Final Report:

Crash of a McDonnell Douglas MD-83 in Lagos: 159 killed

Date & Time: Jun 3, 2012 at 1545 LT
Type of aircraft:
Operator:
Registration:
5N-RAM
Survivors:
No
Site:
Schedule:
Abuja - Lagos
MSN:
53019/1783
YOM:
1990
Flight number:
DAV992
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
147
Pax fatalities:
Other fatalities:
Total fatalities:
159
Captain / Total flying hours:
18116
Captain / Total hours on type:
7466.00
Copilot / Total flying hours:
1143
Copilot / Total hours on type:
808
Aircraft flight hours:
60850
Aircraft flight cycles:
35220
Circumstances:
On 3rd June, 2012 at about 1545:00hrs, 5N-RAM, a Boeing MD-83, a domestic scheduled commercial flight, operated by Dana Airlines (Nig.) Limited as flight 0992 (DANACO 0992), crashed into a densely populated area of Iju-Ishaga, a suburb of Lagos, following engine number 1 loss of power seventeen minutes into the flight and engine number 2 loss of power while on final approach to Murtala Muhammed Airport Lagos, Nigeria. Visual Meteorological Conditions prevailed at the time and the airplane was on an instrument flight plan. All 153 persons onboard the airplane, including the six crew were fatally injured. There were also six confirmed ground fatalities. The airplane was destroyed. There was post impact fire. The flight originated at Abuja (ABV) and the destination was Lagos (LOS). The airplane was on the fourth flight segment of the day, consisting of two round-trips between Lagos and Abuja. The accident occurred during the return leg of the second trip. DANACO 0992 was on final approach to runway 18R at LOS when the crew declared a Mayday call “Dual Engine Failure – negative response from the throttles.” According to records, the flight arrived ABV as Dana Air flight 0993 at about 1350:00hrs and routine turn-around activities were carried out. DANACO 0992 initiated engine start up at 1436:00hrs. Abuja Control Tower cleared the aircraft to taxi to the holding point of runway 04. En-route ATC clearance was passed on to DANACO 0992 on approaching holding point of runway 04. According to the ATC ground recorder transcript, the aircraft was cleared to line-up on runway 04 and wait, but the crew requested for some time before lining-up. DANACO 0992 was airborne at 1458:00hrs after reporting a fuel endurance of 3 hours 30 minutes. The aircraft made contact with Lagos Area Control Centre at 1518:00hrs and reported 1545:00hrs as the estimated time of arrival at LOS at cruising altitude of 26,000 ft. The Cockpit Voice Recorder (CVR) retained about 30 minutes 53 seconds of the flight and started recording at 1513:44hrs by which time the Captain and First Officer (F/O) were in a discussion of a non-normal condition regarding the correlation between the engine throttle setting and an engine power indication. However, they did not voice concerns then that the condition would affect the continuation of the flight. The flight crew continued to monitor the condition and became increasingly concerned as the flight transitioned through the initial descent from cruise altitude at 1522:00hrs and the subsequent approach phase. DANACO 0992 reported passing 18,100ft and 7,700ft, at 1530:00hrs and 1540:00hrs respectively. After receiving radar vectors in heading and altitude from the Controller, the aircraft was issued the final heading to intercept the final approach course for runway 18R. According to CVR transcript, at 1527:30hrs the F/O advised the Captain to use runway 18R for landing and the request was made at 1531:49hrs and subsequently approved by the Radar Controller. The crew accordingly changed the decision height to correspond with runway 18R. At 1531:12hrs, the crew confirmed that there was no throttle response on the left engine and subsequently the Captain took over control as Pilot Flying (PF) at 1531:27hrs. The flight was however continued towards Lagos with no declaration of any distress message. With the confirmation of throttle response on the right engine, the engine anti-ice, ignition and bleed-air were all switched off. At 1532:05hrs, the crew observed the loss of thrust in No.1 Engine of the aircraft. During the period between 1537:00hrs and 1541:00hrs, the flight crew engaged in prelanding tasks including deployment of the slats, and extension of the flaps and landing gears. At 1541:46hrs the First Officer inquired, "both engines coming up?" and the Captain replied “negative” at 1541:48hrs. The flight crew subsequently discussed and agreed to declare an emergency. At 1542:10hrs, DANACO 0992 radioed an emergency distress call indicating "dual engine failure . . . negative response from throttle." At 1542:35hrs, the flight crew lowered the flaps further and continued with the approach and discussed landing alternatively on runway 18L. At 1542:45hrs, the Captain reported the runway in sight and instructed the F/O to retract the flaps and four seconds later to retract the landing gears. At 1543:27hrs, the Captain informed the F/O, "we just lost everything, we lost an engine. I lost both engines". During the next 25 seconds until the end of the CVR recording, the flight crew attempted to recover engine power without reference to any Checklist. The airplane crashed into a densely populated residential area about 5.8 miles north of LOS. The airplane wreckage was approximately on the extended centreline of runway 18R, with the main wreckage concentrated at N 06o 40.310’ E 003o 18.837' coordinates, with elevation of 177ft. During the impact sequence, the airplane struck an uncompleted building, two trees and three other buildings. The wreckage was confined in a small area, with the separated tail section and engines located at the beginning of the debris trail. The airplane was mostly consumed by post crash fire. The tail section, both engines and portions of both wings representing only about 15% of the airplane, were recovered from the accident site for further examination.
Probable cause:
Probable Causal Factors:
1. Engine number 1 lost power seventeen minutes into the flight, and thereafter on final approach, Engine number 2 lost power and failed to respond to throttle movement on demand for increased power to sustain the aircraft in its flight configuration.
2. The inappropriate omission of the use of the Checklist, and the crew’s inability to appreciate the severity of the power-related problem, and their subsequent failure to land at the nearest suitable airfield.
3. Lack of situation awareness, inappropriate decision making, and poor airmanship.

Tear down of the engines showed that the no.1 engine was overhauled in the U.S in August 2011 and was not in compliance with Service Bulletin SB 6452. Both engines had primary and secondary fuel manifold assemblies fractured, cracked, bent, twisted or pinched which led to fuel leaks, fuel discharge to bypass duct, loss of engine thrust and obvious failure of engine responding to
throttle movement. This condition was similar to the no.1 engine of a different Dana Air MD-80, 5N-SAI, that was involved in an incident in October 2013 when the aircraft returned to the departure airport with the engine not responding th throttle movements. This engine also was not in compliance with Service Bulletin SB 6452. This bulletin was issued in 2003 and called for the installation of new secondary fuel manifold assemblies, incorporating tubes fabricated from new material which has a fatigue life that was approximately 2 times greater than the previous tube material.
Final Report:

Crash of a Socata TBM-700 in Morristown: 5 killed

Date & Time: Dec 20, 2011 at 1005 LT
Type of aircraft:
Operator:
Registration:
N731CA
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Teterboro - Atlanta
MSN:
332
YOM:
2005
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
1400
Aircraft flight hours:
702
Circumstances:
Although the pilot filed an instrument flight rules flight plan through the Direct User Access Terminal System (DUATS), no evidence of a weather briefing was found. The flight departed in visual meteorological conditions and entered instrument meteorological conditions while climbing through 12,800 feet. The air traffic controller advised the pilot of moderate rime icing from 15,000 feet through 17,000 feet, with light rime ice at 14,000 feet. The controller asked the pilot to advise him if the icing worsened, and the pilot responded that he would let them know and that it was no problem for him. The controller informed the pilot that he was coordinating for a higher altitude. The pilot confirmed that, while at 16,800 feet, "…light icing has been present for a little while and a higher altitude would be great." About 15 seconds later, the pilot stated that he was getting a little rattle and requested a higher altitude as soon as possible. About 25 seconds after that, the flight was cleared to flight level 200, and the pilot acknowledged. About one minute later, the airplane reached a peak altitude of 17,800 feet before turning sharply to the left and entering a descent. While descending through 17,400 feet, the pilot stated, "and N731CA's declaring…" No subsequent transmissions were received from the flight. The airplane impacted the paved surfaces and a wooded median on an interstate highway. A postaccident fire resulted. The outboard section of the right wing and several sections of the empennage, including the horizontal stabilizer, elevator, and rudder, were found about 1/4 mile southwest of the fuselage, in a residential area. Witnesses reported seeing pieces of the airplane separating during flight and the airplane in a rapid descent. Examination of the wreckage revealed that the outboard section of the right wing separated in flight, at a relatively low altitude, and then struck and severed portions of the empennage. There was no evidence of a preexisting mechanical anomaly that would have precluded normal operation of the airframe or engine. An examination of weather information revealed that numerous pilots reported icing conditions in the general area before and after the accident. At least three flight crews considered the icing "severe." Although severe icing was not forecasted, an Airmen's Meteorological Information (AIRMET) advisory included moderate icing at altitudes at which the accident pilot was flying. The pilot operating handbook warned that the airplane was not certificated for flight in severe icing conditions and that, if encountered, the pilot must exit severe icing immediately by changing altitude or routing. Although the pilot was coordinating for a higher altitude with the air traffic controller at the time of the icing encounter, it is likely that he either did not know the severity of the icing or he was reluctant to exercise his command authority in order to immediately exit the icing conditions.
Probable cause:
The airplane’s encounter with unforecasted severe icing conditions that were characterized by high ice accretion rates and the pilot's failure to use his command authority to depart the icing conditions in an expeditious manner, which resulted in a loss of airplane control.
Final Report:

Crash of a Beechcraft 65-80 Queen Air in Manila: 13 killed

Date & Time: Dec 10, 2011 at 1415 LT
Type of aircraft:
Registration:
RP-C824
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Manila - San Jose
MSN:
LD-21
YOM:
1962
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
13
Circumstances:
On December 10, 2011, BE-65-80QA (Queen Air) with Registry RP-C824 took off from RWY 13, Manila Domestic Airport on/or about 0610 UTC (1410H) southbound for San Jose, Mindoro. There were three (3) persons on board, the PIC and two (2) other persons; one was seated at the right-hand cockpit seat and the other one at the passenger seat. After airborne, the ATC gave instructions to the pilot o turn right and report five (5) miles out. After performing the right turn, the pilot requested for a reland which was duly acknowledged but the ATC with instructions to cross behind traffic on short final Rwy 06 (a perpendicular international runway) and to confirm if experiencing difficulty. However, there was no more response from the pilot. From a level flight southward at about 200 feet AGL, three (3) loud sputtering/burst sounds coming from the aircraft were heard (by people on the ground) then the aircraft was observed making a left turn that progressed into a steep bank and roll-over on a dive. After about one complete roll on a dive the aircraft hit ground at point of impact (Coordinates 14.48848 N 121.025811 E), a confined area beside a creek surrounded by shaties where several people were in a huddle. Upon impact, the aircraft exploded and fire immediately spread to surrounding shanties and a nearby elementary school building. The aircraft was almost burned into ashes and several shanties were severely burned by post-crash fire. A total of thirteen (13) persons were fatality injured composed of: the 3 aircraft occupants who died due to non survivable impact and charred by post-crash fire, and ten (10) other persons on the ground, all residents at vicinity of impact point, incurred non-fatal injuries and were rushed to a nearby hospital for medical treatment. About 20 houses near the impact point were completely burnt and the adjacent Elementary School building was severely affected by fire.
Probable cause:
The Aircraft Accident Investigation and Inquiry Board determined that the probable cause of this accident was:
- Immediate Cause:
(1) Pilot’s Lack of event proficiency in emergency procedures for one (1) engine in-operative condition after-off. Pilot Error (Human Factor)
While a one engine in-operative condition during take-off after V1 is a survivable emergency event during training, the pilot failed to effectively maintain aircraft control the aircraft due to inadequate event proficiency.
- Contributing Cause:
(1) Left engine failure during take-off after V1. (Material Factor)
The left engine failed due to oil starvation as indicated by the severely burnt item 7 crankshaft assembly and frozen connecting rods 5 & 6. This triggered the series of events that led to the failure of the pilot to manage a supposedly survivable emergency event.
- Underlying Causes:
(1) Inadequate Pilot Training for Emergency Procedure. Human Factor
Emergency event such as this (one engine inoperative event – twin engine aircraft) was not actually or properly performed (discussed only) in actual training flights/check-ride and neither provided with corresponding psycho-motor training on a simulator. Hence, pilot’s motor skill/judgment recall was not effective (not free-flowing) during actual emergency event.
(2) Inadequate engine overhaul capability of AMO. Human Factor
There was no document to prove that engine parts scheduled to be overhauled aboard were complied with or included in the overhaul activity. The presence unauthorized welding spot in the left-hand engine per teardown inspection report manifested substandard overhaul activity.
(3) Inadequate regulatory oversight (airworthiness inspection) on the overhaul activity of the AMO (on engine overhaul). Human Factor
The airworthiness inspection on this major maintenance activity (engine overhaul) failed to ensure integrity and quality of replacement parts and work done (presence of welding spots).
(4) Unnecessary Deviation by ATC from the AIP provision on Runway 13 Standard VFR Departure Southbound.
The initiative of the AY+TC for an early right turn southbound after airborne was not in accord with the standard departure in the AIP which provides the safest corridor for takeoff and the ample time to stabilize aircraft parameters in case of a one engine inoperative emergency event for a successful re-land or controlled emergency landing.
Final Report: