Crash of a Beechcraft E90 King Air in Karnack: 1 killed

Date & Time: Jul 7, 2012 at 0404 LT
Type of aircraft:
Operator:
Registration:
N987GM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
DeKalb - Brownsville
MSN:
LW-65
YOM:
1973
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5300
Aircraft flight hours:
15082
Circumstances:
Before the flight, the pilot did not obtain a weather briefing and departed without approval from company personnel. The airplane departed the airport about 0230 and climbed to 14,500 feet mean sea level. The pilot obtained visual flight rules (VFR) flight following services from air traffic control (ATC) personnel during the flight. While the airplane was en route, ATC personnel advised the pilot that an area of moderate precipitation was located about 15 miles ahead along the airplane’s flight path. The pilot acknowledged the transmission and was then directed to contact another controller. About 3 minutes later, the new controller advised the pilot of an area of moderate to extreme precipitation about 2 miles ahead of the airplane. The pilot responded that he could see the weather and asked the controller for a recommendation for a reroute. The controller indicated he didn’t have a recommendation, but finished by saying a turn to the west (a right turn) away from the weather would probably be better. The pilot responded that he would make a right turn. There was no further radio contact with the pilot. Flight track data indicated the airplane was in a right turn when radar contact was lost. A review of the radar data, available weather information, and airplane wreckage indicated the airplane flew through a heavy to extreme weather radar echo containing a thunderstorm and subsequently broke up in flight. Postaccident examination revealed no mechanical malfunctions or anomalies with the airframe and engines that would have precluded normal operation. During the VFR flight, the pilot was responsible for remaining in VFR conditions and staying clear of clouds. However, Federal Aviation Administration directives instruct ATC personnel to issue pertinent weather information to pilots, provide guidance to pilots to avoid weather (when requested), and plan ahead and be prepared to suggest alternate routes or altitudes when there are areas of significant weather. The weather advisories and warnings issued to the pilot by ATC were not in compliance with these directives. The delay in providing information to the pilot about the heavy and extreme weather made avoiding the thunderstorm more difficult and contributed to the accident.
Probable cause:
The pilot's inadvertent flight into thunderstorm activity, which resulted in the loss of airplane control and the subsequent exceedance of the airplane’s design limits and in-flight breakup. Contributing to the accident was the failure of air traffic control personnel to use available radar information to provide the pilot with a timely warning that he was about to encounter extreme precipitation and weather along his route of flight or to provide alternative routing to the pilot.
Final Report:

Crash of a Beechcraft C90GT King Air in Morgantown: 1 killed

Date & Time: Jun 22, 2012 at 1001 LT
Type of aircraft:
Registration:
N508GT
Flight Type:
Survivors:
No
Schedule:
Tidioute - Farmington - Morgantown
MSN:
LJ-1775
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
22000
Aircraft flight hours:
1439
Circumstances:
The airplane, operated by Oz Gas Aviation LLC, was substantially damaged when it struck a communications tower near Morgantown, West Virginia. The certificated airline transport pilot was fatally injured. No flight plan had been filed for the positioning flight from Nemacolin Airport (PA88), Farmington, Pennsylvania, to Morgantown Municipal Airport (MGW), Morgantown, West Virginia conducted under Title14 Code of Federal Regulations (CFR) Part 91. At 0924 on the morning of the accident, the airplane departed from Rigrtona Airport (13PA), Tidioute, Pennsylvania for PA88 with the pilot and three passengers onboard. The airplane landed on runway 23 at PA88 at 0944. The pilot then parked the airplane; shutdown both engines, and deplaned the three passengers. He advised them that he would be back on the following day to pick them up. After the passengers got on a shuttle bus for the Nemacolin Woodlands Resort, the pilot started the engines. He idled for approximately 2 minutes, and then back taxied on runway 23 for takeoff. At 0957, he departed from runway 23 for the approximately 19 nautical mile positioning flight to MGW, where he was going to refuel and spend the night. After departure from PA88, the airplane climbed to 3,100 feet above mean sea level (msl) on an approximately direct heading for MGW. The pilot then contacted Clarksburg Approach Control and was given a discrete code of 0130. When the airplane was approximately nine miles east of the Morgantown airport, the air traffic controller advised the pilot that he had "radar contact" with him. The airplane then descended to 3,000 feet, and approximately one minute later struck the communications tower on an approximate magnetic heading of 240 degrees. According to a witness who was cutting timber across the road from where the accident occurred; the weather was cloudy with lighting and thunder, and it had just started "sprinkling". He then heard a loud "bang", turned, and observed the airplane descending upside down, and then impact. About 20 minutes later it stopped "sprinkling". He advised that he could still see the top of the tower when it was "sprinkling".
Probable cause:
The pilot's inadequate preflight route planning and in-flight route and altitude selection, which resulted in an in-flight collision with a communications tower in possible instrument
meteorological conditions. Contributing to the accident were the pilot's improper use of the enhanced ground proximity warning system's terrain inhibit switch and the air traffic controller's failure to issue a safety alert regarding the proximity of the tower.
Final Report:

Crash of a Beechcraft C90B King Air in Jundiaí: 1 killed

Date & Time: Apr 20, 2012 at 1430 LT
Type of aircraft:
Registration:
PP-WCA
Flight Type:
Survivors:
No
Schedule:
Jundiaí - Jundiaí
MSN:
LJ-1676
YOM:
2002
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot, sole aboard, was completing a local flight from Jundiaí-Comandante Rolim Adolfo Amaro Airport. Shortly after takeoff from runway 36, the pilot reported to ATC that the engine lost power and that he was not able to maintain a safe altitude. He was cleared for an immediate return and completed a circuit. On final approach to runway 18, he lost control of the airplane that crashed 180 metres short of runway and came to rest upside down, bursting into flames. The aircraft was totally destroyed and the pilot was killed.
Probable cause:
The following factors were identified:
- Upon intercepting the final leg for landing, the aircraft crossed the approach axis, and the pilot, in an attempt to make the aircraft join the approach axis again, may have depressed the rudder pedal in an inadequate manner, inadvertently making the aircraft enter a Cross Control Stall.
- The pilot, intentionally, violated a number of aeronautical regulations in force in order to fly an aircraft for which he had no training and was not qualified.
- The short experience of the pilot in the aircraft model hindered the correct identification of the situation and the adoption of the necessary corrective measures.
- The DCERTA’s vulnerability allowed a non-qualified pilot to file a flight notification by making use of the code of a qualified pilot. Thus, the last barrier capable of preventing the accident flight to be initiated was easily thrown down, by making it difficult to implement a more effective supervisory action.
Final Report:

Crash of a Beechcraft C90GTi King Air off Oranjestad

Date & Time: Apr 3, 2012 at 0920 LT
Type of aircraft:
Operator:
Registration:
N8116L
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Wichita - Fort Lauderdale - Willemstad - Belo Horizonte
MSN:
LJ-2042
YOM:
2011
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11700
Captain / Total hours on type:
2600.00
Copilot / Total flying hours:
3649
Copilot / Total hours on type:
33
Aircraft flight hours:
14
Circumstances:
On April 3, 2012, about 0920 atlantic standard time (ast), a Hawker Beechcraft C90GTx, N8116L, operated by Lider Taxi Aereo, was substantially damaged after ditching in the waters of the Caribbean Sea, 17 miles north of Aruba, following a dual loss of engine power during cruise. The flight departed Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, Florida, and was destined for Hato International Airport (TNCC), Willemstad, Curacao. The airline transport pilot and the pilot rated passenger were uninjured. Visual meteorological conditions prevailed, and an instrument flight plan was filed for the delivery flight conducted under 14 Code of Federal Regulations Part 91. The Amsterdam arrived at the ditching location at 1120. The airplane was partially submerged. The crew of the Amsterdam attempted to prevent the airplane from sinking by placing a cable around it and hoisting it onboard. However during the attempted recovery, the fuselage broke in half and the airplane sank.
Probable cause:
Review of the fuel ticket revealed that the misspelled words; "Top Neclles" was handwritten on it. It was also signed by the pilot. Further review revealed that only 25 gallons had been uploaded to the airplane, and this number had been entered in the box labeled "TOTAL GALLONS DELIVERED". Review of the start reading and end reading from the truck meter also concurred with this amount. Furthermore, It was discovered that the "134 gallons" that the pilot believed had been uploaded to the airplane was in fact the employee number of the fueler that had topped off the nacelle tanks and had entered his employee number on the "FUEL DEL BY:" line. Utilizing the information contained on the fuel ticket, it was determined that the airplane had departed with only 261 gallons of fuel on-board. Review of performance data in the POH/AFM revealed that in order to complete the flight the airplane would have needed to depart with 328 gallons on-board.
Final Report:

Crash of a Beechcraft F90 King Air off Belém

Date & Time: Feb 8, 2012 at 2244 LT
Type of aircraft:
Operator:
Registration:
PT-OFD
Survivors:
Yes
Schedule:
São Paulo – Belém
MSN:
LA-118
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5500
Captain / Total hours on type:
70.00
Copilot / Total flying hours:
6750
Copilot / Total hours on type:
7
Circumstances:
The aircraft departed São Paulo-Congonhas Airport at 1630LT on a flight to Belém, carrying two passengers and two pilots. During the approach to Belém-Val de Cans-Júlio Cezar Ribeiro Airport runway 06 by night, one of the engine flamed out. Few seconds later, the second engine failed as well. The crew ditched the aircraft in the Bay of Guajará, about 1,2 km short of runway 06 threshold. All four occupants were rescued by servicemen of the Naval Base who were on duty at the time of the accident. A pilot was slightly injured while three other occupants escaped uninjured. The aircraft sank and the wreckage was recovered 12 days later.
Probable cause:
The following findings were identified:
a) The pilots had valid aeronautical medical certificates;
b) The pilots had valid technical qualification certificates;
c) The aircraft captain had qualification and enough experience for the flight in question;
d) The copilot was under training;
e) The aircraft had a valid airworthiness certificate;
f) The planning of the flight from SBSP to SBBE was done by the pilot in command, who took in consideration an aircraft with a full load of fuel;
g) The flight plan read that the fuel endurance was 7 hours and 30 minutes of flight, for an estimated elapse time of 5 hours and 40 minutes at FL230;
h) When the aircraft was passing over the city of Palmas, State of Tocantins, the pilots decided, in conjunction, to proceed non-stop to the destination, discarding the need to make an intermediate landing for refueling;
i) The aircraft was registered in the passenger transport category (TPP) and was engaged in the transport of a sick person;
j) The fuel quantity indicators and the fuel flow indicators of the aircraft were not showing dependable information;
k) The flight plan for the leg betwren SBSP and SBBE contained information of sick person transportation, but there was no sick person on board;
l) The aircraft made a ditching near the banks of Guajará Bay, at a distance of approximately 1,200 meters from the threshold of runway 06 of SBBE;
m) The passengers and crew were rescued by Brazilian Navy servicemen on duty on the Naval Base of Val de Cans;
n) One of the pilots and both passengers got out uninjured, while the other pilot suffered minor injuries; and
o) The aircraft sustained substantial damage.
Contributing factors:
Concerning the operation of the aircraft
a) Attitude – a contributor
The captain failed to comply with norms and procedures by accepting to fly an aircraft on his day of rest, even knowing that he was to start his on-call duty hours as soon as he landed in SBBE.
He also showed to be overconfident when he decided to fly directly from SBSP to SBBE, trusting the 7-hour fuel endurance of his aircraft and the fuel consumption information displayed by the instruments, even after identifying their malfunction. The pilot under training, in turn, was complacent by accepting and agreeing with the pilot-in-command’s decision, without questioning his calculations or motivations for flying direct to the destination.
b) Motivation – a contributor
The captain was eager to return to SBBE on that same day, because he was supposed to start his on-call duty hours in the air taxi company for which he worked.
c) Decision-making process – a contributor
The captain failed to comply with important aspects concerning the route conditions and aircraft instruments by making a decision to fly directly from SBSP to SBBE.
Psychosocial information
a) Communication – a contributor
There was lack of assertiveness on the part of the copilot since he did not question the captain’s calculations and/or motivations to fly non-stop, when he (the copilot) considered that making a stop for refueling would be safer.
b) External influence – a contributor
The involvement of the captain with activities of another company on that same day, in addition to events belonging to his private life, had influence on his decisions in the initial planning of the flight and during the flight en route.
Organizational information
a) Work organization – a contributor
The company delegated responsibility for the entire planning of the flight to the pilots. Therefore, there was not any interference on the part of the company in the crew’s work day and in the legs defined for the flight.
b) Organizational culture – a contributor
The fact that the company performed an operation for which it was not certified reflected the fragility of an organizational culture which allowed it to perform activities unfavorable to operational safety.
Operational Factor
Concerning the operation of the aircraft
a) Flight indiscipline – a contributor
On several occasions during the flight, the pilots failed to comply with the norms and regulations in force, such as the sections 91.167 and 91.205 of the RBHA 91, the Pilot Operating Handbook and FAA Approved Airplane Flight Manual, and the Lei do Aeronauta (Law of the Aeronaut, Law nº 7.183 of 5 April 1984).
b) Training – undetermined
Before the ditching, the pilot unlocked the rear door of the aircraft and, then, failed to instruct the passengers as to the opening of the emergency exit. This fact shows a probable deviation in the process of training previously received by the captain, since the procedure prescribed for the situation was to abandon the aircraft through the emergency exit, which had to be unlocked after the ditching.
c) Piloting judgment – a contributor
At the moment of their decision to proceed non-stop to the destination, there was an inappropriate evaluation on the part of the crew, because they did not consider the hourly consumption until that point, and the malfunction of the fuel capacity indicator did not allow them to know the exact amount of fuel remaining in the tanks.
d) Flight planning – a contributor
There was a mistake on the part of the captain relative to the planning of the flight, since, in addition to a total flight time of 5 hours and 40 minutes, he did not consider the fuel necessary to fly to an alternate airport plus 45 minutes of flight. The captain and the pilot under training made an inappropriate evaluation of the effects brought by the operational conditions along the flight route.
Final Report:

Crash of a Beechcraft F90 King Air in Midland

Date & Time: Dec 2, 2011 at 0810 LT
Type of aircraft:
Registration:
N90QL
Flight Type:
Survivors:
Yes
Site:
Schedule:
Wharton - Midland
MSN:
LA-2
YOM:
1979
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4600
Captain / Total hours on type:
25.00
Aircraft flight hours:
8253
Circumstances:
The aircraft collided with terrain while on an instrument approach to the Midland Airpark (MDD), near Midland, Texas. The commercial pilot, who was the sole occupant, sustained serious injuries. The airplane was registered to and operated by Quality Lease Air Services LLC., under the provisions of 14 Code of Federal Regulations Part 91 as a positioning flight. Instrument meteorological conditions prevailed and an instrument flight rules (IFR) flight plan had been filed for the cross-country flight. The flight originated from the Wharton Regional Airport (ARM), Wharton, Texas, about 0626. The pilot obtained a weather briefing for the flight to MDD. The briefing forecasted light freezing drizzle for the proposed time and route of flight. While on approach to MDD, the airplane was experiencing an accumulation of moderate to severe icing and the pilot stated that he had all the deicing equipment on. According to the pilot, the autopilot was flying the airplane to a navigational fix called JIBEM. He switched the autopilot to heading mode and flew to the final approach fix called WAVOK. He deployed the deice boots twice before approaching WAVOK. An Airport Traffic Control Tower (ATCT) controller informed the pilot, that according to radar, he appeared to be flying to JIBEM. The pilot responded that he was correcting back and there was something wrong with the GPS. The controller canceled the airplane's approach clearance and the controller issued the pilot a turning and climbing clearance to fly for another approach. The pilot stated that his copilot's window iced up at that point. The pilot was vectored for and was cleared for another approach attempt. The pilot said that his window was "halfway iced up." About two minutes after being cleared for the second approach, the controller advised the pilot that the airplane appeared to be "about a half mile south of the course." The pilot responded, "Yep ya uh I got it." The pilot was given heading and climb instructions in case of a missed approach and was subsequently cleared to change to an advisory frequency. The pilot responded with, "Good day." The pilot had configured the aircraft with approach flaps and extended the landing gear prior to reaching the final approach fix. The pilot stated the aircraft remained in this configuration and he did not retract the gear and flaps. The pilot stated that he descended to 3,300 feet and was just under the cloud deck where he was looking for the runway. The pilot's accident report, in part, said: Everything was flying smooth until I accelerated throttles from about halfway to about three quarters. At this point I lost roll control and the airplane rolled approximately 90 degrees to the left. I disengaged autopilot and began to turn the yoke to the right and holding steady. It was slow to respond and when I thought that I had it leveled off the airplane continued to roll approximately 90 degrees to the right. At this time I was turning the yoke back to the left and pulling back to level it off, but it continued to roll to the left again. I was turning the yoke to the right again as I continued to pull back and the airplane rolled level, and the stall warning horn came on seconds before impact on the ground. The pilot stated he maintained a target airspeed speed of 120 knots on approach and 100 knots while on final approach. He stated he was close to 80 knots when the aircraft was in the 90° right bank. Witnesses in the area observed the airplane flying. A witness stated that the airplane's wings were "rocking." Other witnesses indicated that the airplane banked to the left and then nosed down. The airplane impacted a residential house, approximately 1 mile from the approach end of runway 25, and a post crash fire ensued. The pilot was able to exit the airplane and there were no reported ground injuries.
Probable cause:
The pilot's failure to maintain the recommended airspeed for icing conditions and his subsequent loss of airplane control while flying the airplane under autopilot control in severe
icing conditions, contrary to the airplane's handbook. Contributing to the accident was the pilot's failure to divert from an area of severe icing. Also contributing to the accident was the lack of an advisory for potential hazardous icing conditions over the destination area.
Final Report:

Crash of a Beechcraft B90 King Air in Hillsboro

Date & Time: Sep 17, 2011 at 1145 LT
Type of aircraft:
Registration:
N125A
Survivors:
Yes
Schedule:
Hillsboro - Hillsboro
MSN:
LJ-360
YOM:
1968
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1900
Captain / Total hours on type:
200.00
Aircraft flight hours:
9254
Circumstances:
While landing, the airplane touched down short of the runway, the left main landing gear impacted the edge of the runway and collapsed, and the airplane departed the edge of the runway into a culvert. The airplane’s left wing sustained substantial damage.
Probable cause:
The pilot's failure to obtain a proper touchdown point, which resulted in a runway undershoot.
Final Report:

Crash of a Beechcraft C90 King Air in Kaduna: 2 killed

Date & Time: May 24, 2011 at 1154 LT
Type of aircraft:
Operator:
Registration:
N364UZ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Old Kaduna - Old Kaduna
MSN:
LJ-805
YOM:
1979
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Aircraft flight hours:
9665
Circumstances:
On 24th May, 2011 at 11:54 h, a Beechcraft C90 aircraft with nationality and registration marks N364UZ, operated by Shoreline Energy International Limited (SEIL), departed Old Kaduna (Military) airport on a test flight with a pilot and another person onboard with three hours fuel endurance. The test flight was on a visual flight rules (VFR) flight plan. According to an eye witness, the aircraft sound was unusual and the aircraft seemed not to be gaining altitude after takeoff. Another eye witness (a local farmer), stated that he saw the aircraft moving up and down with increasing and decreasing engine sound. Thereafter, the aircraft impacted a mango tree, turned and crashed. The local farmer further stated that he and some military personnel tried all they could to rescue the occupants inside the aircraft but their efforts were not successful. At 11:59 h, the aircraft crashed on a farm-land 878 meters short of RWY 23 (military) and engulfed into flames. The two occupants were fatally injured. Dornier Aviation Nigeria AIEP (DANA) and Nigerian Air Force (NAF) fire-fighting personnel were dispatched immediately. There was no direct access between the runway and the accident site, which delayed the fire trucks from reaching the aircraft at accident site on time. The accident occurred in day light, in visual meteorological conditions (VMC).
Probable cause:
Causal Factor:
Inability of the pilot to control the aircraft to landing due to inadequate power to enable the pilot maintain the appropriate approach profile (height, speed and glide path) to cover the required distance to threshold.
Contributory factors:
1. Non-adherence to approved storage procedure.
2. Non-adherence to approved return from storage procedure.
3. Inadequate regulatory oversight by the authority on flight operation and maintenance of foreign registered aircraft in Nigeria.
Final Report:

Crash of a Beechcraft E90 King Air in Bournemouth

Date & Time: May 18, 2011 at 1131 LT
Type of aircraft:
Registration:
N46BM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bournemouth - Manchester
MSN:
LW-198
YOM:
1976
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
800
Captain / Total hours on type:
660.00
Circumstances:
The pilot had planned to fly from Bournemouth Airport to Manchester Airport operating the flight as a single pilot, with a passenger seated in the co-pilot’s seat. He arrived at the airport approximately one hour before the planned departure time of 1130 hrs, completed his pre‑flight activities and went to the aircraft at approximately 1110 hrs. The 1120 hrs ATIS gave the weather at the airport as: surface wind from 230° at 10 kt, visibility 10 km or greater, few clouds at 1,000 ft, broken cloud at 1,200 ft and at 2,000 ft, temperature 16°C, dew point 12°C and QNH 1015 hPa. After starting the engines, the pilot was cleared to taxi to holding point ‘N’ for a departure from Runway 26 and he was given clearance to take off at 1127 hrs. At 1129:45 hrs, approximately 55 seconds after the aircraft became airborne, the aerodrome controller transmitted “four six bravo mike do you have a problem?” because he believed the aircraft was not climbing normally. The pilot replied “november four six bravo going around” and, shortly afterwards, “four six bravo requesting immediate return”. The controller cleared the pilot to use either runway to land back at the airport but received no reply. The pilot carried out a forced landing into a field 1.7 nm west of the Runway 08 threshold at Bournemouth Airport and neither he nor his passenger was hurt.
Probable cause:
The pilot experienced symptoms of symmetrical power loss sufficient to prevent the aircraft from sustaining level flight and made a forced landing into a field. The deficiency in the aircraft’s takeoff performance suggested that its powerplants were not producing sufficient thrust. As fuel contamination was discounted and no fault was found in either engine, it was concluded that, in all probability, the poor performance was not caused by a failure in either powerplant. Maximum rpm was not selected for departure but it was unlikely that this explained the aircraft’s poor performance on the runway or in the air. The pilot insisted that he had set torque to the takeoff limit. There was insufficient evidence to enable the cause of the apparent power loss to be determined.
Final Report:

Crash of a Beechcraft B90 King Air in Harrisburg

Date & Time: Feb 8, 2011
Type of aircraft:
Registration:
N90BU
Flight Type:
Survivors:
Yes
MSN:
LJ-425
YOM:
1969
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Harrisburg Airport, the undercarriage collapsed and the aircraft came to rest on its belly. Both occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The exact cause of the accident remains unknown as no investigation was completed by the NTSB.