On the morning of 9 January 2015, a Regional Express operated SAAB 340B aircraft, registered VH-OLM struck a flock of birds during its landing roll at Moruya, New South Wales. Inspection of the aircraft by the flight crew found bird impact marks but no visually identifiable damage. The crew continued their schedule to Merimbula, New South Wales. At Merimbula, the first officer noticed the tip of one propeller blade was missing, and the aircraft was subsequently grounded.
What the ATSB found
The blade tip failure was almost certainly a result of the birdstrike during the landing roll of the previous flight, weakening the internal structure of the blade.
The flight crew conducted a visual inspection in accordance with the operator’s procedures, and this inspection did not find any damage. However, the propeller manufacturer’s birdstrike inspection procedure was deemed a maintenance task. As such, it was not suitable for flight crew.
What's been done as a result
The operator changed its birdstrike procedures to ensure aircraft remained on the ground until a maintenance inspection was carried out in accordance with appropriate documented inspection procedures. In addition, pilot and engineering notices were issued clarifying these requirements.
Adherence to regulations and company procedures is essential for the ongoing airworthiness of aircraft. Therefore, it is vital that procedures are clear and do not lead to ambiguity or misinterpretation. Where uncertainty exists, seeking clarification from the relevant authority can reduce the risk of an unserviceability affecting flight safety.
On the morning of 9 January 2015, the crew of a Regional Express operated Saab 340B aircraft, registered VH-OLM, and were conducting a series of scheduled passenger flights between Sydney, Moruya and Merimbula, New South Wales. The first officer was the pilot flying on the Sydney to Moruya sector.
At about 0955 Eastern Daylight-saving Time, a visual, straight-in approach was conducted to land on runway 18 at Moruya. The aerodrome forecast for arrival at Moruya showed a 7 kt wind from the north-east, good visibility and cloud from 2,000 ft above the aerodrome.
After touchdown, as the aircraft slowed through 80 kt, the captain took control of the aircraft for the taxi to the terminal in accordance with normal company operating procedures. The crew reported that, shortly after the captain took control, a large flock of galahs took off from the grass to the west (right) of the runway and flew at a low height over the runway eastbound (Figure 1). In anticipation of a birdstrike, the captain increased wheel braking and applied reverse thrust on both engines. Prior to reaching the galahs forward thrust was selected. Despite that action, about halfway down the runway the first officer observed birds had impacted the aircraft.
Figure 1: Moruya Airport showing aircraft and galah flock direction of travel and approximate impact point
Source: Google maps (Modified by the ATSB)
On reaching their designated parking area, and in accordance with the operator’s birdstrike procedures, the flight crew carried out testing of the ice protection system before the engines were shut down, with no issues identified. Once the passengers who were disembarking at Moruya had left the aircraft, the first officer commenced an external inspection of the aircraft. The captain notified the airport reporting officer of the birdstrike. The airport safety officer subsequently found around 10 bird carcases on the runway.
The first officer found clear evidence of multiple birdstrikes on the right side of the fuselage, and the right engine and propeller, in the form of blood staining and bird carcass debris. One of the left engine propeller blades also displayed blood staining and white powder marks, consistent with a birdstrike. Despite the bird impacts, no evidence of ingestion into the engines or physical damage to the aircraft or propeller blades was observed.
The captain and the first officer reported that they subsequently carried out a detailed visual examination of the birdstrike-affected blades. The examination included rotating the propellers so that the forward and aft blade surfaces could be inspected for cracking, buckling, chips, dents or deformation along each affected blade’s leading edge. When no damage was identified, the captain contacted the operator for further technical advice and the crew were subsequently cleared to continue with the flight schedule.
The crew then operated the aircraft from Moruya to Merimbula. After engine shutdown at Merimbula, the first officer opened the forward left door and observed that the tip of one of the left propeller blades had detached (Figure 2). The aircraft was declared unserviceable and grounded.
There were no reported injuries to the crew or passengers. No damage to the aircraft structure was identified as a result of the loss of the blade tip.
Source: Regional Express
Both the captain and first officer held valid Class 1 medical certificates, and were appropriately qualified to conduct the flight. The captain had a total aeronautical experience of approximately 7,000 hours with 4,300 hours flying Saab 340 aircraft. The first officer had a total aeronautical experience of around 5,400 hours with 4,200 hours flying Saab 340 aircraft.
A review of the crew’s recent history indicated that fatigue was not a factor, with both crew reporting they had an average to good sleep during the previous 72 hours.
The aircraft, a Saab Aircraft CO 340B-2, was manufactured in 1990 and entered the Australian aviation register in October of that year. The aircraft is a twin engine turbo-prop and configured to carry 36 passengers and three crew. The aircraft was maintained under Civil Aviation Safety Regulation Part 42, which detailed the continued airworthiness requirements for regular public transport aircraft.
Aircraft damage information
The majority of the bird remains were found on the right side of the fuselage behind the forward right door, which was consistent with birds contacting the lower half of the right propeller disc. Small items of debris were also observed on both engine nacelles. There was no evidence of debris entering either engine. All of the blades on the right propeller showed evidence of impact with birds. Only one blade on the left propeller displayed evidence of bird contact.
Data from the aircraft’s flight data recorder for the flight from Moruya to Merimbula was examined. That data did not show any anomalies that would have identified the point when the propeller blade tip separated.
Propeller blade construction
The propeller blades were manufactured by Dowty Propellers. They were made of composite construction with a polyurethane foam core, carbon fibre spars, glass fibre skin, and a polyurethane coating. A braided metal strip between the glass fibre and polyurethane coating ran from the tip of the blade to its root, providing lightning protection (Figure 3).
Figure 3: Propeller blade construction
Source: Dowty Propellers modified by ATSB
Left propeller blade damage
The left propeller blade presented with white powder impact marks toward the trailing edge, about 300–400 mm from the blade tip; about one third up the blade’s length. A section of blade was missing from the tip. Within the tip damage region, splitting at the trailing edge was identified (Figure 4). Damage to the leading edge erosion strip near the tip was also identified, with kinking on the back, and a corresponding crack on the front of the blade.
Figure 4: Left propeller blade damage showing tip separation, kinking, crack, and splitting of trailing edge
A review of the damaged blade’s service history showed it was installed on the propeller as a new item in 2000. The propeller had also undergone a number of inspections since that time, including overhaul in 2011. The overhaul facility advised that during the 2011 propeller overhaul, ultrasonic NDT was carried out on the propeller’s blades. All of the blades were found to be serviceable. There were no reported incidents of impact to the blade prior to this occurrence.
The damaged blade was sent to the ATSB for in initial assessment. A visual inspection, and a ‘tap test’ using a metallic object were conducted on the blade. That test revealed a potential area of delamination or disbond under the surface extending from the tip separation point.
The blade was subsequently sent to a third party laboratory for NDT and destructive testing under the supervision of the ATSB. A dual probe ultrasonic tester was used over the entire surface of the blade. Disbond was detected in a region extending from the spar through to the tip of the blade (Figure 5A). Further destructive testing in the form of surface grinding was carried out to determine at which layers the disbond had occurred. That action showed disbonding at the carbon fibre spar tips. The disbond had also propagated along the glass fibre layer of the blade beyond the spars (Figure 5B).
The propeller manufacturer determined the damage was consistent with the effects of impact on the blade from the birdstrike. The most likely failure mechanism was considered to be delamination between the blade’s foam core and spar barrier membrane. The delamination then progressed outboard into the fibreglass layer beyond the spar resulting in the subsequent tip failure.
The propeller manufacturer concluded that the kink in the erosion strip on the back of the blade (Figure 4) was consistent with an impact on the front of the blade near the tip, bending the blade tip rearwards rather than forwards. The manufacturer considered this damage was consistent with a bird or other hard object impact. It also stated that it considered that the buckling of the guard would probably have occurred as a result of the impact rather than due to subsequent aerodynamic loading. Therefore, it believed the kink would most likely have been present at the time the blade was inspected at Moruya.
Propeller and blade maintenance requirements
The operator’s policy and procedures manual included a section on birdstrikes, which stated:
Following a known or suspected Bird Strike the Flight Crew must complete the External Inspection (Crew Change) in its entirety in accordance with the Saab 340 Flight Crew Operating Manual [FCOM].
Generally, blood and/or feathers are noticeable in the impact area of a bird strike. In low light conditions a torch must be used.
Any defect, major damage or evidence of ingestion into an engine or airframe intake (include AC & DC Generator intakes) must be entered in an AML [aircraft maintenance log] and an engineering inspection must be performed prior to any subsequent flight.
If the inspection does not reveal the existence of a defect or damage, and there was no effect on the aircraft’s performance following the event, the aircraft may continue to operate.
Prior to the next flight, the Ice Protection must be checked in accordance with the Saab 340 Flight Crew Operating Manual.
Flight crew inspections
The operator’s Saab 340 flight crew operating manual (FCOM) included procedures for three types of external aircraft inspections by flight crew:
- daily inspection, conducted prior to the first flight of the day
- crew change inspection, conducted prior to the next flight when a flight crew accept an aircraft previously flown by another crew that day, if the aircraft has been taken off-line for maintenance during the day, or the aircraft is left unattended and not under continuous surveillance of the flight crew
- post flight inspection, conducted at the conclusion of each flight.
The FCOM procedures for a daily inspection and a crew change inspection both included a detailed list of items required to be checked by a flight crew. The only propeller specific items were:
Inspect propeller assembly for oil or grease leakage from hub assembly
Inspect propeller de-icer boots…
The FCOM procedures for a post-flight inspection included a smaller list of items. In terms of propellers, the items included:
Propellers – including freedom of rotation and each blade front and back for obvious damage.
The operator’s system of maintenance was conditional on the inclusion of the relevant manufacturer’s maintenance manuals. Consequently, birdstrike inspection procedures were derived from the aircraft manufacturer’s aircraft maintenance manual (AMM) for airframe inspections, and the propeller manufacturer’s component maintenance manual (CMM) and an aircraft specific propeller maintenance manual (PMM) for propeller inspections.
The CMM and PMM provided the primary source of information on maintenance requirements and serviceability limitations of the propeller and its blades. Contained within the introduction chapter of the CMM was the statement:
Use qualified personnel and good engineering practice for all procedures and standard practices used in this manual.
The PMM inspection and check section included the following requirements in a section titled ‘Bird Strike or other Impact Damage’:
1. Propellers which have had, or are thought to of had a bird strike or other impact must be examined immediately.
2. Refer to propeller blade damage limits for allowable damage limits and repairs. Refer to CMM 61-10-39 Check. If the damage is within the allowable limits the propeller can stay in service.
3. If the damage is more than the allowable limits, but within the repair limits, a ferry flight may be allowed. The operator should write a ferry flight request on a concession form and send it to Dowty Propellers. Refer to Service Letter E340.
4. Equipment sent for repair must be clearly identified with the reason why.
The CMM 61-10-39 check section described the procedure of examination as a two-level process, consisting of a general check of all parts and a special check of specific parts. The section also contained non-destructive testing (NDT) techniques to be used on the blade assemblies and it provided blade damage limits relevant to blade location.
The CMM general check procedure included a section titled ‘Impact Damage’, which applied to birdstrikes. This section stated:
1. If the propeller has had impact damage, do the applicable visual and NDT inspection procedures given for the area of impact.
2. If the position of the impact will cause impact damage to other propeller components, do the applicable visual and NDT inspection procedures given for ‘secondary’ area of impact…
3. If it is not clear where the damage is, or if there is doubt concerning secondary impact damage contact Dowty Propellers.
The ATSB found ambiguity in the CMM procedures for assessing blades following a birdstrike impact. It was not readily apparent from the procedures whether the bird contact alone would constitute damage or whether subsequent blade NDT was required. As a result, the ATSB sought clarification from the manufacturer. The manufacturer advised:
Generally, the intent is that there must be signs of damage before NDT is required.... Not many impacts leave no trace at all and generally, anything that is going to cause structural damage will have an associated visual indicator…
Dowty would not consider evidence of animal matter as damage however it would be an indication that there had been an impact and that further investigation may be needed, again we would always recommend caution if there was any doubt.
Therefore, according to the manufacturer, the presence of feathers and dust marks (a visual indicator), while not displaying visible damage, may require further investigation.
In 2011, the operator applied to the Civil Aviation Safety Authority (CASA) for approval to allow flight crew to undertake birdstrike inspections of aircraft. The CASA response (9 February 2012) highlighted the requirements of the Civil Aviation Safety Regulation Part 42 and the associated Part 42 Manual of Standards. Guidance on the continuous airworthiness requirements was provided, including examples of situations that would exclude flight crews’ ability to undertake inspections, as well as situations where flight crew inspections would be allowed.
CASA determined that where a specific birdstrike inspection was required by a manufacturer, that inspection would be deemed an engineering maintenance task and outside the scope of flight crew approved maintenance. Where specific inspection requirements did not exist and where there had been no effect on the aircraft’s performance, external inspection by flight crews to determine if damage had been sustained was acceptable. CASA stated that the operator needed to submit its proposed procedures to CASA’s oversighting office for the operator.
Based on the CASA advice, and believing there was no manufacturer specific inspection, the operator developed a draft birdstrike inspection procedure for flight crew. The draft procedure (and associated external inspections) was submitted to CASA’s oversighting office for the operator and, following minor amendments, was issued to flight crew in an operations notice on 24 February 2012, and incorporated into the operator’s policy and procedures manual in April 2012.
Following the 9 January 2015 occurrence, the operator advised the ATSB that it had misinterpreted the requirements in the CASA letter. The operator also advised that when it developed its birdstrike procedure, it relied on the aircraft manufacturer’s AMM and information from the aircraft manufacturer. It inadvertently did not consider the propeller manufacturer’s PMM. As noted in in the previous section, the PMM documented a birdstrike inspection.
The operator advised the ATSB that it had approached the propeller manufacturer to include tap testing of the blade surface as part of the engineering birdstrike inspection procedure. The manufacturer indicated that a tap test of the blade is of very limited value because it did not give a sufficiently definitive result and risked not detecting blade delamination, except for the blade erosion strip.
Wildlife hazard management requirements and guidance
General requirements and guidance
A number of regulations, standards, and guidelines apply to wildlife hazard management at airports. The International Civil Aviation Organization established the standards for the management of collisions between wildlife and aircraft. It also provides guidance on effective wildlife management programs.
Within Australia, CASR 139 required a certified aerodrome to have an aerodrome manual, which must include details regarding bird and animal hazard management. The Manual of Standards (MOS) for Part 139 provides more detailed requirements. These included a requirement that, where regular monitoring confirmed the existence of a bird or animal hazard, or at the direction of CASA, the aerodrome operator must develop a bird or animal hazard management plan. The plan had to be developed by a suitably qualified person such as an ornithologist or biologist, and had to address the following factors:
- hazard assessment, including monitoring action and analysis;
- pilot notification [reporting];
- liaison and working relationships with land use planning authorities;
- on-airport bird and animal attractors which provide food, water or shelter
- suitable harassment methods; and
- an ongoing strategy for bird and animal hazard reduction, including provision of appropriate fencing.
Advisory Circular (AC) 139-26(0) Wildlife hazard management at aerodromes provides further guidance information about managing wildlife hazards at aerodromes. It states that that once a wildlife hazard is identified, appropriate and effective treatment should be employed. Treatment methods fall into two categories:
- pre-emptive (such as removal of food sources, maintenance of grass, etc.) and where necessary
- active (such as scare tactics using horns, siren, or dogs).
Further guidance on wildlife hazard management is available from the Australian Aviation Wildlife Hazard Group document Wildlife Risk Assessment and Analysis, and the Australian Airport Association’s publication Wildlife Hazard Management at Airport - Airport Practice Note 9.
The ATSB’s bird information data sheets for the management of birdstrike risks at airports, ATSB bird information sheet number 6, refers to the galah (reproduced in the Appendix). The information sheet advises that all bird management strategies should seek to make an airport as undesirable as possible to birds through habitat modification. With regard to galahs, amongst various suggestions, it recommends that:
- a tall grass policy (30 cm) be maintained as galahs find it difficult to see approaching predators
- manage grasslands to limit production of seeds.
Additional active management strategies that can be used to disperse and control the birds include:
- use of pyrotechnics (cracker shells), portable distress callers, sirens, lights and vehicles
- use of trained animals (birds of prey, dogs, etc.), and where necessary, and permitted, culling may be required.
Moruya was a certified, uncontrolled, two runway airport situated close to the coastline (Figure 1).
The airport had a bird and animal (wildlife) management program. This includes daily inspection of the airport with reporting on wildlife activity, low level harassment with a vehicle to disperse wildlife, and maintenance of grass areas to minimise or deter habitation. The airport coordinator advised that the local galahs tended to stay close to the buildings and trees, but it was not usual for them to be in the runway area. The grass around the runway was long and had been scheduled for cutting that day. The airport coordinator considered the longer grass may have attracted the galahs to feed on the grass seeds.
The airport’s records of wildlife strikes indicated they were not seasonal, with birdstrikes occurring throughout the year, over the previous five years. In 2014, however, the only three reported birdstrikes were confined to the first quarter of the year (January to March). None of these involved galahs.
A review of the 2014 annual report revealed a consistent number of galahs resided at the airport, with between two and 10 birds observed regularly. Their activity was predominantly around the terminal area in the early morning, usually departing before 0800. There was only one instance of flocking behaviour by galahs in the 2014 report. That occurrence was in February 2014 when large groups of about 32 galahs were observed coming in from a nearby camping area to graze near the terminal building, and departing by about 0800.
The presence of birds at Moruya Airport was frequent and significant enough for the aeronautical information package, En Route Supplement Australia, to include an additional information note that a bird hazard exists.
The ATSB compared birdstrike rates per 10 000 aerodrome movements for Moruya against other regional aerodromes, and the birdstrike rates for Moruya were considerably lower than most.
A review of the ATSB occurrence database for the period 1977 to 2014 did not reveal any additional blade failures or in-flight blade tip failures for the propeller type due to a birdstrike.
During the landing roll at Moruya Airport, a number of birds were struck. On the following flight, the left propeller blade tip failed. This analysis examines the actions of the flight crew, the failure mechanism of the blade, inspection requirements following a birdstrike, and factors that may have identified the potential risk of blade failure.
Flight crew actions
The presence of galahs to the right of the runway during the landing roll presented a high risk of impact to approaching aircraft. The captain followed appropriate actions to maximise aircraft deceleration while minimising potential impact damage through effective use of reverse thrust and aircraft wheel braking. Despite the crew’s best efforts, the subsequent impact with the birds was considered unavoidable.
The birdstrike inspection carried out by the flight crew was in accordance with the operator’s procedures. The crew reported performing a thorough visual inspection of the individual blades on both propellers, including rotation of the propellers to sight along each blade surface for damage or deformation. Despite the lack of visible damage associated with the bird impacts, the captain sought further advice from the operator’s engineering department before determining the aircraft was serviceable. The engineering department reportedly advised the captain to follow the flight crew’s documented procedures, and if no damage was evident, continue with the flight schedule.
Blade failure mechanism
Review of the blade’s service history showed it had undergone numerous non-destructive tests (NDT) and inspections, including an ultrasound inspection in 2011. None of those inspections revealed evidence of internal delamination. As there were no previously reported incidents of impact to the blade, it is unlikely that a pre-existing defect below the blade surface existed or influenced the blade’s failure.
Examination of the blade found that the failure mode was consistent with a bird impact. Consequently, given the failure occurred on the flight following the birdstrike, it is almost certain that impact with one or more galahs initiated the internal delamination of the blade. This led to a rapid decay of its structural integrity and subsequent separation of the tip, as the blade was subjected to aerodynamic loads during the following flight.
The propeller manufacturer indicated that the buckling of the blade guard would probably have occurred as a result of the impact rather than due to subsequent aerodynamic loading, and the damage to the guard would have been evident when the blade was inspected by the flight crew at Moruya.
The ATSB agrees it is plausible that the birdstrike resulted in cracking of the leading edge of the guard. However, the extent to which the damage to the guard would have been readily detectable when the blade was inspected at Moruya is unclear. Once the leading edge guard lost structural integrity, together with internal delamination damage, it is difficult to determine the nature of the subsequent loading conditions during flight.
The flight crew were not familiar with the propeller manufacturer’s inspection procedure, however, there were specific propeller inspection instructions in their normal procedures following a birdstrike, and the captain and first officer reported carrying out a thorough visual examination of the propeller blades in line with these procedures. Regardless of the nature of the flight crew’s inspection, both CASA and the propeller manufacturer considered the inspection to be a maintenance task, and required it to be carried out by qualified maintenance personnel.
The ATSB could not determine if an engineering inspection would have highlighted any possible damage. However, if an appropriately qualified person inspected the multiple bird impacts on the blades, they may have sought further advice from the propeller manufacturer in accordance with the documented propeller manufacturer’s maintenance procedure ‘if there is doubt concerning secondary impact damage…’ As the flight crew did not have this document, they would not have been aware of this procedure. Despite this, the captain did seek further advice from the operator’s engineering department. As an on-site engineering inspection was not carried out, the operator’s engineering department may not have had a full appreciation regarding the multiple birdstrikes.
The discussion between engineering and the flight crew focused on the presence of visible damage to the blade, and the documented flight crew inspection procedures. Consequently, the reported blade condition did not raise concerns with the engineering department about potential secondary damage or reduced structural integrity. That determination presented a missed opportunity to undertake an engineering inspection of the aircraft prior to take off. Consequently, the potential to detect sub-surface damage was also missed.
The Civil Aviation Safety Authority (CASA) provided the operator with advice on interpreting regulations for situations where pilots may or may not undertake birdstrike inspections. That advice included that if specific birdstrike inspection procedures within instructions for continuing airworthiness (ICA) deemed the inspection task as being a maintenance requirement then they were not suitable for flight crew. It is apparent the operator misinterpreted the advice from CASA as only referring to the aircraft manufacturer’s procedures and not also the propeller manufacturer’s procedures. As a result, the operator’s procedures allowed flight crew to undertake visual inspections after a birdstrike (beyond confirmation of whether there was a strike).
Moruya Airport bird and animal control
The frequency of bird and animal (wildlife) strike incidents over a 10 year period did not indicate that an increasing wildlife problem existed at Moruya Airport. The presence of galahs was common, however the galahs were typically in small numbers, and contained to around the buildings and treed areas.
According to the Moruya 2014 bird and animal report, and along with the birdstrike statistics for Moruya, the airport’s reliance on the maintenance of the grass adjacent to the runway as a pre-emptive means of bird management generally appeared to work for maintaining low wildlife strike incidents. On the day of the occurrence, the grass around the runway was long, and was scheduled for cutting later in the day. The ATSB bird information sheet indicates long grass can deter galahs. However, in this instance, the presence of grass seeds on the long grass may have contributed to their increased numbers and proximity to the runway. Consequently, when birds are located in the grass adjacent to the runway, an increased risk of aircraft strikes existed.
From the evidence available, the following findings are made with respect to the damage and subsequent propeller blade tip separation associated with the birdstrike occurrence involving a Saab 340B, registered VH-OLM, at Moruya Airport, New South Wales on 9 January 2015. These findings should not be read as apportioning blame or liability to any particular organisation or individual.
- The impact from multiple galahs almost certainly reduced the structural integrity of a propeller blade, resulting in the separation of its tip during the subsequent flight.
Other factors that increased risk
- The permitting of flight crew to carry out post birdstrike inspections was outside the approval of the regulator and propeller manufacturer, and reduced the likelihood of identifying serviceability issues.
Safety issues and actions
Additional safety action
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. The ATSB has been advised of the following proactive safety action in response to this occurrence.
As a result of this occurrence, Regional Express advised the ATSB that it had undertaken pro-active safety action through issuing the following:
- Notice to aircrew NOTAC 091/15, REPORTING OF BIRD AND WILDLIFE STRIKES - REISSUED. Which stated:
If there is any evidence of impact (blood/feathers/dust) on the propellers following wildlife strike the aircraft must not depart until an engineering inspection is complete. In addition to the requirements of PPM 13.1 1-Bird Strike, an AML [aircraft maintenance log] must be raised for wildlife impact with the propeller. All bird and wildlife strikes or suspected strikes encountered on approach/departure, take-off/landing should be reported to the Network Ops Centre (NOC) as soon as practicable following a strike. The NOC will then inform the aerodrome operator to enable immediate dispatch of the ARO [aerodrome reporting officer] to inspect the runway and vicinity of the airport in the effort to locate and remove any animal remains, as well as assisting in the identification of the species for wildlife management within the region. The SMS requirements remain unchanged.
- Notice to engineers NOTEM 83, Bird Strike Inspections. Which stated:
Until further notice if a bird (wildlife) strike is reported and there is evidence of impact (blood/feathers/dust) on the propeller then the aircraft must not be released to service until both the CAM [continued airworthiness manager] and Chief Pilot have given approval. AML is required to be raised for any event where there is evidence of impact on the propeller.
- Engineering technical notice TN-SAAB-6100-008-15, Propeller Bird Strikes. Which stated:
This Technical Notice is issued to provide information for engineers dealing with aircraft bird strikes involving contact with propeller or any other impact experienced by the propeller whilst installed.
When an aircraft is reported to have experienced a bird strike and there is evidence of contact with the propeller an AML must be raised and an engineering inspection of the propeller must be conducted IAW the applicable maintenance manual.
For Dowty propellers refer to the applicable Maintenance Manual and Component Maintenance Manual, a flow chart is provided on page 2 of this TN to help engineers perform the required inspection and make airworthiness assessment for Dowty propellers.
For the Hamilton Sundstrand propeller refer to the Maintenance Manual P5199, CHECK, Inspection After Impact procedure. A copy of this procedure is included on page 3 of this TN. Note: It is a requirement to check the blade track as part of this procedure.
The same procedures should be used for any report of impact experienced by the propeller while it is installed.
These notices were subsequently included in relevant manual updates.
Sources and submissions
Sources of information
The sources of information during the investigation included the:
- flight crew
- aircraft operator (Regional Express)
- propeller manufacturer
- propeller overhaul organisation
- Moruya airport operator
- United Kingdom Air Accidents Investigation Branch
- Swedish Accident Investigation Authority
- Australian Bureau of Meteorology.
Under Part 4, Division 2 (Investigation Reports), Section 26 of the Transport Safety Investigation Act 2003 (the Act), the Australian Transport Safety Bureau (ATSB) may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. Section 26 (1) (a) of the Act 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 captain, first officer, Regional Express, Moruya airport operator, Civil Aviation Safety Authority (CASA), Dowty Propellers, and the United Kingdom Air Accidents Investigation Branch.
Submissions with comments were received from the operator, CASA and the propeller manufacturer. The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.
Appendix A: ATSB Bird Information Sheet No 6
|Date:||09 January 2015||Investigation status:||Completed|
|Time:||10:50 ESuT||Investigation level:||Defined - click for an explanation of investigation levels|
|State:||New South Wales||Occurrence type:||Birdstrike|
|Release date:||14 December 2017||Occurrence category:||Serious Incident|
|Report status:||Final||Highest injury level:||None|
|Aircraft manufacturer||Saab Aircraft Co.|
|Type of operation||Air Transport Low Capacity|
|Damage to aircraft||Minor|
|Departure point||Moruya, NSW|