Country
code

Victoria

Crash of a Beechcraft B200 Super King Air in Melbourne: 5 killed

Date & Time: Feb 21, 2017 at 0858 LT
Registration:
VH-ZCR
Flight Phase:
Survivors:
No
Site:
Schedule:
Melbourne - King Island
MSN:
BB-1544
YOM:
1996
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
7681
Captain / Total hours on type:
2400.00
Aircraft flight hours:
6997
Circumstances:
On 21 February 2017, the pilot of a Beechcraft B200 King Air aircraft, registered VH-ZCR (ZCR), and operated by Corporate & Leisure Aviation, was conducting a charter passenger flight from Essendon Airport, Victoria to King Island, Tasmania. There were four passengers on board. ZCR had been removed from a hangar and parked on the apron the previous afternoon in preparation for the flight. The pilot was first seen on the apron at about 0706 Eastern Daylight-saving Time. Closed-circuit television recorded the pilot walking around the aircraft and entering the cabin, consistent with conducting a pre-flight inspection of the aircraft. At about 0712, the pilot entered ZCR’s maintenance provider’s hangar. A member of staff working in the hangar reported that the pilot had a conversation with him that was unrelated to the accident flight. The pilot exited the hangar about 0715 and had a conversation with another member of staff who reported that their conversation was also unrelated to the accident flight. The pilot then returned to ZCR, and over the next 4 minutes he was observed walking around the aircraft. The pilot went into the cabin and re-appeared with an undistinguishable item. The pilot then walked around the aircraft one more time before re-entering the cabin and closing the air stair cabin door. At about 0729, the right engine was started and, shortly after, the left engine was started. Airservices Australia (Airservices) audio recordings indicated that, at 0736, the pilot requested a clearance from Essendon air traffic control (ATC) to reposition ZCR to the southern end of the passenger terminal. ATC provided the clearance and the pilot commenced taxiing to the terminal. At the terminal, ZCR was refueled and the pilot was observed on CCTV to walk around the aircraft, stopping at the left and right engines before entering the cabin. The pilot was then observed to leave the aircraft and wait for the passengers at the terminal. The passengers arrived at the terminal at 0841 and were escorted by the pilot directly to the aircraft. At 0849, the left engine was started and, shortly after, the right engine was started. At 0853, the pilot requested a taxi clearance for King Island, with five persons onboard, under the instrument flight rules. ATC instructed the pilot to taxi to holding point 'TANGO' for runway 17, and provided an airways clearance for the aircraft to King Island with a visual departure. The pilot read back the clearance. Airservices Automatic Dependent Surveillance Broadcast (ADS-B) data (refer to section titled Air traffic services information - Automatic Dependent Surveillance Broadcast data) indicated that, at 0854, ZCR was taxied from the terminal directly to the holding point. The aircraft did not enter the designated engine run-up bay positioned near holding point TANGO. At 0855, while holding at TANGO, the pilot requested a transponder code. The controller replied that he did not have one to issue yet. Two minutes later the pilot contacted ATC and stated that he was ready and waiting for a transponder code. The controller responded with the transponder code and a clearance to lineup on runway 17. At 0858, ATC cleared ZCR for take-off on runway 17 with departure instructions to turn right onto a heading of 200°. The pilot read back the instruction and commenced the takeoff roll. The aircraft’s take-off roll along runway 17 was longer than expected. Witnesses familiar with the aircraft type observed a noticeable yaw to the left after the aircraft became airborne. The aircraft entered a relatively shallow climb and the landing gear remained down. The shallow climb was followed by a substantial left sideslip, while maintaining a roll attitude of less than 10° to the left. Airservices ADS-B data indicated the aircraft reached a maximum height of approximately 160 ft above ground level while tracking in an arc to the left of the runway centreline. The aircraft’s track began diverging to the left of the runway centreline before rotation and the divergence increased as the flight progressed. Following the sustained left sideslip, the aircraft began to descend and at 0858:48 the pilot transmitted on the Essendon Tower frequency repeating the word ‘MAYDAY’ seven times in rapid succession. Approximately 10 seconds after the aircraft became airborne, and 2 seconds after the transmission was completed, the aircraft collided with the roof of a building in the Essendon Airport Bulla Road Precinct - Retail Outlet Centre (outlet centre), coming to rest in a loading area at the rear of the building. CCTV footage from a camera positioned at the rear of the building showed the final part of the accident sequence with post-impact fire evident; about 2 minutes later, first responders arrived onsite. At about 0905 and 0908 respectively, Victoria Police and the Metropolitan Fire Brigade arrived. The pilot and passengers were fatally injured and the aircraft was destroyed. There was significant structural, fire and water damage to the building. Additionally, two people on the ground received minor injuries and a number of parked vehicles were damaged.
Probable cause:
From the evidence available, the following findings are made with respect to the collision with terrain involving Beechcraft B200 King Air, registered VH-ZCR that occurred at Essendon Airport, Victoria on 21 February 2017. These findings should not be read as apportioning blame or liability to any particular organisation or individual.

Contributing factors:
- The aircraft's rudder trim was likely in the full nose-left position at the commencement of the take-off.
- The aircraft's full nose-left rudder trim setting was not detected by the pilot prior to take-off.
- Following a longer than expected ground roll, the pilot took-off with full left rudder trim selected. This configuration adversely affected the aircraft's climb performance and controllability, resulting in a collision with terrain.

Other factors that increased risk:
- The flight check system approval process did not identify that the incorrect checklist was nominated in the operator’s procedures manual and it did not ensure the required checks, related to the use of the cockpit voice recorder, were incorporated.
- The aircraft's cockpit voice recorder did not record the accident flight, resulting in a valuable source of safety related information not being available.
- The aircraft's maximum take-off weight was likely exceeded by about 240 kilograms.
- Two of the four buildings within the Bulla Road Precinct Retail Outlet Centre exceeded the obstacle limitation surface (OLS) for Essendon Airport, however, the OLS for the departure runway was not infringed and VH-ZCR did not collide with those buildings.

Other findings:
- The presence of the building struck by the aircraft was unlikely to have increased the severity of the outcome of this accident.
- Both of the aircraft’s engines were likely to have been producing high power at impact.
Final Report:

Crash of a Rockwell Shrike Commander 500S in Clonbinane: 2 killed

Date & Time: Jul 31, 2007 at 2000 LT
Operator:
Registration:
VH-YJB
Flight Phase:
Survivors:
No
Site:
Schedule:
Melbourne – Shepparton
MSN:
500-3299
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2342
Captain / Total hours on type:
970.00
Aircraft flight hours:
4558
Circumstances:
At 1946 Eastern Standard Time on 31 July 2007, a Rockwell International Aero Commander 500S, registered VH-YJB (YJB), departed Essendon Airport, Vic. on a business flight to Shepparton that was conducted at night under the instrument flight rules (IFR). On board were the pilot and one passenger. At 1958, while in the cruise at 7,000 ft above mean sea level (AMSL) in Class C controlled airspace, radar and radio contact with the aircraft was lost simultaneously by air traffic control when it was about 25 NM (46 km) north-north-east of Essendon. The air traffic controller declared a distress phase after a number of unsuccessful attempts to contact the pilot. At 2003, the Operations Director at Melbourne Centre declared the aircraft as probably lost and advised AusSAR. A search was commenced using a helicopter and an aeroplane in addition to ground search parties. No emergency locator transmitter signal was reported. At 2147, aircraft wreckage was located by a searching aircraft in timbered ranges near Clonbinane, approximately 50 km north of Melbourne. At about 2200, a ground search party confirmed that the wreckage was that of YJB and that there were no survivors. The flight was arranged to take the company owner, who was also a licensed aircraft maintenance engineer (LAME), to Shepparton to replace an unserviceable starter motor in another of the operator‟s aircraft. The pilot, who had landed at Essendon at 1915 from a previous flight in another of the operator‟s aircraft, was tasked to fly the owner to Shepparton. The pilot transferred to YJB, which had previously been prepared for flight by another company pilot. At 1938, while taxiing for takeoff, the pilot advised the aerodrome controller of the intention to conduct the IFR flight, adding, „…and request a big favour for a submission of a flight plan, with an urgent departure Essendon [to] Shepparton [and] return‟. The aerodrome controller did not have the facilities for processing flight notifications and sought the assistance of a controller in the Melbourne air traffic control centre. There were no eyewitnesses to the accident. Residents living in the vicinity of the accident site were inside their homes and reported difficulty hearing anything above the noise made by the wind and the foliage being blown about. One of the residents reported hearing a brief, loud engine noise. Another resident thought the noise was that of a noisy vehicle on the road. The noise was described as being constant, „…not spluttering or misfiring‟ and lasted for only a few seconds. Some of those residents near the accident site reported hearing and feeling an impact only moments after the engine noise ceased. The aircraft was seriously damaged by excessive in-flight aerodynamic forces and impact with the terrain. The vegetation in the immediate vicinity of the main aircraft wreckage was slightly damaged as the aircraft descended, nearly vertically, through the trees. The pilot and passenger were fatally injured.
Probable cause:
Structural failure and damage:
From the detailed examination and study of the aircraft wreckage undertaken by ATSB investigation staff, it was evident that all principal structural failures had occurred under gross overstress conditions i.e. stresses significantly in excess of the physical strength of the respective structures. The examination found no evidence of pre-existing cracking, damage or material degradation that could have appreciably reduced the strength of the failed sections, nor was there any indication that the original manufacture, maintenance or repair processes carried out on the aircraft were in any way contributory to the failures sustained.

Breakup sequence:
From the localised deformation associated with the spar failures, it was evident that the aircraft had sustained a large negative (downward) loading on the wing structure. That downward load resulted in the localised bending failure of the wing around the station 145 position (145” outboard of the aircraft centreline). The symmetry of both wing failures and the absence of axial twisting within the fuselage section suggested that the load encountered was sudden and well in excess of the ultimate strength of the wing structure. Based upon the witness marks on both wing under-surfaces and the crushing and paint transfer along the leading edges of the horizontal stabilisers, it was concluded that after separating from the inboard structure, both wings had moved aft in an axial twisting and rotating fashion; simultaneously impacting the leading edges of both horizontal tailplanes. Forces imparted into the empennage structure from that impact subsequently produced the rearward separation of the complete empennage from the fuselage. The loss of the left engine nacelle fairing was likely brought about through an impact with a section of wing leading edge as it rotated under and to the rear. The damage sustained by all of the aircraft‟s control surfaces was consistent with failure and separation from their respective primary structure under overstress conditions associated with the breakup of the aircraft. There was no evidence of cyclic or oscillatory movement of the surfaces before separation that might have suggested the contribution of an aerodynamic flutter effects.

Findings
The following statements are a summary of the verified findings made during the progress of the aircraft wreckage structural examination and analysis:
- All principal failures within the aircraft wings, tailplanes and empennage had occurred as a result of exposure to gross overstress conditions.
- The damage sustained by the aircraft wreckage was consistent with the aircraft having sustained multiple in-flight structural failures.
- The damage sustained by the aircraft wreckage was consistent with the structural failure sequence being initiated by the symmetric, downward bending failure of both wing sections, outboard of the engine nacelles.
- Breakup and separation of the empennage was consistent with having been initiated by impact of the separated outboard wings with the leading edges of the horizontal stabilisers.
- There was no evidence of material or manufacturing abnormalities within the aircraft structure that could be implicated in the failures and breakup sustained.
- There was no evidence of service-related degradation mechanisms (such as corrosion, fatigue cracking or environmental cracking) having affected the aircraft structure in the areas of failure.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Mount Hotham: 3 killed

Date & Time: Jul 8, 2005 at 1725 LT
Operator:
Registration:
VH-OAO
Survivors:
No
Schedule:
Melbourne - Mount Hotham
MSN:
31-8252021
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
4770
Captain / Total hours on type:
1269.00
Aircraft flight hours:
9137
Circumstances:
On 8 July 2005, the pilot of a Piper PA-31-350 Navajo Chieftain, registered VH-OAO, submitted a visual flight rules (VFR) flight plan for a charter flight from Essendon Airport to Mount Hotham, Victoria. On board the aircraft were the pilot and two passengers. At the time, the weather conditions in the area of Mount Hotham were extreme. While taxiing at Essendon, the pilot requested and was granted an amended airways clearance to Wangaratta, due to the adverse weather conditions at Mount Hotham. The aircraft departed Essendon at 1629 Eastern Standard Time. At 1647 the pilot changed his destination to Mount Hotham. At 1648, the pilot contacted Flightwatch and requested that the operator telephone the Mount Hotham Airport and advise an anticipated arrival time of approximately 1719. The airport manager, who was also an accredited meteorological observer, told the Flightwatch operator that in the existing weather conditions the aircraft would be unable to land. At 1714, the pilot reported to air traffic control that the aircraft was overhead Mount Hotham and requested a change of flight category from VFR to instrument flight rules (IFR) in order to conduct a Runway 29 Area Navigation, Global Navigation Satellite System (RWY 29 RNAV GNSS) approach via the initial approach fix HOTEA. At 1725 the pilot broadcast on the Mount Hotham Mandatory Broadcast Zone frequency that the aircraft was on final approach for RWY 29 and requested that the runway lights be switched on. No further transmissions were received from the aircraft. The wreckage of the aircraft was located by helicopter at 1030 on 11 July. The aircraft had flown into trees in a level attitude, slightly banked to the right. Initial impact with the ridge was at about 200 ft below the elevation of the Mount Hotham aerodrome. The aircraft had broken into several large sections and an intense fire had consumed most of the cabin. The occupants were fatally injured.
Probable cause:
Findings:
• There were no indications prior to, or during the flight, of problems with any aircraft systems that may have contributed to the circumstances of the occurrence.
• The pilot continued flight into forecast and known icing conditions in an aircraft not approved for flight in icing conditions.
• The global navigation satellite constellation was operating normally.
• The pilot did not comply with the requirements of the published instrument approach procedure.
• The pilot was known, by his Chief Pilot and others, to adopt non-standard approach procedures to establish his aircraft clear of cloud when adverse weather conditions existed at Mount Hotham.
• The pilot may have been experiencing self-imposed and external pressures to attempt a landing at Mount Hotham.
• Terrain features would have been difficult to identify due to a heavy layer of snow, poor visibility, low cloud, continuing heavy snowfall, drizzle, sleet and approaching end of daylight.
• The pilot’s attitude, operational and compliance practices had been of concern to some Airservices’ staff.
• The operator’s operational and compliance history was recorded by CASA as being of concern, and as a result CASA staff continued to monitor the operator. However, formal surveillance of the operator in the preceding two years had not identified any significant operational issues.
Significant factors:
• The weather conditions at the time of the occurrence were extreme.
• The extreme weather conditions were conducive to visual illusions associated with a flat light phenomenon.
• The pilot did not comply with the requirements of flight under either the instrument flight rules (IFR) or the visual flight rules (VFR).
• The pilot did not comply with the requirements of the published instrument approach procedure and flew the aircraft at an altitude that did not ensure terrain clearance.
• The aircraft accident was consistent with controlled flight into terrain.
Final Report:

Crash of a Piper PA-31T Cheyenne II near Benalla: 6 killed

Date & Time: Jul 28, 2004 at 1048 LT
Type of aircraft:
Registration:
VH-TNP
Survivors:
No
Site:
Schedule:
Bankstown – Benalla
MSN:
31-7920026
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
14017
Captain / Total hours on type:
3100.00
Aircraft flight hours:
5496
Circumstances:
At 0906 Eastern Standard Time on 28 July 2004, a Piper Aircraft Corporation PA31T Cheyenne aircraft, registered VH-TNP, with one pilot and five passengers, departed Bankstown, New South Wales on a private, instrument flight rules (IFR) flight to Benalla, Victoria. Instrument meteorological conditions at the destination necessitated an instrument approach and the pilot reported commencing a Global Positioning System (GPS) non-precision approach (NPA) to Benalla. When the pilot had not reported landing at Benalla as expected, a search for the aircraft was commenced. Late that afternoon the crew of a search helicopter located the burning wreckage on the eastern slope of a tree covered ridge, approximately 34 km southeast of Benalla. All occupants were fatally injured and the aircraft was destroyed by impact forces and a post-impact fire.
Probable cause:
Significant factors:
1. The pilot was not aware that the aircraft had diverged from the intended track.
2. The route flown did not pass over any ground-based navigation aids.
3. The sector controller did not advise the pilot of the divergence from the cleared track.
4. The sector controller twice cancelled the route adherence monitoring alerts without confirming the pilot’s tracking intentions.
5. Cloud precluded the pilot from detecting, by external visual cues, that the aircraft was not flying the intended track.
6. The pilot commenced the approach at an incorrect location.
7. The aircraft’s radio altimeter did not provide the pilot with an adequate defence to avoid collision with terrain.
8. The aircraft was not fitted with a terrain awareness warning system (TAWS).
Final Report:

Crash of a Cessna 208 Caravan I in Nagambie: 1 killed

Date & Time: Apr 29, 2001 at 1312 LT
Type of aircraft:
Operator:
Registration:
VH-MMV
Flight Phase:
Survivors:
Yes
Schedule:
Nagambie - Nagambie
MSN:
208-0003
YOM:
1985
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4000
Captain / Total hours on type:
700.00
Aircraft flight hours:
8576
Circumstances:
Four parachutists were practising as a team for a skydiving competition. They had completed seven parachute descents prior to the accident flight. Each descent had been video recorded by a cameraman using a helmet-mounted camera. The parachutists used a Cessna Aircraft Company Caravan aircraft. That aircraft was climbed to 14,000 ft with the team of four parachutists, their cameraman, six other parachutists and the pilot. At the drop altitude, the team members carried out their ‘pin check’ in which each parachutist’s equipment was checked to ensure that the release pins for the main and reserve parachutes were correctly positioned. Approaching overhead the drop zone, a roller blind, which covered the exit doorway on the left side of the aircraft, and minimised windblast during the climb, was raised. The cameraman positioned himself on the step outside and to the rear of the exit doorway. The first three members of the team positioned themselves in the exit doorway. The team member nearest to the front of the aircraft faced out and the next two members faced into the aircraft. The team member in the middle grasped the jumpsuits of the adjacent parachutists. The fourth member was inside the aircraft facing the exit. As the team exited the aircraft, the middle parachutist’s reserve parachute’s pilot chute deployed. Due to the bent over position of that parachutist, the action of the ejector spring in the pilot chute pushed the chute upwards and over the horizontal stabiliser of the aircraft, pulling the reserve canopy with it. The parachutist passed below the horizontal stabiliser resulting in the reserve parachute risers and lines tangling around the left elevator and horizontal stabiliser. Eleven seconds later, the empennage separated from the aircraft and the left elevator and the parachutist separated from the empennage. The parachutist descended to the ground with the reserve and main parachutes entangled and landed 800 metres west of the drop zone landing strip. A short section of the elevator was tangled in the parachute lines. The parachutist’s rate of descent was estimated to be 3.6 times greater than that for an average parachutist under canopy. Immediately after the empennage separated, the aircraft entered a steep, nose-down spiral descent. The pilot instructed the remaining parachutists to abandon the aircraft. The last one left the aircraft before it descended through 9,000 ft. The pilot transmitted a mayday call, shutdown the engine and left his seat. On reaching the rear of the cabin, he found that the roller blind had closed, preventing him from leaving the aircraft. After several attempts, the pilot raised the blind sufficiently to allow him to exit the aircraft, and at an altitude of approximately 1,000 ft above ground level, he deployed his parachute and landed safely. The aircraft, minus the empennage, descended almost vertically and crashed on the drop zone landing strip. It was destroyed by impact forces and the post-impact fire. The empennage, in several pieces, landed 600 metres west of the landing strip. A Country Fire Authority fire vehicle arrived at the accident site within two minutes of the accident and extinguished the fire. The parachutist that had been entangled was fatally injured. The injuries sustained when entangled on the horizontal stabiliser made the parachutist incapable of operating the main parachute. The other parachutists and the pilot were uninjured.
Probable cause:
The following factors were identified:
- The parachutist’s reserve parachute deployed prematurely, probably as a result of the parachute container coming into contact with the aircraft doorframe/handrail.
- The reserve parachute risers and lines tangled around the horizontal stabiliser and elevator.
- The reserve canopy partially filled, applying to the aircraft empennage a load that exceeded its design limits.
- The empennage separated from the aircraft and the elevator separated from the empennage, releasing the parachutist and sending the aircraft out of control.
Final Report:

Crash of a Gippsland GA8 Airvan in Latrobe Valley

Date & Time: Feb 7, 1996 at 1845 LT
Type of aircraft:
Operator:
Registration:
VH-PTR
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Latrobe Valley - Latrobe Valley
MSN:
GA8-0001
YOM:
1995
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6500
Captain / Total hours on type:
100.00
Circumstances:
The prototype GA-8 aircraft was undertaking test flying from the manufacturer's facility at the Latrobe Valley airfield. The test flying was scheduled by the designer under the provisions of a permit to fly approved by the Civil Aviation Safety Authority. For a series of spin tests the aircraft was fitted with fixed and jettisonable ballast, a jettisonable pilot's door, and a tail mounted anti-spin parachute attached to a long lanyard. On this flight the aircraft was set up at 9,000 feet above ground level with full power, flaps fully down, an extreme aft centre of gravity (C of G) and maximum all up weight. The test pilot, who was the only occupant, applied full left rudder and full right aileron to initiate a spin. After the aircraft entered a spin to the left the pilot applied standard control inputs to effect a recovery to normal flight. The aircraft did not respond and at 6,500 feet, 13 seconds after the spin commenced, the pilot jettisoned the ballast and deployed the anti-spin parachute. The aircraft still did not respond and at about 32 seconds into the spin, at 5,200 feet, the pilot initiated release of the jettisonable door, released his harness, baled out, and was clear of the aircraft as it passed through 3,600 feet. At 1,800 feet the aircraft was observed to stop spinning. Fifty seconds after the commencement of the spin, the aircraft dived into the ground and was destroyed. The pilot sustained minor injuries during his landing.
Probable cause:
This was a prototype aircraft and some deficiencies and/or problems during testing are to be expected. With this particular aircraft the fact that the inadequate rudder hinge moment was masked throughout flight testing meant that the inadequate rudder performance during critical spin recovery was not clearly detected until it combined with other factors to become critical. These other factors included an ineffective anti-spin parachute, extensive blanking of the fin and rudder, and flight at the extremes of the weight and C of G envelope. It is not known what , if any, effect the previous rerigging of the elevator controls had on this flight.
The following factors were reported:
1. The rudder and fin effectiveness was inadequate for the spin test being undertaken.
2. The anti-spin protection systems were ineffective.
3. The aircraft was not able to be recovered from an intentional spin.
Final Report:

Crash of a De Havilland DHC-2 Beaver near Yea

Date & Time: Mar 16, 1995 at 1400 LT
Type of aircraft:
Operator:
Registration:
VH-IDB
Flight Phase:
Survivors:
Yes
Schedule:
Yea - Yea
MSN:
883
YOM:
1956
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1468
Captain / Total hours on type:
244.00
Circumstances:
The pilot reported that the flight departed from an agricultural strip located in a valley surrounded by hills. The aircraft carried a full load of superphosphate to be spread on a property approximately one mile from the strip. The pilot had previously surveyed the property and the flight path. He had selected a route that took him up through a valley between hills and then over a low ridge to the property. After take off the pilot set climb power and selected climb flap in order to follow his predetermined route to the property. The pilot advised that as the aircraft flew towards the low ridge it appeared to be descending rather than climbing. He elected to carryout a partial dump and to apply extra flap to clear a clump of trees. The speed deteriorated to 60 knots from the initial climb speed of 70 knots. The pilot did not increase power. Some 300 metres later another partial dump was carried out to clear another tree. As that tree was cleared the pilot again initiated a partial dump and turned to the right in an endeavour to escape from a rapidly deteriorating situation. Immediately the turn was initiated the right wing dropped and the aircraft stalled, impacting the ground onto the right wing and cartwheeled to a stop some 50 metres from the initial impact. The company chief pilot examined the accident site and advised that the flight path through the valley was in a classic false horizon situation whereby the surrounding hills caused the pilot to consider that the flight path was over flat terrain whilst in reality the terrain was rising approximately 5 degrees up to the ridge. The chief pilot also advised that the aircraft would not have been able to outclimb the terrain at high gross weight with only cruise power set.
Probable cause:
Examination of the wreckage did not disclose any pre-impact factors that may have contributed to the accident. Weather and pilot workload were not considered to be factors in this accident.
The pilot had flown approximately 1200 hours on agricultural operations and 244 hours on the type. His loss of situational awareness could be due in part to his relatively low experience.
The following factors were considered relevant to the development of the accident:
- At high weight, and with climb power applied, the pilot flew the aircraft on an inappropriate flight path into rising terrain.
- The pilot did not take appropriate remedial actions when the aircraft could not outclimb the terrain and the aircraft speed deteriorated.
- The pilot lost control of the aircraft while attempting a turn at low speed.
Final Report:

Crash of a Mitsubishi MU-2B-30 Marquise in Melbourne: 1 killed

Date & Time: Dec 21, 1994 at 0324 LT
Type of aircraft:
Registration:
VH-IAM
Flight Type:
Survivors:
No
Schedule:
Sydney – Melbourne
MSN:
517
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5000
Captain / Total hours on type:
150.00
Circumstances:
The aircraft departed Sydney for Melbourne International airport at 0130 on 21 December 1994. En-route cruise was conducted at flight level 140. Melbourne Automatic Terminal Information Service (ATIS) indicated a cloud base of 200 feet for the aircraft's arrival and runway 27 with ILS approaches, was in use. Air Traffic Control advised the pilot of VH-UZB, another company MU2 that was also en-route from Sydney to Melbourne, and the pilot of VH-IAM while approaching the Melbourne area, that the cloud base was at the ILS minimum and that the previous two aircraft landed off their approaches. VH-UZB was slightly ahead of VH-IAM and made a 27 ILS approach and landed. In response to an inquiry from the Tower controller the pilot of VH-UZB then advised that the visibility below the cloud base was 'not too bad'. This information was relayed by the Tower controller to the pilot of VH-IAM, who was also making a 27 ILS approach about five minutes after VH-UZB. The pilot acknowledged receipt of the information and was given a landing clearance at 0322. At 0324 the Approach controller contacted the Tower controller, who had been communicating with the aircraft on a different frequency, and advised that the aircraft had faded from his radar screen. Transmissions to VH-IAM remained unanswered and search-and-rescue procedures commenced. Nothing could be seen of the aircraft from the tower. A ground search was commenced but was hampered by the darkness and reduced visibility. The terrain to the east of runway 27 threshold, in Gellibrand Hill Park, was rough, undulating and timbered. At 0407 the wreckage was found by a police officer. Due to the darkness and poor visibility the policeman could not accurately establish his position. It took approximately another 15-20 minutes before a fire vehicle could reach the scene of the burning aircraft. The fire was then extinguished.
Probable cause:
The following factors were reported:
1. The company's training system did not detect deficiencies in the pilot's instrument flying skills.
2. The cloud base was low at the time of the accident and dark night conditions prevailed.
3. The pilot persisted with an unstabilised approach.
4. The pilot descended, probably inadvertently, below the approach minimum altitude.
5. The pilot may have been suffering from fatigue.
Final Report:

Crash of a De Havilland DH.104 Dove 5 in Melbourne

Date & Time: Dec 3, 1993 at 2037 LT
Type of aircraft:
Operator:
Registration:
VH-DHD
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Melbourne - Melbourne
MSN:
04104
YOM:
1948
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18154
Captain / Total hours on type:
1500.00
Aircraft flight hours:
21259
Circumstances:
The pilot had planned to conduct a night charter flight over Melbourne and Port Phillip Bay, starting from and returning to Essendon Airport. Dinner was to be served in flight. The pilot gave a safety briefing to the passengers before starting the engines. He completed engine runups and pre-takeoff checks, including selecting 20° of flap. At 2036 ESuT, in daylight, the pilot initiated takeoff on runway 17 using standard take-off power setting of 7.5 lb/in2 of boost and 3,000 RPM. Wind conditions were light and variable, visibility was about 10 km and the temperature was 19°C. The aircraft became airborne and, just as it achieved the take-off safety speed of 84 kts, at a height not above 50 ft, the right engine lost power. The aircraft yawed right. The pilot reported to the investigation team that he briefly noticed a reading of 3 lb of boost on the MAP gauge and assessed the problem as a possible partial right engine failure. He then selected the landing gear up but it did not retract. He cycled the landing gear selector once and the gear then retracted. By this time several seconds had elapsed and the airspeed had decayed to 76 kts. The pilot then assessed the airspeed as too low to retract the flaps and left them at 20°. The airspeed continued to decay until VMCA, 72 kts, was reached. When indicated airspeed had further decayed to 68 kts, the pilot reduced power on the left engine to avoid an uncontrollable roll to the right. He was able to maintain wings level and attempted to track the aircraft toward a street but was unable to maintain height. The aircraft collided with powerlines and then struck the roofs of several houses before coming to rest, on its left side, against the front wall of a house. About one minute had elapsed from initiation of takeoff until the accident. The pilot and all but one of the passengers remained conscious throughout the accident sequence. All occupants were evacuated, some without assistance and others with the assistance of the pilot, other passengers, emergency services personnel or bystanders.
Probable cause:
The following factors were reported:
- The right engine fuel control unit fuel pump failed causing the engine to fail at a critical phase of flight.
- Maintenance inspections did not detect the abnormal wear on the thrust face of the right engine fuel control unit fuel pump.
- The landing gear did not retract on the first attempt and aircraft performance decayed while the pilot resolved this problem.
- The pilot was probably forced to abandon the emergency procedures to concentrate on maintaining control of the aircraft.
- The aircraft was unable to maintain altitude and airspeed with the right propeller windmilling and 20° of flap.
- The investigation identified organisational factors concerning deficiencies in the manuals and procedures available to, and used by, the operator for the operation and maintenance of the accident aircraft.
Final Report:

Crash of a Boeing 707-368C off Woodside Beach: 5 killed

Date & Time: Oct 29, 1991 at 1147 LT
Type of aircraft:
Operator:
Registration:
A20-103
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Richmond - §Avalon
MSN:
21103
YOM:
1975
Flight number:
Windsor 380
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The aircraft departed Richmond on a flight to Avalon, carrying five crew members. While cruising at an altitude of 5,000 feet along the coast, the aircraft lost height and plunged in the sea. The wreckage was found about one km off Woodside Beach and all five occupants were killed. At the time of the accident, weather conditions were good.
Crew:
Cpt Mark Lewin, pilot,
F/Lt Tim Ellis, copilot,
F/Lt Mark Duncan, pilot,
W/O Jon Fawcett, flight engineer,
W/O Al Gwynne, loadmaster.
Probable cause:
The Board of Inquiry concluded that the instructor devised a demonstration of asymmetric flight that was 'inherently dangerous and that was certain to lead to a sudden departure from controlled flight' and that he did not appreciate this. The Board noted there were deficiencies in the acquisition and documentation of 707 operational knowledge within the RAAF combined with the absence of effective mechanisms to prevent the erosion of operational knowledge at a time when large numbers of pilots were resigning from the air force. There was no official 707 QFI conversion course and associated syllabus and no adequate QFI instructors' manual. There were deficiencies in the documented procedures and limitations pertaining to asymmetric flight in the 707 and a lack of fidelity in the RAAF 707 simulator in the flight regime in which the accident occurred, which, assuming such a requirement existed, required actual practise in flight. 'The captain acted with the best of intentions but without sufficient professional knowledge or understanding of the consequences of the situation in which he placed the aircraft,' the Board said.