Loss of control

Bell 47G-3B1, VH-UTY

Safety Action

Because of possible fleet-wide safety implications, the Australian Transport Safety Bureau advised the Civil Aviation Safety Authority (CASA) of its preliminary factual findings regarding the incorrect fitment of the tail rotor control pedals.

CASA conducted an immediate survey of operators of this helicopter type and requested an immediate inspection by all operators for compliance with AD/Bell 47/69. At least two other operators at that time reported that they had Bell 47 helicopters with tail rotor control pedals that did not comply with the AD. As a result, CASA issued AD/Bell 47/69 Amdt 1, that became effective on 30 September 2004, requiring all variants of the Bell Helicopter 47 series to be inspected for compliance within 10 hours after the effective date of the directive and every 12 months thereafter.

Factual Information

At approximately 1211 Eastern Standard Time on 2 April 2004, the pilot of a Bell Helicopter Company 47G Soloy helicopter, registered VH-UTY, was conducting fire-ant baiting operations at Nudgee, about 5 km north-west of Brisbane Airport. The operator's chief pilot occupied the right control position and was supervising the pilot.

Near the end of a baiting run, the chief pilot told the pilot that he wanted to demonstrate a procedural turn and asked the pilot to follow him through the manoeuvre. Both pilots reported that, during the turn, the helicopter began to yaw right. The chief pilot then said that he was taking control of the helicopter. He reduced engine power but was unable to arrest the right yaw. The helicopter continued to descend towards a canal and struck the water slightly nose down and banked to the right. Both occupants were injured in the impact but were able to exit from the helicopter unaided.

The pilot reported that he had completed two previous baiting operations in the helicopter during that day without incident.

A subsequent examination of the helicopter found that the tail rotor control pedals installed at the right control position operated in the reverse sense, compared with the tail rotor control pedals installed at the left control position. That meant that tail rotor control pedal inputs made by the chief pilot would have produced a yaw response opposite to that which would normally be expected.

The helicopter operator reported that the tail rotor control pedals for the right control position had been refitted to the helicopter before the accident flight.

In 1954, the Bell Aircraft Corporation, as it was then known, issued Service Bulletin (SB) 98. The SB required installation of a stop assembly (part number 47-722-165-1), under both control position footrests. The purpose of the stop assembly was to prevent the incorrect re-installation of the tail rotor control pedals. UTY was manufactured in 1966, and the stop assembly would have been incorporated as a standard build item during manufacture.

In October 1971, the then Australian Department of Civil Aviation issued Airworthiness Directive (AD) AD/Bell47/69 titled Tail Rotor Control Pedal Assembly Interference Bracket. That AD, which mandated the installation of the interference (stop) brackets to all Bell 47G series helicopters as introduced by Bell SB 98, was still current at the time of the accident.

Examination of the helicopter showed that only part of the tail rotor control pedal assembly bracket as specified in AD/Bell 47/69, remained fitted in the helicopter. The majority of the bracket had previously been removed. There was no evidence to indicate that the removal was as a result of wear or damage sustained in the accident. The maintenance organisation that certified for the last scheduled maintenance check advised that the bracket was in place, and that the co-pilot tail rotor control pedals were not fitted at that time.

The helicopter's maintenance documentation contained no record of the installation of the right tail rotor control pedals, or of the required independent inspection of the flight controls after the installation of the tail rotor control pedals.

The helicopter examination also found that the forward section of the tail rotor drive output shaft, from the main gearbox to just forward of the first bearing hanger assembly, had separated. The separated section was not found. Examination of the remaining broken section of the drive shaft indicated that it had separated due to overload forces that occurred during the accident impact sequence. There was no evidence found of any pre-existing fault in the shaft.

Summary

At approximately 1211 Eastern Standard Time on 2 April 2004, the pilot of a Bell Helicopter Company 47G Soloy helicopter, registered VH-UTY, was conducting fire-ant baiting operations at Nudgee, about 5 km north-west of Brisbane Airport. The operator’s chief pilot occupied the right control position and was supervising the pilot.

Occurrence summary

Investigation number 200401217
Occurrence date 02/04/2004
Location 5 km NW Brisbane, Aerodrome
State Queensland
Report release date 26/10/2005
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Serious

Aircraft details

Manufacturer Bell Helicopter Co
Model 47
Registration VH-UTY
Serial number 6548
Sector Helicopter
Operation type Aerial Work
Departure point Brisbane QLD
Destination Brisbane QLD
Damage Substantial

Bell 47G-4A, VH-MTX

Safety Action

As a result of this occurrence, the Australian Transport Safety Bureau highlights to the helicopter industry articles regarding helicopter dynamic rollover, including:

  • Advisory Circular 90-87, Helicopter Dynamic Rollover, FAA. 1986.
  • Preventing Dynamic Rollover, Major Joseph H. Schmid, Flight Safety Foundation, Helicopter Safety, Volume 14, No.1, January/February 1989.
  • Dynamic Rollover: A new look at an old problem, CASA Flight Safety Australia, April 1999.
  • Dynamic Rollover, Peter Rogers, Heli-News Australasia, May 2003.

1 The mobile HLS is referred to in this report as the 'mobile platform'.
2 VH-MTX was flown from the left seat.
3 The main rotor of these types rotate in the opposite directions, which require different ant-torque flight control input.
4 Helicopter rotor blades are identified by a colour-coding system for maintenance purposes.
5 Flight Safety Australia, April 1999, pp33-34.
6 Done in: Dynamically, Captain J.P. Cress, USMC, Naval Postgraduate School.

Significant Factors

  1. The pilot was not recently experienced on the occurrence helicopter type.
  2. The pilot in command allowed the helicopter to move laterally during the lift-off to the hover.
  3. The pilot in command did not raise the helicopter to a hover height sufficient to prevent contact with the mobile platform.

Analysis

Post-occurrence technical examination of the helicopter did not reveal any evidence of an airframe, engine or system fault that may have contributed to the accident. In addition, examination of the mobile platform did not reveal any evidence of it having moved throughout the rollover sequence.

The circumstances of the accident are consistent with the phenomenon known as dynamic rollover. Scrape marks from the helicopter's right skid were found on the lip along the right side of the mobile platform. That indicated that the helicopter was not raised to a height sufficient to clear the platform in the event of lateral movement. There was no wind reported at the time of the occurrence that could have contributed to the lateral movement. The pilot had extensive flying experience and normally flew a mix of different types, including a mix of European and North American types. Due to that experience, the investigation considered that confusion with respect to correct flight control input to control yaw was unlikely.

If the pilot had prevented the lateral movement of the helicopter during the lift off to the hover, and had raised the helicopter to a hover height sufficient to clear the platform, dynamic rollover would most probably have not occurred. Therefore, the investigation considered that the design or use of the mobile platform was not a factor in the occurrence.

The pilot had not flown a Bell 47 type helicopter during the preceding three months, and had not previously flown a turbine-powered Bell 47. It is likely that the pilot's lack of recency in the helicopter type, combined with his not having flown a turbine-powered Bell 47 previously, contributed to his:

  • not making sufficient flight control input to correct the right lateral movement during the lift-off to the hover
  • not raising the helicopter to a hover height sufficient to prevent contact with the platform.

The pilot's injuries were consistent with him being struck by the main transmission assembly as it separated from its mount as a result of the dynamics associated with main rotor ground contact.

Summary

History of the flight

At approximately 0830 EST, the pilot of the Bell 47G-4A turbine-powered (Soloy) helicopter, registered VH-MTX, was conducting a lift-off to the hover from a mobile helicopter landing site (HLS)1 at Caboolture aerodrome, when the helicopter rolled onto its right side. Weather conditions at the time of the occurrence were reported to be '…little or no wind, warm and humid, some cloud but clearing.' The helicopter was substantially damaged and there was no post-occurrence fire. The pilot, who occupied the left seat2, was fatally injured and the passenger, who occupied the right seat, sustained minor injuries.

Pilot in command

The pilot held an Airline Transport Pilot (Helicopter) Licence, a Commercial Pilot (Aeroplane) Licence, a Command Multi Engine Instrument Rating (CMEIR) (Helicopter), a CMEIR (Aeroplane), and a Grade 1 Instructor (Helicopter) Rating. According to his pilot flying logbooks, he had accumulated approximately 8,293 hours total flying experience, of which approximately 7,180 hours was on helicopters, including 14.8 hours on the Bell 47G helicopter type. He had flown 2.0 hours in the last 30 days and 15.7 hours in the preceding 90 days. His last flight prior to the occurrence flight was nine days previously in a Bell 206 type helicopter. He had last flown a Bell 47G type helicopter on 19 December 2002, including taking off from and landing back on the mobile platform involved in the occurrence. He had not previously flown a turbine-powered Bell 47G helicopter.

The pilot was endorsed to fly Bell 47G type helicopters in accordance with Section 40.3.0 of the Civil Aviation Orders (CAO). In accordance with paragraph 3.3 of those orders, he was permitted to fly turbine-powered Bell 47G helicopters without further endorsement. The operator also reported that, in accordance with paragraph 3A.4 of CAO 40.3.0, prior to the occurrence flight, the pilot was offered refresher training in the turbine-powered Bell 47G type, however the pilot declined that offer.

The pilot met the recency requirements of Civil Aviation Regulation 5.178, having completed CMEIR (Helicopter) and Instructor (Helicopter) Rating renewals on 13 May 2002, in a Bell 412 helicopter type.

Due to the nature of his employment, the pilot had flown 10 aircraft types in the preceding 12 months, of which 7 were helicopters. Those helicopter types included a mix of European and North American types, a mix of single engine and multi-engine types3, and a mix of turbine and piston engine types. Most of the pilot's helicopter flying experience was in turbine engine types. The pilot was experienced in operating helicopters from mobile platforms.

Passenger

The passenger was employed by the same organisation as the pilot in command. He was an experienced helicopter pilot, who reported that he had accumulated approximately 4,700 hours total flying experience, of which approximately 4,500 hours was on helicopters. He reported that he was not in current flying experience. According to witnesses, he did not have his hands or feet near the flying controls during the occurrence.

Medical information

The pilot's aviation medical certificate was valid and carried a restriction for him to have available reading vision correction. A review of his medical records, investigation interviews, results of the post-mortem examination and toxicological testing, found no evidence of pre-existing medical conditions or the presence of any substance that may have influenced his performance.

Survival information

Four-point restraint harnesses with inertia reel shoulder straps were fitted at the pilot and right side passenger positions. Post-occurrence technical examination revealed that they were firmly secured to their mounts, and the inertia reels appeared to operate normally. The pilot occupied the left seat and remained restrained during the rollover sequence. He sustained severe impact injuries to the rear of the upper torso and lacerations to the back of the head.

Helicopter information

Type: Bell 47 helicopter
Model: 47G-4A (Soloy)
Registration: VH-MTX
Serial Number: 7765
Year of manufacture 1971
Engine: Rolls Royce 250-C18
Total time in service: Approximately 5,570 hours
Maintenance release: Number 09425 issued 14/03/03 at 5,549.7 hours

The helicopter had been imported from Japan in October 2002, receiving an Australian Certificate of Airworthiness in December 2002. The helicopter was maintained in accordance with the manufacturer's and CASA approved documents and schedules, and had flown approximately 20 hours since its last 100-hourly inspection.

Damage to the helicopter

The helicopter came to rest on its right side, with its right skid landing gear resting on the right rear corner of the platform. The canopy bubble had shattered. The main rotor, mast and transmission assembly had detached from the helicopter as a single unit and was located next to the helicopter. The 'white' main rotor blade4 was lying across the cockpit. Evidence, in the form of multiple main and tail rotor impact marks, was observed in the ground with an area of burned grass beneath the helicopter's engine exhaust. One of the tail rotor blades had detached and was located approximately 30 metres from the helicopter. The tip of the 'red' main rotor blade was found approximately 150 metres to the east of the helicopter. Both arms of the main rotor stabiliser bar had fractured and were found within 20 metres of the helicopter. All major components were located and identified at the site. Post-occurrence technical examination of the helicopter did not reveal any evidence of an airframe, engine or system fault that may have contributed to the accident.

Mobile platform information

The mobile platform was a flat-based metal construction on wheels, measuring 365 x 300 cm and was approximately 22 cm above the ground. A 5 cm high metal lip ran along both sides of the platform. There were no metal lips at the front or rear of the platform. The front wheels were positioned forward of the base and were approximately 27 cm in diameter. The rear wheel axles were in line with the platform base, allowing the 38 cm-diameter wheels to sit approximately 18 cm above the base. There were two prominent worn strips along the base approximately 38 cm from the side lips, which indicated the usual positioning of the helicopter skids on the platform. At the time of the occurrence, the platform was connected to a small tractor. The tractor brake was engaged and there was no evidence of the tractor having moved throughout the accident sequence.

Civil Aviation Regulation 92 (1) states that:

An aircraft shall not land at, or take-off from, any place unless:

(d) the place… is suitable for use as an aerodrome for the purposes of the landing and taking-off of aircraft;

and, having regard to all the circumstances of the proposed landing or take-off (including prevailing weather conditions), the aircraft can land at, or take-off from, the place in safety.

GEN 2.2 of the Aeronautical Information Publication, defines an aerodrome as:

A defined area of land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and movement of aircraft.

Guidelines for the establishment and use of HLS are at Civil Aviation Advisory Publication (CAAP) 92-2 (1), which defined an HLS as:

…a place that may be used as an aerodrome for the purposes of landing or taking off of helicopters.

The definition of '…place…' in CAAP 92-2 (1) included '…on a structure…'.

There is no CASA regulation or guidance concerning the design or use of mobile platforms. Additionally, international standards and recommended practices contained in Annex 14 to the International Civil Aviation Organization (ICAO) Convention on International Civil Aviation, Aerodromes, Volume II - Heliports, do not refer to mobile platforms. A search of international regulatory authorities found no documentary guidance regarding design or use of mobile platforms.

The investigation found that mobile platforms of varying design are used throughout the Australian civil helicopter industry. Some of those designs incorporated side lips and others had no protrusions above the platform surface. Most of the platforms were tractor-towed.

Damage to the mobile platform

Examination of the mobile platform revealed two fresh scratch marks on the right lip approximately 50-85 cm from the rear of the platform. Also evident were fresh gouges on the rear edge of the platform, adjacent to the right wheel axle, which indicated that the helicopter had been moving rearwards as it contacted the lip. Examination of the platform did not reveal any evidence of it having moved throughout the rollover sequence.

Organisational information

Pilot employees from the same organisation as the occurrence pilot reported that they each received funding for up to 40 flying hours each financial year to maintain recency on selected aircraft types. They also reported that, due to the nature of their employment, some pilots had a requirement to maintain recency on a number of types simultaneously.

Dynamic rollover

The phenomenon known as dynamic rollover was described in helicopter textbooks, training manuals and industry and safety publications. It was included at:

  • items 10.7 and 12.1 of the CASA Day (VFR) Syllabus - Helicopters, Issue 3, January 1999, which applied from Student through to Commercial Helicopter Licence standard
  • item 2.1.14 of the Air Transport Pilot (Helicopter) Licence - Aeronautical Knowledge Syllabus, Issue 3, January 1999.

Dynamic rollover has been defined as:

The occurrence of a rolling motion, while any part of the landing gear is acting as a pivot that causes the aircraft to exceed a critical angle and roll over5.

Another definition states that:

Put simply, dynamic rollover is the result of the helicopter developing excess angular momentum about the skid in contact6...

Dynamic rollover typically occurs when a critical rollover angle is exceeded. That angle is dependent upon control limits and in most helicopters is in the order of 15 degrees. Accidents attributed to dynamic rollover have occurred previously on a number of surfaces, including open flat grassed surfaces.

Occurrence summary

Investigation number 200300982
Occurrence date 19/03/2003
Location Caboolture, (ALA)
State Queensland
Report release date 26/02/2004
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Bell Helicopter Co
Model 47
Registration VH-MTX
Serial number 7765
Sector Helicopter
Operation type Flying Training
Departure point Caboolture, QLD
Destination Caboolture, QLD
Damage Substantial

Lancair IV-T, VH-CIV, 6 km north-east of Drysdale, Victoria, on 20 December 2002

Safety Action

Local safety action

The Sports Aircraft Association of Australia (SAAA) announced in July 2003 that it is scoping the development and implementation of a four-stage flight safety assistance program for members. The program adopts some of the existing programs run by the association and will develop into a broader program incorporating aspects not currently covered.

The intention is to encourage members to sign onto the total program while still giving them the choice under the experimental rules.

During July /August 2003, the Association's technical coordinator travelled overseas to meet with United States of America Experimental Aircraft Association officials to discuss that organisation's flight advisor program.

An outline of the SAAA intended program was introduced to SAAA members in October 2003.

The Association will also include a note and link to this report on its website www.saaa.com.

Analysis

Planned activities on the 9 December 2002 flight had indicated that the aircraft became laterally unstable as the aircraft approached the stall speed. Recorded flight data indicated that the aircraft also entered a stall during the flight on 9 December, even though this was not planned. It is possible that this stall was an unplanned activity. There was no evidence that any of the aircraft's performance and handling characteristics encountered in this unplanned stall, such as stalling airspeed, were considered when preparing for the flight when the accident occurred, when stalls were part of the test program.

Lateral instability, as the aircraft speed approached the stall speed, had been experienced and noted in a previous flight. The test flight program did not include a lateral stability test for the flight and the recorded aircraft data did not indicate that a lateral stability test had been undertaken on the flight. It is possible that the notes referred to a tendency for the aircraft to drop a wing as it approached the stall, or stalled, as similarly experienced during the accident flight.

During the flight when the accident occurred, the aircraft departed controlled flight from a deliberately induced stall during a test flight. The aircraft then descended rapidly, at an airspeed that was not consistent with a stalled or spinning configuration.

The aircraft instruments displayed a stall speed that was significantly below the actual stall speed in that configuration. It is possible that the stall occurred before the flight crew expected it.

The aircraft was based on an established aircraft design, but had significant design changes from the original. Those design changes were likely to have changed the performance and handling characteristics of the aircraft and the cumulative effect of those changes would have been hard to predict.

The test flight program had been developed in accordance with some of the approved advisory material. The advisory material gave detailed guidance on what was to be done, and how it should be done. It did not give detailed guidance on defining what should be expected during the test program, and what to do if something unexpected occurred during the program. As an example, a particular aircraft design is normally expected to stall at a particular airspeed for a given configuration and flight condition. The particular handling characteristics as the aircraft approaches and passes through a stall should also be predictable and expected. When these characteristics are examined during a test flight, they would be expected to fall within a defined range. The guidance material did not detail what to do if any of the performance or handling characteristics were outside the expected ranges.

There was no evidence of a significant risk management process, other than preflight briefings conducted by the pilot of the first two flights, throughout the design, construction, or test flight program development for the aircraft. Such a program could have assisted in identifying hazards and their attendant risks, and for managing them appropriately from initial construction though to certification. While there was no requirement for an owner/builder to have a risk management process, such a process would have been prudent considering the significant changes made to the aircraft.

The test program did not incorporate flight instrument calibration and therefore the accuracy of the flight instruments was unknown. It would not have been possible to confidently establish the exact speeds at which the aircraft's handling and performance were assessed.

The test flight program only required one person on board the aircraft for test flights. The investigation was not able to identify an operational reason for the owner/builder to be on board the aircraft.

Factual Information

History of the flight

The Lancair, registered VH-CIV, was a homebuilt aircraft operating under an experimental certificate of airworthiness. The owner had recently built the aircraft and had commenced a test flight program. The aircraft departed with a test pilot occupying the pilot seat, and the owner/builder occupying the right seat. Witnesses reported seeing the aircraft flying in the Drysdale area before descending steeply. It subsequently impacted the ground and the two occupants were fatally injured.

The pilot departed from Point Cook and flew along the coast, southwest of Point Cook aerodrome, at altitudes between 3,000 ft and 4,000 ft. After crossing Port Phillip Bay to the Bellarine Peninsula the pilot climbed the aircraft to between 5,000 ft and 6,000 ft. Recorded flight data indicated that the aircraft was slowed, and stalled at an altitude of 5,200 ft. The pilot recovered from the stall, but the aircraft entered another stall during the recovery at 4,950 ft. The pilot recovered the aircraft from that stall, and then repositioned it and entered a third stall at an altitude of 6,200 ft. The aircraft rolled at the initiation of the stall, and continued to roll as it then descended rapidly, accelerating to approximately 150 kts at an angle of approximately 40 degrees from the horizontal, with low engine power. The engine power increased shortly before the aircraft impacted the ground.

The aircraft impacted the ground upright, with the wings level, at a pitch angle of 40 degrees nose down. The landing gear was retracted at the time of impact, and the flaps were either completely or nearly retracted. There was no indication of any mechanical failure prior to impact. The accident was not survivable.

Flight crew

The pilot was an experienced ex-military pilot with 6,500 hours total aeronautical experience, including experience over many years in aircraft with a wide range of performances.

The owner/builder had a Commercial Pilot (Aeroplane) Licence issued 16 October 2001. He had 352 hours total aeronautical experience in a range of general aviation aircraft with a level of complexity and performance up to four-seat single-engine aircraft, with a constant speed propeller and retractable landing gear.

Aircraft

The aircraft was originally being constructed to comply with the requirements of Civil Aviation Safety Authority (CASA) Civil Aviation Order (CAO) 101.28. During construction, the experimental designation concept was developed and the aircraft construction was subsequently changed and completed in accordance with the experimental designation under Advisory Circular (AC) 21.4(2) issued September 2000. The certification requirements in the experimental category were less prescriptive than those in CAO 101.28 as experimental aircraft are not type-certificated. 'Experimental' is not a category but rather a designation. It is also important to note that an experimental certificate does not attest to an aircraft being fully airworthy (Civil Aviation Safety Authority Advisory Circular 21.1(1) - Aircraft Airworthiness Certification Categories and Designations Explained - Revised December 2000).

The aircraft was based on a Lancair IV-T kit plane that was originally designed to use a high-performance piston engine. The owner/builder decided to replace the engine with a turbo-propeller engine and sought assistance from a number of people to redesign the aircraft to accommodate the new engine.

Documentation indicated that during construction, numerous changes had been made to the original design, including the engine type and the design of the aircraft from the firewall forward. The propeller had been modified by removing 20 cm of the propeller tips. No evidence was found to indicate that any form of risk assessment had been undertaken to consider the safety implication of these aircraft design changes. A risk assessment was not required for aircraft constructed under the experimental designation.

Aircraft equipment

The aircraft was equipped with an integrated electronic flight information system (EFIS) comprised of a number of data acquisition units and three liquid crystal multi-function display (MFD) units, that could be configured to present operational information in different ways. The instrumentation system received data from a variety of sources, and integrated that data to present operational information to the pilot. Each MFD also contained a memory unit that recorded information that was sent to it. This information was used by the ATSB to determine the flight profile prior to the accident.

The MFDs could be selected by the pilot to display primary flight information, navigation information, or engine system information. The primary flight information consisted of an electronically generated artificial horizon display upon which a number of other information displays were overlayed. Indicated airspeed (IAS) was also displayed on the left side of this display. The IAS was presented as a vertical tape display of airspeed with a range of approximately 100 kts, in increments of 10 kts. The actual airspeed was also displayed numerically on the left side of the artificial horizon display, adjacent to the IAS speed tape display. The airspeed tape display contained a number of coloured regions to indicate various speed ranges and included the stall speed of the aircraft. The stall speed was dynamically generated and changed with varying flight loads on the aircraft. The displayed stall speed was known as the G-corrected stall speed. The EFIS derived the G-corrected stall speed from the aircraft's static 1G stall speed. The 1G stall speed had to be manually entered into the EFIS. The aircraft instrumentation system had been programmed with a 1G indicated stall speed of 69 kts with flaps and landing gear retracted.

The aircraft was also equipped with a video camera mounted on the ceiling just behind the two front seats, which was aimed at the instrument panel. This camera operated for some of the test flights, and some of the recordings were recovered from the camera after the accident.

The original aircraft design (with a piston engine) had a declared indicated stall speed of 84 mph, or 73 kts with flaps and landing gear retracted. The Comparative Aircraft Flight Efficiency (CAFE) foundation test flight of this version of the aircraft type recorded a stall speed of 78 kts with flaps and landing gear retracted. That test flight was conducted with a calibrated pitot/static boom, so the indicated airspeed would have been accurate in that instance. A theoretical aerodynamic calculation for the accident aircraft indicated a stall speed of 82 kts. Recorded information indicated that the aircraft stalled at 82 kts at the commencement of the accident sequence.

A flight path marker symbol, in the centre of the primary flight display, indicated the current pitch attitude of the aircraft. At an airspeed of 20 kts above the G-corrected stall speed, an amber pitch limit indicator symbol appeared above the flight path marker. The pitch limit indicator symbol moved down toward the flight path marker symbol as the airspeed decreased towards the stall speed. At 5 kts above the stall speed, the pitch limit indicator symbol turned red. At the point of stall, the pitch limit indicator symbol overlayed the flight path marker symbol. Coincident with the pitch limit indicator symbol changing to red, an aural annunciator would repeat a voice warning of 'stall' and a red stall flag symbol would display in the bottom left corner of the primary flight display.

The aircraft was also equipped with an angle of attack sensing device that used pressure information from two ports on the upper and lower sides of the left wingtip to derive the angle of attack. This instrument could have indicated when the aircraft was approaching a stall. The investigation did not determine if it had been calibrated before the accident flight.

During a test flight on 9 December 2002, the test pilot had decelerated the aircraft until it was approaching the stall as a part of the test flight program. Written records from that flight noted:

'A/c [aircraft] becomes laterally unstable below 80 Kts.'

Recorded flight data indicated that the aircraft stalled three times during this flight, from speeds of 72, 75 and 76 kts. The test pilot had also noted:

'Close to stall at 75 Kts with 10 [degrees] flap
Close to stall at 72 Kts with full flap'.

Video recordings from the flight indicated that the aircraft had stalled, and rolled 45 degrees to the left, and then 45 degrees to the right of horizontal during the recovery from the stall. Stalls were not a part of the test flight program for the flight.

Test program

A friend of the owner/builder developed a program for the flight testing of the aircraft. That program followed the guidelines in the Federal Aviation Administration (FAA) Advisory Circular 90-89A - Amateur-built Aircraft and Ultralight Test flighting Handbook. The CASA Advisory Circular 21.4(2) - Amateur Built Experimental Aircraft - Certification, advised that CASA:

'...most strongly urges [Amateur-built experimental aircraft builders] to make detailed reference to [this document], prior to their flight programs commencing, and [to] follow the guidance provided.' (section 14.4).

The test flight program was detailed, and was clearly developed in accordance with the recommendations of Advisory Circular 90-89A. Neither the advisory material, nor the test flight program considered action to be taken if aircraft handling or performance produced unexpected results.

CASA Advisory Circular 21.4(2) stated:

'14.5 Those undertaking test flight programs may also derive benefit in consulting the following additional references, as applicable to the class of aircraft involved:

'(a) CAA publication dated January 91, Flight Test Guide for Certification of CAO 101.28 Category Aeroplanes...'

This document recommended calibration of aircraft flight instruments, so that the limits of the flight envelope could be accurately determined. The test flight program for the accident aircraft did not include the in-flight calibration of aircraft flight instruments, including the airspeed indicator. Comparison of the recorded airspeed from the satellite navigation system, fitted to the aircraft as apart of the EFIS, with the recorded airspeed from the pitot/static system showed no inaccuracy in airspeed indication.

There was no evidence that any significant risk assessment was undertaken during construction of the aircraft and in the development of the test flight program. Such a risk assessment could have examined the planned activities and considered any potential hazards for their likely impact on the aircraft's safety during test flights.

The friend who developed the test program stated that he conducted the first two flights of the aircraft, but subsequently did not participate any further in the test program. Prior to those initial flights, he conducted an operational pre-flight briefing with the owner. These briefings included hazards and potential actions. The investigation did not determine whether the test pilot for the accident flight conducted similar operational pre-flight briefings for subsequent flights.

There was no evidence that any significant re-evaluation of risk was done during the subsequent conduct of the test flight program. Such a risk assessment process could have examined the results of test flights for hazards that became apparent from analysis of observations and data from each flight. This could have allowed for a considered assessment of any risk mitigators for their likely impact on the aircraft's safety during subsequent test flights, as the aircraft flight envelope was expanded. For example, if unexpected handling characteristics had been encountered during a stall sequence, then previously identified mitigation procedures, such as moving the centre of gravity forward, could have been considered.

Aircraft design

An aircraft operated as an experimental aircraft does not have to comply with any specific design. Builders may comply exactly with a design, or may deviate from that design as much as they wish, or may build an aircraft independent of any previously developed design.

If an aircraft is built mainly in accordance with an established design, but with some design differences, then it may perform differently from an aircraft built exactly in accordance with that established design. If design differences are incorporated one at a time, then it is possible to measure the effect of any single design difference. If many design differences are incorporated at one time, the effect of a single design difference on the behaviour of the aircraft may be impossible to predict due to the compounding effect of other incorporated design differences. The accident aircraft had been constructed with many differences compared with the original Lancair IV-T design.

Required persons on board during test flights

A CASA delegate had issued a special certificate of airworthiness authorising flight in accordance with the test flight program. The approval included operating limitations for the test flight program, such as geographical limitations, minimum weather conditions for flight and the maximum number of persons to be on board the aircraft.

Test flights are hazardous compared with normal flight. Accordingly, there is normally a requirement for only operational persons to be on board an aircraft during a test flight. The special certificate of airworthiness under which the accident flight was made stated 'Only personnel essential for the conduct of the testing may fly on board the aircraft. The carriage of passengers is prohibited.'

This aircraft type was normally flown as a single crew operation, and the cockpit of this aircraft was configured for single crew operation. There was no evidence that the test flighting required two persons on board.

Occurrence summary

Investigation number 200206005
Occurrence date 20/12/2002
Location 6 km NE Drysdale
State Victoria
Report release date 04/11/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Neico Aviation Inc
Model Lancair IV-T
Registration VH-CIV
Sector Piston
Operation type Private
Departure point Point Cook, VIC
Destination Point Cook, VIC
Damage Destroyed

Saab SF-340B, VH-OLM

Summary

On the evening of 28 June 2002, a Saab 340B, VH-OLM, was being operated on a regular public transport service, from Sydney to Bathurst, NSW. The pilot in command (PIC), the flying pilot, had commenced a descent from 12,000 ft for a Katoomba-Bathurst Global Positioning System (GPS) arrival and subsequent landing on runway 17 at Bathurst. The PIC reported that as the aircraft descended to the minimum descent altitude (MDA), visibility alternated between visual and instrument flight conditions. During the descent, the PIC had retarded the power to about 17 per cent and slowed the aircraft to about 135 kts in preparation for a Category B circling approach.

The copilot, non-flying pilot, reported that during the descent the engine anti-ice was on, but not the propeller de-ice, nor had the airframe boot de-ice system been activated. The PIC reported that during descent, they entered cloud a number of times and noted ice accretion on the windshield wiper. The flight crew reported that they did not observe any wing ice during the descent.

At the MDA (3,810 ft), the aircraft's Flight Guidance and Autopilot System (autopilot) captured the altitude and, as the airspeed was decreasing due to the reduced power setting, commanded the trim system to progressively raise the nose of the aircraft to maintain the MDA. The PIC commanded the autopilot to roll the aircraft to the right to begin tracking downwind for runway 17. At about this time, the copilot observed that the airspeed was decreasing and called 'speed'. As the PIC applied power to compensate for the decreasing airspeed, the aircraft rolled to the left and pitched down without warning. During the recovery from the steep pitch and bank angles, the aircraft rolled to the right and descended to 112 ft AGL. The PIC regained control of the aircraft and climbed it to the missed approach altitude and carried out an uneventful landing.

The aircraft's aerodynamic stall warning systems of stick shaker, audible alarm, visual warnings and stick pusher, did not activate during the initial roll to the left. However, theautopilot disconnected during the subsequent roll to the right, due to activation of the stall warning.

The investigation determined that following capture of the MDA by the autopilot, the aircraft speed continued to decrease due to the reduced power setting. As a consequence,the aircraft stalled. However, this occurred prior to the stall warning system operating due to the likely presence of airframe ice that had accumulated during the descent.

The investigation found that it is possible for the aircraft to stall prior to the activation of the stall warning system if the aircraft has accumulated ice on the wings.

The investigation, classed as a serious incident, identified a number of other occurrences involving Saab 340 aircraft stalling where little to no stall warning had been provided to flight crew while operating in icing conditions. This included a Saab operated by an Australian operator, which resulted in a number of ATSB recommendations being issued in that investigation, not all of which were accepted and acted upon. Some of those recommendations have been re-issued.

Related Documents: |Media Release|

Occurrence summary

Investigation number 200203074
Occurrence date 28/06/2002
Location 7 km ESE Bathurst, (NDB)
State New South Wales
Report release date 28/01/2004
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer Saab Aircraft Co.
Model 340
Registration VH-OLM
Serial number 340B-205
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Sydney, NSW
Destination Bathurst, NSW
Damage Nil

de Havilland DH-82A, VH-AJG

Safety Action

As a result of this occurrence, the Australian Transport Safety Bureau issues the following safety recommendation:

RECOMMENDATION 20030027

The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority review the inspection procedures with regard to the continuing airworthiness of wooden wings and propellers that were manufactured with the use of Casein adhesive.

Analysis

The investigation could not determine the reason for the pilot losing control of the aircraft. There was no physical evidence indicating that the right wheel destroying two taxiway lights during take-off damaged any major structural element or in any way contributed to the accident. Also, no evidence was found to support the reported observations of the left or the right wings folding up or a part of the aircraft separating in flight. The evidence suggested that the portion of the right-wing rear spar interplane strut that was found approximately 73 metres from the accident site, was thrown to its location as a result of impact forces when the right wings struck the tree.

The aircraft was observed cruising in level flight when it apparently departed controlled flight. It was not observed changing altitude or commencing a turn and would have been experiencing approximately 1g loads only, well below the minimum design load of 5g.

The timber examination reports noted failures of the laminated members, on wings of the original manufacture. This was probably due to the Casein glue having been attacked by micro-organisms after the wood and the glue moisture content rose above 18%. The attack by micro-organisms was least evident in areas close to the edges of the glued joints. Circulating air quickly dries these areas causing any attack by micro-organisms to cease while it can continue on the inner areas of the joint that remain moist. This, and the fact that the glued joints were further secured by nails, bolts and screws would most likely prevent detection of any glued joint that had been attacked by micro-organisms. It is also considered likely that the presence of `Irish linen' and the thick coat of paint on the propeller would disguise any underlying delamination.

The wreckage and the exposed wood were soaked wet while on site. The possibility of attack by micro-organisms commencing at that time was not considered likely, because once the wreckage was removed from the site it was stored in dry environment. That prevented elevated moisture content and attack by micro-organisms.

CONCLUSIONS

The pilot was appropriately qualified and endorsed on the aircraft.

No evidence was found indicating that the aircraft striking and destroying two taxiway lights during take-off contributed to the accident.

It could not be determined if any part of the aircraft structure or the propeller failed prior to the aircraft departing from the level flight.

The wood that the wings were constructed from was of a high quality and there was no evidence to indicate that a failure of wood was a factor in the accident.

A number of laminated members on three wings of the original manufacture and the propeller failed at the glue line rather than in the wood, probably as a result of Casein glue having been attacked by micro-organisms.

Current inspection procedures would not allow detection of delaminated Casein glued joints.

Summary

The pilot hired the de Havilland DH82A Tiger Moth aircraft, registered VH-AJG, to undertake a local pleasure flight with a friend. The aircraft took off from a grassed area parallel to the Royal Australian Air Force (RAAF) base Williamtown's main runway between the eastern end of the runway and taxiway `A'. During the take-off, the aircraft was observed to veer right and strike and destroy two taxiway lights with the right wheel. The pilot continued the take-off and the aircraft departed the Williamtown circuit area at 1428 Eastern Summer Time.

Based on witness reports and radio transmissions by the pilot, the aircraft initially conducted a sightseeing flight over the coastal suburbs of Newcastle City. About 20 minutes after takeoff, the pilot broadcast that he was transiting north through the Williamtown Mandatory Broadcast Zone west of the coast. The aircraft subsequently joined the Williamtown circuit from the north at 1519. The actual flight profile and manoeuvres conducted during the flight are not known. Shortly after joining the circuit, the aircraft was observed to depart level flight and impact the ground approximately 2 km southwest of the Williamtown airport. Both occupants were fatally injured and there was no evidence of fire in flight or after the impact.

A helicopter with an instructor and student on board was in the circuit area, about 1.5 km behind the Tiger Moth. The helicopter was about 800 ft above ground level and maintaining approximately 60 kts. The helicopter crew estimated that the Tiger Moth was flying at the same speed and altitude. The helicopter's pilots reported observing the left wings fold up, the aircraft rotate and fall almost vertically in a steep nose-down attitude rotating only a couple of times before impacting the ground.

A witness on the ground reported observing the aircraft's right wings fold back, followed by the aircraft spinning or spiralling to the ground. Another witness reported seeing the right wings folding up, making the wings into an `L' shape and about a metre long silver pole flying up from the cockpit area. The aircraft then started turning to the right. None of the witnesses reported observing the aircraft changing altitude or commencing a turn prior to the loss of control.

Personnel information

The pilot held a valid Australian Special Pilot Licence and had accumulated 360.6 hours total of which 4.1 hours were on the Tiger Moth. The pilot's tail-wheel experience totalled 7.9 hours. He was endorsed on the type and flew earlier that day with an instructor. The accident flight was his first unsupervised flight on the type.

The Australian Special Pilot Licence authorises a pilot with a current overseas private or higher class of licence to undertake private flights in Australia. The pilot held a United Kingdom private licence. He held an Australian Class 2 (private) medical certificate valid until October 2005, issued by the Civil Aviation Safety Authority (CASA) on the basis of his United Kingdom medical. There was no evidence of any physiological condition affecting the pilot that may have contributed to the occurrence.

Operation and weather

The aircraft was operated by the RAAF Williamtown Flying Club located on the base and the accident flight was the aircraft's third flight of the day. The weather was reported to be fine with a light north-easterly breeze.

The aircraft and its history

The Tiger Moth was a fabric covered biplane aircraft with two open cockpits in tandem arrangement. The pilot sat in the rear cockpit. The truss type fuselage was made from steel tubes while the wings and tail surfaces were constructed from wood. The two-spar, single-bay wings were reinforced by a system of drag struts, drag and anti-drag wires. Each spar was made from a single piece of wood with a reinforcing doubler glued at the interplane strut attachment. The spars were fitted with metal fittings used to attach the wings to the fuselage and cabane centre section upper struts. The flying, landing and cabane wires, tie rods and interplane struts gave the wings the required rigidity.

The aircraft was stressed to withstand maximum loads of approximately 7.5g (acceleration due to earth gravity). Information from the manufacturer indicated that even with the reinforcing doubler delaminated and ineffective, the aircraft was designed to withstand manoeuvre loads of about 5g.

The aircraft was manufactured in 1942 and used by the RAAF until August 1947, when it was decommissioned and received civilian registration. The aircraft was substantially damaged during an accident in 1967. It was then dismantled and stored until 1988 when it was rebuilt and had since accumulated approximately 48.35 flying hours. The fuselage truss structure was repaired and an overhauled engine was installed. The aircraft was fitted with four wings and propeller of original manufacture. The previous history of the wings and the propeller could not be determined.

In November 2001, the left lower wing was damaged when the landing gear collapsed on landing in Newcastle after a ferry flight from Bankstown. A new wing was manufactured and fitted in December 2001. On 13 January 2002, the left lower wing contacted the ground while the aircraft taxied after a flight.

The aircraft was used to perform only limited aerobatic manoeuvrers such as barrel rolls, loops and stalls. A few steep turns and dives were performed during the flights on the morning of 16 February 2002.

The aircraft was maintained in accordance with the applicable and current maintenance requirements. The maintenance release was valid until 9 March 2002. Examination of maintenance documents indicated that all required maintenance had been carried out. The aircraft had no known maintenance deficiencies and was considered capable of normal operation prior to the accident.

Accident site and wreckage examination

The impact site was an area of dense undergrowth, tall grass and 10 to 12 m high trees. The ground was soft and waterlogged. The wreckage was contained within a small area at the foot of a tall tree, its distribution indicated that the aircraft impacted in a steep nose-down attitude while rotating to the left. The aircraft and its four wings were extensively damaged. The wing spars were splintered and broken at numerous locations. The right wings struck a tree during impact and their damage was significantly more severe than the damage sustained by the left wings.

With the exception of both propeller blades and parts of the right wing rear spar interplane struts, all aircraft components and extremities were accounted for at the accident site. The propeller boss that remained attached to the engine shaft was the only part of the propeller recovered. Propeller contact marks on the tree indicated that the propeller was rotating at the time of impact. A part of the missing interplane strut was found some six months after the accident approximately 73 m from the accident site.

Examination of the engine, systems and flight controls did not reveal any pre-impact defect that would have prevented them from normal operation. The left front and rear flying wires and the left cabane wire were severed in overload. There was no fuel remaining in the ruptured fuel tanks, but fuel was evident at the accident site.

Sections of the wing spars were examined by a timber specialist who concluded that the wood was of high quality and in good condition. It was free of decay and there was no evidence to indicate that a failure of the wood was a factor in the accident. Some blue colouring of wood was present in one laminate of the propeller boss, but there was no evidence to link this discolouration with failure of the propeller. The specialist reported that many of the wood failures, on the three wings of the original manufacture, were brash rather than splintering, indicating some embrittling associated with the age of the wood.

Adhesive failure

The specialist also reported that some laminated members on the three wings of the original manufacture and the propeller failed at the glue line rather than in the wood. The failure was due to the glue line being devoid of the adhering adhesive. The adhesive was identified as Casein. The specialist reported that the observed failure was typical of that of Casein that was exposed to attack by micro-organisms and that the attack was evident all over the glued area of the joint except on small areas close to the edges of the glued components. No delamination was observed on the new wing fitted in December 2001. This wing was manufactured using modern synthetic resin adhesive.

Casein is a milk-based glue that was particularly popular around the 1940s, when the three wings and the propeller were most likely manufactured. Since it contains protein, it could be subject to attack by micro-organisms and weakened if the moisture content of the wood and the adhesive is allowed to increase above a certain level. The Casein glued joints, however, do not degrade instantaneously when wet. The amount of degradation is proportional to the time the joint is allowed to remain moist.

The specialist advised that the attacks by micro-organisms occurs when the wood and adhesive moisture content is approximately 18% or greater. A moisture content of 18% could be achieved if the wood was exposed to a relative humidity of 85% or greater. While such humidity is experienced in tropical Australia, the average moisture content of the wood and the adhesive is not likely to reach this level due to lower values during various times of the day. The evidence, however, indicated that the glued joints were probably subjected to a number of periods when the moisture content was high, allowing micro-organisms to attack the adhesive. Such periods were further evidenced by the presence of corrosion around the nails, bolts and screws securing the joints.

However, the specialist concluded that there is little or no evidence indicating that any single glue failure may have resulted in a catastrophic failure of a major structural element of the aircraft or the propeller.

Propeller

The numbers stamped on the propeller boss were consistent with the propeller having been manufactured in the 1940s. The wooden propeller consisted of a number of laminates. After the propeller was manufactured, the centre part of each blade was wrapped with a layer of `Irish linen'. The entire propeller was then coated with a relatively thick coat of dark coloured cellulose-based paint.

Occurrence summary

Investigation number 200200377
Occurrence date 16/02/2002
Location 2 km SW Williamtown, Aero.
State New South Wales
Report release date 27/02/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer de Havilland Aircraft
Model DH-82
Registration VH-AJG
Serial number 382
Sector Piston
Operation type Private
Departure point Williamtown, NSW
Destination Williamtown, NSW
Damage Destroyed

Cessna U206F, VH-STL

Significant Factors

  1. Weather conditions at Horn Island aerodrome were less than visual meteorological conditions at the time of the occurrence.
  2. The pilot was not current for flight in IMC.
  3. The pilot lost control of the aircraft at an altitude from which recovery was not considered possible.



 

Summary

The pilot of a Cessna 206 (C206), departed from Badu Island, Qld at about 1210 Eastern Standard Time (EST) on a positioning flight to Horn Island, Qld in accordance with the visual flight rules (VFR). The aircraft had an estimated fuel endurance of 270 minutes. The pilot, who was the sole occupant, had been tasked to conduct a charter flight from Horn Island at 1330 with passengers who were reported as arriving on a scheduled flight from Cairns.

At about 1221 the pilot broadcast on the Torres Mandatory Broadcast Zone (MBZ) frequency that he was over Wednesday Island and tracking for a 3 NM final approach to runway 26 at Horn Island. A short time later he broadcast that he was holding until the weather over the runway cleared. At about 1238 the pilots of two aircraft in the Bamaga area reported hearing a MAYDAY broadcast from the pilot of the C206 on the MBZ frequency. The pilot did not describe the nature of the emergency. Further efforts by the pilots operating in the Bamaga area to contact the pilot of the C206 were unsuccessful and they advised air traffic services of the MAYDAY they had heard on the MBZ frequency.

An air and sea search was commenced. Later that day floating debris, identified as belonging to the C206, was located. The recovered items included the left main wheel and landing gear leg, the nose wheel and part of the nose gear landing leg and a seat. The following day divers located the aircraft approximately 3 NM east of Horn Island in 7 m of water but the pilot was not found.

The aircraft was recovered from the sea floor where it had been submerged for just over two days. It had been extensively damaged by impact forces. The nature of the recovery process resulted in further disruption of the wreckage. The outer left wing, left aileron and the engine cowls were not recovered. Salt-water corrosion had affected many of the aircraft components. The flaps were found in the retracted position and damage to the propeller blades was consistent with low engine power at the time of impact. Damage was consistent with the aircraft having struck the water at a moderate to high speed in a nose-down, left wing low attitude. The collision with the water was not survivable.

Examination of the damaged gyroscopic flight instruments did not reveal any indication of pre-impact malfunction. The vacuum pump was found in good condition and capable of normal operation. Although the aircraft was equipped with appropriate instrumentation for flight in instrument meteorological conditions (IMC) it was maintained to the VFR standard, as appropriate to the category of operation. Maintenance requirements were certified as having been performed and no evidence was found to indicate that the aircraft was other than serviceable prior to the flight. Analysis of recorded audio data determined that engine operation was normal during the pilot's radio transmissions.

The pilot was reported to have obtained a forecast from Airservices electronic briefing facility using the company computer terminal at Badu Island. That forecast predicted north-westerly stream weather characteristic of conditions normally experienced during the wet season in the Torres Strait area between October and April. The terminal area forecast for Horn Island, valid from 0600 to 1800, indicated light showers of rain and a visibility greater than 10 km. Throughout the forecast period, a temporary deterioration in conditions (up to 60 minutes) was forecast due to thunderstorms, with visibility reduced to 2000 m in rain and a cloud base of 800 ft. Approximately 40 minutes before he departed Badu Island, the pilot received a telephone call from the senior base pilot. The senior base pilot had flown from Badu Island to Horn Island that morning and advised him of the actual weather conditions he had encountered, including 20 minutes holding east of Horn Island while awaiting a rain shower to move from over the aerodrome.

Witnesses reported that the weather conditions at Horn Island aerodrome between 1230 and 1245 were less than visual meteorological conditions. Heavy rain had reduced visibility to less than 100 m. One witness reported seeing lightning to the north of the aerodrome. A Bureau of Meteorology assessment of weather conditions for the area east of Horn Island at the time of the occurrence indicated that the generally low overcast cloud contained embedded thunderstorm cells, with associated heavy rain and a cloud base less than 1,000 ft. The recorded rainfall intensity was heaviest between 1230 and 1300. Weather conditions at Horn Island at the time of the occurrence were described by witnesses as being the most severe seen that season.

The pilot held a Commercial Pilot (Aeroplane) Licence and a valid Class 1 medical certificate. He had obtained his commercial pilot licence in September 2000 and qualified for a command multi-engine instrument rating in April 2001. The pilot's logbook was not found. A compilation of flight time records showed that at the time of the occurrence the pilot had between 270 and 290 hours total flying experience that included approximately 45 hours on type. The company did not require the pilot to maintain IFR currency there was no evidence that the pilot had met recency requirements for instrument flight. The pilot was not reported to be suffering from any physiological condition that may have affected his capability as a pilot. He had been off duty for the two days prior to commencing duty on the morning of the accident.

In July 2001 the pilot moved to the Torres Strait area and gained some occasional flying experience with another operator. In November 2001 the pilot commenced employment with the operator he was working for at the time of the accident as a VFR charter pilot on C182 and C206 aircraft. On 19 November 2001, before commencing operational duties, the pilot had flown a familiarisation flight under supervision of the senior base pilot. On 27 November he had demonstrated proficiency on the C182 in normal and emergency procedures to an approved company check pilot. That flight of one and a half hours also incorporated a short area familiarisation. The pilot was then certified as competent to conduct company charter flights. On 1 December 2001 he flew the C206 while acting in-command under the supervision of the senior base pilot.

The flight was being conducted under the VFR, at an altitude that required the aircraft to remain clear of cloud, and with a minimum flight visibility of 5,000 m. The operator's operations manual instructed pilots to consider uplifting additional fuel for diverting or holding when the forecast indicated elements of weather below the minimum required for the flight. The pilot had departed with ample fuel reserves for holding or diverting. Company pilots reported that diversions and holding, due to rain showers and associated poor visibility, were not unusual during the wet season. The pilot had broadcast his intention to hold until weather conditions improved.

Although the pilot of the C206 had flown in IMC during his training he did not have any instrument flight recency and had very little exposure to tropical wet season weather conditions and its characteristic heavy rain shower activity.

The circumstances of the occurrence were consistent with a loss of control at low level and at an altitude from which recovery was not considered possible. Due to the limited information available to the investigation, the reason for the loss of control could not be determined. However, the circumstances were consistent with VFR flight into IMC.

Occurrence summary

Investigation number 200200035
Occurrence date 11/01/2002
Location 9 km E Horn Island, Aero.
State Queensland
Report release date 24/09/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 206
Registration VH-STL
Serial number U20603389
Sector Piston
Operation type Charter
Departure point Badu Island, QLD
Destination Horn Island, QLD
Damage Destroyed

Messerschmitt BK117 B-2, VH-BKZ

Summary

The pilot of a BK117 helicopter reported that while in a gentle climb at about 4,600 feet during a post maintenance test flight, the helicopter suddenly pitched nose-up. The indicated airspeed decreased to zero and the helicopter then pitched nose-down to a slightly inverted attitude. After descending about 2,000 feet, the pilot regained control and landed safely.

Inspection of the helicopter systems by the company maintenance personnel could not find any reason for the sudden loss of control.

A Bureau of Meteorology area forecast, issued on the day of the incident, indicated severe turbulence below 10,000 feet. The forecast also included increasing westerly wind speeds ranging from 30 knots at 2,000 feet to 45 knots at 10,000 feet. The actual weather report for the area that the helicopter was operating in, indicated westerly wind speeds increasing from 35 knots at 2,000 feet to 50 knots at 7,000 feet. These conditions are conducive to mountain wave and rotor activity.

A rotor is a large air mass rotating about a substantially horizontal axis. It is generated in the lee of a mountain or sharp ridge in strong wind conditions.

The helicopter was operating on the lee side of a mountain range when the pilot experienced the rapid loss of control. It is probable that the helicopter encountered a rotor.

Occurrence summary

Investigation number 200003143
Occurrence date 17/07/2000
Location 9 km E Warragamba Dam, (VTC Check Point)
State New South Wales
Report release date 03/05/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Messerschmitt-Bolkow-Blohm
Model BK117
Registration VH-BKZ
Serial number 7213
Sector Helicopter
Operation type Aerial Work
Departure point Bankstown, NSW
Destination Bankstown, NSW
Damage Substantial

Cessna A185F, VH-TLO

Summary

The Cessna 185 (C185) aircraft had returned and landed at the departure aerodrome after completing a charter flight of approximately 90 minutes duration. The pilot reported that following a normal landing and after the tail wheel had been lowered to the runway, the aircraft nose commenced to yaw to the right. The pilot estimated that the aircraft was travelling at about 20 kts and despite applying full rudder and the use of differential braking it was not possible to regain directional control and the aircraft ground-looped. The left main gear-leg collapsed and the outboard portion of the left wing was substantially damaged when it struck the surface of the runway. The propeller also was damaged on contact with the runway. The pilot and three passengers were not injured and vacated the aircraft without assistance.

The pilot had been endorsed on the aircraft approximately one week before the accident. Although he had significant experience operating other tail-wheel equipped aircraft, he had logged only 18 hours on the C185. The majority of that experience had been accumulated while ferrying the aircraft from Moorabbin to Broome.

Following the accident, archived data from the Broome automatic weather station was retrieved from the Bureau of Meteorology. The data indicated that at the time of the accident a southerly wind was blowing with wind gusts recorded up to 11 kts. Analysis of the data indicated that the pilot could have encountered a right crosswind of up to 10 kts during the landing. That was within the aircraft manufacturer's demonstrated crosswind limit of 15 kts.

The aircraft centre of gravity was calculated to have been within published limits. However, it was close to the aft limit, thereby making directional control more difficult in the gusting crosswind conditions.

The weather conditions prevailing at the time of the accident would have made the aircraft more difficult to control, especially during the later stages of the landing roll as the aircraft slowed down and the rudder became less effective. Directional control at lower speeds becomes increasingly dependent on tail-wheel steering and the use of differential braking. The directional instability would have been further exacerbated with any sudden increase in crosswind component due to the gusty crosswind conditions.

Occurrence summary

Investigation number 200002700
Occurrence date 27/06/2000
Location Broome, Aero.
State Western Australia
Report release date 27/09/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 185
Registration VH-TLO
Serial number 18503658
Sector Piston
Operation type Charter
Departure point Broome, WA
Destination Broome, WA
Damage Substantial

Cessna 172R, VH-EWO

Summary

The pilot of the Cessna 172R had planned a private flight, with three friends, from Moorabbin via Williamstown, Laverton, Melton and Torquay before returning to Moorabbin. Before departure, the pilot arranged for the fuel load on the aircraft to be adjusted in order to ensure that the aircraft did not exceed its maximum allowable weight limit. The aircraft departed Moorabbin at about 1350 Eastern Summer Time.

Witnesses, including some with relevant aviation experience, reported seeing the aircraft conducting steep turns south of Melton township, north-east of Melton aerodrome, north of Gisborne and in the vicinity of the accident site. This information is consistent with photographs taken from the aircraft during the flight.

Radar information indicated that between 1432 and 1435, the aircraft was flown in a sequence of left turns through 360 degrees in the vicinity of the accident site. These turns were conducted at an altitude of between 1,900 ft and 2,300 ft above mean sea level (approximately 550 to 950 ft above ground level).

Witnesses reported that after completing two 360 degree left turns in the vicinity of the accident site, the aircraft headed north and adopted a nose-high attitude before entering a steep turn to the left. Most of the witnesses, including an experienced pilot, described seeing the aircraft's bank angle steepen as it passed a westerly heading and then the nose dropped such that the aircraft was heading approximately south in a near vertical, nose-down attitude. However, one witness described seeing the aircraft roll in a right-wing-over-left manoeuvre before it pitched nose-down.

One witness reported seeing the aircraft spiral to the ground however most witnesses saw it descend straight to the ground in a nose-down, near vertical attitude. Witness reports and wreckage evidence indicated that the aircraft impacted the ground heading approximately south and in a nose-down, right wing low attitude. The aircraft, which was destroyed by the impact, came to rest approximately 27 m from the initial impact point. There was no fire. The occupants received fatal injuries.

The wreckage was located in a paddock approximately 400 m north of the Gisborne-Kilmore Road, approximately half-way between Gisborne and Riddells Creek. The residence of one of the passengers was less than 1 km from the accident site. The elevation of the accident site was about 1,350 ft and Mount Macedon (3,284 ft) was 11 km to the north-north-west. The damage indicated that the engine was producing power and that the flaps were extended to approximately 10 degrees at the time of impact. The investigation did not identify any pre-existing defects that could have affected the operation of the aircraft.

Coordinated use of aileron, elevator and rudder controls will ensure that an aircraft maintains balanced flight. Discussions with the US Federal Aviation Authority (FAA) indicated that the Cessna 172 aircraft will exhibit mild stall characteristics if the aircraft stalls during balanced flight, and a pilot can regain control of the aircraft with a minimal loss of height. Most aircraft would require significantly more height above the ground to allow a pilot to recover control following a stall during unbalanced flight.

The Cessna Integrated Flight Training System Manual of Flight stated that a stall during a steep turn will result in a sharp nose and wing drop and that recovery actions must be prompt and precise.

The pilot held a private pilot licence and was endorsed on the aircraft type. He had completed spin recovery training, however the training was conducted in a different aircraft type. The pilot had accrued approximately 68 hours total flying experience. The post-mortem and toxicological examination did not identify any pre-existing conditions that could have affected the pilot's ability to fly the aircraft.

At the time of the accident the prevailing weather conditions were fine with scattered high level cloud. The Kilmore Gap automatic weather observation taken at 1430 indicated that the wind was 340 degrees at 19 kts gusting to 27 kts. The observation taken at Melbourne's Tullamarine airport at 1431 indicated that the wind was 360 degrees at 15 kts gusting to 27 kts and that the temperature was 33 degrees Celcius. During strong, gusting wind conditions such as existed at the time of the accident, hills and mountains can induce severe turbulence and downdraughts.

The aircraft was probably operating in turbulent conditions at the time of the accident, given the location of Mount Macedon upwind of the accident site. The manoeuvre described by witnesses was consistent with the aircraft stalling during the steep left turn. It is likely that the aircraft's reduced performance in the ambient temperature and the gusty and turbulent conditions contributed to the stall. In addition, the turbulent conditions would have made it very difficult for the pilot to maintain the aircraft in balanced flight during the sequence of steep turns. The loss of control following the stall and the pilot's failure to recover control in the height available was consistent with the stall occurring during unbalanced flight.

Occurrence summary

Investigation number 199905698
Occurrence date 01/12/1999
Location 6 km NE Gisborne
State Victoria
Report release date 05/04/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 172
Registration VH-EWO
Serial number 17280172
Sector Piston
Operation type Private
Departure point Moorabbin, VIC
Destination Moorabbin, VIC
Damage Destroyed

Cessna U206G, VH-EOY, Wrotham Park Aerodrome, Queensland, on 20 October 1999

Summary

The pilot of a Cessna 206 aircraft, and two passengers, were returning to Weipa from Rockhampton.

They departed Rockhampton at about 1130 Eastern Standard Time on the day before the accident, and landed to refuel at Charters Towers. Witnesses reported that the pilot seemed to be in a hurry and had stated his intention to fly to Weipa that day.

The pilot subsequently encountered severe smoke haze during the flight. Reduced visibility in the smoke haze made visual navigation difficult. Shortly before last light, the pilot saw an airstrip at the pastoral property "Wrotham Park" and landed the aircraft. The pilot believed he had landed at "Bellvue" until he was informed of the correct location. The manager of "Wrotham Park" provided food and overnight accommodation for the pilot and passengers.

At first light the following morning, the pilot taxied the aircraft for take-off from runway 24. While the aircraft was taxiing, the station manager noticed that a bag belonging to one of the aircraft occupants had been left behind. He drove out to the aircraft and handed the bag to the pilot, who had left the aircraft to collect it. Soon after, the pilot began the take-off.

The aircraft was heard to take-off, followed by the sound of impact.

Examination of the wreckage and assessment of the flight path and impact sequence determined that shortly after lift-off the aircraft yawed and rolled to the left, and began to descend. The leading edge of the left wing struck a powerline 8 m above the ground and about 100 m south-east of the runway centreline. The aircraft then cartwheeled through the top of a building, and its right side struck the ground while travelling slowly rearwards. It came to rest on its right side, about 5 m from the building and about 130 m south-east of the runway centreline. The passengers, who occupied the right seats of rows one and two, were seriously injured. The pilot was fatally injured.

One of the passengers later recalled hearing the stall warning activate shortly after lift-off.

The right wing had been severed and the windscreen shattered; however, the cockpit and cabin were almost intact. The wreckage examination did not reveal any pre-impact technical defect that may have contributed to the accident. Tests on fuel removed from the aircraft tanks found it to be free of the contaminant ethylene diamine.

Rescuers reported that the pilot was not restrained by a seat belt when they arrived at the accident site.

Civil Aviation Safety Authority records indicated the pilot's medical certificate was current. The autopsy and toxicology analysis on the pilot did not reveal any pre-existing medical condition that may have contributed to the accident.

The airfield at Wrotham Park was unlicensed. The field was 500 ft above mean sea level, and consisted of a single runway, 915 m in length, designated 06/24. The surface was gravel and was in good condition at the time of the accident. There were no obstructions affecting the approach or departure flight paths in either direction.

The Bureau of Meteorology assessed the weather conditions at the time of the accident as fine with a light breeze of less than 5 kts from the north-north-east. Visibility was assessed as good but with a small chance of patches of fog. Visibility in fog, if present, was assessed as approximately 500 m.

The pilot had flown about 22 hours in the aircraft, having purchased it 6 weeks before the accident. He had no prior experience on the aircraft type. The runway at Wrotham Park was both the shortest, and the first gravel runway the pilot had used in this aircraft. The pilot apparently did not fasten his seatbelt after collecting the bag, indicating that he may have been under some stress, possibly because he was concerned about the delay in his return to Weipa.

Why the pilot lost control of the aircraft during the take-off could not be determined.

Occurrence summary

Investigation number 199904898
Occurrence date 20/10/1999
Location Wrotham Park, Aero.
State Queensland
Report release date 19/09/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 206
Registration VH-EOY
Serial number U20605933
Sector Piston
Operation type Business
Departure point Wrotham Park, QLD
Destination Weipa, QLD
Damage Destroyed