ATSB welcomes the reappointment of Ms Carolyn Walsh as a member of the ATSB Commission.
The Australian Transport Safety Bureau (ATSB) welcomed the reappointment of Ms Carolyn Walsh as a member of the ATSB Commission. Ms Walsh’s appointment by the Minister for Infrastructure and Transport, the Hon Anthony Albanese will commence on 8 March 2013 and will run for a further three years.
Ms Walsh has a wealth of experience in the field of transport safety in both policy and regulatory roles. She has specialist expertise in safety (both transport and occupational health and safety), risk management and the regulatory framework governing transport operations in Australia. She was the Chair of the national steering committee that advised the National Transport Commission on the development of the national Model Bill for Rail Safety.
Before becoming a Commissioner of the ATSB Ms Walsh was the Chief Executive of the NSW Independent Transport Safety and Reliability Regulator. She is currently a member of a number of Audit and Risk Committees for NSW Government agencies including: Aboriginal Lands Council (Chair), Information and Privacy Commission (Chair), Police Integrity Commission (member) and Office of the Director of Public Prosecutions (member).
The ATSB’s Chief Commissioner, Martin Dolan, said that he welcomes the opportunity to continue working with Ms Walsh to advance the national transport safety agenda.
On 21 January 2013 the ATSB welcomed a delegation from the Republic of the Union of Myanmar. The delegation includes officials from the Myanmar Department of Civil Aviation and the Myanmar Aircraft Accident Investigation Bureau, and representatives from airlines within Myanmar.
On 21 January 2013 the ATSB welcomed a delegation from the Republic of the Union of Myanmar. The delegation includes officials from the Myanmar Department of Civil Aviation and the Myanmar Aircraft Accident Investigation Bureau, and representatives from airlines within Myanmar.
The Australian Transport Safety Bureau is providing specialist assistance to Myanmar with its accident investigation into a Fokker 100 jet that crashed on 25 December 2012. The jet, carrying 71 people, including 5 Australians, landed in a field short of the runway at Heho Airport, which is the portal to the popular tourist destination of Inle Lake. There were fog patches in the area at the time. Two persons were killed, one a passenger in the plane and the other, a motorcyclist on the ground. The plane was badly damaged when its wings were shorn off and it caught fire. Ten passengers required hospital treatment and a further 26 were taken to hospital for medical checks.
The ATSB’s assistance involves the provision of technical specialists and facilities in Canberra to download and decode data from the aircraft’s flight data recorder and the cockpit voice recorder (commonly referred to as black boxes). This assistance is underpinned in Annex 13 to the Convention on International Civil Aviation, which promotes cooperation between member States internationally and details the protocols to facilitate the provision of such assistance.
Providing such assistance is also consistent with the Minister for Infrastructure and Transport’s statement of expectations of the ATSB that includes the requirement that, subject to available resources, we provide assistance to accident investigations in other countries, in accordance with international protocols. Under these arrangements, Australia provides assistance widely in the Asia-Pacific region and has assisted countries such as New Zealand, Papua-New Guinea and Indonesia, as well as other Pacific Island states.
The ATSB welcomes the opportunity to work with our counterparts in the region. It is hoped that the ATSB’s work will provide significant assistance to the Myanmar investigation and contribute more broadly to the enhancement of aviation safety internationally. These opportunities also provide a valuable means by which the ATSB can develop and exercise the skills and experience of its own specialist investigators.
The ATSB’s Chief Commissioner, Martin Dolan, has just published his latest blog post.
In his post, Martin talks about the ATSB’s expanded role as Australia’s independent national rail safety investigator and the contribution the ATSB will make to prevent future accidents and improve rail safety.
Carburettor icing can have serious safety implications for aircraft. This was shown most recently in an accident near Miranda Downs in Queensland.
Carburettor icing can have serious safety implications for aircraft. This was shown most recently in an accident near Miranda Downs in Queensland. On 6 July 2012, a Robinson R22 Beta was conducting mustering operations when the right skid struck a tree and collided with terrain.
The operator’s investigation into the accident—which examined GPS and Bureau of Meteorology data— found that the combination of temperature and dew point indicated a moderate carburettor icing risk at cruise power and a serious icing risk at descent power.
Pilots are reminded to maintain awareness of the weather conditions that are conducive to carburettor ice formation and closely monitor their aircraft performance during times when the risk exists.
Carburettor ice can occur in temperatures as high as 32° C with high humidity.
The investigation report AO-2012-091 provides important advice about carburettor icing. You can find this and other investigations in the ATSB’s Aviation Short Investigation Bulletin issue 13. The bulletin highlights valuable safety lessons for pilots, operators and safety managers.
More information:
The following publications provide useful information on carburettor icing and avoidance:
Systemic safety issues in Queensland coastal pilotage operations have been identified in an Australian Transport Safety Bureau (ATSB) investigation report, released today.
Systemic safety issues in Queensland coastal pilotage operations have been identified in an Australian Transport Safety Bureau (ATSB) investigation report.
Coastal pilots form a key defence against a serious shipping incident in parts of the Great Barrier Reef and Torres Strait as part of a suite of broader protective measures already in place.
The ATSB began an investigation into coastal pilotage operations in December 2010 following the release of its report into the grounding of the piloted tanker Atlantic Blue in the Torres Strait and a request from the Australian Maritime Safety Authority (AMSA)—the coastal pilotage safety regulator. That report identified safety issues affecting coastal pilotage which indicated that other systemic issues may also exist that would benefit from the ATSB further investigating.
The ATSB’s safety issue investigation found that under the coastal pilotage regulations, no organisation, including the pilotage provider companies, has been made clearly responsible and held accountable for managing the safety risks associated with pilotage operations. This has meant that responsibility for managing the most safety critical aspects of pilotage has rested with individual pilot contractors instead of an organisation that systematically manages safety risk.
The investigation also identified systemic safety issues surrounding pilot training, fatigue management, incident reporting, competency assessment and use of coastal vessel traffic services.
AMSA has already taken and proposed safety action to address the issues identified and is working with pilots, pilotage providers and industry to make further improvements to shipping safety in the region. Significant AMSA action includes the publishing of standard passage plans for pilotage, and requiring pilotage providers to develop standard operating procedures for pilotage tasks undertaken by their contractor pilots. On 1 July 2012, AMSA also began a review of its coastal pilotage regulations.
The ATSB welcomes AMSA’s response but considers further action is necessary to fully address the safety issues. In particular, the ATSB is recommending that AMSA ensures that the coastal pilotage regulations specifically assign responsibility for the safe management of pilotage operations to the pilotage providers or another organisation.
The ATSB has also issued recommendations to the three coastal pilotage providers to take safety action in relation to fatigue management and incident reporting to facilitate action by AMSA.
Following the allowed 90-day period after the issue of its recommendations, the ATSB will reassess the safety risk based on the action taken and proposed by AMSA, and the pilotage providers to address the issues.
As a result of evidence provided at a recent Coronial Inquest, CASA issued an Airworthiness Bulletin (AWB 02-041 Issue 2) recommending that operators and maintenance organisations review the fatigue index records for BAC Strikemaster 167 aircraft.
Operators of BAC 167 Strikemaster aircraft are being urged to check the safety of their aircraft following a Coronial inquest into a fatal Strikemaster accident.
On 5 October 2006, a BAC 167 Strikemaster aircraft broke up in flight and crashed into the Turon State Forest (near Bathurst, NSW) during an adventure flight. The pilot and passenger died in the accident.
Earlier this year, the Office of the NSW State Coroner began a Coronial Inquest into the accident. During evidence at the Inquest, details of the calculation of Fatigue Index (FI) penalties applicable to Strikemaster aircraft was provided.
As a result of this evidence, CASA recently issued an Airworthiness Bulletin (AWB 02-041 Issue 2). The bulletin recommends registered operators and maintenance organisations review the FI records for BAC Strikemaster 167 aircraft and determine if a FI penalty should be applied.
The ATSB is investigating today’s train derailment that occurred 15 km south of Cadney Park in South Australia. The derailment occurred on the Defined Interstate Rail Network between Adelaide and Alice Springs at about 6.20am this morning.
The ATSB is investigating today's train derailment that occurred 15 km south of Cadney Park in South Australia.
The derailment occurred on the Defined Interstate Rail Network between Adelaide and Alice Springs at about 6.20am this morning.
Initial reports indicate that 22 wagons derailed and around 300 metres of track will require replacement. No one was injured.
Two ATSB investigators will arrive on the accident site later this afternoon to begin the onsite investigation.
More information on the investigation is available on the ATSB website, RO-2010-012
Further updates will be provided as information comes to hand.
On the afternoon of 3 October 2022, a Pilatus Britten-Norman Islander BN2A-21, registered VH-WQA and operated by Torres Strait Air, was conducting a non-scheduled passenger air transport flight from Saibai Island Airport, Queensland (QLD) to Horn Island Airport, QLD. There was 1 pilot and 6 passengers on board.
About 19 km NE of Moa Island both engines began to surge. The pilot diverted towards Kubin Airport on Moa Island. As the aircraft passed to the south of the township of Saint Pauls, the pilot determined there was insufficient altitude remaining to reach the airport. As a result, the pilot conducted a forced landing on a road 7 km ENE of Kubin Airport. There were no reported injuries to the pilot or the passengers. The aircraft was substantially damaged.
What the ATSB found
The ATSB found that the dual engine speed fluctuations and associated power loss was probably the result of fuel starvation.
The mechanism was not conclusively determined, however it was identified that the pilot did not operate the aircraft's fuel system in accordance with the aircraft flight manual, and that the configuration and location of the aircraft’s fuel controls and tank quantity gauges were probably not conducive to rapid and accurate interpretation. The aircraft manufacturer released a service letter in June 2022 that detailed an optional modification to centralise the fuel system controls and gauges, however this modification was not fitted to VH-WQA. The ATSB considered that these factors increased the risk of inadvertent fuel tank selection.
Safety message
Accidents involving fuel mismanagement are an ongoing aviation safety concern. Pilots are reminded of the importance of understanding an aircraft’s fuel supply system and being familiar and proficient in its use. Adhering to procedures, maintaining an accurate fuel record, and ensuring appropriate tank selections are made for the phase of flight will lessen the likelihood of fuel starvation.
The investigation
Decisions regarding the scope of an investigation are based on many factors, including the level of safety benefit likely to be obtained from an investigation and the associated resources required. For this occurrence, a limited-scope investigation was conducted in order to produce a short investigation report and allow for greater industry awareness of findings that affect safety and potential learning opportunities.
The occurrence
On the afternoon of 3 October 2022, a Pilatus Britten-Norman Islander BN2A-21 (Islander), registered VH‑WQA and operated by Torres Strait Air, was conducting a non-scheduled passenger air transport flight from Saibai Island Airport, Queensland (QLD) to Horn Island Airport, QLD. There was 1 pilot and 6 passengers on board.
At about 1333, when the aircraft was at a cruise altitude of 6,000 ft and approximately 19 km NE of Moa Island (Figure 1), the pilot recalled that the right engine began to surge. The pilot observed the right engine speed fluctuate, accompanied by yawing[1] of the aircraft.
Figure 1: VH-WQA Torres Strait flightpath
Source: Google Earth annotated by the ATSB
About 40–50 seconds later, the left engine also began to surge. The pilot recalled disconnecting the autopilot, selecting auxiliary fuel pumps on and placing the left and right engine mixture, pitch and power levers in the full forward position. The pilot then varied the throttle and mixture levers in an attempt to resolve the issue, but the surging continued. The pilot reported that they did not check the fuel contents indicators at the time, as they believed the main tanks were supplying fuel to the engines and there was sufficient fuel within those tanks to complete the flight.
As a result of the engine issues, the pilot was unable to maintain level flight and recalled descending at 800–1,100 ft per minute to maintain an airspeed of about 75–85 knots. When the engine issues commenced, the closest land to the aircraft was Moa Island. However, the pilot initially elected to divert to Badu Island, as there was cloud along the track[2] to Moa Island. The pilot commenced a right turn towards Badu Island and recalled advising Brisbane Centre air traffic control of the diversion.
A short time later, the pilot revised their diversion plans and set a course for Kubin Airport on Moa Island. As the aircraft passed to the south of the township of Saint Pauls, the pilot determined there was insufficient altitude remaining to reach Kubin Airport (Figure 2). The pilot considered the available options and chose to land on a road that ran east–west. At an altitude of about 600–700 ft, the pilot recalled switching the fuel supply from main tanks to wing tip tanks but noticed no improvement in engine performance.
Figure 2: VH-WQA Moa Island flightpath
Source: Google Earth annotated by the ATSB
About 15 seconds prior to touchdown, the pilot recalled the right engine stopped. They then shut down the left engine and recalled setting both mixtures to cut-off, closing the throttles, and selecting the main fuel cocks to off. The pilot positioned the aircraft to land on the road, before noticing a power line in the intended touchdown area, which they manoeuvred to avoid. The pilot continued to fly the aircraft above the road and as the road traversed a hill and made a left turn, the pilot followed with the aircraft. At this point the pilot recalled that the stall warning system[3] sounded and that they called for the passengers to ‘brace’.
At about 1339, the aircraft impacted the ground heavily, with the rear fuselage and tail breaking away from the aircraft. The aircraft came to rest in an area of vegetation on the northern side of the road. The pilot reported instructing the passengers to evacuate, which they did through the emergency window hatches. The pilot then exited through the pilot door.
There were no reported injuries to the pilot or the passengers. The aircraft sustained substantial damage.
Context
Pilot information
The pilot held a commercial pilot licence (aeroplane), issued in January 2018 with single and multi-engine aircraft class ratings, multi-engine instrument rating, and a valid Class 1 medical. The pilot had accrued a total flight time of about 2,400 flying hours, including about 200–250 hours flying the Islander, and commenced employment with Torres Strait Air in April 2022.
The pilot reported they were well rested and the ATSB found no risk indicators of the pilot experiencing a level of fatigue known to affect performance.
Aircraft information
VH-WQA was a Pilatus Britten-Norman Islander BN2A-21; a twin-engine, high-wing, unpressurised aircraft, with fixed landing gear and seating for up to 9 passengers. It was fitted with Textron Lycoming IO-540-K1B5 piston engines and Hartzell HC-C2YK-2CUF propellers. The aircraft was manufactured in 1975 and first registered in Australia on 5 October 1978. Torres Strait Air became the registered operator of the aircraft on 14 August 2018.
The last periodic inspection was carried out on 21 September 2022. There were no defects recorded on the aircraft’s maintenance release. At the time of the accident, the aircraft had accumulated 14,081.92 hours total time in service, and the left and right engines had accumulated 294.15 and 2,185.36 hours since overhaul respectively.
Fuel system
The fuel system in VH-WQA was specification Mod NB/M/364 that consisted of a tip tank and main fuel tank within each wing. The usable capacity of each main tank was about 65 US gallons (246.1 l), and 27.5 US gallons (104.1 l) for each wing tip tank.
Fuel was fed from either the main or wing tip tanks (but not simultaneously) to the auxiliary fuel pumps, and then supplied to either engine via the main fuel cocks (Figure 3).
Figure 3: Fuel system
Source: Britten-Norman
The electrically actuated tank cocks were controlled via an overhead panel, located above the windscreen central pillar. The panel consisted of port and starboard switches that selected either the wing tip tank or main tank. There was a corresponding indicator light for each selection. The panel also contained a switch that controlled the brightness of the tip tank indicator light when that tank was selected (dim or bright). The same switch also determined the main tank indicator light when that tank was selected, either on or off (for the tip tank light positions of dim or bright, respectively) (Figure 4, Label A).
Figure 4: VH-WQA cockpit fuel system configuration
Source: Queensland Police annotated by the ATSB
The main tank contents indicators were located above the fuel tank section panel, with corresponding auxiliary fuel pump switches located either side (Label B). The wing tip tank contents indicators were located on the right side of the cockpit above the side window (Label C). The main fuel cock rotary selectors were located above the main tank contents indicators (Label D).
Fuel system placards,[4] highlighting the configuration and usage of the fuel tanks, were located between the main fuel contents indicators and to the left of the wing tip tank contents indicators (Figure 5). The placards indicated that wing tip tanks were to be used last (after main tanks), and that main tanks were not to be used for landings when the gauge reads less than 3 gallons.
Figure 5: VH-WQA fuel system placards
Source: Queensland Police annotated by the ATSB
Service letter SL 145
On 1 June 2022, Britten-Norman released service letter (SL) 145 applicable to all BN2 series Islander aircraft with Mod NB/M/364 wing tip tanks. The service letter detailed an optional modification to provide an alternative pilot interface that centralised the fuel system controls, specifically relocating the wing tip tank indicators to the overhead panel adjacent to the main tank fuel indicators, with the fuel selection switches mounted between the indicators. VH-WQA did not have this modification fitted.
Aircraft flight manual
The aircraft flight manual[5] for VH-WQA contained a supplement that detailed procedures, limitations, and information for the operation of the modified fuel system. This supplement stated that 13.5 US gallons (51 l) of fuel was to be retained in each wing tip tank at all times for structural reasons, except that this fuel could be used as reserve for holding or diversion to an alternate airfield. The wing tip tanks were required to be refuelled before the main tanks and used in flight after the main tanks were exhausted. The supplement stated:
The fuel in the main tanks may be used below the zero marking in cruise flight until the tanks are empty. Between 40 and 50 seconds of warning are given before engine malfunction occurs due to fuel exhaustion of the main tanks. The warning is characterised first by a drop-off of fuel pressure followed by a gentle hunting of the propeller.
Fuel
The flight time records indicated that VH-WQA flew 6 sectors on the day of the occurrence, prior to the accident flight. The occurrence pilot flew all of those sectors (Table 1).
Table 1: VH-WQA flight time records 3 October 2023
LT 40, LM 175, RM 190, RT 35 (after refuelling and before sector)
123
317
Murray I. – Yorke I.
0810
28
317
-
44
273
Yorke I. – Horn I.
0843
48
273
LT 40, LM 55, RM 75, RT 35 (after sector)
87
186
Horn I. – Moa I.
1026
19
186
-
27
159
Moa I. – Horn I.
1113
22
159
LT 30, LM 30, RM 45, LT 25
(after sector)
29
130
Horn I. – Saibai I.
1200
49
350
LT 55, LM 120, RM 120, RT 55
(after refuelling and before sector)
83
267
Saibai I. – Horn I.
1308
-
267
-
-
-
Source: Torres Strait Air
The aircraft was refuelled with avgas[7] at Horn Island Airport at 0626 (300.3 l) and again at 1150 (200.3 l). The pilot recalled using a fuel dipstick[8] to check the contents of the 2 main tanks and 2 wing tip tanks following refuelling, as well as checking drained fuel for water contamination. The flight time records contained a fuel discrepancy following the 1150 refuelling (the aircraft had an additional 20 l) and recorded tank contents on the Yorke Island – Horn Island sector (which is 19 l more than the recorded fuel remaining). Despite these discrepancies, the aircraft departed Horn Island Airport with a recorded 350 l of fuel on board, which was sufficient for the round trip to Saibai Island Airport. This was composed of 120 l in each of the main tanks and 55 l in each of the wing tip tanks.
The aircraft was recorded to have used 83 l on the flight to Sabai Island Airport, but the pilot did not record the individual levels of each tank in the flight time records on arrival at Saibai Island Airport. The ATSB calculated that 81 l of fuel was required to complete the intended flight from Saibai Island Airport to Horn Island Airport. About 44 l fuel would likely have been used for the flight from Saibai Island Airport to the vicinity where the pilot recalled that the engine surging commenced.
Pilot fuel management
The pilot was familiar with VH-WQA’s modified fuel system and during interview, recalled the correct use of the tip tanks. Despite this, flight time records indicated that the pilot had, on occasion, operated VH-WQA without the required 51 l of fuel in the wing tip tanks and had also used these tanks when fuel remained in the main tanks. The pilot did not give a reason for this usage of the tip tanks.
Site and wreckage
The ATSB did not examine the accident site or wreckage. The site was attended on 6 October 2022 by representatives from the aircraft operator, insurance provider, independent maintenance provider, and Queensland Police. The site inspection was recorded by Queensland Police and the video footage was provided to the ATSB along with forensic photographs taken on the day of the accident. The aircraft wreckage was not guarded during the period between the accident occurring and the on-site examination.
The wreckage was located a short distance from the road in an area of low foliage approximately 6.5 km ENE of Kubin Airport. The undercarriage and empennage were separated from the aircraft and the fuselage was resting right wing low (Figure 6 and Figure 7). No obvious airframe or engine defects were reported by those that attended the site.
Figure 6: Accident site from road
Source: Queensland Police
Figure 7: Accident site
Source: Queensland Police
The right main tank and wing tip tank were ruptured during the accident sequence. The left main fuel tank and wing tip tank were reported as being intact and found to contain approximately 60 l, and less than 500 ml of fuel respectively. No fuel contamination was apparent, and the fuel selectors were found to work correctly when electrical power was applied to the aircraft. Table 1 depicts the positions of the fuel controls as documented in forensic photographs taken shortly after the accident. The wing tip tanks were selected for use, the auxiliary pumps were on, and the main fuel cocks were selected ‘off’, which was consistent with the pilot’s recollection of the occurrence.
Table 2: Fuel system cockpit control positions
Control
Position
Left electrically actuated tip fuel cock
Wing TIP tank
Right electrically actuated tip fuel cock
Wing TIP tank
Tank indicator light setting
Wing tip tanks DIM
Left auxiliary fuel pump
ON
Right auxiliary fuel pump
ON
Left main fuel cock
OFF
Right main fuel cock
OFF
Source: Queensland Police
Related occurrences
Collision with terrain, Pilatus Britten–Norman aircraft BN2B-27 near Marcel Marchant Aerodrome, Chile on 16 April 2019, 1895SP (Directorate General of Civil Aviation Chile)
On 16 April 2019, a Pilatus Britten–Norman aircraft BN2B-27 with modified fuel system (Mod NB/M/364) collided with terrain shortly after take-off from Marcel Marchant Aerodrome, Chile. The pilot and 5 passengers on board were fatally injured and the aircraft was destroyed. The final investigation report concluded the near-empty wing tip tanks were likely selected to supply fuel to the engines, resulting in fuel starvation.
Collision with terrain, Pilatus Britten–Norman aircraft BN2B-21 near Devil’s Hole, approximately 2.5 nm north of Jersey Airport, Channel Islands on 3 November 2013, Air Accidents Investigation Branch United Kingdome Bulletin: 10/2014
During a search and rescue flight at night in poor weather conditions, one engine ceased producing power and eventually stopped. During the subsequent diversion towards Jersey Airport the other engine also stopped. The pilot was able to reach the Jersey coast and make a forced landing, in which the aircraft suffered significant damage. The aircraft had operated a previous flight with the fuel system configured so that tip tank fuel was being supplied to the engines. The aircraft departed on the accident flight in the same configuration and the engines stopped when the tip tank fuel became exhausted. The investigation also noted the layout of the fuel controls and tank quantity gauges as a source of complication with regard to the presentation of fuel source information to the pilot.
Australian occurrences
The ATSB has conducted a number of investigations that involved fuel management and fuel starvation. Examples include:
Fuel starvation involving Cessna 310R, VH-JQK, Sunshine Coast Airport, QLD, on 18 August 2022 (AO-2022-040)
Fuel starvation and forced landing involving Piper PA-28, VH-BDB, 15 km WSW of Bankstown Airport, NSW, on 19 September 2017 (AO-2017-094)
Fuel starvation involving Cessna 206, 3.5 NM NE of Aldinga, SA, on 3 February 2019 (AB-2019-004)
Cessna C310R, VH-HCP, 3km E Newman Aerodrome, WA, on 26 January 2001 (200100348)
The 2013 ATSB publication, Avoidable Accidents No. 5: Starved and exhausted: Fuel management aviation accidents (AR-2011-112) focused on accidents involving fuel starvation due to fuel management, stating:
Keeping fuel supplied to the engines during flight relies on the pilot’s knowledge of the aircraft’s fuel supply system and being familiar and proficient in its use. Adhering to procedures, maintaining a record of the fuel selections during flight, and ensuring the appropriate tank selections are made before descending towards your destination will lessen the likelihood of fuel starvation at what may be a critical stage of the flight.
Safety analysis
At a cruise altitude of 6,000 ft the pilot reported that the right engine and, shortly after, the left engine began to surge. There were limited potential reasons for two fuel-injected engines to behave in this manner, and (almost) simultaneous dual technical failure of independent systems would be highly unlikely. The most probable contributing factor was a fuel-related issue, which was also consistent with the onset of surging described by the pilot.
The aircraft departed Horn Island Airport with sufficient total fuel for the round trip to Saibai Island Airport and a significant quantity of fuel remained in the left main tank after the accident. The aircraft therefore did not suffer fuel exhaustion. The aircraft was filled with the correct fuel type and no fuel contamination was apparent to those on site. Additionally, the aircraft had already flown for over an hour since refuelling, which suggested that an issue with fuel quality was unlikely.
The reported fuel burn from Horn Island to Saibai Island, and the ATSB’s calculated fuel usage for the return flight, to the point of engine surging, totalled 127 l. Each of the main tanks were recorded as commencing the round trip with 120 l. This meant that the (approximately) 60 l of fuel found on site in the left main tank was correct if the flights to that point had been flown entirely on the main tanks, and assuming the breached right main tank contained the same volume. This also supported the pilot’s recollection of the occurrence, along with the fuel system cockpit control positions.
However, the calculated fuel usage was also close to the reported amount of fuel in the wing tip tanks (55 l each, 110 l total) upon refuelling at Horn Island. It was therefore considered whether the wing tip tanks had been selected for most or all of the flight duration and became exhausted. Previous occurrences have highlighted this as a possibility and it was also consistent with the small quantity of fuel found remaining within the reportedly unbreached left wing tip tank (<500 ml).
The pilot reported that they did not verify the fuel remaining in the aircraft's main or wing tip tanks when attempting to restore engine performance, following the onset of the engine surging. This oversight was possibly due to confirmation bias, as the pilot believed there was sufficient fuel in all 4 tanks at that time. The fuel controls and tank contents indicators were also probably not conducive to rapid and accurate interpretation due to the potentially confusing configuration of the fuel system panels, and the disparate location of the wing tip tank contents indicators on the right side of the cockpit. In addition, fuel records from earlier flights showed that the pilot was using the wing tip tanks when fuel remained in the aircraft's main tanks, which was not in accordance with the approved flight manual. The ATSB considered that both of these factors increased the likelihood of the wing tip tanks being inadvertently selected during part or all of the round trip, leading to the exhaustion of the wing tip tanks. However, it is noted that this scenario is inconsistent with the pilot’s recollection of switching to the tip tanks in attempting to restore power – the position to which the tanks were found selected during the wreckage examination.
The ATSB was unable to account for the fuel tank content discrepancy for either scenario. However, the aircraft wreckage was not guarded during the period between the accident occurring on 3 October 2022 and the on-site examination on 6 October 2022. Consequently, while there was not evidence of tampering, it is possible that during this time fuel was removed (syphoned or pumped) from either tank or leaked from the fuel system, through a mechanism not obvious during the on-site examination. Ultimately the fuel discrepancies were unable to be resolved from the evidence available. However, on the balance of probabilities and in the absence of any other likely mechanical or fuel related issue, the dual engine speed fluctuations and associated power loss was most probably the result of fuel starvation.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition ‘other findings’ may be included to provide important information about topics other than safety factors.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the Engine power loss and forced landing involving Pilatus Britten-Norman Islander BN-2A, registered VH-WQA, Moa Island, Queensland on 3 October 2022.
Contributing factors
The engine power loss was likely the result of fuel starvation.
Other factors that increased risk
The pilot did not use the aircraft’s wing tip tanks in accordance with the flight manual. In addition to aircraft structural considerations, this also increased the likelihood of an inadvertent inappropriate fuel tank selection.
For Britten-Norman Islander aircraft fitted with wing tip tanks, but without the alternative pilot interface per service letter number SL145, the configuration and location of the fuel controls and tank quantity gauges were probably not conducive to rapid and accurate interpretation.
Sources and submissions
Sources of information
The sources of information during the investigation included the:
pilot of the accident flight
aircraft operator
UK Air Accident Investigation Branch
Civil Aviation Safety Authority
Queensland Police Service
aircraft manufacturer
Airservices Australia
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
pilot of the accident flight
aircraft operator
Civil Aviation Safety Authority
UK Air Accident Investigation Branch.
Submissions were received from:
UK Air Accident Investigation Branch.
The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1] Yawing: the motion of an aircraft about its vertical or normal axis.
[2] Track: the path of the aircraft across the earth’s surface.
[3] Stall warning system: activates an audible alert at a desired point above the stall.
[4] Placard: a notice affixed to an aircraft that my contain warnings, limitation or reference information.
[5] Aircraft flight manual: a document produced by the aircraft manufacturer that contains information on the specifications and operation of the aircraft.
[6] Block time: elapsed period from when an aircraft starts to move at the beginning of the flight, to the time it comes to rest at the conclusion of the flight.
[7] Avgas: a type of aviation fuel used in aircraft with a spark-ignited internal combustion engine.
[8] Dipstick: a graduated tool that is inserted into a fuel tank and used to determine the level of fuel within the tank.
On 17 October 2022, at about 1345 local the pilot of a Mooney Aircraft Corporation M20J aircraft, registered VH-UDQ, departed Maitland Airport, NSW for a local flight. The pilot flew to Cessnock Airport, NSW and completed an orbit, then continued to Luskintyre airfield, NSW. When overhead Luskintyre airfield, the pilot broadcast their intent to track to Maitland Airport.
Witnesses near Luskintyre airfield reported observing the aircraft in what appeared to be descending to land. They further reported that smoke and flames were seen trailing the aircraft. At about 1359 VH-UDQ collided with terrain about 330 metres short of runway 30 with witnesses describing an explosion and accompanying fireball.
The aircraft was destroyed by an intense post-impact fire. The pilot survived the collision but eventually succumbed to injuries sustained during the accident.
What the ATSB found
The ATSB determined that an O-ring seal fitted to the engine-driven fuel pump outlet fitting remained in service until it became age-affected and failed to provide an effective seal. The escaping fuel from the age-affected O-ring seal ignited and created an engine compartment fire. In response to the fire, the pilot initiated an emergency descent towards the runway but subsequently landed in a field resulting in the aircraft impacting trees. That led to a break-up of the aircraft and a severe post‑impact fire that consumed the aircraft.
The ATSB also established that the aircraft had been recently refurbished. The refurbishment included repainting the aircraft and replacing interior furnishings with alternate materials. Neither the refurbishment activity nor details of the flammability assessment of the substituted materials, were recorded in the aircraft log books. The effect this refurbishment had on the in-flight fire, or the survivability of the pilot could not be determined.
What has been done as a result
In response to this accident, the Civil Aviation Safety Authority proposed to review Airworthiness Bulletins AWB 02-001 relating to on-condition maintenance, and AWB 85-004 regarding aircraft piston engine calendar time overhaul and most likely update them. The review would serve to highlight that ‘on-condition’ was not a ‘fit and forget’ approach to preventative maintenance.
The ATSB has issued safety advisory notice SAN AO-2022-049-001 in conjunction with this investigation report. The SAN draws attention to the proactive replacement of O-ring seals fitted to engines and engine components, should inspection of aircraft records indicate they have been in service for a significant period.
Safety message
Piston engines, and the components necessary for their operation, installed in aircraft operating in the private or airwork category are permitted to remain in service beyond their recommended calendar time overhaul interval. As O-ring seals fitted to such engines are susceptible to deterioration due to age, being aware of their accumulated time-in-service may initiate replacement action before they fail.
Maintaining an aircraft’s internal appearance may require the introduction of alternate materials when original products may no longer be available. Aircraft owners are encouraged to document aircraft refurbishment action in the aircraft logbook and to include details of materials if substituted, and their suitability for use in aircraft interiors.
Summary video
The investigation
Decisions regarding the scope of an investigation are based on many factors, including the level of safety benefit likely to be obtained from an investigation and the associated resources required. For this occurrence, a limited-scope investigation was conducted in order to produce a short investigation report, and allow for greater industry awareness of findings that affect safety and potential learning opportunities.
The occurrence
On 17 October 2022, at about 1345 the pilot of a Mooney Aircraft Corporation M20J aircraft, registered VH‑UDQ, departed Maitland Airport, NSW for a local flight. The aircraft travelled to the south-east before turning west towards Cessnock Airport. The pilot conducted an orbit of Cessnock Airport and by about 1353, was headed north-east towards Luskintyre airfield (Figure 1). At 1357:29, when about 2,150 ft above ground level (AGL)[1] during an orbit of Luskintyre airfield, the pilot made a broadcast on the common traffic advisory frequency[2] alerting other pilots in the area that they were overhead Luskintyre airfield and intending to track to join crosswind for runway 23[3] at Maitland Airport.
Figure 1: VH-UDQ Maitland to Luskintyre flight with inset showing flight path north of Sydney, NSW
Source: Google and AvPlan flight data. Annotated by ATSB.
Witnesses reported observing a light aircraft near the airfield that appeared to be descending to land. As VH-UDQ descended towards a line of trees to the south of their position, one witness observed flames coming from the front of the aircraft. The other witnesses reported seeing the aircraft with smoke trailing behind. No distress or emergency calls from the pilot were recorded (Figure 2).
Figure 2: Orbit and descent towards Luskintyre airfield
Source: Google and AvPlan flight data. Annotated by ATSB.
VH-UDQ continued its descent, and touched down in a grass field that was divided by a line of trees. At about 1359 VH-UDQ collided with the trees that were located about 330 metres short of runway 30 with witnesses describing an explosion and accompanying fireball. The collision with trees resulted in the break-up of the aircraft with the fuselage coming to rest about 70 m beyond the tree line.
The witnesses proceeded to the scene and on arrival, they located the pilot lying in the field about 10 m away from the burning aircraft. The pilot advised the witnesses that the aircraft engine had caught fire and that they had suffered smoke inhalation.
The aircraft was destroyed by an intense post-impact fire. Although the pilot survived the collision and escaped from the aircraft, the pilot sustained substantial burns. The pilot was taken to hospital but succumbed to these injuries about 10 weeks later.
Context
Pilot information
The pilot held a Commercial Pilot Licence (Aeroplane) and a valid Class 1 aviation medical certificate. The pilot was issued with a private pilot licence in 1998 and a commercial pilot licence in 2008. The pilot, who was an associate of the aircraft owner, held the required ratings and endorsements for the flight. According to the last medical examination report in October 2021, the pilot reported that they had accumulated about 990 flying hours experience.
Aircraft information
General
VH-UDQ was a Mooney Aircraft Corporation M20J, manufactured in the United States in 1978 and assigned serial number 24-0588. The aircraft Log Book Statement for maintenance direction specified that the airframe was to be periodically inspected in accordance with Civil Aviation Safety Authority (CASA) Schedule 5 and the engine per AD/ENG/4 as amended. For special inspections and lifed component changes, the aircraft maintenance manual was to be consulted.
Engine history
The aircraft was fitted with a 4-cylinder Lycoming engine, model IO‑360-A3B6D, serial number L‑22956-51A. Records show that the engine was last overhauled in May 1993 and had accumulated 1,806.3 hours, time-in-service since overhaul. At the time of the accident, the engine had been operating for 29.5 years since overhaul.
The engine manufacturer recommended that the engine type was to be overhauled on accumulating 2,000 hours, time-in-service or every 12 years. Continued operation in service beyond 12 years was permitted provided the continuing airworthiness requirements of CASA AD/ENG/4 Amendment 11 for ‘on-condition’[4] operation was met. Additional maintenance related information is addressed in Airworthiness directives and airworthiness bulletins.
This engine was installed in VH-UDQ in September 2021. The aircraft owner reported that the engine was replaced by the former owner prior to the sale of the aircraft. The engine had accumulated 27.4 hours since it was installed and the time of the accident.
A piston engine condition report conducted at the 100‑hour inspection addressed the continuing airworthiness requirements did not identify any faults with the engine. The available aircraft records did not contain maintenance activity related to engine‑driven fuel pump replacement or repair.
Airframe information
At the last 100-hour periodic inspection on 14 September 2022, a maintenance release was issued, permitting day VFR operations and showed that the airframe had accumulated 19,128.3 hours, time-in-service.
Refurbishment
Prior to the 100-hour inspection, the aircraft had been refurbished by the current owner. The refurbishment included new external livery and replacement of interior furnishings. The interior refurbishment included re-covering of the seats with leather and the renewal of cabin and baggage compartment linings and floor panels. The owner confirmed that the backing material used for some of the cabin and baggage compartment linings were of carbon fibre construction. Details of the specific furnishings used in the aircraft were not recorded in the aircraft maintenance log books.
Meteorological information
The Maitland weather observation recorded at 1400 was wind from 160º at 12 kt, greater than 10 km visibility, cloud bases broken at 3,500 ft and 7,900 ft above airfield elevation, temperature and dew point of 21º and 14º respectively, and QNH 1019 hPa with no rainfall recorded since 0900. The ten‑minute weather observations for Maitland recorded the wind direction from 165º at 11 kt with a maximum gust of 14 kt in the period 1350-1400.
Luskintyre airfield
Luskintyre airfield is located about 8 km to the north-west of Maitland Airport. The airfield consists of a grass runway 12/30[5] which is 760 m long. The airfield has an elevation of about 35 m above mean sea level and is surrounded by fenced pastures containing dwellings and occasional stands of trees lining boundary fences.
Recorded data
Flight information sourced from AvPlan[6] indicated that at about 1358, VH-UDQ completed the orbit of Luskintyre airfield and commenced a descending turn to the right, reducing altitude from 1,863 ft AGL at 1358:02 to 1,597 ft at 1358:22. By 1358:32, VH-UDQ had begun a left turn and by 1358:42 was at 1,273 ft in an established turn and descending towards Luskintyre airfield. The final turn resulted in a tailwind component as the aircraft descended (Figure 3).
Figure 3: Aircraft flight - final turn towards Luskintyre airfield with time stamps
Image description: Overhead view of flight path with displayed height referenced to the elevation of Luskintyre airfield.
Source: AvPlan and Google, annotated by ATSB
Analysis of the data when VH-UDQ was established in the final turn and approach to the tree line, indicated that the aircraft rate of descent peaked at 3,504 feet per minute. Prior to initial ground contact, when at 52 ft AGL, the rate of descent was 1,032 feet per minute and a ground speed of 108 kt was recorded (Table 1).
Table 1: Aircraft performance during descent towards Luskintyre airfield
Time (local)
Groundspeed (kt)
Altitude (ft - AGL)
Average rate of descent (ft/min)
1358:27
91
1,522
-
1358:42
94
1,273
996
1358:47
106
981
3,504
1358:57
124
551
2,580
1359:12
111
138
1,652
1359:17
108
52
1,032
Source: ATSB
Emergency procedures
The Mooney M20 pilot’s operating handbook (POH) advised pilots that in the event of an engine fire in‑flight, the emergency is to be treated in the following manner:
Fuel Selector Valve – OFF
Throttle and mixture – CLOSED and at IDLE CUTOFF
Cabin ventilation and heating controls – CLOSED
Landing gear – UP or DOWN, depending on terrain
Flaps – Extend as necessary
The POH noted that if the fire is not extinguished, pilots should attempt to increase the airflow over the engine by increasing the glide speed and to attempt a power off landing. They should not attempt to restart the engine.
For a power off landing associated with an engine failure, the POH advised pilots to secure the engine by moving the mixture control to the idle cut-off position and to switch the magnetos off. Wing flaps were to be set to the full down position and undercarriage selected as necessary. Prior to landing, the master switch was to be in the off position and the aircraft approach speed to be 71 kts indicated airspeed.
Site and wreckage information
The initial ground contact points were tyre marks in a grass field ahead of a tree line that separated two grass fields and was located about 330 metres before the runway 30 threshold. The tyre marks began about 67 metres from the tree line and ended about 22 metres before the tree line, indicating that VH-UDQ had become airborne again before colliding with the trees in a near-level attitude. The collision with the closely spaced trees separated the wings from the fuselage and was followed by a progressive break-up of the rest of the aircraft. The resulting wreckage trail was spread over a distance of about 70 metres, on a heading of about 282 degrees (magnetic). Ignited fuel from the ruptured wing tanks created the initial fireball reported by witnesses and generated an intense post‑impact fire that consumed the cockpit and cabin area of the fuselage (Figure 4).
Figure 4: VH-UDQ wreckage trail and location of major items
Source: ATSB
The complete aircraft was present at the accident site with all the flight control surfaces and major components accounted for. Examination of the aircraft control systems did not identify any defects that may have affected control of the aircraft. When examining the fuselage remains, the ATSB identified sections of carbon-fibre based products in the aircraft cabin and baggage compartment.
The nose undercarriage was noted to be in the down and locked position however the left and right main undercarriages were found housed in the wheel wells. The main undercarriage actuation and locking mechanism was found to be broken and the damage attributed to the wings separating from the fuselage.
The flap and tailplane trim actuators were retrieved from the accident site and details of their respective jack screw positions were provided to the aircraft manufacturer for comment. The aircraft manufacturer reported that in consideration of the position of the flap jack screw, the wing flaps were set in a slightly down position. The tailplane trim position could not be accurately determined.
Assessment of ground slash marks created by propeller rotation indicated that the propeller was operating between 1,590 and 1,150 revolutions per minute.[7] The engine manufacturer reported that the propeller speed was above that expected for an engine to be windmilling.
Due to the post-impact fire, the position prior to impact of cockpit switches and magneto selection, the fuel selector valve, the throttle and mixture controls, and the cabin ventilation and heating controls, could not be determined.
Engine examination
A detailed engine examination was undertaken at the ATSB technical facilities in Canberra, ACT. The following observations were noted:
Evidence of scorching and soot residue on engine hoses and components, presented as a distinct flame path that commenced at the rear of the engine and progressed to the front (Figure 5).
The origin of the engine fire was localised to the area surrounding the engine-driven fuel pump.
Pressure testing of the engine fuel supply and distribution hoses did not reveal any fluid leak associated with a hose defect.
Pressure testing of the engine-driven, mechanical fuel pump detected fluid leakage at the base of the fuel outlet fitting of the pump.
Figure 5: Underside of engine showing components and direction of flame travel
Source: ATSB
The fuel pump inlet and outlet fittings were removed to allow for examination of the O-ring seals installed between the fittings and the fuel pump body. Inspection of the outlet fitting seal revealed a deteriorated elastomer that had lost its pliability and its round, cross‑sectional shape. Further, the seal showed signs of permanent deformation and contained surface defects (Figure 6).
Figure 6: Fuel pump fittings and O-ring seals showing loss of natural shape and surface defects
Source: ATSB
The inlet fitting seal exhibited similar in-service defects as the outlet fitting seal, however the deterioration had not progressed to failing to provide an effective seal. The examination indicated that fuel under pressure was leaking past the outlet fitting O-ring.
Maintenance records and requirements
Responsibility of registered operators – conduct and recording of maintenance
Section 3 of the Civil Aviation Act1988, describes maintenance as:
Any task required to ensure, or that could affect, the continuing airworthiness of an aircraft or aeronautical product, including one or a combination of overhaul, repair, inspection, replacement of an aeronautical product, modification or defect rectification.
The owner or if appointed, the registered operator is responsible for the airworthiness and maintenance control of the aircraft to ensure its safe operation. Provision for the recording and certification of maintenance that is carried out are contained in the aircraft logbooks.
Maintenance activity or modifications which may include repainting of exterior surfaces or internal furnishings renewal, may change the aircraft’s empty weight and its centre of gravity position. If the change varies by more than the specified amount detailed in the aircraft’s weight and balance record, or the effect of the change is unknown, the aircraft may need to be re-weighed to determine its new empty weight and centre of gravity position. Maintaining the accuracy of the aircraft’s weight and balance information is necessary to ensure that changes do not adversely impact the performance of the aircraft as published in the aircraft flight manual.
To ensure that aircraft type certification standards are maintained and occupant survivability in the case of fire is not further degraded, modifications that include changes to materials used in interior furnishings are subject to approval by an authorised entity. The approval process will likely involve testing of the materials to evaluate their flash or flame resistance.
Airworthiness directives and airworthiness bulletins
An airworthiness directive (AD) is a document issued by the aircraft State of Design or CASA, if an unsafe condition exists in a kind of aircraft or aeronautical product. Registered operators are to comply with the requirements of an AD or an approved alternate means of compliance. CASA also issues Airworthiness Bulletins (AWBs) to inform the aviation public of essential information or make recommendations that are not considered mandatory.
Airworthiness directives – continuing airworthiness of aircraft and aeronautical products
CASA airworthiness directive AD/ENG/4, Piston engine continuing airworthiness requirements, was first issued in March 1995. Amendment 11 became effective on 15 January 2009 and specified the piston engine continuing airworthiness requirements. It required that registered operators of aircraft operated in either the private or airwork categories, in addition to scheduled engine maintenance, conduct additional maintenance actions to confirm the serviceability of the engine.
AD/ENG/04 also referenced CASA Airworthiness Bulletin AWB 85-004, Aircraft piston engine calendar time overhaul, that provided guidelines for additional inspections related to engine calendar time overhaul. The purpose of this AWB was specified as:
This AWB provides guidelines for procedures to be followed to ensure continued airworthiness of the engines that have exceeded the calendar time overhaul limits specified by the manufacturer. These guidelines are in addition to the recommendations by the manufacturers relating to inspections for corrosion.
The AWB highlights corrosion and degradation of elastomers as factors contributing to engine deterioration associated with calendar time. The AWB recommended inspecting elastomer components such as engine mounts, hoses and other elastomer related items for deterioration, however O-ring seals fitted to engine components were not specifically mentioned.
Airworthiness Bulletins
While airworthiness bulletins are for information only, they contain useful information concerned with the airworthiness of aircraft and aeronautical products. CASA recommends that all aircraft owners, and other key stakeholders involved in the operation or maintenance of aircraft, review AWBs for applicability and take any action they consider appropriate.
Airworthiness Bulletin AWB 02-1, On-condition maintenance, was issued on 27 November 2001, and provided information relating to ‘on-condition’ maintenance.
‘On-condition’ maintenance means that the condition of the item is monitored continuously or at specified intervals. When its performance or physical appearance is observed to no longer meet an appropriate standard, the resultant action is the removal of the item before it fails in service. Items in the engine may remain in service longer than the manufacturer recommended time‑in‑service, provided they continue to meet desired physical conditions and performance standards. The AWB identified that ‘on-condition’ is not an opportunity to fit and forget until a failure occurs. The AWB further advised that the condition of an item may require appropriate judgement to determine that failure of the item will not occur prior to the next scheduled inspection.
CASA recommended that where applicable, certificate of registration holders utilise the philosophy of ‘on condition’ maintenance to detect the potential for failures of critical items or products, especially when the time-in-service is approaching the manufacturer’s recommended overhaul period.
Flammability resistance
CASA (2011) AWB 25-016 Cabin interior and cargo compartment flammability provided guidance regarding flammability requirements for aircraft material and advised that when repairing or replacing interior material in an existing aircraft, the applicable flammability requirements are to be understood, and compliance with, is shown.
Factors to consider are the minimum flammability requirements for the aircraft, which is dependent on the aircraft category and the standard applicable at the time that the aircraft was first certificated. Certification information is contained in a document usually referred to as the Type Certificate Data Sheet.
The Type Certificate Data Sheet for the Mooney M20 showed that the aircraft was certified under Part 3 of the United States Civil Air Regulations as amended in 1956, which required that materials making up the cabin interior be ‘flash resistant’, or ‘flame resistant’ if the compartment could be used for (cigarette) smoking.
For a material to be flash resistant, AWB 25-016 notes that the material is to be of a type that is not susceptible to burning violently when ignited. To be flame resistant, it is not to be susceptible to combustion to the point of propagating a flame beyond a limit when the ignition source is removed.
Elastomer type products used in aircraft systems
Aircraft and engine systems carrying petroleum-based products use fluid carrying hoses, seals and gaskets that commonly involve nitrile rubber in the manufacturing process (Brink, Czernik and Horve, 1993). Nitrile rubber is a widely used, synthetic elastomer that is resistant to oil, fuel and chemicals with inherent properties that include tear and abrasion resistance, tensile strength, resilience,[8] and compression set.[9] Distinguishing characteristics of elastomer type products are their ability to be stretched up to several hundred percent and given their ability to store energy, to return to their near original shape when significantly compressed (Brady and Clauser,1991). Hoses, seals and gaskets are normally subject to handling, inspection and replacement requirements while in service.
Following installation, standard aviation maintenance practices described in US Advisory Circular AC-43-13, Acceptable methods, techniques and practices-aircraft inspection and repair (FAA, 1998), require that O-ring seals should not be re-used if disturbed during maintenance or disassembly of the part to which they are fitted. The O-ring seal may have swelled from exposure to fluid, hardened over time, or gained a permanent set. When installed as a gasket within a recessed area to seal a fluid carrying fitting, leaks are not normally acceptable. However, opportunities to replace or physically examine O-ring seals are reliant on scheduled maintenance where the component to which they are fitted is targeted for attention, or unscheduled maintenance in response to the component developing a defect when in service.
As specified by the Logbook Statement,[10] contained in VH-UDQ’s logbook, when considering aircraft components, reference is to be made to the overhaul and replacement schedule provided in the Mooney M20J aircraft maintenance manual. The schedule specifies that fuel and oil system flexible hoses containing elastomer type material are replaced every two to seven years, or at engine overhaul, whichever occurs first. The schedule also specifies that all other fuel and oil system components such as an engine‑driven fuel pump are treated as on-condition items and may remain in service until an inspection, or their performance reveals an unserviceable condition.
Additional information
Annex 13 to the convention on international civil aviation is published by the International Civil Aviation Organization and details the standards and recommended practices for aircraft accident and incident investigation. For statistical purposes, an injury is classified as a fatal injury when death results within thirty days of the date of the accident. The pilot involved in this accident did not succumb to injuries until after the 30-day period, and therefore, the accident is not registered as a fatal collision, despite the outcome.
Related occurrences
Between 2014 and 2023, the ATSB investigated two accidents (described below) involving aircraft in-flight fires that resulted in a fatality or serious injuries. In one accident, the origin of the fire was attributed to burning oil due to engine failure while the other was attributed to a fuel-fed cabin fire.
On 28 March 2014, the pilot of a Cessna Aircraft Company 210L aircraft departed Numbulwar, Northern Territory, on a charter flight with one passenger on board for a return flight to Tindal, Northern Territory.
When about 22 NM west of Numbulwar, smoke was detected in the cabin and following a ‘MAYDAY’ call advising of an engine failure, the pilot applied the cabin fire extinguisher which quickly stopped the smoke. The aircraft landed heavily and collided with trees. The pilot and passenger suffered serious injuries and the aircraft was destroyed.
The ATSB determined that a piston connecting rod broke resulting in a catastrophic engine failure. The smoke entering the cockpit was likely from burning oil.
On 16 April 2022, the pilot of a Beechcraft B58 Baron aircraft, on a charter flight with one passenger on board from Broome Western Australia, commenced a straight in approach to runway 12 at the East Kimberley Regional Airport, Western Australia.
When attempting to extend the landing gear, smoke emerged from forward of the pilot’s circuit breaker panel. The pilot made a PAN-PAN call, by which time flames were observed to be coming from the area of the source of the smoke. Attempts to extinguish the fire were unsuccessful with flames and thick smoke filling the cockpit.
The aircraft collided with terrain about 800 m from the threshold of runway 12 and was consumed by the post-impact fire. The passenger succumbed to their injuries and the pilot received serious injuries.
The ATSB determined that a fault associated with the landing gear electrical system likely ignited fuel from the cabin heater supply line, resulting in a significant and sustained cockpit fire.
NTSB investigation
A similar occurrence in the United States was investigated by the National Transportation Safety Board. The accident was attributed to an engine compartment fuel leak and described in NTSB report, ERA17LA284 as summarised below.
On August 20, 2017, the pilot of a Mooney M20C aircraft registered N6833N departed Palm Coast, Florida on a private flight with one passenger on board to Fort Lauderdale, Florida.
During take‑off and climb the pilot noticed that the engine was losing power. Upon reaching 400 ft above ground level the engine lost total power. During touchdown for the subsequent forced landing to a road, the pilot noticed flames coming into the cabin near the passenger’s feet. The pilot was able to stop the aircraft and both occupants were able to egress quickly after landing.
The pilot and passenger were not injured however the aircraft was substantially damaged.
The NTSB investigation found that a crack in the engine’s No. 4 cylinder resulted in a rough running engine and a subsequent loss of power. The increased vibration loosened a fuel line fitting that generated a fuel leak and was the source of the in-flight fire.
Safety analysis
Introduction
On 17 October 2022, at about 1345 the pilot of a Mooney Aircraft Corporation M20J aircraft, registered VH-UDQ, departed Maitland Airport, NSW for a flight in the local area. While overhead Luskintyre airfield the pilot broadcast an intent to track to Maitland Airport. However, witnesses nearby saw the aircraft descending towards Luskintyre airfield while trailing smoke and flames. Following an initial touch-down in a grass field, VH-UDQ collided with a line of trees. The witnesses described an explosion and accompanying fireball. The pilot was seriously injured but subsequently succumbed to injuries after 10 weeks. The aircraft was destroyed.
The following analysis will consider the cause of the in-flight engine compartment fire, the O‑ring seals of the engine fuel pump, and the recording of maintenance activity in the aircraft logbook. The risk to occupant safety when substituting materials used for interior furnishings is also discussed.
Fire and emergency descent
Witnesses in the area reported flames and smoke coming from the aircraft, and the pilot reported to first responders that the engine was on fire and that they had inhaled smoke. In consideration of the leak found with the engine-driven fuel pump outlet O‑ring seal (see O‑ring seal replacement below), it was likely that fuel leaking from the pump outlet fitting produced a vapor that was ignited by heat in the lower engine compartment.
Given that the pilot made a normal, inbound call for a landing at Maitland Airport, it is likely the pilot only became aware of the presence and/or extent of the engine compartment fire after the orbit of Luskintyre airfield and after the inbound call. However, once the pilot became aware of the fire, they abandoned their intention to land at Maitland Airport and the flight path suggests they instead intended to land at Luskintyre airfield due to its proximity.
The approach towards runway 30 at Luskintyre airfield was at a very high rate of descent, which was consistent with an emergency reaction to a fire that the pilot perceived as high risk to their safety. The available recorded data shows that the descent from 1,522 ft to 52 ft occurred in 50 seconds. From the available evidence it was not clear if, during that time, all of the pilot operating handbook checklist items for an in-flight fire were conducted. One item included cutting off fuel to reduce the source of fire, but the calculated propeller speed at collision suggested that the engine was rotating at well above windmilling speed and was not consistent with configuring the aircraft for a power off landing.
While a landing on a runway is generally safer than in a field, the high descent rate close to the ground may have limited the pilot’s ability to reach runway 30. However, it is also possible that the pilot was becoming more affected by heat, fire and/or smoke as the aircraft descended, and made a decision to land in the paddock to expedite the landing.
The relatively wings-level attitude when the aircraft touched down and then collided with the tree line indicates the aircraft was in an attitude appropriate for landing, albeit at a high ground speed and descent rate. The high speed at which the aircraft’s wheels first contacted the ground and the proximity of the tree line from the initial ground contact point indicated that the collision with trees and subsequent break-up of the aircraft was unavoidable. The release and atomisation of fuel as the wings separated from the fuselage was likely ignited by the pre-existing fire within the engine compartment and the generated heat ignited combustible materials of the aircraft.
As the fuselage was subsequently consumed by the post-impact fire, it was not possible to determine whether cockpit furnishings had started to burn in-flight due to radiant heat from the engine compartment fire, or that cockpit related smoke in-flight, contributed to the reported smoke inhalation.
O-ring seal replacement
An engine compartment fuel leak during the accident flight originated from the engine‑driven, mechanical fuel pump outlet fitting due to an O‑ring seal that had deteriorated with age and had lost the ability to provide an adequate seal. Maintenance related standard practices specify that O‑ring seals are not reused, and they should be replaced when disturbed during maintenance or when a leak is detected.
Unlike the engine fluid carrying hoses that were periodically replaced per the aircraft’s maintenance schedule, the fuel pump and the O-ring seals were on condition and had not required replacement while the engine was in service. Additionally, the maintenance records did not contain evidence of other opportunities to access and physically examine the condition of the O-ring seals that are normally hidden from view when installed on the fuel pump fittings.
O-ring seals were not specifically identified in the broad classification of elastomer type products described in CASA airworthiness bulletin AWB 85-004. Since the O-ring seals were not specifically targeted for attention, this may have resulted in them being overlooked for proactive replacement of easily accessible seals.
In the absence of physical examination or replacement opportunity, assurance that the O‑ring seals were functional, was reliant on checking for fluid leaks at specific intervals. When last inspected it was likely that no discernible leak was detected at the fuel pump outlet fitting. However, the engine was about 17.5 years past its normal overhaul calendar life and the potential for a leak to develop between scheduled inspection intervals was increasingly likely as the O‑ring seals continued to age. A review of the records may have identified the prolonged time-in-service of O‑ring seals, and if documented, the modifications that may have affected the weight of the aircraft, or the flammability attributes of materials used during interior refurbishment.
Flammability assessment
The interest in giving the aircraft a renewed look may have influenced the selection of products as interior furnishings. The use of alternate products was not prohibited. However, to understand the risk associated with substituting materials, an assessment of the substituted materials’ flammability was required. When conducted, the assessment would have indicated the suitability of the material in terms of potential impact on occupant safety in the case of a fire.
Regarding material type, those having flame or flash resistant attributes were permitted for use as cabin furnishings and was dependent on whether smoking was permitted in the aircraft. Considering the common practice of not permitting smoking in aircraft interiors, assurance that occupant safety was not compromised could have been achieved by using products that at a minimum, were determined to be flash resistant. However, a record of their use and their suitability needed to be included in the aircraft records.
Due to the intensity of the post-impact fire, and the lack of records, the ATSB was unable to determine the full extent of product or material substitution, or whether the replacement materials had fed or suppressed the fire.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition, ‘other findings’ may be included to provide important information about topics other than safety factors.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the collision with terrain involving Mooney Aircraft Corporation M20J, registration VH-UDQ, near Luskintyre airfield, NSW on 17 October 2022.
Contributing factors
In response to an engine compartment fire, the pilot initiated an emergency descent towards the runway but subsequently landed in a field resulting in the aircraft impacting trees. That led to a break-up of the aircraft and a severe post‑impact fire that consumed the aircraft.
An O-ring seal fitted to the engine-driven fuel pump outlet fitting remained in service until it became age-affected and failed to provide an effective seal. The escaping fuel ignited and created an engine compartment fire.
Other factors that increased risk
The aircraft had recently been refurbished and changes included new external livery and replacement of interior furnishings. The aircraft records did not indicate that the refurbishment had been conducted, and consequently, there was no evidence of a flammability assessment for the materials used.
Safety actions
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out to reduce the risk associated with this type of occurrences in the future. The ATSB has so far been advised of the following proactive safety action in response to this occurrence.
Safety action by the ATSB
In response to this accident, the ATSB has issued safety advisory notice SAN AO‑2022‑049‑001 in conjunction with this investigation report. The safety advisory notice draws attention to the management of O-ring seals in engine components and their pro‑active removal from service, should inspection of aircraft records indicate a significant time‑in‑service.
Safety Action by the Civil Aviation Safety Authority
In response to the investigation finding related to deteriorated O-ring seals, the Civil Aviation Safety Authority proposed to review Airworthiness Bulletins AWB 02-001 and AWB 85-004 and most likely update them. The update would serve as a reminder to industry of some of the concepts and philosophy related to ‘on-condition’, which is not a ‘fit and forget’ approach to preventative maintenance.
Sources and submissions
Sources of information
The sources of information during the investigation included the:
Civil Aviation Safety Authority
aircraft manufacturer
registered operator
maintenance organisation for VH-UDQ
accident witnesses
recorded data from AvPlan.
References
Brady, G.S. and Clauser, H. R. (1991), Materials Handbook: An Encyclopaedia for Managers, Technical Professionals, Purchasing and Production Managers, Technicians, Supervisors, and Foremen, McGraw-Hill, Inc. New York, NY, USA
Brink, R.V., Czernik, D.E., and Horve, L.A. (1993), Handbook of fluid sealing, McGraw-Hill, Inc. New York, NY, USA.
Federal Aviation Administration (1998), Advisory Circular 43.13-1B, Acceptable methods, techniques and practices-aircraft inspection and repair, U.S. Department of Transportation, Oklahoma City, OK, USA.
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
aircraft manufacturer
Civil Aviation Safety Authority
engine manufacturer
National Transportation Safety Board
registered operator/owner.
Submissions were received from the Civil Aviation Safety Authority.
The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1]All heights in this report are referenced to the Luskintyre airfield elevation of 35 m (115 ft)
[2]Common traffic advisory frequency (CTAF): a local VHF radio frequency used for air‑to‑air communication at non‑towered airports. The frequency was shared between airfields in the local area that included Maitland and Cessnock Airports and Luskintyre airfield.
[3]Runway number: the number represents the magnetic heading of the runway.
[4]On-condition: A type of aircraft maintenance in which parts are replaced only when their condition appears no longer airworthy, instead of at pre-determined intervals of operation.
[5]Runway numbers: the number and its reciprocal represent the magnetic headings of the runways.
[6]AvPlan: the AvPlan EFB application allows users, with appropriate setting selected, to track and record flight path information based on the position of the device. This data can then be downloaded either from the device or from the application servers.
[7]RPM: Revolutions per minute – a measure of the speed of a rotating unit.
[8]Resilience: In material science, resilience is the ability of a material to absorb energy when it is deformed elastically and release that energy upon unloading. An ability to return to its original size and shape after deformation.
[9]The decrease in thickness of a rubber specimen which has been deformed under specific conditions of load, time and temperature.
[10]Log Book Statement: a document forming part of the log book that specifies an aircraft’s maintenance needs that includes CASA and the aircraft manufacturer’s requirements, any special conditions, and the validity period of the maintenance release.
[11]For statistical purposes, an injury is classified by the International Civil Aviation Organization as a fatal injury when death results within thirty days of the date of the accident.
On the afternoon of 28 September 2022, a Boeing Company 787-9 (787), registered G-ZBKF, was being operated by British Airways as flight number BA16, on an air transport flight from Sydney, New South Wales, to Singapore. At the same time, an Airbus A330-202 (A330), registered VH-EBK, was being operated by Qantas Airways as flight number QF926, on an air transport flight from Sydney to Cairns, Queensland.
At approximately 1508 local time, BA16 was cleared for take-off from runway 16R to conduct the DEENA SEVEN (DEENA 7) standard instrument departure (SID). Shortly after, QF926 was also cleared for take-off conducting the same SID. The Departure controller cleared both aircraft, in sequence, to climb to flight level 280 via the SID.
During the departure, the following aircraft climbed faster than the controller anticipated and turned towards the next waypoint inside the preceding aircraft, resulting in a loss of separation.
What the ATSB found
The ATSB found that the actual climb performance of the A330 was greater than the climb performance of the 787 which was not expected, or identified, by the controller due to their focus on other aircraft. This resulted in the A330, while complying with the SID, turning inside the leading 787, resulting in the loss of separation.
The ATSB also found that the design of the DEENA SEVEN SID did not provide a positive method of providing separation assurance to aircraft with different performance characteristics. As the aircraft had to satisfy 2 separate conditions prior to turning, there was no way of ensuring aircraft would turn at the same distance from the airport. That is, separation could not be assured.
What has been done as a result
Airservices Australia advised that the DEENA SEVEN SID has been redesigned to remove the conditional requirements of the procedure. The change has been approved and planned to be released as part of the Western Sydney International (Nancy-Bird Walton) Airport project. At the time of writing Airservices Australia was developing a timeline for the implementation of the redesigned SID. As such, the ATSB will continue to monitor the safety issue and provide website updates.
Safety message
Maintaining separation in high traffic terminal areas, such as Sydney, requires that both controllers and flight crews remain vigilant, maintain open communications, and use the available systems and tools to minimise the risk of errors. When sequencing departures, controllers should consider a number of factors, including how the flight duration (and the associated fuel load), will likely affect aircraft climb performance.
Standard instrument departures are designed to expedite the safe and efficient flow of air traffic operating from airports through the use of specific routings, levels, speed restrictions and waypoints. Where a SID, with limited designed separation assurance is used, it is important that air traffic controllers regularly monitor individual aircraft performance rather than rely on expected flight characteristics.
The occurrence
On the afternoon of 28 September 2022, a Boeing Company 787-9 (787), registered G-ZBKF, was being operated by British Airways as flight number BA16, on air transport flight from Sydney, New South Wales, to Singapore. At the same time, an Airbus A330-202 (A330), registered VH-EBK, was being operated by Qantas Airways as flight number QF926, on air transport flight from Sydney to Cairns, Queensland.
The Sydney Airport automatic terminal information service (ATIS)[1] indicated that parallel runways were in use, including simultaneous independent departures[2] from runways 16R and 16L.[3]
At approximately 1508 local time, BA16 was cleared for take-off from runway 16R by the Sydney tower controller. They were cleared to conduct a DEENA SEVEN (DEENA 7) standard instrument departure (SID)[4] (Figure 1) from runway 16R and to climb to 5,000 ft.
The DEENA 7 SID required an aircraft to turn right as soon as practicable after take-off, towards the DUNES waypoint[5] and then turn left to track 152° towards the DEENA waypoint. The aircraft was required to have passed DEENA and climbed above 6,000 ft prior to turning right towards the ANKUB waypoint. If the aircraft had not reached 6,000 ft at DEENA, there was a requirement to continue on a heading of 152° until passing an altitude of 6,000 ft, before turning towards ANKUB.
Passing 1,500 ft, the flight crew contacted the departure controller (Departures) and advised them that they were a heavy aircraft[6] on climb to 5,000 ft, departing via the DEENA 7 SID. Departures advised the flight crew the aircraft was identified on radar and instructed them to climb via the SID to flight level (FL) 280.[7]
Figure 1: DEENA SEVEN standard instrument departure (SID) from runway 16R
Source: Airservices Australia, annotated by ATSB
At approximately 1511, and with 6.3 NM spacing behind BA16, QF926 departed from runway 16R, also cleared on a DEENA 7 SID. During the initial climb, the flight crew contacted Departures advising that they were a heavy aircraft, passing 1,500 ft on climb to 5,000 ft, cleared on a DEENA 7 SID. Departures subsequently cleared them to climb to FL 280 via the SID.
BA16 climbed through 6,000 ft at around 25 km from Sydney Airport and initiated a turn to ANKUB in accordance with the SID. QF926 passed DEENA approximately coincident with climbing through 6,000 ft and initiated a turn to ANKUB at approximately 20 km from the airport, also in accordance with the SID (Figure 2).
Figure 2: Flight tracks of both aircraft during their departure from Sydney
Qantas Q926 is depicted in orange and BA16 is depicted in green.
Source: Google Earth with Flight Radar 24 tracks and annotated by ATSB
As QF926 was turning, the controller detected that the aircraft had climbed faster than they had anticipated and instructed QF926 to stop their climb at 9,000 ft, to which the flight crew advised they would do their best. The controller then instructed BA16 to expedite their climb through 10,000 ft.
The controller subsequently advised the flight crew of QF926 that there was a 787 above their aircraft, and they would step climb their aircraft underneath the 787. The Qantas flight crew advised they had sighted the higher aircraft.
There was a loss of separation standards (see the section titled Required separation) between the two aircraft with the minimum vertical separation reducing to 600 ft and lateral separation reducing to 2.4 NM.
The flight crew in BA16 later advised that they had received a traffic alert and collision avoidance system (TCAS)[8] traffic advisory[9] during the event and the first officer subsequently visually identified the A330. They also advised they were informed by air traffic control of the traffic, however this was not recorded on the departures frequency.
Context
Air traffic controller information
The controller had worked as a controller from 2008 and had moved to Sydney in 2015 where they had qualified in both the Sydney Approach Director and Departures positions. While they mainly worked in the Approach Director position, they were rostered in the Departures position regularly to remain current in that role.
They had conducted compromised separation training in their last departures refresher training session in June 2022.
The controller advised that they expected the A330 would have a comparative climb performance to the 787. Hence, they instructed them to follow the 787. Qantas typically utilised the A330 on international routes, however, more recently had been utilising the A330 on domestic routes, including Sydney to Cairns, with correspondingly lower fuel loads and higher climb performance.
The controller then proceeded to assess other traffic in the area. Specifically, they were assessing a track for an aircraft, on descent from FL 280 to Shellharbour to ensure separation between this aircraft and an Airbus A380, which was in the list to depart runway 16R. They were also assessing the departure tracks for other aircraft due to depart from runway 16L and coordinating a media helicopter, overflying the airspace at 500 ft, with the Bankstown Airport tower controller. The controller advised they considered their workload to be manageable at the time.
Air traffic control procedures
Departure procedures
At the time, auto-release departures were in progress at Sydney Airport. This procedure allowed the tower controller (Tower) to depart aircraft without prior coordination with the departures controller (Departures). Departures had a list of aircraft on their console which were due to depart. These aircraft were listed in order of departure from the runway they were using, but the Tower controller could depart the aircraft from either runway in the order which allowed best use of the runways.
Tower was required to ensure there was a minimum separation between the aircraft of 5 NM when aircraft were departing from runway 16R. When using the DEENA 7 SID, Tower cleared the aircraft to climb to 5,000 ft via the SID, this ensured that departing aircraft continued on a heading of 152° and would not initiate a turn unless they received a further clearance from Departures.
Required separation
The required separation standards at Sydney are specified in the manual of air traffic services (MATS). The manual specified that the separation standard in the Sydney terminal control unit (TCU) was 3 NM lateral or 1,000 ft vertical separation. However, the wake turbulence standards between 2 heavy aircraft, required a minimum of 4 NM separation where aircraft were departing using the same runway, which was the case for this departure.
The A330 departed with the required spacing behind the preceding B787.
Controller traffic alerts
The controller advised they did not receive a short-term conflict alert (STCA) on their console during the event. A replay of the recorded surveillance data indicated the STCA was displayed on a number of occasions. However, Airservices advised that the replay was not a reproduction of the controller’s screen at the time. The parameters for a STCA in the TCU environment are that within the following 60 seconds the aircraft will infringe 2.1 NM lateral separation and or 600 ft vertical separation. In this case, as the separation reduced to 600 ft and 2.4 NM in a turn, it is possible that due to the dynamics of the event, the STCA may not have shown on the controller’s console. However, the ATSB was unable to determine whether the controller received a STCA on their console.
Issuing safety alerts
According to MATS, where a controller becomes ‘aware that an aircraft is in a situation that places it is unsafe proximity to…other aircraft’, the controller should issue a ‘safety alert’. They should also use the term ‘avoiding action’ prior to instructions when in the controller’s judgement, the aircraft ‘is in a situation that places it at risk of a collision with another aircraft under surveillance’.
Weather
The weather at the airport during the occurrence was fine, with good visibility, scattered[10] cloud at 3,000 ft and a 15 kt easterly wind.
Replanning of Sydney Airspace
Airservices Australia advised that in response to the replanning of the airspace in the Sydney area due to the establishment of the Western Sydney International (Nancy-Bird Walton) Airport, which is due to open in 2026, the DEENA 7 SID has been redesigned.
Related occurrences
In the last 10 years, across Australia, there have been 8 occurrences of a loss of separation reported to the ATSB involving aircraft cleared on a SID where a following aircraft has climbed faster than the preceding aircraft.
Of these, 6 occurrences were at Sydney Airport and 5 of these involved the DEENA 7 SID. Of these, 1 occurred in 2012, 1 in 2019, 1 in 2020, and 2 in 2022.
Safety analysis
During the departure of two heavy aircraft conducting the DEENA SEVEN standard instrument departure (SID), the controller assessed that the following Airbus A330 would have a similar climb performance to the leading Boeing 787, without considering that the A330 was conducting a domestic flight and would therefore have a significantly lower fuel load and better climb performance than the preceding heavily‑loaded 787. The controller cleared both aircraft, in sequence, to climb to the same level. The controller then became distracted, planning the separation between 2 other aircraft and did not detect the variation in climb performance between the departing A330 and 787.
As the actual climb performance of the A330, on a domestic route, was greater than the climb performance of the 787 on an international route, the separation reduced. When the controller detected the closing aircraft, they instructed both flight crew to take action to increase the separation between their aircraft. During the occurrence, it is likely the controller did not receive a short-term conflict alert (STCA) warning however, they did suspect there had been loss of separation and did not provide a safety alert or advise that the instruction was an avoiding action.
The use of SIDs ‘enable the safe and efficient processing of instrument flight rules[11] aircraft … from airports’ (Airservices Australia) and will ‘deconflict potentially conflicting traffic by the use of specific routings, levels, speed restrictions and check points’ (Skybrary). They are particularly useful in high traffic airspace such as departing Sydney Airport. However, according to Airservices Australia, SIDs do not provide longitudinal separation between aircraft which are following in trail with another aircraft, with controller action ensuring the maintenance of separation.
Despite this, the design of the DEENA SEVEN SID (and possibly others) did not provide a positive method of providing lateral separation assurance to departing aircraft with differing climb performance. As the aircraft had to satisfy 2 separate conditions prior to turning, there was no way of ensuring aircraft would turn at the same distance from the airport. As such, lateral separation could not be assured.
Airservices Australia advised that the DEENA SEVEN SID had been redesigned to remove the conditional requirements of the procedure. At the time of writing, the change had been approved and was planned to be released in the first implementation package for the Western Sydney International (Nancy-Bird Walton) Airport project. However, no timeframe for the release of the package was provided.
Findings
ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition ‘other findings’ may be included to provide important information about topics other than safety factors.
Safety issues are highlighted in bold to emphasise their importance. A safety issue is a safety factor that (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
From the evidence available, the following findings are made with respect to the loss of separation involving Airbus A330, VH-EBK, and Boeing 787, G-ZBKF near Sydney Airport, New South Wales on 28 September 2022.
Contributing factors
When clearing two aircraft on the DEENA 7 standard instrument departure, the controller incorrectly assessed that they would have similar climb performance and became distracted and did not detect the relatively higher climb performance of the departing Airbus A330 aircraft. This resulted in the A330 turning inside the preceding Boeing 787 and a loss of separation standards with that aircraft.
The DEENA 7 standard instrument departure has no designed positive separation assurance method, making it susceptible to loss of separation occurrences. (Safety issue)
Safety issues and actions
Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies.
Depending on the level of risk of a safety issue, the extent of corrective action taken by the relevant organisation(s), or the desirability of directing a broad safety message to the aviation industry, the ATSB may issue a formal safety recommendation or safety advisory notice as part of the final report.
All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out or are planning to carry out in relation to each safety issue relevant to their organisation.
Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.
DEENA 7 Standard instrument departure had no positive separation assurance method
Safety issue description: The DEENA 7 standard instrument departure has no designed positive separation method, making it susceptible to loss of separation occurrences.
Glossary
ATC Air traffic control
ATIS Automatic terminal information service
FL Flight level
IAS Indicated airspeed
MATS Manual of air traffic services
SID Standard instrument departure
STCA Short-term conflict alert
TCAS A type of airborne collision avoidance system (ACAS).
TCU Terminal control unit
Sources and submissions
Sources of information
The sources of information during the investigation included the:
involved air traffic controller
flight crew notifications
Airservices Australia
Skybrary
Submissions
Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.
A draft of this report was provided to the following directly involved parties:
Involved air traffic controller
Airservices Australia
Civil Aviation Safety Authority
Qantas
Air Accidents Investigation Branch, United Kingdom
A submissions was received from:
Airservices Australia
The submission was reviewed and, where considered appropriate, the text of the report was amended accordingly.
Purpose of safety investigations
The objective of a safety investigation is to enhance transport safety. This is done through:
identifying safety issues and facilitating safety action to address those issues
providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.
It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.
Terminology
An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.
Publishing information
Released in accordance with section 25 of the Transport Safety Investigation Act 2003
Ownership of intellectual property rights in this publication
Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.
Creative Commons licence
With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.
Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.
The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau
Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.
[1] Automatic terminal information service (ATIS): continuous broadcast of recorded aeronautical information. ATIS broadcasts contain essential information, such as current weather information, active runways, available approaches, and any other information required by flight crew.
[2] Simultaneous independent departures are simultaneous departures for aircraft departing in the same direction from parallel runways.
[3] Runway number: the number represents the magnetic heading of the runway. The runway identification may include L, R or C as required for left, right or centre.
[4] Standard instrument departure (SID): an air traffic control (ATC) defined procedure, that simplifies departure tracking while also balancing terrain/obstacle avoidance, noise abatement and airspace management considerations.
[5] Waypoint: A defined position of latitude and longitude coordinates, primarily used for navigation.
[6] Wake turbulence separation is determined by aircraft maximum take-off weight. Aircraft with a maximum take-off weight of 136,000 kg or greater are categorised as heavy aircraft.
[7] Flight level: at altitudes above 10,000 ft in Australia, an aircraft’s height above mean sea level is referred to as a flight level (FL). FL 280 equates to 28,000 ft.
[8] Traffic alert and collision avoidance system (TCAS): a type of airborne collision avoidance system (ACAS).
[9] Traffic advisory (TA): an alert issued by an airborne collision avoidance system (ACAS) when the detected traffic may result in a conflict. Pilots are expected to initiate a visual search for the traffic causing the TA.
[10] Cloud cover: in aviation, cloud cover is reported using words that denote the extent of the cover – ‘scattered’ indicates that cloud is covering between a quarter and a half of the sky
[11] Instrument flight rules (IFR): a set of regulations that permit the pilot to operate an aircraft in instrument meteorological conditions (IMC), which have much lower weather minimums than visual flight rules (VFR).
Occurrence summary
Investigation number
AO-2022-047
Occurrence date
28/09/2022
Location
Near Sydney Airport
State
New South Wales
Report release date
03/03/2023
Report status
Final
Investigation level
Defined
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
Airbus
Model
A330-202
Registration
VH-EBK
Serial number
0945
Aircraft operator
Qantas Airways
Sector
Jet
Operation type
Part 121 Air transport operations - larger aeroplanes