Crash of a Beechcraft B90 King Air in Laguna del Sauce: 10 killed

Date & Time: Mar 19, 2015 at 2038 LT
Type of aircraft:
Operator:
Registration:
LV-CEO
Flight Phase:
Survivors:
No
Schedule:
Laguna del Sauce – San Fernando
MSN:
LJ-454
YOM:
1969
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
9348
Copilot / Total flying hours:
5095
Aircraft flight hours:
10319
Circumstances:
The twin engine airplane departed Laguna del Sauce Airport on a charter flight to San Fernando Airport near Buenos Aires, carrying eight passengers and two pilots. Shortly after a night takeoff from Laguna del Sauce Airport runway 01, the aircraft entered a controlled descent and crashed in shallow water some 2 km northwest of the airport, bursting into flames. The aircraft was destroyed by a post crash fire and all 10 occupants were killed.
Probable cause:
The accident resulted from impact with the ground without loss of control due to the combination of the following factors:
- The aircraft's climb profile did not meet the manufacturer's recommendations for speed and rate of climb,
- The center of gravity was outside the flight envelope,
- The total weight of the aircraft at the time of the accident was 124 kilos above the MTOW,
- Both pilots were tired due to a lack of rest time and a shift of more than 18 hours,
- The captain did not fly this type of aircraft since 1997 and was used to flying jets,
- The copilot had no experience on this type of aircraft despite being in possession of a valid license,
- The pilots' knowledge and understanding of the aircraft's systems and operation was inadequate,
- The operational checklists found on board the aircraft were not up to date,
- The pilots flew for the first time at night on this aircraft and for the second time together,
- The aircraft was operated under commercial rules on behalf of a travel agency while it could only fly privately,
- The instructor in charge of the training of both pilots and the person in charge of scheduling the flight refused to be questioned by the board of inquiry,
- An excessive workload for the crew and a lack of rest contributed to the pilots' loss of situational awareness,
- Both engines' compressors were running at low speed on impact,
- Both engines' propellers were turning at a speed close to low pitch,
- No mechanical anomalies were found on the engines and their components,
- Insufficient qualifications of the crew to fly on this type of aircraft,
- Pressure from the aircraft's owner to complete the flight,
- Crew fatigue and stress,
- Inadequate maintenance of the aircraft.
Final Report:

Crash of a Rockwell 500U Shrike Commander in Badu Island

Date & Time: Mar 8, 2015 at 1230 LT
Operator:
Registration:
VH-WZV
Flight Phase:
Survivors:
Yes
Schedule:
Badu Island - Horn Island
MSN:
500-1656-11
YOM:
1966
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 8 March 2015, the pilot of an Aero Commander 500 aircraft, registered VH-WZV, prepared to conduct a charter flight from Badu Island to Horn Island, Queensland, with five passengers. The aircraft had been refuelled earlier that day at Horn Island, where the pilot conducted fuel drains with no contaminants found. He had operated the aircraft for about 2 hours prior to landing at Badu Island with no abnormal performance or indications. At about 1330 Eastern Standard Time (EST), the pilot started the engines and conducted the standard checks with all indications normal, obtained the relevant clearances from air traffic control, and taxied for a departure from runway 30. As the pilot lined the aircraft up on the runway centreline at the threshold, he performed a pre-take-off safety self-brief and conducted the pre-takeoff checks. He then applied full power, released the brakes and commenced the take-off run. All engine indications were normal during the taxi and commencement of the take-off run. When the airspeed had increased to about 80 kt, the pilot commenced rotation and the nose and main landing gear lifted off the runway. Just as the main landing gear lifted off, the pilot detected a significant loss of power from the left engine. The aircraft yawed to the left, which the pilot counteracted with right rudder. He heard the left engine noise decrease noticeably and the aircraft dropped back onto the runway. The pilot immediately rejected the take-off; reduced the power to idle, and used rudder and brakes to maintain the runway centreline. The pilot initially assessed that there was sufficient runway remaining to stop on but, due to the wet runway surface, the aircraft did not decelerate as quickly as expected and he anticipated that the aircraft would overrun the runway. As there was a steep slope and trees beyond the end of the runway, he steered the aircraft to the right towards more open and level ground. The aircraft departed the runway to the right, collided with a fence and a bush resulting in substantial damage. The pilot and passengers were not injured.
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage in Spokane: 1 killed

Date & Time: Feb 22, 2015 at 1405 LT
Registration:
C-GVZW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Villeneuve – Spokane – Stockton
MSN:
46-36281
YOM:
2000
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
667
Captain / Total hours on type:
63.00
Aircraft flight hours:
2388
Circumstances:
The pilot was conducting a cross-country flight from Canada to California and had landed to clear customs into the United States and to refuel his airplane. The pilot then departed to continue the flight. During the initial climb after takeoff, the engine experienced a total loss of power, and the pilot attempted to make an off-airport forced landing. The right wing struck railroad tracks at the top of a hill, and the airplane continued down an embankment, where it came to rest adjacent to the bottom of a railroad bridge. Postaccident interviews revealed that, when requesting fuel from the fixed-base operator (FBO), the pilot did not specify a grade of fuel to be used to service the airplane. The refueler mistakenly identified the airplane as requiring Jet A fuel, even though the fuel filler ports were placarded "AVGAS (aviation gasoline) ONLY." The fueler subsequently fueled the airplane with Jet A instead of aviation gasoline. Additionally, the fueling nozzle installed on the fuel truck at the time of the refueling was not the proper type of nozzle. Jet A and AvGas fueling nozzles are different designs in order to prevent fueling an airplane with the wrong type of fuel. Following the fueling, the pilot returned to the FBO and signed a receipt, which indicated that the airplane had been serviced with Jet A. There were no witnesses to the pilot's preflight activities, and it is unknown if the pilot visually inspected or obtained a fuel sample before takeoff; however, had the pilot done this, it would have been apparent that the airplane had been improperly fueled.
Probable cause:
A total loss of engine power due to the refueler's incorrect refueling of the airplane. Contributing to the accident was the fixed-base operator's improper fueling nozzle, which facilitated the use of an incorrect fuel, and the pilot's inadequate preflight inspection.
Final Report:

Crash of an Antonov AN-26 in Quelimane

Date & Time: Feb 14, 2015 at 1530 LT
Type of aircraft:
Operator:
Registration:
FA312
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Quelimane – Mocuba
MSN:
116 03
YOM:
1981
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Quelimane on a cargo/military/supply mission to Mocuba, carrying six crew members and a load of equipment for the victims of the recent flood in northern Mozambique. Shortly after takeoff, one of the engines failed. The crew attempted an emergency landing when the aircraft crash landed in a field and came to rest about 150 metres past the runway end. All six occupants escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Piper PA-46-500TP Malibu Meridian in Västerås

Date & Time: Feb 13, 2015 at 1203 LT
Registration:
N164ST
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Västerås – Prague
MSN:
46-97064
YOM:
2001
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
674
Captain / Total hours on type:
184.00
Aircraft flight hours:
2767
Circumstances:
The aircraft, a Piper PA46-500TP Malibu Meridian, should carry out a private flight from Västeras airport to Prague. On board were a pilot and two passengers. Shortly after take-off an engine failure occurred and the pilot decided to make an emergency landing on Björnö Island, situated slightly to the right in the flight direction. The aircraft hit the ground with the left wing first and then rolled a number of times before it came to a final stop. During the accident both wings and parts of the tail separated from the aircraft. The fuselage remained relatively undamaged during the crash course. All three occupants escaped with minor injuries. A special study of the sequence of events shows that the impact, with the left wing first, caused the airplane's wings to act as shock absorbers, which greatly contributed to that the occupants only received minor injuries. During the accident - which occurred next to a secondary protection zone for water supply to the city of Västerås – a significant amount of fuel leaked out from the wreckage. The accident site was decontaminated after the accident. Examination undertaken in the area after the accident has not showed any trace of residual contamination in the soil.
Probable cause:
The engine failure was caused by damage to the engine's power turbine section. Most likely, the damage has been initiated in a labyrinth seal to the power turbine. The cause of the initial damage of the seal has not been established. The technical failure can not be assessed to be in a risk category where the risk of repeated failures of the same type is high. The accident was caused by damage to the power turbine which occurred over time, and that could not be identified by the engine's maintenance program.
Final Report:

Crash of a Beechcraft 1900C in Kendall: 4 killed

Date & Time: Feb 11, 2015 at 1439 LT
Type of aircraft:
Registration:
YV1674
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kendall - Procidenciales
MSN:
UC-47
YOM:
1988
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
19053
Captain / Total hours on type:
1476.00
Copilot / Total flying hours:
9529
Copilot / Total hours on type:
152
Aircraft flight hours:
35373
Circumstances:
The accident flight was a repositioning flight being operated by two airline transport pilots, and it was the multiengine turboprop airplane's first flight after an aviation maintenance technician (AMT) had replaced the left engine propeller with an overhauled propeller. The AMT subsequently performed an engine run, which included verifying correct power settings and corresponding blade angles. A review of flight data recorder (FDR) data revealed that, about 2 seconds after rotation, the left engine propeller rpm decreased to 60 percent, and the left engine torque increased off-scale (beyond 5,000 ft lbs), which is consistent with the left propeller traveling to the feathered position and the engine torque increasing in an attempt to maintain propeller rpm. About 30 seconds later, the flight crew shut down the left engine and attempted to return to the departure airport. Postaccident examination of the rudder trim actuator revealed that the rudder trim was at its full-right limit, which would have occurred to counteract the left engine drag before its shutdown. Based on this evidence, it is likely that the flight crew did not readjust the trim when the drag was alleviated, which resulted in the airplane being operated in a crosscontrolled attitude for about 50 seconds with a left bank and full-right rudder trim. Although the airplane should have been able to climb about 500 ft per minute with one engine operating, it slowed and descended from 300 ft in the cross-controlled attitude until it stalled, as indicated by a stall warning recorded by the cockpit voice recorder, and subsequently impacted terrain. Examination of the wreckage, including teardown examination of the left engine and propeller, did not reveal any preimpact mechanical anomalies. Review of the airplane maintenance manual revealed instructions to check the propeller reversing linkage on the front end of the engine, which controlled the beta valve, for proper rigging during propeller installation. The manual also contained a warning that misadjustment of the beta valve can cause unplanned feathering of the propeller and result in a possible hazard to airplane operation and over torque damage to the engine; however, the beta valve rigging could not be verified postaccident due to impact damage. Additionally, the ground/flight idle solenoid energizes when weight becomes off wheels and further opens the beta valve, which could exacerbate an existing misrigged condition as soon as the airplane becomes airborne, which is when the airplane experienced the uncommanded propeller feathering. The FDR data were consistent with the flight crew not performing the Before Takeoff (Runup) checklist. One of the items on that checklist was a low-pitch solenoid test, which would have energized the solenoid and possibly driven the left propeller uncommanded to feather during ground operations rather than in flight. A similar test during the post maintenance engine-run would have had the same results.
Probable cause:
The left engine propeller's uncommanded travel to the feathered position during takeoff for reasons that could not be determined due to impact damage. Contributing to the accident was the flight crew's failure to establish a coordinated climb once the left engine was shut down and the left propeller was in the feathered position.
Final Report:

Crash of an ATR72-600 in Taipei: 43 killed

Date & Time: Feb 4, 2015 at 1054 LT
Type of aircraft:
Operator:
Registration:
B-22816
Flight Phase:
Survivors:
Yes
Schedule:
Taipei - Kinmen
MSN:
1141
YOM:
2014
Flight number:
GE235
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
53
Pax fatalities:
Other fatalities:
Total fatalities:
43
Captain / Total flying hours:
4914
Captain / Total hours on type:
3151.00
Copilot / Total flying hours:
6922
Copilot / Total hours on type:
5687
Aircraft flight hours:
1627
Aircraft flight cycles:
2356
Circumstances:
The twin turboprop took off from runway 10 at 1052LT. While climbing to a height of 1,200 feet, the crew sent a mayday message, stating that an engine flamed out. Shortly later, the aircraft stalled and banked left up to an angle of 90° and hit the concrete barrier of a bridge crossing over the Keelung River. Out of control, the aircraft crashed into the river and was destroyed. It has been confirmed that 40 occupants were killed while 15 others were rescued. Three occupants remains missing. A taxi was hit on the bridge and its both occupants were also injured. According to the images available, it appears that the left engine was windmilling when the aircraft hit the bridge. First investigations reveals that the master warning activated during the initial climb when the left engine was throttled back. Shortly later, the right engine auto-feathered and the stall alarm sounded.
Probable cause:
The accident was the result of many contributing factors which culminated in a stall-induced loss of control. During the initial climb after takeoff, an intermittent discontinuity in engine number 2’s auto feather unit (AFU) may have caused the automatic take off power control system (ATPCS) sequence which resulted in the uncommanded autofeather of engine number 2 propellers. Following the uncommanded autofeather of engine number 2 propellers, the flight crew did not perform the documented abnormal and emergency procedures to identify the failure and implement the required corrective actions. This led the pilot flying (PF) to retard power of the operative engine number 1 and shut down it ultimately. The loss of thrust during the initial climb and inappropriate flight control inputs by the PF generated a series of stall warnings, including activation of the stick shaker and pusher. After the engine number 1 was shut down, the loss of power from both engines was not detected and corrected by the crew in time to restart engine number 1. The crew did not respond to the stall warnings in a timely and effective manner. The aircraft stalled and continued descent during the attempted engine restart. The remaining altitude and time to impact were not enough to successfully restart the engine and recover the aircraft.
The following findings related to probable causes were noted:
An intermittent signal discontinuity between the auto feather unit (AFU) number 2 and the torque sensor may have caused the automatic take off power control system (ATPCS):
- Not being armed steadily during takeoff roll,
- Being activated during initial climb which resulted in a complete ATPCS sequence including the engine number 2 autofeathering.
The available evidence indicated the intermittent discontinuity between torque sensor and auto feather unit (AFU) number 2 was probably caused by the compromised soldering joints inside the AFU number 2.
The flight crew did not reject the take off when the automatic take off power control system ARM pushbutton did not light during the initial stages of the take off roll.
TransAsia did not have a clear documented company policy with associated instructions, procedures, and notices to crew for ATR72-600 operations communicating the requirement to reject the take off if the automatic take off power control system did not arm.
Following the uncommanded autofeather of engine number 2, the flight crew failed to perform the documented failure identification procedure before executing any actions. That resulted in pilot flying’s confusion regarding the identification and nature of the actual propulsion system malfunction and he reduced power on the operative engine number 1.
The flight crew’s non-compliance with TransAsia Airways ATR72-600 standard operating procedures - Abnormal and Emergency Procedures for an engine flame out at take off resulted in the pilot flying reducing power on and then shutting down the wrong engine.
The loss of engine power during the initial climb and inappropriate flight control inputs by the pilot flying generated a series of stall warnings, including activation of the stick pusher. The crew did not respond to the stall warnings in a timely and effective manner.
The loss of power from both engines was not detected and corrected by the crew in time to restart an engine. The aircraft stalled during the attempted restart at an altitude from which the aircraft could not recover from loss of control.
Flight crew coordination, communication, and threat and error management (TEM) were less than effective, and compromised the safety of the flight. Both operating crew members failed to obtain relevant data from each other regarding the status of both engines at different points in the occurrence sequence. The pilot flying did not appropriately respond to or integrate input from the pilot monitoring.
The engine manufacturer attempted to control intermittent continuity failures of the auto feather unit (AFU) by introducing a recommended inspection service bulletin at 12,000 flight hours to address aging issues. The two AFU failures at 1,624 flight hours and 1,206 flight hours show that causes of intermittent continuity failures of the AFU were not only related to aging but also to other previously undiscovered issues and that the inspection service bulletin implemented by the engine manufacturer to address this issue before the occurrence was not sufficiently effective. The engine manufacturer has issued a modification addressing the specific finding of this investigation. This new modification is currently implemented in all new production engines, and another service bulletin is available for retrofit.
Pilot flying’s decision to disconnect the autopilot shortly after the first master warning increased the pilot flying’s subsequent workload and reduced his capacity to assess and cope with the emergency situation.
The omission of the required pre-take off briefing meant that the crew were not as mentally prepared as they could have been for the propulsion system malfunction they encountered after takeoff.
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage JetProp DLX in Sézenove: 1 killed

Date & Time: Jan 30, 2015 at 1201 LT
Operator:
Registration:
N246PR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Geneva - Genk
MSN:
46-36063
YOM:
1996
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1073
Captain / Total hours on type:
89.00
Aircraft flight hours:
1997
Circumstances:
The pilot, sole on board, departed Geneva-Cointrin Airport on a private flight to Genk-Zwartberg Airport where the aircraft was supposed to follow a maintenance program. The single engine aircraft departed runway 23 at 1157LT and continued to climb in IMC conditions. About 30 seconds after he was transferred to the departure frequency, the pilot was cleared to climb to FL090. At an altitude of 4,200 feet and at a speed of 142 knots, the aircraft climbed steeply then veered to the left. About 12 seconds later, the aircraft stopped to climb and another period of 8 seconds was necessary to stabilize and to follow the route. At 1159LT, the aircraft deviated to the left during 20 seconds, drifting about 555 metres from the runway axis. After following various headings with huge variations in ground speed and altitude, the aircraft entered an uncontrolled descent and crashed in an open field located in Sézenove, about 7,8 km southwest from Geneva-Cointrin Airport runway 05 threshold. The aircraft disintegrated on impact and the pilot was killed.
Probable cause:
The accident was due to a loss of control that brought the aircraft into unusual attitudes, which the pilot was unable to restore and which led to his fall. The insufficient skills of the pilot when faced with a high performance aircraft, whose systems are complex, contributed to the occurrence of the accident.
Final Report:

Crash of a Canadair BD-700-1A11 Global 5000 in Tacloban

Date & Time: Jan 17, 2015 at 1345 LT
Type of aircraft:
Registration:
RP-C9363
Flight Phase:
Survivors:
Yes
Schedule:
Tacloban - Manila
MSN:
9363
YOM:
2009
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On or about 1000H January 17, 2015, the Holy Father “Pope Francis” visited the typhoon-devastated province of Leyte and utilized an Airbus 320 aircraft for Tacloban airport, and Bombardier Global 5000 RP-C9363 aircraft was part of the Papal entourage with passengers on board. The weather condition was worsening and the visit of the Pope had to cut short due to approaching tropical storm code named “AMANG”, with strong winds of up to 130km/h(80mph) according to PAGASA and moderate rain as signal n°2 was already forecasted at the province of Leyte. At 1304H, the Global 5000 RP-C9363 was given start up clearance by tower controller and subsequently a taxi clearance at 1308H to exit via south taxiway next to the departing Airbus320 PAL8010. At 1306H, the First Airbus 320 PAL8010 aircraft carrying the Papal entourage took-off utilizing RWY 36 with prevailing wind condition of 290̊/18 knots crosswind and temperature of 24°. At 1311H, RP-C 9363 was not allowed to move from present position to proceed to the active runway via south taxiway by the military ground marshaller. At 1322H, the 2nd Airbus 320 PAL8191 took-off with prevailing wind conditions of 290°/23 kts crosswind. The separation time between the Global 5000 to the first and second aircraft were 29 minutes and 13 minutes respectively. At 1335H, finally RP-C9363 Global 5000 was cleared for take-off at runway 36 bound for Ninoy Aquino International Airport (RPLL) with two (2) pilots and 14 passengers on board. The wind condition at that time was 300°/18 kts with gustiness and temperature of 24°. The aircrew performed rolling take-off and the acceleration was normal, the pilot nonflying (NPF) called for air speed alive, 80 knots, V1 and Rotate. Before approaching south taxiway abeam the terminal building, the aircraft started to veer to the left side of the runway centerline. The aircraft continued to roll veering to the left side of the runway and the left hand main landing gear was already out of the runway after the north taxiway. The aircraft underwent runway excursion and sustained substantial damage after simultaneous collision with the concrete bases of runway edge lights and to the concrete culvert before it came to a complete stop at approximately 1500 meters from the take-off point. Immediate evacuation was performed to all passengers. The crash and fire rescue personnel arrived at the area and assisted the passengers and aircrew.
Probable cause:
The Aircraft Accident Investigation and Inquiry Board determined that the probable cause of this accident was:
- Lack of recurrent training of the flight crew:
Routine flights do not prepare a pilot for unusual situations, whether they are unexpected crosswinds or systems/engine anomalies. Pilots should receive regular recurrent training to include abnormal and emergency procedures.
- The existing runway edge light design:
The PIC tried to recover the aircraft back to the runway but apparently the aircraft left main landing gears already hit or bumped the concrete base of runway edge lights. The design of runway strips or shoulder must be free from fixed objects other than frangible visual aids provided for the guidance of aircraft and must not be constructed
with sharp edges; and where the lights will not normally come into contact with aircraft wheels, such as threshold lights, runway end lights and runway edge lights;
- Human Factors:
Due to deteriorating adverse weather conditions and due to the delay of their initial request for take-off clearance plus the sudden change of flight plan affected the Captain’s ability to perform a take-off procedure as recommended in the aircraft flight manual and instead delegated flight control duties to the F/O resulting in the loss of coordination between the light crew.
Final Report:

Crash of an Antonov AN-26B in Magadan

Date & Time: Jan 3, 2015 at 1119 LT
Type of aircraft:
Operator:
Registration:
RA-26082
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Petropavlovsk-Kamchatsky – Magadan – Mirny – Nizhnevartovsk
MSN:
117 05
YOM:
1981
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3783
Captain / Total hours on type:
2240.00
Copilot / Total flying hours:
11986
Copilot / Total hours on type:
94
Aircraft flight hours:
13698
Aircraft flight cycles:
6810
Circumstances:
During the take off run, at a speed of 250 km/h, the crew initiated the rotation when the aircraft failed to lift off. The captain decided to abandon the take off and started an emergency braking. The aircraft veered off runway to the right, went through a snow covered terrain, lost its nose and right main gear before coming to rest 490 meters further, with the right wing bent. The aircraft was considered as damaged beyond repair while all eight occupants were unhurt.
Probable cause:
The accident occurred as result of the aircraft departing the side of the runway after the commander rejected takeoff after having been unable to use the elevator because of the yoke's locked position. The roll beyond the edge of the runway was likely caused by the flight engineer while attempting to operate the handle to release the flight controls lock while the aircraft was already accelerating for takeoff. The accident was thus caused by this combination of factors:
- violation of requirements by FCOM to ascertain the flight controls were free and usable before engine start,
- failure by the crew to execute the checklists to check elevator, rudder and ailerons were free to move before takeoff,
- flight crew receives insufficient practice in real flight to maintain skills acquired during simulator training in the management of the aircraft and its systems resulting in negative impact during emergency situations.
Final Report: