Cessna 210D, 21058498

Analysis

The aircraft which was seen or heard by witnesses minutes before the accident was probably UNH.

The fuel on board UNH was more than adequate for the flight.

Weather reports by witnesses confirm that non VMC existed near Woodend and over the Mount Macedon feature to an altitude of about 4,500 ft AMSL

It is probable that the pilot of UNH flew from Kyneton into worsening weather conditions near Woodend while trying to find a visual route to Moorabbin. When he realised that he could no longer track 160 deg due to cloud, he turned towards the north-east because he recalled how sunny it was to the north-east when passing Kyneton. He probably left his decision to turn away from bad weather too late and encountered cloud before or in the turn. The difference in elevation between the aircraft reportedly flying low near Woodend and the accident site strongly suggests that the pilot controlled the aircraft while climbing in cloud. He was probably aware of the general location of Mount Macedon and probably tried to out-climb the feature. The last recorded groundspeed of 77 kts was appropriate for a climb speed.

Summary

On 8 June 1998, at 0855 EST, the pilot of a Boeing 737 air transport aircraft reported receiving an emergency locator transmitter (ELT) signal about 25 NM west of Melbourne. The pilots of several other aircraft also reported hearing the emergency beacon signal on 121.5 MHZ. At 0949 the Australian search and rescue centre received the distress signal via a satellite and had a possible location in the Mount Macedon area. At 1012, VH-SAR, a dedicated search aircraft, departed Moorabbin tasked with locating the beacon using a homing device. The pilot of SAR reported that the cloud tops over Mount Macedon were about 4,500 ft. By about 1245, Cessna 210, UNH, was assessed to be the missing aircraft. UNH had been conducting a no search and rescue (NOSAR), visual flight rules (VFR) flight from Bendigo to Moorabbin. At 1302 a ground party discovered the wreckage of UNH on the north western slope of the Mount Macedon feature at a ground elevation of about 2,840 ft above mean sea level (AMSL). The aircraft had cut a 100 metre swath through tall trees in the direction of 060 degrees magnetic. Both wings and the tail plane were torn off before the fuselage impacted sloping ground.

Melbourne radar recorded only one minute 35 seconds of UNH's flight path. UNH had maintained a steady track of about 160 degrees magnetic at 122 kts groundspeed from Kyneton before turning east in the Woodend area. Shortly thereafter the aircraft turned onto an east north easterly heading before disappearing off radar. Briefly during the recorded easterly turn, the radar recorded a groundspeed of 153 kts. The groundspeed then decreased to 77 kts just before the aircraft disappeared off the radar screen. The forecast wind at the time was 180 deg (true) at 20 kts at 2,000 ft AMSL, and 170/20 kts at 5,000 ft. There was no altitude recorded for UNH on the radar tape.

A few minutes before the accident a qualified pilot, on the ground 6.5 km S of Kyneton, witnessed an aircraft meeting the description of UNH. This aircraft was flying SE at about 500 ft above ground level (AGL) just below the cloud. The weather to the north of Kyneton was clear sunshine. The cloud line was from Kyneton to the northern edge of Woodend. The Mount Macedon feature was obscured by cloud. The aircraft maintained a steady track towards Gisborne. He reported that the aircraft's engine sounded normal. He lost sight of the aircraft as it neared Woodend. At 0829 two other people heard an aircraft flying very low over their house near Woodend but they did not see it. They described the weather conditions as heavy fog to below the tops of tall trees. Another qualified pilot witnessed the weather from the ground in the Woodend area at about the time of the accident. He described the cloud as low stratus in the form of fog. He also said that Mount Macedon was not visible due to cloud coverage.

The ground level at Kyneton was about 1700 ft AMSL and at Woodend about 1900 ft, compared to about 2,840 ft at the accident site.

The Bureau of Meteorology described the weather conditions as: "Rain showers and drizzle accompanied by patchy low cloud, generally widespread on and south of the Great Dividing Range mainly east of 144 deg E, while conditions to the north were quite clear due to the drying out of the airstream". There was no cloud and excellent visibility at Bendigo and visual meteorological conditions (VMC) prevailed at Moorabbin. At Melbourne airport, 30 minutes after the accident, there were three OKTAS of cloud at 300 ft AGL, seven OKTAS at 800 ft, plus drizzle.

The 37-year-old pilot held a private pilot's licence, issued in August 1982. He was qualified to fly the Cessna 210, UNH, which he owned. He held a valid class two medical certificate with a restriction of needing vision correction to meet the near vision standard. No evidence was found that the pilot was suffering from any medical condition which could have contributed to the accident. Vision correction spectacles were found at the accident site and a taxi driver, who drove the pilot to Bendigo airport on the morning of the accident, stated that the pilot was wearing spectacles. The pilot had logged total flight time of 340 hours, comprised of 120 hours dual and 220 hours as pilot-in-command by day. He had never qualified for an instrument rating. He had logged only eight hours of simulated instrument flight time but was reported to have gained more simulated instrument flight rules (IFR) experience by practising with a safety pilot in accordance with the provisions of Civil Aviation Regulation 153. He was reported to have accrued 1.5 hours simulated IFR flight time as recently as 30 May 1998 between Mildura and Leigh Creek. His last biennial flight review was conducted on 28 May 1998. From 29 May 1998 until 8 June 1998, the pilot had logged 17 hours as pilot-in-command of UNH. He had shared the flying with another private pilot from Moorabbin to the Northern Territory to Bendigo. He was on the last leg of the return flight from the Northern Territory to Moorabbin when the accident occurred.

Late on the afternoon of 7 June 1998, the pilot, his companion pilot and two passengers had arrived at Bendigo in UNH. They refuelled the aircraft with 243 litres of AVGAS. Their intention was to continue the flight to Moorabbin that day but as there was some doubt about reaching Moorabbin before last light, the pilot elected to remain overnight at Bendigo and to continue the flight on 8 June 1998, weather permitting. For reasons unrelated to the accident, the companion pilot and one of the passengers elected to be driven by road to Melbourne on the night of 7 August 1998.

At 0644 on the morning of 8 June 1998, the pilot telephoned an Airservices Australia briefing officer and was given weather details for the proposed flight from Bendigo to Moorabbin. He did not submit a flight plan or a search and rescue time (SARTIME) to the briefing office for the flight. A flight log sheet, found in the aircraft after the accident, confirmed that the pilot had planned the flight from Bendigo to Moorabbin via Kyneton, Mount Cottrell and Point Ormond. On the recent flight legs from Victoria to the Northern Territory and return the pilot had nominated SARTIMEs to Airservices Australia.

For the trip to the Northern Territory and return to Victoria, the pilot had used his portable Garmin 195 global positioning system (GPS) to assist with navigation. He was reported to have been quite competent with its use. Another pilot, who had flown UNH in the past, using a similar portable GPS, reported experiencing erratic GPS tracking in the Mount Macedon area. However, on 30 June 1998 Airservices conducted flight test trials in the Mount Macedon area using a Gulfstream Commander 1000 test aircraft fitted with five GPS receivers. One GPS was a handheld Garmin GPS 90 with an external antenna, comparable to the GPS used in UNH. No fault was found with GPS tracking in the Mount Macedon area at the time of the trials.

The aircraft was examined at the accident site before being retrieved to Moorabbin airport where it was subjected to detailed examination. Evidence was found at the accident site that there was fuel on board the aircraft at impact. Damage sustained by the engine crankshaft confirmed that the engine was producing power at impact. No fault was found with the airframe or engine which may have contributed to the accident. Damage sustained by instruments and avionics was consistent with impact forces.

Occurrence summary

Investigation number 199802069
Occurrence date 08/06/1998
Location Mt Macedon
State Victoria
Report release date 01/02/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category VFR into IMC
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 210
Registration VH-UNH
Serial number VH-UNH
Sector Piston
Operation type Private
Departure point Bendigo, VIC
Destination Moorabbin, VIC
Damage Destroyed

Piper PA-28-181, VH-UZR

Safety Action

As a result of this accident and a later collision on Hoxton Park aerodrome, the following recommendations were issued to the Civil Aviation Safety Authority on 15 June 1999:

IR990077

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority increase the number of mandatory broadcasts to include a set of critical location broadcasts for those locations where the risk of collision is increased.

IR990078

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority extend the proposed radio requirements as outlined in the Notice of Proposed Rulemaking (NPRM9702RP) to include both licensed aerodromes and any unlicensed aerodrome into which fare-paying passenger services operate.

IR990079

The Bureau of Air Safety Investigation recommends that the Civil Aviation Safety Authority amend current procedures/airspace for aircraft operating into and departing from Hoxton Park in order to reduce the potential for further aircraft collisions.

Significant Factors

  1. The pilot of the Archer was unaware of the presence of the Tomahawk and subsequently did not see that aircraft in time to avoid a collision.
  2. The pilot of the Tomahawk did not see and avoid the Archer.
  3. The CTAF requirement for only one broadcast from an approaching aircraft reduced the possibility for a pilot to receive location-specific information about another conflicting aircraft, thus reducing the opportunity of sighting that aircraft.

Analysis

The investigation was unable to determine the flight path of the Tomahawk after it had departed from Bankstown on a VFR flight to the training area and Hoxton Park earlier in the morning. The damage to the right wing of the Tomahawk, together with witness observations, indicated that the Archer had approached from the rear right quadrant of that aircraft. The location of the collision point, and the respective tracks of the two aircraft, make it likely that the Tomahawk had been flying parallel to runway 34 on the non-active side of the circuit and that it had commenced to, or was about to, turn left to join the crosswind leg.

The investigation was also unable to determine if the pilot of the Tomahawk had made the required CTAF broadcast approaching Hoxton Park. There CTAF frequency was not recorded nor was it required to be recorded. The pilot may have made the required CTAF broadcast before the pilot of the Archer had changed to that frequency. Nevertheless, the pilot of the Tomahawk should have heard the pilot of the Archer reporting inbound to Hoxton Park and been aware of the approximate location of that aircraft. Had the pilot of the Tomahawk acknowledged the broadcast from the pilot of the Archer, the situational awareness of that pilot would have been enhanced, making his efforts to sight and avoid other aircraft more effective.

Summary

A Piper Archer and a Piper Tomahawk collided at an altitude of about 1,200 ft as the Archer was tracking to enter the crosswind leg for a landing on runway 34 at Hoxton Park aerodrome. The collision occurred in fine and clear conditions, about 0.5 NM east of the upwind end of the runway. Both aircraft were being flown under the visual flight rules (VFR). The pilot of the Archer was able to maintain control of his aircraft and make a successful approach and landing on runway 34, although the nose landing gear had been substantially damaged in the collision. The aircraft was stopped on the runway, resting on the collapsed nose landing gear.

The collision was observed by witnesses who reported that the Tomahawk immediately spiralled down and crashed into an unoccupied house in a suburban housing area. Both occupants were fatally injured. There was no fire and there were no injuries to persons on the ground.

Operations at Hoxton Park are not directed by air traffic control services and rely on pilots seeing and avoiding other aircraft. The aerodrome is located within a common traffic advisory frequency (CTAF) area, extending to a 2 NM radius from the aerodrome and to a height of 1,700 ft. Pilots of radio-equipped aircraft intending to operate within that area are required to make a radio broadcast when approaching the CTAF boundary. That broadcast must include aircraft callsign and type, position, level, and intentions. No other radio report is required prior to landing.

The pilot of the Archer reported that he had made a broadcast on the CTAF when 3 NM inbound to Hoxton Park. He then descended to 1,200 ft and tracked to join the crosswind leg for runway 34, making a "joining crosswind" broadcast while still approaching the upwind end of the runway. He saw another aircraft turning onto crosswind after taking off from runway 34, and a second aircraft on the downwind leg. At about that time, he saw to his left the underside of an aircraft turning to the left, about 50 m away, but skidding towards him at about the same altitude. The pilot of the Archer said he started to turn to the right to avoid a collision, but there was a bang just moments after he first saw the aircraft. He briefly glanced back and saw the aircraft spiralling down to the left. It appeared to him that the outboard end of the right wing of the other aircraft was bent upward at about 45 degrees and that the aircraft appeared to be totally out of control. As he was concerned for the safety of his own aircraft, he concentrated on landing as soon as possible. At no stage prior to the accident was he aware of the presence of the Tomahawk.

Investigation of the wreckage of the Tomahawk indicated that the engine had been torn out during the impact with the house. There was major disruption to the aircraft structure and cockpit area. Small sections from the right wing were scattered about the immediate neighbourhood. The cockpit instruments and controls were too severely damaged to provide any useful information. The very high frequency radio was selected to the CTAF frequency. There was no evidence of any pre-existing defects or abnormalities with either aircraft that may have contributed to the accident.

A metallurgical examination of a section of the right outboard wing from the Tomahawk revealed that a propeller blade of the Archer had first cut through the wing-tip plastic moulding near the trailing edge. The propeller had then cut through the wing at about the mid-chord area before finally striking the leading edge. The action of the propeller blades striking the wing resulted in disruption of the wing structure, with an associated upward bending of the outer section of the wing.

Occurrence summary

Investigation number 199802022
Occurrence date 06/06/1998
Location 2 km NE Hoxton Park, Aero.
State New South Wales
Report release date 24/12/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Airborne collision
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-28
Registration VH-UZR
Serial number 28-8190154
Sector Piston
Operation type Private
Departure point Hoxton Park, NSW
Destination Hoxton Park, NSW
Damage Substantial

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-38
Registration VH-FTX
Serial number 38-79A0268
Sector Piston
Operation type Private
Departure point Bankstown, NSW
Destination Bankstown, NSW
Damage Destroyed

Boeing 737-376, VH-TAI

Safety Action

As a result of this investigation, and a number of similar occurrences, the Bureau of Air Safety Investigation issued a report (B98/90) of an investigation of systemic issues at the Sydney Terminal Control Unit. Nine recommendations were made in the report, the following four of which are considered valid for this investigation:

"R980157

Airservices Australia review the application of the "teams" concept within the Sydney Terminal Control Unit to ensure that teams are resourced appropriately and that there is an ongoing commitment to the provision of adequate training in order to achieve a high level of controller proficiency and standardisation."

"R980158

Airservices Australia ensure that adequate refresher training is undertaken by controllers in order to provide for high levels of controller proficiency and standardisation and so that the integrity of safety cases, in which refresher training is deemed to be a mitigating strategy for identified hazards, is maintained."

"R980159

Airservices Australia reassess the human factor hazard analysis for both Stage One and Stage Two of the LTOP safety cases so that the mitigating strategies applied to identified hazards adequately allow for the fundamental limitations of human performance. In reassessing this hazard analysis, BASI recommends that Airservices Australia seek the assistance of human performance expertise."

"R980160

Airservices Australia consider restructuring the current roster operating in the Sydney Terminal Control Unit to ensure that contemporary fatigue management research is translated into meaningful duty hour regulations. In any restructure of the roster, BASI recommends that Airservices Australia expand its absentee management program to include individuals who expose themselves to the risks of fatigue by participating in excessive amounts of overtime and/or emergency duty."

Summary

Sydney airport and associated airspace was being operated in accordance with Mode 9 of the Long-Term Operating Plan. A Boeing 737 (B737) departed runway 34R for Melbourne and was cleared initially to 5,000 ft on a MARUB ONE standard instrument departure (SID), with a Wollongong transition. The SID required the crew to intercept and track via the 075 Sydney VOR radial to 15 NM (waypoint MARUB), and to then turn right and track 144 degrees until passing 9,000 ft.

At the same time, another B737 inbound to Sydney on a CHEZA THREE standard arrival route (STAR) for a landing on runway 34R had passed waypoint WHALE, located 20 NM east of Sydney, and was maintaining 7,000 ft in accordance with its clearance.

The Departures South controller cancelled the 5,000 ft altitude restriction for the departing B737 and issued a clearance for the aircraft to climb to Flight Level 280. The 5,000 ft restriction would have assured separation with the inbound B737. When the altitude restriction was removed, the controller relied on monitoring the flight paths of both aircraft and intervening, if necessary, to maintain separation.

When the departing B737 turned right to track 144 degrees in accordance with the SID, there was a breakdown in separation between the two aircraft. Separation was reduced to 2.5 NM horizontally and 500 ft vertically, whereas the required standard was either 3 NM or 1,000 ft. Traffic information was passed to the crew of the departing B737, who sighted the other B737 while passing behind it.

The Departures South controller was relatively inexperienced, having held a control rating in the Sydney Terminal Control Unit for only three weeks. The controller was distracted from the monitoring role by coordination activities with Bankstown control tower, and by radio transmissions to other aircraft. The controller also considered himself to have been fatigued as a result of local rostering practices.

Occurrence summary

Investigation number 199802135
Occurrence date 12/06/1998
Location 28 km E Sydney, (VOR)
State New South Wales
Report release date 18/06/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-TAI
Serial number 23483
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Melbourne, VIC
Damage Nil

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration FODGX
Sector Jet
Operation type Air Transport High Capacity
Departure point Noumea, New Caledonia
Destination Sydney, NSW
Damage Nil

Boeing 737-33A, VH-CZU

Safety Action

As a result of this investigation, and a number of similar occurrences, the Bureau of Air Safety Investigation undertook a systemic investigation into factors underlying air safety occurrences in Sydney Terminal Area airspace and issued report B98/90 on 18 August 1998. Nine recommendations were made in the report; the following three were considered relevant to this investigation.

R980157

"The Bureau of Air Safety Investigation recommends that Airservices Australia review the application of the "teams" concept within the Sydney Terminal Control Unit to ensure that teams are resourced appropriately and that there is an ongoing commitment to the provision of adequate training in order to achieve a high level of controller proficiency and standardisation."

R980158

"The Bureau of Air Safety Investigation recommends that Airservices Australia ensure that adequate refresher training is undertaken by controllers in order to provide for high levels of controller proficiency and standardisation so that the integrity of safety cases, in which refresher training is deemed to be a mitigating strategy for identified hazards, is maintained."

R980159

"The Bureau of Air Safety Investigation recommends that Airservices Australia reassess the human factor hazard analysis for both Stage One and Stage Two of the Long Term Operating Plan safety cases, so that the mitigating strategies applied to identified hazards adequately allow for the fundamental limitations of human performance. In reassessing this hazard analysis, BASI recommends that Airservices Australia seek the assistance of human performance expertise".

The following responses were received from Airservices Australia on 16 November 1998:

[R980157]

"A recent review of Sydney ATS has resulted in a "spill" of all management positions and a subsequent recruitment program which will be completed by 16 November 1998 to coincide with the Airservices' Business Transformation program.

The first step in this review has been to ensure that the management structure of the facility can operate effectively and that appropriate skills are available within the team. The manner in which the teams operate is the subject of a concurrent review process.

In support of these reviews, a consultant has completed a wide ranging review of supervision within air traffic services and its application within Teams.

Recommendations from these studies will be introduced into the Sydney rostering committee deliberations examining a better framework for TCU rosters. Sydney ATS management plan to introduce a revised roster in the TCU by 1 February 1999.

Team Leader training is recognised as vital to the success of teams and during October and November all Team Leaders will complete a series of Human Factors and Team Resource training modules. To further ensure that Team Leaders are better equipped to perform their duties a specific training programme for each Team Leader will be developed by 22 December 1998".

Response classification: CLOSED - ACCEPTED

[R980158]

"Airservices provides familiarisation training in various forms before the introduction of new procedures and to maintain controller skill levels. This ongoing programme has been augmented by an additional period of refresher training which all TCU controllers will undertake during the remainder of this year".

Response classification: CLOSED - PARTIALLY ACCEPTED

[R980159]

"The LTOP Stage One and Stage Two Safety Cases have been subject to review by independent experts in the field as well as being the subject of a number of post implementation reviews. Recommendations arising from those reviews have been progressively evaluated and applied as appropriate.

Airservices will consider augmenting its review processes with human factors expertise in future".

Response classification: OPEN

Significant Factors

  1. Appropriate separation assurance techniques were not implemented by either controller.
  2. Coordination between controllers was ineffective.

Analysis

The investigation revealed that each controller had different expectations of the intentions of the other. The DN controller had expected the AN controller's Metro would continue on its current track, and that the two aircraft tracks would cross. Conversely, the AN controller expected to keep his aircraft inside the track of the departing B737. Neither the coordination nor communication between controllers was effective. The unexpected turn onto downwind by the Metro, towards the B737, reduced the distance available for the B737 to climb safely above the Metro. The DN controller attempted to stop the B737 at 6,000 ft, but that instruction, combined with the rate of climb of the aircraft, was unable to prevent a breakdown of the vertical separation standard.

Summary

A Boeing 737 (B737) departed runway 34R on an ENTRA ONE standard instrument departure (SID), on climb to 5,000 ft. Immediately after departure, the crew established communication with the Departures North (DN) controller.

A Metro, inbound to Sydney from the north, was being radar vectored for a wide downwind leg to runway 34R, maintaining 7,000 ft, having earlier been diverted to the east for sequencing with preceding slower traffic. Although this track placed the aircraft in DN airspace, the Metro crew, as instructed, remained in communication with the Approach North (AN) controller. On request, the AN controller had been granted approval by the DN controller for the Metro to transit through the DN controller's airspace. The weather conditions were fine, and runway 34 parallel operations had been in progress for 18 minutes.

The DN controller had elected to provide vertical separation between the two aircraft by issuing instructions that would enable the B737 to climb above the Metro. This plan was coordinated with the AN controller. A clearance to climb to flight level 280 was issued to the crew of the B737, with a request to expedite climb through 8,000 ft. As this transmission was being made by the DN controller, the AN controller instructed the crew of the Metro to turn right onto a heading of 170 degrees for the downwind leg.

Subsequently, it was perceived by the DN controller that the effective climb performance of the B737 would be insufficient to ensure that the required separation standard of 1,000 ft vertically or 3 NM horizontally between the two aircraft would be maintained. The controller amended the clearance and instructed the crew of the B737 to maintain 6,000 ft. However, because the B737 was climbing at 4,500 ft/min, it had climbed to 7,000 ft before the crew were able to stop the climb and commence descent. As there was now less than 3 NM between the aircraft, both controllers passed traffic information to the crew of their respective aircraft. The crew of the B737 sighted the Metro, passing beneath that aircraft with approximately 600 ft of vertical separation. The crew of the Metro did not sight the B737.

During the two years since the AN controller had been rated, the system in which he was working had changed significantly due to noise-sharing arrangements at Sydney (Kingsford-Smith) Airport. The controller's training and endorsement had been undertaken and achieved in a less complex environment. The unpredictability of the more complex arrangements required a high degree of coordination for which the controller had not been adequately trained.

Conversely, the DN controller had gained his initial rating in the days when air traffic control was more reactive and dynamic than the present more regulated system. In the previous, less structured air traffic control environment that the controller had been trained in, there had been undocumented procedures that everyone was aware of. Those procedures were passed on from controller to controller as skills were developed and refined. The DN controller expected that his intentions and plan would be readily interpreted by the AN controller.

Occurrence summary

Investigation number 199801905
Occurrence date 29/05/1998
Location 22 km NE Sydney, Aero.
State New South Wales
Report release date 16/09/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-CZU
Serial number 27267
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Coolangatta, QLD
Damage Nil

Aircraft details

Manufacturer Fairchild Industries Inc
Model SA227
Registration VH-NEK
Serial number AC-615B
Sector Turboprop
Operation type Air Transport Low Capacity
Departure point Tamworth, NSW
Destination Sydney, NSW
Damage Nil

Boeing 747-312, VH-INH

Safety Action

As a result of this investigation, the Bureau of Air Safety Investigation issued two safety recommendations regarding the regulation and use of seatbelts by passengers:

IR980222 was issued to the Civil Aviation Safety Authority, recommending that a regulatory requirement be developed for passengers to wear seatbelts at all times when seated.

IR980223 was issued to all Australian airlines, recommending that they introduce a company requirement for passengers to wear seatbelts at all times when seated.

Summary

A Boeing 747, while en-route from Kansai to Brisbane at Flight Level 370, encountered unforecast clear air turbulence, which lasted for about 10 seconds. One flight attendant and 16 passengers suffered minor injuries. The aircraft sustained minor damage to internal ceiling panels in the rear cabin. A number of panels which contained the passenger overhead lighting and air vent controls were dislodged. However, the overhead cabin baggage lockers remained intact during the event.

An examination of the aircraft flight data recorder indicated that the turbulence had been preceded by a period of smooth air, which lasted for 40 seconds. The data revealed that during the event, the aircraft had sustained a positive G-loading of about 1.55, and a negative loading of about 0.21. The aircraft also deviated 250 ft above, and 30 ft below, its assigned flight level. No anomalies were recorded that might have suggested a malfunction of the aircraft systems.

A forecast for the area indicated no significant weather, although a subsequent analysis of relevant satellite images revealed isolated cumulo-nimbus clouds. A report by the Bureau of Meteorology suggested that turbulence above those clouds may have been responsible for the occurrence.

During the flight, the pilot in command had recommended that the passengers, when seated, should keep their seatbelts fastened. The pilot in command subsequently advised that prior to the turbulence, flight conditions had been smooth. The night was dark, and the aircraft weather radar did not indicate adverse weather. Consequently, the crew did not illuminate the seatbelt signs.

A flight attendant reported that, at the time of the occurrence, a number of passengers did not have their seatbelts fastened and were injured when they were thrown from their seats. Some of those passengers had refused to fasten their seatbelts when seated. One of the passengers was injured when a piece of ceiling panel fell on him. A flight attendant was injured when she was thrown to the ceiling and then to the floor. Five passengers admitted to hospital were later released the same day.

In order to alert other crews in the area, the airline's standard operating procedures required the crew to report severe turbulence to air traffic services. However, flight service records indicated that this did not occur.

Occurrence summary

Investigation number 199801888
Occurrence date 27/05/1998
Location 1438 km NE Port Moresby, Aero.
State International
Report release date 04/05/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level Minor

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration VH-INH
Serial number 23026
Sector Jet
Operation type Air Transport High Capacity
Departure point Kansai, JAPAN
Destination Brisbane, QLD
Damage Minor

American Aircraft Corp AA-5A, VH-IJI

Analysis

As there was no evidence to indicate a control or power problem with the aircraft, the pilot may have intentionally descended to avoid cloud on track. Such action would have demanded that the pilot fly and navigate the aircraft at low level in adverse weather and terrain. This situation would have placed very high demands on the pilot's judgement, handling and perception.

The Human Factors specialist assessment of the pilot's known workload concluded that the pilot was probably suffering from fatigue. A level of fatigue may have influenced the pilot's judgement and decision-making ability. The fatigue, together with the effects of the prescription drugs detected in the pilot's blood, may have impaired his ability to make appropriate decisions during the flight or to recognise a dangerous situation developing. The pilot should have been aware of the potentially serious hazards of using these medications in the flight environment.

CONCLUSION

It is likely that the pilot descended due to low cloud and rain showers in order to maintain enroute visual reference with the ground. Fatigue and the presence of prescription drugs may have affected the pilot's ability to safely operate an aircraft.

Summary

Earlier on the day of the accident the pilot had flown the aircraft to Stanthorpe before returning to Casino at about 1100 EST. He had refuelled the aircraft with approximately 60 litres of Mogas (automotive fuel) immediately prior to departure at about 1250. The aircraft was approved to operate on Mogas.

The last confirmed radio transmission from the pilot after he departed Casino was at 1332 when he reported to Air Traffic Services (ATS) that he was 62 NM from Archerfield, maintaining 4,500 ft. A search was mounted for the aircraft after it was reported overdue on the flight to Archerfield. The following two days of the search were hampered by low dense cloud in the area. Several pilots of overflying aircraft reported hearing transmissions from an emergency locator transmitter in the area of Mt Chingee, near the Queensland-New South Wales border.

Searchers located the wreckage of the aircraft early on the third day of the search, at approximately 2,500 ft AMSL, in densely wooded terrain on the slopes of Mt Chingee. The pilot did not survive the accident. The area where the wreckage was located was known to be a popular poor weather route for VFR traffic through the area.

The Bureau of Meteorology analysed the weather conditions in the area of Mt Chingee on the day of the accident. The analysis indicated that low cloud and probably precipitation would have prevailed at the time of the accident. Residents in the area reported weather conditions consistent with the Bureau of Meteorology analysis.

The Bureau did not conduct an on-site examination for this investigation. An assessment of the aircraft wreckage was carried out using police photographs and video footage. The following assessment is based on the photographic and documented evidence. The aircraft attitude at impact and the damage sustained by the airframe and propeller suggest that the aircraft was in near level flight when it first struck trees. This suggests it was probably under control. The majority of the airframe was severely disrupted by impact forces. The type of torque twisting of both propeller blades and the manner in which the propeller hub separated from the engine, indicate that the engine was developing significant power at impact. The aircraft had a current Maintenance Release that showed no outstanding maintenance requirements.

The last altitude and position report given by the pilot, placed the aircraft at 4,500 ft, approximately 7 NM or about 3 minutes flight time from the accident site. The site was approximately 2,500 ft AMSL.

The pilot usually kept his personal logbook and the aircraft records in the aircraft. None of these records were recovered for examination. Records held by the Civil Aviation Authority show that he held a Private Pilot Licence. He did not hold an instrument rating. His total aeronautical experience was approximately 650 hours. He held a night VMC rating however, it could not be established if the pilot ever exercised the privileges of the rating.

The investigation established that the pilot commonly worked long hours in demanding employment. A Human Factors specialist assessed the pilot's known workload. The specialist advised that the pilot was likely to have experienced sleep deprivation and high workload in the two days preceding the accident. When these factors are combined, fatigue, whether of an acute or a chronic nature, will eventually be experienced. The effects of fatigue on performance vary from individual to individual and may include poor judgement and decision making, increased reaction times, mental haziness or lethargy, and a general decrement in psychomotor performance.

The investigation sought the assistance of a specialist in Aviation Medicine for the interpretation and analysis of the pilot's post-mortem report toxicological results which indicated the presence of prescription drugs. This was done to determine the possible effects these drugs would have on the pilot's ability to safely operate an aircraft. Prescription drugs used alone or in combination may seriously interfere with an individual's ability to safely operate an aircraft, particularly as a single pilot in bad weather. The pilot should have been aware of the potentially serious hazards of using these medications in the flight environment. A review of the CASA aircrew medical examinations of this pilot could find no evidence of any recorded medical problems warranting the use of the drugs described in the toxicology report.

Occurrence summary

Investigation number 199801517
Occurrence date 03/05/1998
Location Mt Chingee, near Rathdowney
State Queensland
Report release date 01/06/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer American Aircraft Corp
Model AA-5
Registration VH-IJI
Serial number AA5A-0432
Sector Piston
Operation type Private
Departure point Casino, NSW
Destination Archerfield, QLD
Damage Destroyed

Cessna 210R, VH-IOR

Summary

The pilot of the Cessna 210 was to be accompanied by five passengers on a flight from Merimbula to Albury. A flight notification was submitted by telephone to the Airservices Australia regional briefing office which indicated that the aircraft would be operating under the instrument flight rules and would track to Albury via Cooma and Corryong at 10,000 ft. The pilot obtained a pre-flight briefing from the Airservices Australia automated pilot briefing system (AVFAX) and selected a product code that provided weather forecasts and operational information for aviation meteorological forecast Area 21.

The Area 21 forecast was applicable for the sector of the flight from Merimbula to approximately 30 NM east of Corryong. At that point the aircraft would enter the eastern part of the adjoining Area 30. The pilot did not order any briefing products for Area 30 from the AVFAX system, which would have included information for his destination aerodrome. No information was requested from the briefing officer during the telephone submission of the flight plan and it was not possible to establish if the pilot had obtained an Area 30 or destination aerodrome forecast from alternative briefing sources. It was reported however, that prior to departing Merimbula the pilot had telephoned a family member to inquire about the prevailing weather conditions in Albury.

The forecast for Area 21 indicated that there would be significant cloud extending up to 8,000 ft over the Snowy Mountain ranges, with some isolated tops to 11,000 ft in the far south of the area. Moderate icing was forecast in the tops of cumulus cloud. The freezing level was forecast to be at 6,000 ft in the south. A hazard alert had been issued for occasional severe turbulence below 10,000 ft over, and to the east of, the ranges. A westerly wind of 30 knots was forecast at the pilot's intended cruise level.

The conditions forecast for Area 30 were similar to those for Area 21. Broken cumulus cloud tops were forecast to extend to 10,000 ft with broken altocumulus/altostratus from 8,000 to 20,000 ft in the east of the area. Moderate icing was forecast in cloud above the freezing level and areas of isolated severe turbulence near the ranges below 10,000 ft. The cloud forecast for Area 30 indicated that flight along the proposed route could possibly require flight in cloud, above the forecast freezing level. The aircraft was not equipped for flight in known icing conditions.

The aircraft departed Merimbula at 1200 Eastern Standard Time and the pilot reported to flight service that he was tracking for Cooma and was on climb to 10,000 ft. Although the aircraft would not enter controlled airspace until just before Albury, an en-route radar controller would provide the pilot with a flight information service from 30 NM south-east of Cooma. The pilot was issued with a transponder code for radar identification and was given frequency change instructions. Flight service also passed information to the pilot on a hazard alert that had been issued for Albury aerodrome, due to cloud at 1,200 ft above ground level, which had not cleared as had been forecast.

As the aircraft approached top of climb it appeared on the en-route controller's radar display. The radar return from the aircraft's transponder indicated that the aircraft had levelled off at 10,100 ft and its ground speed was observed to steadily increase from 78 knots and then stabilise for a short period at approximately 140 knots. The ground speed was then observed to commence a gradual reduction, which was accompanied by some minor variations in the radar-recorded transponder altitude.

At 1233 the pilot reported overhead the Cooma non-directional beacon at an altitude of 10,000 ft. The radar-derived groundspeed was reducing through 110 knots at this time and continued to reduce at a constant rate, before stabilising at approximately 95 knots.

When the aircraft was 8 NM northwest of Cooma the controller observed the pilot to be conducting what appeared to be a descending turn to the right. The controller requested that the pilot confirm that aircraft operations were normal and the pilot responded that "operations are not normal" and indicated that he was diverting to Cooma for a landing. The recorded radar data indicated that the initial stage of the descent was uneven, with erratic rates of descent and some increases in altitude. The final part of the descent was conducted at a stable rate.

A short time later, the pilot advised the controller that he was tracking 310 degrees at an altitude of 7,500 ft and that the descent had been necessary due to an accumulation of airframe ice. The pilot indicated that he had "unloaded" the ice and commented that he was able to get over the cloud at Kosciusko without going "to that height". The investigation was unable to determine what the comment "to that height" meant.

The aircraft was observed on radar to be flying a steady north westerly ground track, at a constant altitude of 7,600 ft. The groundspeed stabilised at approximately 145 knots before radar contact with the aircraft was lost at 1243. The controller informed the pilot that radar contact with his aircraft had been lost and nominated a time for the pilot to make an operations normal report.

At 1248 the pilot reported that he was tracking direct to Corryong and had commenced a climb to 10,000 ft. The pilot confirmed that he was tracking north of his original track and again stated that the ice had been "unloaded". He also indicated that the cloud conditions looked much better about 5 or 10 miles north of his planned track.

An unidentified person made several incomplete transmissions, which appeared to be inter-cabin type conversation, on the area VHF frequency. The background noise from these transmissions very closely matched the background noise contained in other reports made by the pilot. At 1252 the person was heard to say, "... you have a standing wave? Well, it's ...".

The aircraft reappeared on the controller's radar display at 1253 flying a south-westerly track, climbing through a transponder-indicated altitude of 8,400 ft with a ground speed of approximately 45 knots. At 1254, as the aircraft climbed through 8,800 ft, the climb performance appeared to reduce significantly. The transponder return stabilised at an altitude of 9,000 ft, although the ground speed did not increase as would normally be expected if the aircraft had levelled out at this altitude. The aircraft was then observed to take up a more westerly track and appeared to be tracking direct for Corryong.

The aircraft disappeared from the controller's radar display at 1257. The last return received from the transponder indicated an altitude of 8,800 ft with a radar-derived ground speed of 47 knots. During the last 20 seconds of recorded data, the transponder indicated a descent of approximately 200 ft, without any significant increase in groundspeed.

Prior to disappearing from radar the aircraft was flying directly towards Mt Jagungal (6,760 ft AMSL) and was operating downwind of the mountain. Meteorological conditions were conducive to the formation of mountain waves and this type of activity was evident on meteorological satellite imagery that had been taken a short time before the accident. Mountain waves, also known as standing waves are characterised by "waves" of ascending and descending air in the lee of a mountain range, and can be associated with moderate to severe turbulence. These waves can extend for significant distances downwind of the range and can pose a serious hazard to the safety of light aircraft.

Several witnesses had seen or heard the aircraft shortly before the accident. One witness saw the aircraft fly overhead, making slow progress towards Mount Jagungal. The engine sounded as if it was operating normally and could still be heard even after visual contact with the aircraft was lost. The witnesses described a low layer of broken cloud close to the ground, with the aircraft apparently flying in clear air above this cloud. Several persons on the ground reported that the aircraft noise increased in pitch, as if in a dive, shortly before the sound of an impact. This account of engine operation to the point of impact indicates that there was no significant reduction in engine power during the final stages of the flight.

The following morning the aircraft wreckage was located at a position that was consistent with the last recorded radar data. It had impacted the ground at high speed, in a near vertical attitude, and in an apparent left turn. Impact forces had destroyed the aircraft, and all six persons on board sustained fatal injuries. The accident site was located 3.4 NM directly east of Mt Jagungal, approximately 5,700 ft above mean sea level.

The impact crater contained the engine and the forward section of the fuselage. The remainder of the wreckage was located a short distance away. Examination of the wreckage did not reveal any defect that could have affected the operation of the aircraft prior to impact.

The pilot held a valid single-engine command instrument rating. He had satisfactorily completed the requirements for the renewal of his rating on 11 April 1997. The pilot had logged a total of 2904.4 hours aeronautical experience, of which approximately 580 hours had been flown in Cessna 210 type aircraft. He had regularly operated his aircraft as pilot in command during the previous 12 months and had frequently flown between Albury and Merimbula under instrument flight rules. The passenger who was believed to have been in the co-pilot's seat held a private pilot licence, which was valid for flight under the visual flight rules.

Colleagues of the pilot reported that he was familiar with the use of the systems on-board the aircraft and would normally use the autopilot during cruise. They stated that his usual habit was to hand fly the aircraft during climb/descent and when operating in turbulent conditions.

The pilot had completed a Class 1 flight crew medical examination on 18 November 1997, which had included a requirement for completion of a stress electrocardiogram (ECG). Although this testing did not return an abnormal result, post-mortem examination of the pilot did reveal that he was suffering severe coronary artery disease. The examining pathologist commented that the stress associated with operating the aircraft in difficult weather conditions could have precipitated a sudden deterioration in his cardiac condition, possibly resulting in a sudden medical incapacitation.

Prior to departing from Albury on the outbound leg of the flight, the aircraft had been fuelled with 200 litres of avgas. It was not possible to determine how much fuel was on board the aircraft prior to the commencement of the fuelling operation. Based on a minimum fuel quantity of 200 litres for departure from Albury, at least 70 litres of fuel is estimated to have be on board the aircraft at the time of the accident.

The aircraft departed Merimbula with sufficient fuel to complete the flight to Albury, with the recommended IFR reserves intact. As it has not been established that the pilot had obtained an aerodrome forecast for his destination, the extent to which he may have made provision for holding fuel or flight to a suitable alternate aerodrome was not determined.

The seating position of the passengers could not be positively determined due to the extent of the destruction of the cabin. Estimated pilot and passenger weights and their assumed seating positions were used to calculate the aircraft operating weight and centre of gravity position. The passenger-seating configuration to provide the optimum centre of gravity position was used in the investigation estimation. Based on these assumptions, at the time of the accident the aircraft was operating below its maximum take-off weight, with the centre of gravity in the vicinity of the published rear limit.

The pilot had regularly operated the aircraft when similarly loaded and would have been familiar with its handling characteristics. The published stalling speed (wings-level) for the aircraft at the estimated load configuration was approximately 64 knots indicated air speed (IAS). The published best rate of climb speed was 92 knots IAS.

 

Analysis

The circumstances of this occurrence are consistent with the aircraft being flown at the limit of its performance capabilities, in the prevailing weather conditions. In addition, the reported medical condition of the pilot and the stress associated with operating an aircraft in such weather conditions, requires balanced consideration of the possibility of pilot incapacitation being a factor in the accident.

The Area 21 forecast indicated that the first part of the flight could be conducted clear of cloud during the climb and cruise, with the cloud tops forecast to extend to 8,000 ft in the area through which the aircraft was flying. The recorded radar data indicates that the aircraft was not significantly affected by airframe ice on initially reaching the planned cruising altitude of 10,000 ft.

However, the aircraft did appear to encounter icing conditions as it approached Cooma. The progressive reduction in aircraft groundspeed and the minor altitude variations from the aircraft transponder are consistent with the aircraft operating in convective cloud and accumulating airframe ice. A short time later, the aircraft was observed on radar to conduct a descending orbit and the pilot indicated that he was diverting to Cooma for a landing.

It is likely that during the descent, the aircraft broke clear of cloud and the pilot considered that he was able to continue towards his planned destination. The pilot was familiar with the route sector being flown and would have been aware of the height of terrain in the vicinity. It is unlikely that the pilot would operate the aircraft in cloud, below the lowest safe altitude and continue to fly towards rising terrain.

The apparent improvement in the stability of the radar recorded descent profile also suggests that the pilot had established visual reference during the latter stages of the initial descent from 10,000 ft. The radar recorded data, particularly the groundspeed that the aircraft achieved after levelling off, supports the pilot's report of having "unloaded" the airframe ice. It is likely that the aircraft was no longer operating in cloud and was not significantly affected by airframe ice at this time. The pilot had also commented about being able to get over the cloud at Kosciusko which further suggests the aircraft was established clear of cloud at this time.

Approximately eleven minutes before the accident the pilot reported that he had commenced climbing to 10,000 ft. The aircraft subsequently reappeared on radar and was observed to take up a track that would pass directly overhead Mt Jagungal, in conditions that were conducive to the formation of mountain waves and the forecast probability of occasional severe turbulence. The reported weather conditions at the time of the accident suggest that Mt Jagungal was probably covered by cloud and the pilot may have been unaware of his proximity to the mountain peak.

Based on the reported wind direction and strength, the radar-recorded low groundspeed suggests that the aircraft was climbing at a lower-than-normal airspeed. This would have provided the pilot with a reduced safety margin above the stalling speed. The apparent reduction in climb performance as the aircraft approached 9,000 ft can be attributed to the aircraft flying into the descending air associated with mountain wave activity. Had the pilot elected to level out at this altitude, it would be reasonable to expect that a measurable increase in groundspeed would be associated with the setting of a flight attitude for straight and level flight.

The witness sighting of the aircraft a short time before the accident indicates that at this point, the aircraft was established clear of cloud, but with a broken layer of cloud below. It was not possible to determine if the aircraft was significantly affected by airframe ice at the time of the accident. The presence of any ice on the airframe would have further increased the aircraft's stalling speed and further reduced the margin for any airspeed fluctuations due to turbulence.

It is possible that while attempting to continue climb to 10,000 ft the aircraft encountered moderate to severe turbulence. The unpredictable fluctuation in airspeed could have resulted in an inadvertent stall. The aircraft departed controlled flight immediately prior to the accident and impacted the ground at high speed in a near vertical attitude, consistent with an uncontrolled spiral dive. The reason for the loss of control could not positively be established.

Furthermore, the possibility of pilot incapacitation cannot be excluded as a contributing factor in the occurrence. The reported operation of the aircraft engine to the point of impact, together with the uncontrolled nature of the descent, indicates that there had been no effective response initiated to counter the rapid descent of the aircraft.

Significant factors

  1. The planned route was over mountainous terrain, in adverse weather conditions, and at an altitude above the forecast freezing level.
  2. Moderate to severe turbulence had been forecast in the vicinity of the Snowy Mountain ranges and the meteorological conditions were conducive to the formation of mountain waves.
  3. At the time radar contact with the aircraft was lost, the pilot was attempting to climb the aircraft to an altitude of 10,000 ft and appeared to be flying it at a lower than normal climb speed. The reason for the observed loss of climb performance as the aircraft approached 9,000 ft could not be positively determined.
  4. The aircraft impacted the ground in an attitude consistent with a loss of control. The reason for the loss of control could not be established.

Occurrence summary

Investigation number 199801415
Occurrence date 26/04/1998
Location 16 km west of Eucumbene
State New South Wales
Report release date 24/09/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 210
Registration VH-IOR
Serial number 21064996
Sector Piston
Operation type Private
Departure point Merimbula, New South Wales
Destination Albury, New South Wales
Damage Destroyed

In-flight break up Rans S6, 15 km west of Singleton, New South Wales, on 10 April 1998

Summary

Three ultralight aircraft set out from Maitland aerodrome to fly to Narromine, with an intermediate stop at Cassilus. Near Singleton, one of the aircraft became separated from the other two, due to cloud. Radio contact was also lost. The alarm was raised and search action initiated.

The burnt out wreckage of the missing aircraft was subsequently found the following day. Both occupants had been killed. The Deputy State Coroner requested BASI assistance in the matter.

A limited investigation was carried out and found that the pilots of two of the ultralight aircraft found themselves above an area of cloud near Singleton. The lead aircraft descended through the cloud, into clear conditions below. The pilot of the second aircraft is believed to have also commenced a descent through cloud. The wreckage of that aircraft was subsequently found the following day. The circumstances of the accident were consistent with the wing structure of the aircraft failing from structural overload, following a loss of control by the pilot.

Occurrence summary

Investigation number 199801175
Occurrence date 10/03/1998
Location 15km W Singleton
State New South Wales
Report release date 14/07/1998
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category In-flight break-up
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Rans Aircraft
Model Rans R6
Registration 28-1093
Sector Piston
Operation type Sports Aviation
Damage Destroyed

Bell 47G-3B1, VH-SRQ, 10 km north of Kambalda, Western Australia

Summary

The helicopter was on a private flight from Kambalda to Kalgoorlie. Witnesses reported observing the helicopter flying at a very low height, north along the Kalgoorlie/Kambalda road immediately prior to striking a set of power lines that crossed the road. The helicopter struck the power lines in a level attitude before falling heavily onto the road.

The two passengers were able to escape the cockpit but the pilot had received fatal injuries. Although fuel was flowing from a ruptured fuel tank, there was no post-crash fire. An emergency locator transmitter (ELT) was not fitted to the aircraft. None of the helicopter's occupants carried a portable ELT.

Occurrence summary

Investigation number 199801114
Occurrence date 05/04/1998
Location 10 km north of Kambalda
State Western Australia
Report release date 02/10/1998
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Wirestrike
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Bell Helicopter Co
Model 47
Registration VH-SRQ
Serial number 6625
Sector Helicopter
Operation type Private
Departure point Kambalda, WA
Destination Kalgoorlie, WA
Damage Destroyed

Boeing 747, CCA174

Safety Action

As a result of this occurrence, the Bureau of Air Safety Investigation is investigating a perceived safety deficiency relating to the use of non-standard language by air traffic controllers during communications with flight crew from a non-English speaking background.

Any recommendation issued as a result of this deficiency investigation will be published in the Bureau's Quarterly Safety Deficiency Report.

Analysis

The instructions passed to the pilot of the B747 may have been unnecessarily complex, given that the pilot was from a non-English speaking background. The controller's transmission was not as definitive as it could have been and included extraneous, non-standard phraseology.

The response from the crew may have indicated to the controller that his transmission was not understood, in that the word "into" indicated a possible turn to intercept the localiser. In addition, the controller did not query the unintelligible transmission.

Summary

The Boeing 747 (B747) was on descent for an arrival at Sydney. The crew was being radar vectored to runway 16R for sequencing behind a SAAB 340 that was being radar vectored to runway 16L. Procedures at Sydney had different air traffic controllers responsible for directing the traffic to each of the parallel runways. The Director West controller positioned aircraft on final for runway 16R and the Director East for runway 16L.

The Director West controller was sequencing the B747 and assigned a heading of 060 degrees magnetic with an instruction to report when the crew had the field in sight.

The crew of the B747 reported the field in sight and the Director West controller told the crew to expect to go right up to the localiser, with a right turn to intercept from the eastern side. The crew acknowledged with a partly unintelligible transmission that included the words "roger" (unintelligible) "localiser into".

Almost immediately, the crew of the B747 turned their aircraft away from the assigned heading onto a heading of 110 degrees to intercept the runway 16R localiser. They advised air traffic control that they were now right heading 110. This particular heading placed the aircraft in potential conflict with the SAAB. The Director West controller instructed the crew of the B747 to maintain a heading of 060 degrees to ensure that the aircraft passed behind the SAAB. The Director East controller passed traffic information regarding the B747 to the crew of the SAAB.

Although the crew of the SAAB reported that they had the B747 sighted, radar separation between the two aircraft was reduced to 2.5 NM during the manoeuvre. The separation standard required was either 3 NM horizontally or 1,000 ft vertically. Analysis of the radar data indicated that vertical separation between the two aircraft was reduced to approximately 800 ft when the 3-NM radar separation standard was infringed.

Occurrence summary

Investigation number 199800870
Occurrence date 17/03/1998
Location 20 km NNW Sydney, Aero.
State New South Wales
Report release date 01/01/1999
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of separation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 747
Registration CCA174
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Sydney , NSW
Damage Nil

Aircraft details

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