Flight 675

17-Aug-2007

Home
About Tim
Tributes
Achievments
Photo Galleries
Flight 675
Doing it for Timmy!
Contact Page

 

 

 

On the 7th May 2005 at approximately 11:43 the fifteen people on board Flight 675 flying from Bamaga to Cairns on VH-TFU lost their lives in an horrific crash on South Pap Ridge in Far North Queensland. This the story of that crash.

 

bullet

FLIGHT 675

bullet

THE RESCUE

bullet

THE INVESTIGATION

bullet

ATSB Interim report

bullet

THE FINAL REPORT

bullet

Office of the State Coroner: Findings

bullet

Press Clippings

 

bulletFLIGHT 675: 07/05/05        

 

Back to Top

 

bulletTHE RESCUE

A Heartfelt Thank you is extended by all of the family and friends to:

bulletSpecial Emergency Response Team, Queensland Police
bulletDisaster Victim Identification Squad
bulletQueensland Ambulance Service
bulletQueensland Emergency Service Helicopters from both Cairns and Townsville.
bulletATSB investigation Squad.

Members  of all of these teams were winched into the site in the days following the Crash

                                                                          

 

Back to Top

bullet

THE INVESTIGATION

The ATSB has undertaken an extensive investigation of the crash and the events leading up to it. A copy of the final report can be obtained by following the link below

                                                                           

 

Back to Top

 

bullet

Aviation Safety Investigation Report - Interim Factual Report (download in full)

Abstract

On 7 May 2005, a Fairchild Metroliner SA227-DC, registered VH-TFU, with two pilots and 13 passengers, was being operated under the instrument flight rules (IFR) on a scheduled passenger service from Bamaga to Cairns via Lockhart River, Qld. The crew was flying the third of four sectors scheduled for the day. They commenced duty in Cairns, departing at about 0830 Eastern Standard Time for Bamaga with an intermediate stop at Lockhart River.

The aircraft was refuelled in Bamaga. The copilot reported departure to Brisbane Air Traffic Control (ATC) at 1111. At 1136 he advised ATC that they were on descent passing 9,000 ft with an estimated time of arrival at Lockhart River of 1139.

The crew subsequently reported to ATC that they were conducting the Lockhart River Runway 12 RNAV (GNSS)1 approach. At 1140, they reported on the Lockhart River common traffic advisory frequency (CTAF) passing waypoint ‘Whisky Golf’ (LHRWG) tracking for ‘Whisky India’ (LHRWI). The waypoint LHRWI was located 12 NM2 prior to the missed approach point of the Lockhart River Runway 12 RNAV (GNSS) approach. (Appendix A of Preliminary Report)

About thirty seconds later, following a request from a pilot in another aircraft in the Lockhart River area, the copilot reported the weather conditions as ‘fairly dismal about 900 ft clearance'.

At 1158, when the crew had not reported having landed at the Lockhart River aerodrome, ATC declared an uncertainty phase3. When attempts to contact the aircraft failed, a search was commenced.

At 1625, the burnt wreckage of the aircraft was located in the Iron Range National Park on the north-western slope of ‘South Pap’, a heavily timbered ridge, approximately 11 km north-west of the Lockhart River aerodrome at an elevation of 1,210 ft. The deceleration forces and the severe impact damage resulted in all occupants being fatally injured. The aircraft was destroyed by the impact forces and an intense, fuel-fed, post-impact fire.

Back to Top

 


 
 
 
 

 
This interim factual report contains factual information relating to the accident on 7 May 2005 involving Fairchild Aircraft SA227-DC Metro 23 aircraft, registered VH-TFU. The aircraft, with two pilots and 13 passengers, was being operated on an instrument flight rules (IFR) scheduled
passenger service from Bamaga to Cairns with an intermediate stop at Lockhart River, Qld. At 1143:39 Eastern Standard Time the aircraft impacted terrain about 11 km north-west of the Lockhart River Aerodrome. At the time of the accident, the crew were conducting an area
navigation global navigation satellite system (RNAV (GNSS)) non-precision instrument approach to runway 12. The aircraft was destroyed by the impact forces and an intense, fuel-fed, postimpact fire. There were no survivors. Additional factual information relating to wreckage and the aircraft, the flight data recorder, and a summary of survey and other research dealing with RNAV (GNSS) approaches is included. As the investigation is ongoing, in accordance with international convention, the report does not contain any analysis or findings relating to the factual information.
The analysis and findings of the investigation will be provided in the final report. The investigation is continuing and, among other things, will include further work in the following aspects of the accident: the operator’s management processes, standard operating procedures,
flight crew training and checking, and document control; regulatory oversight of the operator’s activities, including approvals and surveillance undertaken; and the design and chart presentation of RNAV (GNSS) approaches. Further safety action may also arise from this ongoing
investigation and associated research.

 

 

 
bullet

THE FINAL REPORT

Aviation Safety Investigation Report - Final Report - 4/4/07 (Down Load in Full)

 

Abstract

On 7 May 2005, a Fairchild Aircraft Inc. SA227-DC Metro 23 aircraft, registered VH-TFU, with two pilots and 13 passengers, was being operated by Transair on an instrument flight rules regular public transport service from Bamaga to Cairns, with an intermediate stop at Lockhart River, Queensland. At 1143:39 Eastern Standard Time, the aircraft impacted terrain in the Iron Range National Park on the north-western slope of South Pap, a heavily timbered ridge, approximately 11 km north-west of the Lockhart River aerodrome. At the time of the accident, the crew was conducting an area navigation global navigation satellite system (RNAV (GNSS)) nonprecision approach to runway 12. The aircraft was destroyed by the impact forces and an intense, fuel-fed, post-impact fire. There were no survivors.

The accident was almost certainly the result of controlled flight into terrain, that is, an airworthy aircraft under the control of the flight crew was flown unintentionally into terrain, probably with no prior awareness by the crew of the aircraft’s proximity to terrain. The investigation report identifies a range of contributing and other safety factors relating to the crew of the aircraft, Transair's processes, regulatory oversight of Transair by the Civil Aviation Safety Authority, and RNAV (GNSS) approach design and chart presentation. It also details safety action taken by various agencies to address the identified safety issues, and includes safety recommendations relating to those safety issues that had not been addressed by relevant agencies at the time of publication of this report.

 

 

EXECUTIVE SUMMARY

 

Sequence of events

 

On 7 May 2005, a Fairchild Aircraft Inc. SA227-DC Metro 23 aircraft, registered VH•

TFU, with two pilots and 13 passengers, was being operated by Transair on an

instrument flight rules (IFR) regular public transport (RPT) service from Bamaga to

Cairns, with an intermediate stop at Lockhart River, Queensland. At 1143:39 Eastern

Standard Time, the aircraft impacted terrain in the Iron Range National Park on the

north-western slope of South Pap, a heavily timbered ridge, approximately 11 km north•

west of the Lockhart River aerodrome.

At the time of the accident, the crew was conducting an area navigation global

navigation satellite system (RNAV (GNSS)) non-precision approach to runway 12. The

aircraft was destroyed by the impact forces and an intense, fuel-fed, post-impact fire.

There were no survivors.

The accident was almost certainly the result of controlled flight into terrain; that is, an

airworthy aircraft under the control of the flight crew was flown unintentionally into

terrain, probably with no prior awareness by the crew of the aircraft’s proximity to

terrain.

Weather conditions in the Lockhart River area were poor and necessitated the conduct

of an instrument approach procedure for an intended landing at the aerodrome. The

cloud base was probably between 500 ft and 1,000 ft above mean sea level and the

terrain to the west of the aerodrome, beneath the runway 12 RNAV (GNSS) approach,

was probably obscured by cloud.

The flight data recorder (FDR) data showed that, during the entire descent and

approach, the aircraft engine and flight control system parameters were normal and that

the crew were accurately navigating the aircraft along the instrument approach track.

The FDR data and wreckage examination showed that the aircraft was configured for

the approach, with the landing gear down and flaps extended to the half position. There

were no radio broadcasts made by the crew on the air traffic services frequencies or the

Lockhart River common traffic advisory frequency indicating that there was a problem

with the aircraft or crew.

Crew performance

As the copilot was making the radio broadcasts during the approach, it is very likely that

the 40-year old pilot in command was the handling pilot. The pilot in command was

Transair’s base manager at Cairns and an experienced Metro pilot. However, given the

relatively complex type of approach being flown, he would have been reliant on the

relatively inexperienced 21-year old copilot to assist with the high cockpit workload.

There was a significant potential for crew resource management problems within the

crew in high workload situations, given that there was a high trans-cockpit authority

gradient and neither pilot had previously demonstrated a high level of crew resource

management skills.

The crew commenced the Lockhart River Runway 12 RNAV (GNSS) approach, even

though the crew were aware that the copilot did not have the appropriate endorsement

and had limited experience to conduct this type of instrument approach. A nondirectional

beacon approach was also available at Lockhart River, and both pilots were

endorsed for that approach. Despite the weather and copilot inexperience, the pilot in

– xiii –

command used descent and approach speeds and a rate of descent greater than specified

for the aircraft in the Transair Operations Manual, and exceeding those appropriate for

establishing a stabilised approach.

During the approach, the aircraft descended below the segment minimum safe altitude

for the aircraft’s position on the approach. The aircraft’s high rate of descent, and the

descent below the segment minimum safe altitude, were not detected and/or corrected

by the crew before the aircraft collided with terrain.

While the investigation was complicated by an inoperative cockpit voice recorder, no

witnesses, and the extent of destruction of the aircraft, it determined that the crew

probably experienced a very high workload during the approach and probably lost

situational awareness about the aircraft’s position along the approach path.

The pilots’ aircraft endorsements, clearance to line operations, and route checks did not

meet all the relevant regulatory and operations manual requirements to conduct RPT

flights on the Metro aircraft. However, these limitations were not considered to have

had an influence on the conduct of the flight.

Ground proximity warning system

There was no evidence that the ground proximity warning system (GPWS) was not

functioning as designed. Simulation by the GPWS manufacturer indicated that the crew

should have received a one second ‘terrain terrain’ alert about 25 seconds prior to

impact, followed by a second ‘terrain terrain’ alert and a continuous ‘pull up’ warning

for the final 5 seconds of flight. However, research has shown that the alerts and

warnings in the final 5 seconds of flight would not have been sufficient for the crew and

aircraft to effectively respond to the GPWS annunciations.

A terrain awareness and warning system (TAWS, commonly referred to as enhanced

GPWS) provided advantages over standard GPWS. It enhanced pilot situational

awareness by providing coloured terrain information on a continuous terrain display in

the cockpit and providing more timely alerts and warnings. Had the aircraft been fitted

with a TAWS, it is probable that the accident would not have occurred.

Transair processes

In addition to the substantive crew actions and local conditions that contributed to the

accident, the investigation identified a number of safety factors relating to Transair that

contributed to the accident. In particular, the flight crew training program had

significant limitations, such as superficial or incomplete ground-based instruction

during endorsement training, no formal training for new pilots in the operational use of

global positioning system (GPS) equipment, no structured training on minimising the

risk of controlled flight into terrain, and no structured training in crew resource

management (or human factors management) and operating effectively in a multi-crew

environment.

Transair’s processes for supervising the standard of flight operations at the Cairns base

had significant limitations, such as not using an independent approved check pilot to

review operations, reliance on passive measures to detect problems, and no defined

processes for selecting and monitoring the performance of the base manager. In

addition, Transair’s standard operating procedures for conducting instrument

approaches had significant limitations, such as not providing clear guidance on

approach speeds, not providing guidance for when to select aircraft configuration

changes during an approach, no clear criteria for a stabilised approach, and no

– xiv –

standardised phraseology for challenging safety-critical decisions and actions by other

crew members.

Transair’s organisational structure, and the limited responsibilities given to nonmanagement

personnel, resulted in high work demands on the Transair chief pilot. This

resulted in a lack of independent evaluation of training and checking, and created

disincentives and restricted opportunities within Transair to report safety concerns with

management decision making. There was no structured process within Transair for

proactively managing safety-related risk associated with its flight operations.

Furthermore, the chief pilot did not demonstrate a high level of commitment to safety

and appeared to be over-committed, with additional roles as chief executive

officer/managing director of the company, the primary check and training pilot, and

working regularly in Papua New Guinea for an associated company.

In addition, limitations were also identified with Transair’s flight crew proficiency

checking program and the useability of the Transair Operations Manual. However,

these issues were not considered to be contributing safety factors to the accident.

Regulatory oversight

The investigation also identified contributing safety factors relating to the regulatory

oversight of Transair by the Civil Aviation Safety Authority (CASA). In particular,

CASA did not provide sufficient guidance to its inspectors to enable them to effectively

and consistently evaluate several key aspects of operators' management systems. These

aspects included evaluating organisational structure and staff resources, evaluating the

suitability of key personnel, evaluating organisational change, and evaluating risk

management processes. CASA also did not require operators to conduct structured

and/or comprehensive risk assessments, or conduct such assessments itself, when

evaluating applications for the initial issue or subsequent variation of an Air Operator’s

Certificate.

In addition, CASA’s oversight of Transair, in relation to the approval of Air Operator’s

Certificate variations and the conduct of surveillance, was sometimes inconsistent with

CASA’s policies, procedures and guidelines. However, this was not considered to have

been a contributing safety factor.

Other safety factors

The investigation also identified a range of other safety factors which did not meet the

definition of a contributing safety factor or which could not be as clearly linked to the

accident because of lack of evidence, but which were still considered to be important to

communicate in an investigation report with a focus on future safety. In addition to

some aspects of Transair’s processes and regulatory oversight activities, these safety

factors related, among other things, to the possibility of poor intra-cockpit

communication, instrument approach design, instrument approach chart presentation,

and regulatory requirements.

The Australian convention for waypoint names in RNAV (GNSS) approaches did not

maximise the ability to discriminate between waypoint names on the aircraft GPS

display and/or on the instrument approach chart. In addition, there were several design

aspects of the Jeppesen RNAV (GNSS) approach charts, which were very likely to have

been used by the crew, that could lead to pilot confusion or a reduction in situational

awareness. These included limited reference regarding the ‘distance to run’ to the

missed approach point, mismatches in the vertical alignment of the plan-view and

profile-view on charts such as that for the Lockhart River runway 12 approach, use of

– xv –

the same font size and type for waypoint names and altitude limiting steps, and not

depicting the offset in degrees between the final approach track and the runway

centreline. There were also limitations in the terrain information provided on Jeppesen

instrument approach charts.

CASA’s process for accepting an instrument approach did not involve a systematic risk

assessment of pilot workload and other potential hazards and warnings, including

activation of a GPWS. There was also no regulatory requirement for instrument

approach charts (including the Lockhart River Runway 12 RNAV (GNSS) approach

chart) to include coloured contours to depict terrain as required by the International

Civil Aviation Organization (ICAO) Annex 4, to which Australia had not notified a

difference.

Although CASA released discussion papers in 2000, and further development had

occurred since then, there was no regulatory requirement for initial or recurrent crew

resource management (CRM) training or for RPT operators to have a safety

management system. In addition, there was no regulatory requirement for flight crew

undergoing a type rating on a multi-crew aircraft to be trained in procedures for crew

incapacitation and crew coordination including allocation of pilot tasks, crew

cooperation and use of checklists. This was required by ICAO Annex 1, to which

Australia had notified a difference.

The investigation also determined that CASA’s guidance material provided to operators

about the structure and content of an operations manual was not as comprehensive as

that provided by ICAO in areas such as multi-crew procedures and stabilised approach

criteria, and that its process for evaluating the content of an operations manual did not

consider the useability of the manual, particularly in electronic format. There was also

no regulatory requirement for multi-crew RPT aircraft to be fitted with a serviceable

autopilot.

Safety action

This investigation identified important learning opportunities for pilots, operators and

regulatory agencies to improve future aviation safety and to seek to ensure such an

accident never happens again. During the course of the investigation, the ATSB issued

10 safety recommendations and encouraged other safety action.

Safety action has been taken by several organisations to address the safety issues

identified during this investigation. A number of additional safety recommendations

were issued by the ATSB, including seven recommendations to the Civil Aviation

Safety Authority on its regulatory oversight activities and regulatory requirements.

Recommendations on aspects of instrument approach charts were also issued to

Airservices Australia and Jeppesen Sanderson Inc.

The ATSB did not issue recommendations regarding the serious safety issues of the

operator because Transair had surrendered its Air Operator’s Certificate on 4 December

2006 and ceased to operate.

– xvi –

 

 

 

Back to Top

 

     

Home | About Tim | Tributes | Achievments | Photo Galleries | Flight 675 | Doing it for Timmy! | Contact Page

This site was last updated 17-08-07