Crash of a Piper PA-31-310 Navajo C in Aldinga

Date & Time: Jan 29, 2014 at 1132 LT
Type of aircraft:
Operator:
Registration:
VH-OFF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Aldinga - Kangaroo Island
MSN:
31-7812064
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 29 January 2014, at about 1100 Central Daylight-savings Time, the pilot prepared a Piper PA-31 aircraft, registered VHOFF, for a private flight from Aldinga aeroplane landing area (ALA) to Kangaroo Island, South Australia. To check fuel quantities, the pilot entered the cockpit, turned on the master switch and placed the left and right fuel selectors onto the main tank (inboard) position. The gauge for each tank showed just under half full. He then placed each fuel selector onto the auxiliary (outboard) tank position, where the gauge indicated the right and left auxiliary tanks were each about a quarter full. He did not return the selectors to the main tanks. He estimated that refuelling the main tanks would allow sufficient fuel for the flight with over an hour in reserve. He exited the aircraft while it was refuelled and continued preparing for the flight. Once refuelling was completed, the pilot conducted a pre-flight inspection, and finished loading the aircraft. The pilot and passenger then boarded. The pilot was familiar with Aldinga ALA, which is a non-controlled airport. At uncontrolled airports, unless a restriction or preference is listed for a certain runway in either the Airservices en route supplement Australia (ERSA), or other relevant publications, selection of the runway is the responsibility of the pilot. Operational considerations such as wind direction, other traffic, runway surface and length, performance requirements for the aircraft on that day, and suitable emergency landing areas in the event of an aircraft malfunction are all taken into consideration. On this day, the pilot assessed the wind to be favoring runway 14, which already had an aircraft in the circuit intending to land. However, he decided to use runway 03 due to the availability of a landing area in case of an emergency. He then completed a full run-up check of the engines, propellers and magnetos prior to lining up for departure. The pilot reported that all of the pre-take-off checks were normal. Once the aircraft landing on runway 14 was clear of the runway, the pilot went through his usual memory checklist prior to take-off. He scanned and crosschecked the flight and panel instruments, power quadrant settings and trims, but did not complete his usual final check, which was to reach down with his right hand and confirm that the fuel selector levers were on the main tanks. After broadcasting on the common traffic advisory frequency (CTAF) he commenced the take-off. At the appropriate speed, he rotated the aircraft as it passed the intersection of the 14 and 03 runways. Almost immediately both engines began surging, there was a loss of power, the power gauges fluctuated and the aircraft yawed from side to side. Due to the surging, fluctuating gauges and aircraft yaw, the pilot found it difficult to identify what he thought was a non-performing engine. He reported there were no warning lights so he retracted the landing gear, with the intent of getting the aircraft to attain a positive rate of climb, so he could trouble shoot further at a safe altitude. When a little over 50 ft above ground level (AGL), he realized the aircraft was not performing sufficiently, so he selected a suitable landing area. He focused on maintaining a safe airspeed and landed straight ahead. The aircraft touched down and slid about another 75-100 metres before coming to rest. The impact marks of the propellers suggest the aircraft touched the ground facing north-easterly and rotated to the north-west prior to stopping. The pilot turned off the master switch and both he and the passenger exited the aircraft. After a few minutes he re-entered the cockpit and completed the shutdown. Police and fire service attended shortly after the accident.
Probable cause:
Engine malfunction due to fuel starvation.
Final Report:

Crash of a Piper PA-31-310 Navajo in Port Raúl Marín Balmaceda

Date & Time: Dec 28, 2013 at 1000 LT
Type of aircraft:
Operator:
Registration:
CC-CMM
Flight Type:
Survivors:
Yes
Schedule:
Puerto Montt - Port Raúl Marín Balmaceda
MSN:
31-315
YOM:
1968
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7480
Captain / Total hours on type:
3100.00
Circumstances:
The pilot departed Puerto Montt at 0900LT on a positioning flight to Port Raúl Marín Balmaceda to pick up five passengers. On approach, the pilot decided to complete a loss pass to evaluate the landing conditions and the wind component. Shortly later, the aircraft landed on its belly and slid for few dozen metres before coming to rest in a grassy area. The pilot was uninjured and the aircraft was damaged beyond repair.
Probable cause:
The pilot forgot to lower the landing gear prior to landing.
Final Report:

Crash of a Piper PA-31P Pressurized Navajo in Doylestown

Date & Time: Sep 8, 2013 at 1030 LT
Type of aircraft:
Registration:
N57JK
Flight Type:
Survivors:
Yes
Schedule:
Cambridge - Doylestown
MSN:
31-7530020
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1612
Captain / Total hours on type:
1054.00
Aircraft flight hours:
3952
Circumstances:
Following a normal landing, the pilot felt no wheel braking action on the left wheel, and the brake pedal went to the floor. The pilot attempted to maintain directional control; however, the airplane departed the right side of the runway and traveled into the grass. The landing gear collapsed, and the airplane came to a stop, sustaining structural damage to the left wing spar. Postaccident examination confirmed that the left brake was inoperative and revealed a small hydraulic fluid leak at the shaft of the parking brake valve in the pressurized section of the cabin. Air likely entered the brake line at the area of the leak while the cabin was pressurized, rendering the left brake inoperative.
Probable cause:
A leaking parking brake valve, which allowed air to enter the left brake line and resulted in the eventual failure of the left wheel brake during the landing roll.
Final Report:

Crash of a Piper PA-31-310 Navajo C in Eilat: 1 killed

Date & Time: Aug 1, 2013 at 1800 LT
Type of aircraft:
Operator:
Registration:
4X-AKV
Flight Type:
Survivors:
Yes
Schedule:
Herzliya - Eilat
MSN:
31-8112021
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Following an uneventful flight from Herzliya, the pilot started the approach to Eilat Airport in excellent weather conditions. During the last segment, at a height of about 10 feet, the pilot initiated a go-around procedure following a misunderstanding about an ATC transmission that was given to another crew. The pilot mistakenly closed to fuel valve coupled to the right engine while trying to switch fuel tanks, causing the right engine to stop. Due to an asymmetric thrust, the pilot lost control of the airplane that veered to the right and crashed in a drainage ditch, coming to rest upside down. While both passengers were seriously injured, the pilot was killed.

Crash of a Piper PA-31-325 Navajo C/R in Tuxtla Gutierrez: 8 killed

Date & Time: Jan 17, 2013 at 1334 LT
Type of aircraft:
Registration:
XB-EZY
Flight Phase:
Survivors:
No
Schedule:
Tuxtla Gutierrez – Puebla
MSN:
31-8212007
YOM:
1982
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
At 1339LT, the crew was cleared for takeoff from runway 32 at Tuxtla Gutierrez-Angel Albino Corzo Airport. During initial climb, after being cleared to climb to 12,500 feet, the crew informed ATC he was returning to the airport. Shortly later, the aircraft lost height and crashed in a field, bursting into flames. The aircraft was totally destroyed and all 8 occupants were killed.
Probable cause:
One of the engine failed after takeoff due to a fuel pump malfunction. The crew elected to return but the aircraft stalled due to an insufficient speed. Poor engine maintenance was considered as a contributing factor as well as the fact that the crew initiated the flight while the aircraft's weight was above the allowable MTOW.
Final Report:

Crash of a Piper PA-31-310 Navajo C off Jacarepaguá

Date & Time: Jul 24, 2012 at 1610 LT
Type of aircraft:
Operator:
Registration:
PT-WOT
Survivors:
Yes
Schedule:
Jacarepaguá - Jacarepaguá
MSN:
31-7912021
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft was engaged in a survey flight off the State of Rio de Janeiro and departed Jacarepaguá-Roberto Marinho Airport in the afternoon. While returning to his base, the pilot encountered problems and decided to ditch the aircraft. The airplane came to rest few hundred metres offshore. All three occupants were rescued and the aircraft sank.

Crash of a Piper PA-31P-425 Navajo in Dalton: 1 killed

Date & Time: Jun 30, 2012 at 1620 LT
Type of aircraft:
Registration:
N33CG
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Dalton - Dalton
MSN:
31-7300157
YOM:
1973
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1685
Circumstances:
According to a friend of the pilot, the pilot was taking the airplane to have an annual inspection completed. The friend assisted the pilot before departure and watched as the airplane departed. He did not notice any anomalies with the airplane during the takeoff or the climbout. According to a witness in the vicinity of the accident site, he heard the airplane coming toward him, and it was flying very low. He looked up and saw the airplane approximately 200 feet over his house and descending toward the trees. As he watched the airplane, he noticed that the right propeller was not turning, and the right engine was not running. He stated that the left engine sounded as if it was running at full power. The airplane pitched up to avoid a power line and rolled to the right, descending below the tree line. A plume of smoke and an explosion followed. Examination of the right propeller assembly revealed evidence of significant frontal impact. The blades were bent but did not have indications of rotational scoring; thus they likely were not rotating at impact. One preload plate impact mark indicated that the blades were at an approximate 23-degree angle; blades that are feathered are about 86 degrees. Due to fire and impact damage of the right engine and related system components, the reason for the loss of power could not be determined. An examination of the airframe and left engine revealed no mechanical malfunctions or failures that would have precluded normal operation. A review of the airplane maintenance logbooks revealed that the annual inspection was 12 days overdue. According to Lycoming Service Instruction No. 1009AS, the recommended time between engine overhaul is 1,200 hours or 12 years, whichever occurs first. A review of the right engine maintenance logbook revealed that the engine had accumulated 1,435 hours since major overhaul and that neither engine had been overhauled within the preceding 12 years. Although the propeller manufacturer recommends that the propeller be feathered before the engine rpm drops below 1,000 rpm, a review of the latest revision of the pilot operating handbook (POH) revealed that the feathering procedure for engine failure did not specify this. It is likely that the pilot did not feather the right propeller before the engine reached the critical 1,000 rpm, which prevented the propeller from engaging in the feathered position
Probable cause:
The pilot’s failure to maintain airplane control following loss of power in the right engine for reasons that could not be determined because of fire and impact damage. Contributing to the accident was the pilot’s delayed feathering of the right propeller following the loss of engine power and the lack of specific emergency procedures in the pilot operating handbook indicating the need to feather the propellers before engine rpm falls below 1,000 rpm.
Final Report:

Crash of a Piper PA-31-325 Navajo C/R near Two Harbors: 1 killed

Date & Time: Jun 8, 2012 at 1427 LT
Type of aircraft:
Registration:
N174BH
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
South Saint Paul - South Saint Paul
MSN:
31-7612038
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On June 8, 2012, about 1307 central daylight time, a Piper PA-31-325, N174BH, departed from the South St Paul Municipal Airport-Richard E Fleming Field (SGS), South St Paul, Minnesota for a maintenance test flight. The airplane reportedly had one of its two engines replaced and the pilot was to fly for about 4 hours to break-in the engine. The airplane did not return from the flight and was reported overdue. The airplane is missing and is presumed to have crashed. The airline transport pilot has not been located. The airplane was registered to Family Celebrations LLC, and was operated as a 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed and no flight plan was filed. The flight departed SGS with the intention of returning to SGS at the conclusion of the flight. The airplane was reported missing and an alert notification issued about 2225. The last reported contact with the airplane and pilot was about 1300 when the fixed base operator at SGS towed the airplane to the fuel pumps. When he returned about 15 minutes later, the airplane was no longer there. Aircraft radar track data from various ground based sources indicated that the airplane departed SGS about 1307. The airplane maneuvered east of SGS before turning toward the north. The airplane's track continued north toward Duluth, Minnesota. Once the airplane reached Duluth, it followed the west shoreline of Lake Superior. Radar track data indicated that the airplane was at a pressure altitude of 2,800 feet when it reached the shoreline. The airplane continued along the west shoreline toward Two Harbors, Minnesota, flying over the water while maintaining a distance of about 0.5 miles from the shore. As the airplane approached Two Harbors, it descended. The airplane's last recorded position at 1427 was about 30 miles northeast of Duluth, Minnesota, at an uncorrected pressure altitude of 1,600 feet. The Air Force Rescue Coordination Center coordinated a search for the missing airplane. The Civil Air Patrol, United States Coast Guard, and other entities participated in the search efforts. Search efforts were suspended on July 4, 2012.
Probable cause:
Undetermined because the airplane was not found
Final Report:

Crash of a Piper PA-31-325 Navajo C/R near Quellón: 8 killed

Date & Time: Mar 1, 2012 at 1215 LT
Type of aircraft:
Operator:
Registration:
CC-CYM
Flight Phase:
Survivors:
No
Site:
Schedule:
Melinka – Quellón
MSN:
31-8012016
YOM:
1980
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
10508
Aircraft flight hours:
3406
Circumstances:
The twin engine aircraft departed Melinka Airport at 1200LT on a taxi flight to Quellón, carrying seven passengers and one pilot. Eight minutes later, the pilot reported his position at 6,500 feet some 20 NM south of the destination. Six minutes later, at 1214LT, he reported at 3,000 feet some 10 NM southwest of Quellón. Shortly later, radar and radio contacts were lost after the airplane impacted the slope of a mountain located in the Piedra Blanca Mountain Range. The wreckage was found 15 km southwest of Quellón. The aircraft was destroyed by impact forces and all eight occupants were killed. At the time of the accident, weather conditions were poor with rain, fog and strong winds.
Probable cause:
Controlled flight into terrain following the decision of the pilot to continue the flight under VFR mode in IMC conditions.
The following contributing factors were identified:
- Cloudy conditions affecting the area where the accident occurred,
- Entering IMC conditions without clearance,
- Not maintaining the flight under VFR.
Final Report:

Crash of a Piper PA-31-325 Navajo C/R in Welshpool: 2 killed

Date & Time: Jan 18, 2012 at 1117 LT
Type of aircraft:
Operator:
Registration:
G-BWHF
Flight Type:
Survivors:
No
Schedule:
Welshpool - Welshpool
MSN:
31-7612076
YOM:
1976
Location:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
11164
Captain / Total hours on type:
375.00
Copilot / Total flying hours:
17590
Copilot / Total hours on type:
2177
Circumstances:
The commander had retired from flying Commercial Air Transport operations with an airline in August 2011. He had recently renewed his single pilot Instrument Rating and Multi Engine Piston (Land) planes rating and his intention was to continue flying part-time. He had been invited to fly G‑BWHF, which was privately operated for business purposes, but his last flight in this aircraft was on 10 November 1998. Accordingly, he planned to conduct a re-familiarisation flight. The commander was accompanied by another pilot who was not a flight instructor but had recent experience of flying the aircraft and was familiar with the aerodrome. A webcam recorded the pilots towing the aircraft to the refuelling point, refuelling it and carrying out pre‑flight preparations. There were no witnesses to any briefings which may have taken place. The commander first started the right engine, which initially ran roughly and backfired before running smoothly. The left engine started normally. The second pilot took his place in the front right seat. The aircraft taxied to the holding point of Runway 22, and was heard by witnesses to be running normally. A witness who lived adjacent to the airfield but could not see the aircraft heard the power and propeller checks being carried out, three or four times instead of once per engine as was usual. The engines were heard to increase power and the witness observed the aircraft accelerate along the runway and takeoff at 1105 hrs. It climbed straight ahead and through a small patch of thin stratus cloud, the base of which the witness estimated was approximately 1,000 ft aal. The aircraft remained visible as it passed through the cloud and continued climbing. The witness turned away from the aircraft to continue working but stated that apart from the unusual number of run-up checks, the aircraft appeared and sounded normal. The pilot of a Robinson R22 helicopter which departed Welshpool at 1015 hrs described weather to the south of the aerodrome as drizzle with patches of broken stratus at 600-700 ft aal. He was able to climb the helicopter between the patches of stratus until, at 1,500 ft, he was above the tops of the cloud. Visibility below the cloud was approximately 5-6 km but, above the cloud, it was in excess of 10 km. He noted that the top of Long Mountain was in cloud and his passenger took a photograph of the Long Mountain area The R22 returned to the airfield and joined left hand downwind for Runway 22. As it did so, its pilot heard a transmission from the pilot of the PA-31 stating that he was rejoining for circuits. The R22 pilot transmitted his position in order to alert the PA-31, then continued around the circuit and called final before making his approach to the runway, landing at about 1115 hrs. After passing overhead Welshpool, it made a descending left circuit, becoming established on a left hand, downwind leg for Runway 22. A witness approximately 3.5 nm northeast of the accident site saw the aircraft coming towards him with both propellers turning. It made a turn to the left with the engines apparently at a high power setting and, as it passed over Long Mountain, commenced a descent. He could not recall whether he could still hear the engines as the aircraft descended. He then lost sight of it behind the rising ground of Long Mountain. A search was initiated when the aircraft failed to return to Welshpool. Its wreckage was located in an open field on the west slope of Long Mountain. There were no witnesses to the actual impact with the trees or surface of the field but the sound was heard by a witness in the wood who stated that the engines were audible immediately prior to impact. The accident, which was not survivable, occurred at 1117 hrs. Both pilots were fatally injured.
Probable cause:
The aircraft struck the tops of the trees located on the upper slope of Long Mountain, while descending for a visual approach to land on Runway 22 at Welshpool Airport. The trees were probably not visible to the pilots because of cloud covering the upper slopes.
Final Report: