Country
code

South Australia

Crash of a Cessna 441 Conquest II in Renmark: 3 killed

Date & Time: May 30, 2017 at 1630 LT
Type of aircraft:
Operator:
Registration:
VH-XMJ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Renmark - Adelaide
MSN:
441-0113
YOM:
1980
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
14751
Captain / Total hours on type:
987.00
Copilot / Total flying hours:
5000
Copilot / Total hours on type:
1000
Aircraft flight hours:
13845
Circumstances:
On 30 May 2017, a Cessna 441 Conquest II (Cessna 441), registered VH-XMJ (XMJ) and operated by AE Charter, trading as Rossair, departed Adelaide Airport, South Australia for a return flight via Renmark Airport, South Australia. On board the aircraft were:
• an inductee pilot undergoing a proficiency check, flying from the front left control seat
• the chief pilot conducting the proficiency check, and under assessment for the company training and checking role for Cessna 441 aircraft, seated in the front right control seat
• a Civil Aviation Safety Authority flying operations inspector (FOI), observing and assessing the flight from the first passenger seat directly behind the left hand pilot seat.
Each pilot was qualified to operate the aircraft. There were two purposes for the flight. The primary purpose was for the FOI to observe the chief pilot conducting an operational proficiency check (OPC), for the purposes of issuing him with a check pilot approval on the company’s Cessna 441 aircraft. The second purpose was for the inductee pilot, who had worked for Rossair previously, to complete an OPC as part of his return to line operations for the company. The three pilots reportedly started their pre-flight briefing at around 1300 Central Standard Time. There were two parts of the briefing – the FOI’s briefing to the chief pilot, and the chief pilot’s briefing to the inductee pilot. As the FOI was not occupying a control seat, he was monitoring and assessing the performance of the chief pilot in the conduct of the OPC. There were two distinct exercises listed for the flight (see the section titled Check flight sequences). Flight exercise 1 detailed that the inductee pilot was to conduct an instrument departure from Adelaide Airport, holding pattern and single engine RNAV2 approach, go around and landing at Renmark Airport. Flight exercise 2 included a normal take-off from Renmark Airport, simulated engine failure after take-off, and a two engine instrument approach on return to Adelaide. The aircraft departed from Adelaide at 1524, climbed to an altitude about 17,000 ft above mean sea level, and was cleared by air traffic control (ATC) to track to waypoint RENWB, which was the commencement of the Renmark runway 073 RNAV-Z GNSS approach. The pilot of XMJ was then cleared to descend, and notified ATC that they intended to carry out airwork in the Renmark area. The pilot further advised that they would call ATC again on the completion of the airwork, or at the latest by 1615. No further transmissions from XMJ were recorded on the area frequency and the aircraft left surveillance coverage as it descended towards waypoint RENWB. The common traffic advisory frequency used for air-to-air communications in the vicinity of Renmark Airport recorded several further transmissions from XMJ as the crew conducted practice holding patterns, and a practice runway 07 RNAV GNSS approach. Voice analysis confirmed that the inductee pilot made the radio transmissions, as expected for the check flight. At the completion of the approach, the aircraft circled for the opposite runway and landed on runway 25, before backtracking and lining up for departure. That sequence varied from the planned exercise in that no single-engine go-around was conducted prior to landing at Renmark. At 1614, the common traffic advisory frequency recorded a transmission from the pilot of XMJ stating that they would shortly depart Renmark using runway 25 to conduct further airwork in the circuit area of the runway. A witness at the airport reported that, prior to the take-off roll, the aircraft was briefly held stationary in the lined-up position with the engines operating at significant power. The take-off roll was described as normal however, and the witness looked away before the aircraft became airborne. The aircraft maintained the runway heading until reaching a height of between 300-400 ft above the ground (see the section titled Recorded flight data). At that point the aircraft began veering to the right of the extended runway centreline (Figures 1 and 15). The aircraft continued to climb to about 600 ft above the ground (700 ft altitude), and held this height for about 30 seconds, followed by a descent to about 500 ft (Figures 2 and 13). The information ceased 5 seconds later, which was about 60 seconds after take-off. A distress beacon broadcast was received by the Joint Rescue Coordination Centre and passed on to ATC at 1625. Following an air and ground search the aircraft was located by a ground party at 1856 about 4 km west of Renmark Airport. All on board were fatally injured and the aircraft was destroyed.
Probable cause:
Findings:
From the evidence available, the following findings are made with respect to the collision with terrain involving Cessna 441, registered VH-XMJ, that occurred 4 km west of Renmark Airport,
South Australia on 30 May 2017. These findings should not be read as apportioning blame or liability to any particular organisation or individual.
Contributing factors:
• Following a planned simulated engine failure after take-off, the aircraft did not achieve the expected single engine climb performance, or target airspeed, over the final 30 seconds of the flight.
• The exercise was not discontinued when the aircraft’s single engine performance and airspeed were not attained. That was probably because the degraded aircraft performance, or the
associated risk, were not recognised by the pilots occupying the control seats.
• It is likely that the method of simulating the engine failure and pilot control inputs, together or in isolation, led to reduced single engine aircraft performance and asymmetric loss of control.
• Not following the recommended procedure for simulating an engine failure in the Cessna 441 pilot’s operating handbook meant that there was insufficient height to recover following the loss of control.
Other factors that increased risk:
• The Rossair training and checking manual procedure for a simulated engine failure in a turboprop aircraft was inappropriate and, if followed, increased the risk of asymmetric control loss.
• The flying operations inspector was not in a control seat and did not share a communication systems with the crew. Consequently, he had reduced ability to actively monitor the flight and
communicate any identified performance degradation.
• The inductee pilot had limited recent experience in the Cessna 441, and the chief pilot had an extended time period between being training and being tested as a check pilot on this aircraft. While both pilots performed the same exercise during a practice flight the week before, it is probable that these two factors led to a degradation in the skills required to safely perform and monitor the simulated engine failure exercise.
• The chief pilot and other key operational managers within Rossair were experiencing high levels of workload and pressure during the months leading up to the accident.
• In the 5 years leading up to the accident, the Civil Aviation Safety Authority had conducted numerous regulatory service tasks for the air transport operator and had regular communication with the operator’s chief pilots and other personnel. However, it had not conducted a systemic or detailed audit during that period, and its focus on a largely informal and often undocumented approach to oversight increased the risk that organisational or systemic issues associated with the operator would not be effectively identified and addressed.
Other findings:
• A lack of recorded data from this aircraft reduced the available evidence about handling aspects and cockpit communications. This limited the extent to which potential factors contributing to the accident could be analysed.
Final Report:

Crash of a Beechcraft B200 Super King Air in Moomba

Date & Time: Dec 13, 2016 at 1251 LT
Operator:
Registration:
VH-MVL
Flight Type:
Survivors:
Yes
Schedule:
Innamincka – Moomba
MSN:
BB-1333
YOM:
1989
Flight number:
FD209
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 13 December 2016, a Beech Aircraft Corporation B200, registered VH-MVL, conducted a medical services flight from Innamincka, South Australia (SA) to Moomba, SA. On board the aircraft were the pilot and two passengers. On arrival at Moomba at about 1250 Central Daylight-saving Time (CDT), the pilot configured the aircraft to join the circuit with flaps set to the approach setting and the propeller speed set at 1900 RPM. They positioned the aircraft at 150–160 kt airspeed to join the downwind leg of the circuit for runway 30, which is a right circuit. The pilot lowered the landing gear on the downwind circuit leg. They reduced power (set 600-700 foot-pounds torque on both engines) to start the final descent on late downwind abeam the runway 30 threshold, in accordance with their standard operating procedures. At about the turn point for the base leg of the circuit, the pilot observed the left engine fire warning activate. The pilot held the aircraft in the right base turn, but paused before conducting the engine fire checklist immediate actions in consideration of the fact that they were only a few minutes from landing and there were no secondary indications of an engine fire. After a momentary pause, the pilot decided to conduct the immediate actions. They retarded the left engine condition lever to the fuel shut-off position, paused again to consider if there was any other evidence of fire, then closed the firewall shutoff valve, activated the fire extinguisher and doubled the right engine power (about 1,400 foot-pounds torque). The pilot continued to fly the aircraft in a continuous turn for the base leg towards the final approach path, but noticed it was getting increasingly difficult to maintain the right turn. They checked the engine instruments and confirmed the left engine was shut down. They adjusted the aileron and rudder trim to assist controlling the aircraft in the right turn. The aircraft became more difficult to control as the right turn and descent continued and the pilot focused on maintaining bank angle, airspeed (fluctuating 100–115 kt) and rate of descent. Due to the pilot’s position in the left seat, they were initially unable to sight the runway when they started the right turn. The aircraft had flown through the extended runway centreline when the pilot sighted the runway to the right of the aircraft. The aircraft was low on the approach and the pilot realised that a sand dune between the aircraft and the runway was a potential obstacle. They increased the right engine power to climb power (2,230 foot-pounds torque) raised the landing gear and retracted the flap to reduce the rate of descent. The aircraft cleared the sand dune and the pilot lowered the landing gear and continued the approach to the runway from a position to the left of the runway centreline. The aircraft landed in the sand to the left of the runway threshold and after a short ground roll spun to the left and came to rest. There were no injuries and the aircraft was substantially damaged.
Probable cause:
From the evidence available, the following findings are made with respect to the collision with terrain involving Beech Aircraft Corporation B200, registered VH-MVL that occurred at Moomba Airport, South Australia on 13 December 2016. These findings should not be read as apportioning blame or liability to any particular organisation or individual.
Contributing factors:
- The operator did not modify the aircraft to include a more reliable engine fire detection system in accordance with the manufacturer’s service bulletin, and as subsequently recommended by the Civil Aviation Safety Authority’s airworthiness bulletin. The incorporation of the manufacturer’s modification would have reduced the risk of a false engine fire warning.
- During the approach phase of flight, the pilot shutdown the left engine in response to observing a fire warning, but omitted to feather the propeller. The additional drag caused by the windmilling propeller, combined with the aircraft configuration set for landing while in a right turn, required more thrust than available for the approach.

Other factors that increased risk:
- The advice from the Civil Aviation Safety Authority to the operator, that differences training was acceptable, resulted in the pilot not receiving the operator’s published B200 syllabus of training. The omission of basic handling training on a new aircraft type could result in a pilot not developing the required skilled behaviour to handle the aircraft either near to or in a loss of control situation.

Other findings:
- The pilot met the standard required by the operator in their cyclic training and proficiency program and no knowledge deficiencies associated with handling engine fire warnings were identified.
Final Report:

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 Beechcraft 200C Super King Air in Mount Gambier: 1 killed

Date & Time: Dec 10, 2001 at 2336 LT
Operator:
Registration:
VH-FMN
Flight Type:
Survivors:
Yes
Schedule:
Adelaide - Mount Gambier - Adelaide
MSN:
BL-47
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
13730
Captain / Total hours on type:
372.00
Aircraft flight hours:
10907
Circumstances:
The Raytheon Beech 200C Super King Air, registered VH-FMN, departed Adelaide at 2240 hours Central Summer Time (CSuT) under the Instrument Flight Rules for Mount Gambier, South Australia. The ambulance aircraft was being positioned from Adelaide to Mount Gambier to transport a patient from Mount Gambier to Sydney for a medical procedure, for which time constraints applied. The pilot intended to refuel the aircraft at Mount Gambier. The planned flight time to Mount Gambier was 52 minutes. On board were the pilot and one medical crewmember. The medical crewmember was seated in a rear-facing seat behind the pilot. On departure from Adelaide, the pilot climbed the aircraft to an altitude of 21,000 ft above mean sea level for the flight to Mount Gambier. At approximately 2308, the pilot requested and received from Air Traffic Services (ATS) the latest weather report for Mount Gambier aerodrome, including the altimeter sub-scale pressure reading of 1012 millibars. At approximately 2312, the pilot commenced descent to Mount Gambier. At approximately 2324, the aircraft descended through about 8,200 ft and below ATS radar coverage. At approximately 2326, the pilot made a radio transmission on the Mount Gambier Mandatory Broadcast Zone (MBZ) frequency advising that the aircraft was 26 NM north, inbound, had left 5,000 ft on descent and was estimating the Mount Gambier circuit at 2335. At about 2327, the pilot started a series of radio transmissions to activate the Mount Gambier aerodrome pilot activated lighting (PAL).2 At approximately 2329, the pilot made a radio transmission advising that the aircraft was 19 NM north and maintaining 4,000 ft. About 3 minutes later, he made another series of transmissions to activate the Mount Gambier PAL. At approximately 2333, the pilot reported to ATS that he was in the circuit at Mount Gambier and would report after landing. Witnesses located in the vicinity of the aircraft’s flight path reported that the aircraft was flying lower than normal for aircraft arriving from the northwest. At approximately 2336 (56 minutes after departure), the aircraft impacted the ground at a position 3.1 NM from the threshold of runway (RWY) 18. The pilot sustained fatal injuries and the medical crewmember sustained serious injuries, but egressed unaided.
Probable cause:
The following factors were identified:
- Dark night conditions existed in the area surrounding the approach path of the aircraft.
- For reasons which could not be ascertained, the pilot did not comply with the requirements of the published instrument approach procedures.
- The aircraft was flown at an altitude insufficient to ensure terrain clearance.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain off Whyalla: 8 killed

Date & Time: May 31, 2000 at 1905 LT
Operator:
Registration:
VH-MZK
Survivors:
No
Schedule:
Adelaide - Whyalla
MSN:
31-8152180
YOM:
1981
Flight number:
WW904
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
2211
Captain / Total hours on type:
113.00
Aircraft flight hours:
11837
Circumstances:
On the evening of 31 May 2000, Piper Chieftain, VH-MZK, was being operated by Whyalla Airlines as Flight WW904 on a regular public transport service from Adelaide to Whyalla, South Australia. One pilot and seven passengers were on board. The aircraft departed at 1823 central Standard Time (CST) and, after being radar vectored a short distance to the west of Adelaide for traffic separation purposes, the pilot was cleared to track direct to Whyalla at 6,000 ft. A significant proportion of the track from Adelaide to Whyalla passed over the waters of Gulf St Vincent and Spencer Gulf. The entire flight was conducted in darkness. The aircraft reached 6,000 ft and proceeded apparently normally at that altitude on the direct track to Whyalla. At 1856 CST, the pilot reported to Adelaide Flight Information Service (FIS) that the aircraft was 35 NM south-south-east of Whyalla, commencing descent from 6,000 ft. Five minutes later the pilot transmitted a MAYDAY report to FIS. He indicated that both engines of the aircraft had failed, that there were eight persons on board and that he was going to have to ditch the aircraft, but was trying to reach Whyalla. He requested that assistance be arranged and that his company be advised of the situation. About three minutes later, the pilot reported his position as about 15 NM off the coast from Whyalla. FIS advised the pilot to communicate through another aircraft that was in the area if he lost contact with FIS. The pilot’s acknowledgment was the last transmission heard from the aircraft. A few minutes later, the crew of another aircraft heard an emergency locater transmitter (ELT) signal for 10–20 seconds. Early the following morning, a search and rescue operation located two deceased persons and a small amount of wreckage in Spencer Gulf, near the last reported position of the aircraft. The aircraft, together with five deceased occupants, was located several days later on the sea–bed. One passenger remained missing.
Probable cause:
Engine operating practices:
• High power piston engine operating practices of leaning at climb power, and leaning to near ‘best economy’ during cruise, may result in the formation of deposits on cylinder and piston surfaces that could cause preignition.
• The engine operating practices of Whyalla Airlines included leaning at climb power and leaning to near ‘best economy’ during cruise.
Left engine:
The factors that resulted in the failure of the left engine were:
• The accumulation of lead oxybromide compounds on the crowns of pistons and cylinder head surfaces.
• Deposit induced preignition resulted in the increase of combustion chamber pressures and increased loading on connecting rod bearings.
• The connecting rod big end bearing insert retention forces were reduced by the inclusion, during engine assembly, of a copper–based anti-galling compound.
• The combination of increased bearing loads and decreased bearing insert retention forces resulted in the movement, deformation and subsequent destruction of the bearing inserts.
• Contact between the edge of the damaged Number 6 connecting rod bearing insert and the Number 6 crankshaft journal fillet resulted in localised heating and consequent cracking of the nitrided surface zone.
• Fatigue cracking in the Number 6 journal initiated at the site of a thermal crack and propagated over a period of approximately 50 flights.
• Disconnection of the two sections of the journal following the completion of fatigue cracking in the journal and the fracture of the Number 6 connecting rod big end housing most likely resulted in the sudden stoppage of the left engine.
Right engine:
The factors that were involved in the damage/malfunction of the right engine following the left engine malfunction/failure were:
• Detonation of combustion end-gas.
• Disruption of the gas boundary layers on the piston crowns and cylinder head surface increasing the rate of heat transfer to these components.
• Increased heat transfer to the Number 6 piston and cylinder head resulted in localised melting.
• The melting of the Number 6 piston allowed combustion gases to bypass the piston rings.
The flight:
The factors that contributed to the flight outcome were:
• The pilot responded to the failed left engine by increasing power to the right engine.
• The resultant change in operating conditions of the right engine led to loss of power from, and erratic operation of, that engine.
• The pilot was forced to ditch the aircraft into a 0.5m to 1m swell in the waters of Spencer Gulf, in dark, moonless conditions.
• The absence of upper body restraints, and life jackets or flotation devices, reduced the chances of survival of the occupants.
• The Emergency Locator Transmitter functioned briefly on impact but ceased operating when the aircraft sank.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Innemincka

Date & Time: May 29, 1993 at 1258 LT
Registration:
VH-LIC
Flight Phase:
Survivors:
Yes
Schedule:
Port Augusta – Innamincka – Durham Downs
MSN:
31-7652173
YOM:
1976
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2930
Captain / Total hours on type:
966.00
Circumstances:
The pilot was conducting a scheduled passenger service flight from Port Augusta with a stop at Innamincka. A commercial pilot, travelling as a non-paying passenger, occupied the co-pilot's seat to observe the operation. Two additional passengers were on board the aircraft for the entire flight. After landing at Innamincka, the aircraft was refuelled by the pilot in command and the oil levels of both engines were checked by the observer, who experienced difficulty securing the combination oil filler cap-dipsticks. He asked the pilot for instructions and, although some advice was given, the pilot did not check the security of the dipsticks. Take-off was commenced towards the north into a 10-15 knot wind with a surface temperature of about 20 degrees C. Shortly after lift-off, at the first power reduction, the observer in the co-pilot's seat advised that there was oil seeping back along the cowl from the right side oil filler hatch. The pilot reported that he increased power to both engines but believed there was no response from the right. He began an immediate left turn to complete a circuit and attempted to secure the right engine and feather the propeller. The aircraft then began a roll to the right, the nose dropped and the aircraft impacted the ground. As the aircraft rolled right and the nose dropped, the pilot reported that he had secured the left engine and feathered the propeller. The observer in the co-pilot seat reported hearing a continuous stall warning horn as the right wing began to drop. All occupants, although injured, were able to vacate the aircraft through the main cabin door. The pilot provided assistance to the passengers and then returned to the airport to summon help.
Probable cause:
Examination of the wreckage revealed that the aircraft impacted the ground in a nose down, right wing low attitude while turning right. The landing gear collapsed due to impact forces and the right wing separated. Deceleration and impact forces were severe. The right propeller was found in the fine pitch range with no damage to the uppermost blade and the other two bent backwards. The right engine oil filler cap-dipstick was found to be correctly installed in the oil filler neck. There was a pattern of engine oil over the rear of the engine and inside the cowl originating from the oil filler neck. The left engine was partially torn from its mountings and displaced about 90 degrees to the right. Its propeller was in the fully feathered position. The oil filler cap-dipstick was on the ground adjacent to the engine. An oil spill pattern similar to that on the right engine was evident.
Significant Factors:
- The pilot-in-command reacted inappropriately to a perceived engine problem shortly after take-off.
- Control of the aircraft was lost at a height insufficient to effect a recovery.
Final Report:

Crash of a GAF Nomad N.24A at Edinburgh AFB: 1 killed

Date & Time: Mar 12, 1990
Type of aircraft:
Operator:
Registration:
A18-401
Flight Type:
Survivors:
No
Schedule:
Edinburgh AFB - Edinburgh AFB
MSN:
128
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
300
Circumstances:
The pilot, sole on board, was completing a local training flight at Edinburgh AFB. On approach, the tail separated and the aircraft dove into the ground and crashed near the airfield. The aircraft was destroyed and the pilot F/Lt Glenn Kemshall Donovan was killed.
Probable cause:
After being manufactured in 1982, the airplane was used by GAF (renamed Aerospace Technologies of Australia - ASTA in 1987) for testing. Amongst others, service records indicated 177 hours of single engine ground running. This meant that the airplane was subjected to many high frequency asymmetric cycles. Cracks initiated and grew predominately due to torsional loading. Upon delivery to the RAAF, the airplane was inspected but this failed to detect significant cracking. The tailplane centre section failed in flight, 19 hours after the inspection.

Crash of a De Havilland DHC-2 Beaver in Orroroo: 1 killed

Date & Time: Sep 20, 1989 at 1222 LT
Type of aircraft:
Operator:
Registration:
VH-IDD
Flight Phase:
Survivors:
No
Schedule:
Orroroo - Orroroo
MSN:
1532
YOM:
1963
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The aircraft had been delayed in servicing and repair and had only been released six weeks prior to the accident. This delay had caused the operator/pilot to fall behind in his commitments and, according to some witnesses, caused him to worry about the situation. On the day of the accident, the pilot had just completed spraying a 243 hectare paddock and had landed to reload. After take-off for the new task, the pilot was seen to make an aerial inspection of the paddock before entering the first swath run. At the end of this run, the aircraft collided with a Single Wire Earth Return (SWER) powerline and crashed. It was later shown that the aircraft was in a bank to the right of about 18 degrees. The SWER line ran across one end of the paddock at an angle and on the crop side of a windmill just inside the fence which bordered the road. The line contacted the right maingear and outboard sprayboom attachment struts on the right wing. The wire broke after impact but the aircraft hit the ground heavily on the right main gear. The gear detached from the aircraft, the propeller struck the ground and the aircraft slewed around as it came to rest after some 27 metres of ground travel. The front half of the aircraft was destroyed by fire which broke out almost immediately the aircraft stopped. The pilot, sole on board, was killed.
Probable cause:
Two main hypothesis were proposed. One was that the pilot was distracted from a less than demanding task by business worries. The other was that the pilot had perceived that the SWER line was on the right of the windmill and outside the fence and therefore did not present an obstacle to his procedure turn. Neither hypothesis could be substantiated. An additional concern was the fact that the pilot had died from impact injuries in an accident that, prima facie, was survivable. Concern focused on whether the pilot had secured his harness properly and/or whether the inertia reel had failed. Detailed engineering inspection of the inertia reel by the Bureau and the manufacturer could not positively determine the mode of operation of the inertia reel. However, the post mortem report showed that the nature of injuries to the pilot, while sufficient to cause death prior to the fire, were such as to indicate that the inertia reel had probably not failed. The pilot did not see the powerline in time to avoid a collision.
Final Report:

Crash of a Douglas C-47B-35-DK at Edinburgh AFB

Date & Time: Oct 17, 1986
Operator:
Registration:
A65-114
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
16712/33460
YOM:
1945
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Just after liftoff, both engines failed simultaneously. The aircraft stalled and hit the runway surface. On impact, the left main gear collapsed and the aircraft came to rest. There were no casualties but the aircraft was considered as damaged beyond repair and later transferred to the South Australian Aviation Museum in Port Adelaide.
Probable cause:
Double engine failure for unknown reasons.

Crash of a Partenavia P.68B Victor near Adelaide: 2 killed

Date & Time: Nov 9, 1985
Type of aircraft:
Operator:
Registration:
VH-YIH
Flight Phase:
Flight Type:
Survivors:
No
MSN:
134
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Crashed in unknown circumstances in an open field located about 80 km south of Adelaide and burnt. Both occupants were killed.