Air transportation safety investigation report A18P0177
Runway incursion and risk of collision
Pacific Coastal Airlines Ltd., Beechcraft 1900C, C-GIPC
City of Trail airport vehicle (Chevrolet Silverado 1500)
Trail Airport, British Columbia
The Transportation Safety Board of Canada (TSB) investigated this occurrence for the purpose of advancing transportation safety. It is not the function of the Board to assign fault or determine civil or criminal liability. This report is not created for use in the context of legal, disciplinary or other proceedings. See Ownership and use of content.
On 12 December 2018, a Pacific Coastal Airlines Ltd. Beechcraft 1900C aircraft (registration C-GIPC, serial number UC 110), operating as flight PCO451, was on a scheduled flight from Vancouver International Airport (CYVR), British Columbia (BC), to Trail Airport (CAD4), BC, with 2 flight crew members and 19 passengers on board. While the aircraft was conducting an approach to land southbound on Runway 16, an airport vehicle was travelling northbound on the runway, performing a runway inspection. When the aircraft touched down, the airport vehicle was still on the runway. The airport vehicle exited the runway onto the taxiway before the aircraft reached the runway/taxiway intersection, avoiding a collision. Radio communications had not been established between the aircraft and the airport vehicle. There were no injuries, and there was no damage to the aircraft.
1.0 Factual information
The International Civil Aviation Organization (ICAO) and Transport Canada (TC) define a runway incursion as
[a]ny occurrence at an aerodrome involving the incorrect presence of an aircraft, vehicle or person on the protected area of a surface designated for the landing and take-off of aircraft.Footnote 1,Footnote 2
The Transportation Safety Board of Canada (TSB) defines a risk of collision as
a situation in which an aircraft comes so close to being involved in a collision that a threat to the safety of any person, property or the environment exists. Footnote 3
1.1 History of the occurrence
On 12 December 2018, at approximately 0630,Footnote 4 an airport vehicle operator (Operator 1) arrived at Trail Airport (CAD4), BC, to find that the runway was covered in slushy snow that had frozen overnight. A second airport vehicle operator (Operator 2) was called in to assist with snow removal; he arrived at the airport at 0700. Shortly afterward, both vehicle operators began snow removal. Operator 1 was driving a truck and Operator 2 was driving a snowplow.
A Pacific Coastal Airlines Ltd. Beechcraft 1900C aircraft (registration C-GIPC, serial number UC 110), operating as flight PCO451, was conducting an instrument flight rules (IFR) flight from Vancouver International Airport (CYVR), BC, to CAD4. The flight was scheduled to depart CYVR at 0915 with 2 flight crew members and 19 passengers on board. However, the departure was delayed because the runway conditions at CAD4 were reported as poor.
Runway conditions at CAD4 had been filed electronically in an Aircraft Movement Surface Condition Report (AMSCR)Footnote 5 from a laptop on board one of the airport vehiclesFootnote 6 to the NAV CANADA web-based application SNOWiz.Footnote 7 The truck driver filed an AMSCR at 0655 and an updated AMSCR at 1009.
After the flight crew received the updated AMSCR information, the flight departed CYVR at 1021. Its estimated time of arrival at CAD4 was 1123.
When the aircraft was at 12 500 feet, on descent into CAD4, the weather became suitable for visual flight rules (VFR) flight. At 1114, when the aircraft was approximately 21 nautical miles (NM) from CAD4, the flight crew cancelled IFR and continued heading east under VFR, over the city of Trail, which is northeast of CAD4.
At 1117, the snowplow driver stopped at the runway holding position marking for Runway 16/34 (Figure 1). He used the mandatory frequency (MF) to contact the flight crew, requesting the aircraft’s arrival time. The flight crew responded that its estimated time of arrival was in 5 minutes. The snowplow driver informed the flight crew that he would be on the runway to remove an area of slush near the intersection with the taxiway. The flight crew acknowledged this communication, and the snowplow driver entered the runway moments later.
Approximately 30 seconds after the snowplow entered the runway, the truck driver entered the runway via the taxiway without confirming the aircraft’s location or stopping at the runway holding position marking. The truck driver reported making a call on the MF indicating that he was entering the runway; however, the did not hear the radio call. The truck driver then proceeded north on Runway 16.
The snowplow driver observed the truck driving north on the runway and made a call on the MF to inform the truck driver that the aircraft was expected to land in approximately 3 minutes. The truck driver did not respond to this call, and the flight crew did not hear the attempted communication. The snowplow driver turned his focus back to snow-removal activities and, after turning in the opposite direction, lost track of the truck.
At 1118, the snowplow driver exited the runway and reported on the MF that he was clear of the runway. The flight crew received and acknowledged this communication.
After the truck driver reached the threshold of Runway 16, he turned and continued south on the runway toward the threshold of Runway 34 The truck driver needed extra time at the threshold of Runway 34 to inspect ridges on the runway surface and to provide an updated AMSCR, but he did not broadcast his intentions.
While the aircraft was on its final approach, 4 NM from the airport, the flight crew reportedly called on the MF to indicate that they would be landing in 1 minute. Neither driver heard the radio call. Just before the aircraft landed, the flight crew conducted a visual scan of the runway and observed the snowplow on the apron.
After completing the inspection at the threshold of Runway 34, the truck driver turned his vehicle northbound at 1121:45 and drove along the east side of the runway.
At 1122:21, the aircraft touched down on Runway 16 at a speed of 113 knots. Immediately after touching down, the flight crew applied initial reverse to begin slowing the aircraft. As the crew looked down the runway, they observed the truck on the runway and applied full reverse and maximum braking. The aircraft began to skid as a result of the heavy braking; however, the crew was able to maintain control.
Upon seeing the landing aircraft, the truck driver accelerated in an effort to reach the taxiway and exit the runway. He was able to do so before the aircraft reached the intersection with the taxiway.
After passing the taxiway intersection, the aircraft rolled to a stop and turned around on the runway to take the taxiway to the apron, without further incident.
During this occurrence, the aircraft and the truck had come within 228 m of each other (Figure 1). The aircraft passed the taxiway intersection approximately 4 seconds after the truck entered the taxiway.
After Operator 1 had parked his truck beside the apron, he discovered that the volume on the vehicle’s very high frequency (VHF) 2-way radio had been turned down to an inaudible level.
1.2 Injuries to persons
1.3 Damage to aircraft
There was no damage to aircraft.
1.4 Other damage
1.5 Personnel information
1.5.1 Flight crew
The 2 flight crew members — the captain and the first officer — were licensed, qualified, and trained for the flight (Table 1). The crew members were adequately rested, and fatigue was not considered a factor in this occurrence.
The flight crew members both held a Radio Operator Certificate with Aeronautical Qualification (ROC-A). Footnote 8 Training for an ROC-A involves radio operating procedures, radio terminology, and emergency communications. The certificate does not expire, and no revalidation is required.
Airline transport pilot licence (ATPL)
Commercial pilot licence (CPL)
Total flying hours
Flight hours on type
Flight hours in the last 7 days
Flight hours in the last 30 days
Flight hours in the last 90 days
Flight hours on type in the last 90 days
Hours on duty before the occurrence
Hours off duty before the work period
1.5.2 Ground personnel
Operator 1 had been employed as an airport maintenance technician at CAD4 for 14 months. Before taking this position, he had had no airport operations experience.
Operator 2 had been employed at CAD4 for 12 years. Since 2014, he had been employed as an airport operation specialist. Before taking this position, he had had no airport operations experience.
Operator 1 and Operator 2 each possessed a valid Unrestricted Airport Vehicle Operator’s Permit (U -AVOP) Footnote 9 issued by the airport manager. They had both also completed the ROC-A training and possessed a valid certificate. Airport staff do not require regulatory certification for their job functions.
Operator 1 and Operator 2 were adequately rested, and fatigue was not considered a factor in this occurrence.
Airports are required to establish a training program for employees to ensure they are appropriately trained for the tasks they are assigned. Footnote 10, Footnote 11 At CAD4, airport staff have a lengthy list of responsibilities. To support the staff in these duties, the Airport Staff Training ManualFootnote 12 was developed. At the time of the occurrence, the Airport Staff Training Manual contained 67 training items. Operator 1 had completed 36, or 54%, of these items, and Operator 2 had completed 38, or 57%. One of the 67 items that neither operator had completed was a review of TC Advisory Circular (AC) 302-003: Personnel and Equipment within the Critical Portion of the Runway StripFootnote 13.
1.6 Aircraft and vehicle information
The Beechcraft 1900C is a 19-seat aircraft powered by 2 Pratt & Whitney Canada PT6A-65B turboprop engines. Records indicate that the aircraft was certified, equipped, and maintained in accordance with existing regulations. The investigation found no indication that there was any aircraft system malfunction during the occurrence.
126.96.36.199 Airport fleet
CAD4 has a fleet of vehicles used for various maintenance activities (Table 2). Initial training on how to operate the vehicles is provided to operators when they are hired, and the training is reviewed during a winter operations meeting held before each winter season. Vehicle operators decide which equipment to use for each task they are performing.
|Vehicle||Colour||2-way VHF radio|
Airport 1 (truck)
Airport 2 (truck)
* A small highly manoeuvrable vehicle with a large bucket used for loading.
Operator 1 was driving Airport 2, a 2011 Chevrolet Silverado 1500, in this occurrence. Operator 2 was driving Snowplow 1, a 2012 International 7400 SBA 4x2.
188.8.131.52 Airport Vehicle Operator Permit
The ICAO Manual on the Prevention of Runway Incursions recommends the following:
As a result of local hazard analyses in Europe in 2001, the operation of vehicles on the aerodrome has been highlighted as a potentially high-risk activity which demands that a number of formal control measures be put in place to manage the risk. A vehicle driver training programme is one of these control measures and should form part of the overall safety management system of the aerodrome operator.Footnote 14
The policies and procedures regarding the operation of vehicles at CAD4 are described in its Airport Vehicle Operator Permit (AVOP) Study Guide. To obtain an AVOP, candidates are required to complete a written exam and peer training with an experienced employee. At the time of the occurrence, there was no set duration or curriculum for the peer training.
The AVOP Study Guide describes the procedure to follow before proceeding onto the manoeuvring area:
Before proceeding on to maneuvering areas the vehicle operator shall hold short and visually check for arriving and departing aircraft. The operator shall then broadcast his/her intentions on the ATF [aerodrome traffic frequency] frequency. The vehicle may proceed onto the maneuvering area only if there is no indication of arriving or departing aircraft. Vehicle operator shall re-broadcast intentions when changing locations.Footnote 15
The airport procedures state that airport vehicles are to be inspected daily to ensure that they are mechanically sound and functioning as intended.Footnote 16 However, the daily airport vehicle inspection had not been completed on the occurrence vehicle on the day of the occurrence.
The occurrence vehicle was equipped with a functioning VHF radio capable of 2-way communication with aircraft and other airport vehicles. The AVOP Study Guide states that “[e]ach operator shall ensure that the two-way radio is working before the vehicle enters the airport maneuvering area.”Footnote 17
Although the 2-way radio had been used in the morning on the day of the occurrence, it was not confirmed to be working before the vehicle entered the airport manoeuvring area when the incursion occurred. At the time of the occurrence, the volume on the radio was at an inaudible level. The investigation was unable to determine under what circumstances the volume had been turned down.
1.7 Meteorological information
There is no aviation weather reporting at CAD4. The nearest airport to CAD4 that issues aerodrome routine meteorological reports (METARs) is Castlegar/West Kootenay Regional Airport (CYCG), BC, 15 NM north of CAD4.
The conditions recorded at 1100 indicated the following:
- winds 090° true (T) at 3 knots, varying from 340°T to 150°T
- visibility 15 statute miles
- few clouds at 100 feet above ground level (AGL), and scattered clouds at 7500 feet AGL and 11 000 feet AGL
- temperature 0 °C, dew point −1 °C
- altimeter setting 30.03 inches of mercury
The Environment and Climate Change Canada weather observation station closest to CAD4 is at Warfield, BC, 6 NM to the northwest. The conditions recorded at 1100 were a temperature of 2.2 °C and a dew point of −2.5 °C, winds 160°T at 14 km/h.
At the time of the occurrence, the sky was clear and the sun was about 18° above the horizon and directly ahead of the aircraft. Footnote 18 There was snow on the ground surrounding the runway, and the runway was wet. These conditions created glare for both flight crew members during the approach.
1.8 Aids to navigation
CAD4 has established IFR approaches for runways 16 and 34, which are published by NAV CANADA. In this occurrence, the crew conducted an approach to Runway 16 due to favourable winds and an active NOTAM, Footnote 19 which had closed the airspace south of the airport.
According to the Transport Canada Aeronautical Information Manual (TC AIM), an MF area is “established at an aerodrome if the traffic volume and mix of aircraft traffic at that aerodrome is such that there would be a safety benefit derived from implementing MF procedures.” Footnote 20 CAD4 is an uncontrolled aerodrome, Footnote 21 and it has an MF area that extends from the centre of the aerodrome outward to a radius of 5 NM and up to an altitude of 4400 feet ASL or 3000 feet AGL. The TC AIM also states that “[a]ircraft operating within the area in which the MF is applicable (MF area) shall be equipped with a functioning radio capable of maintaining two-way communication.” Footnote 22
Section 602.101 of the Canadian Aviation Regulations (CARs) Footnote 23 stipulates the MF reporting procedures for VFR aircraft approaching an uncontrolled aerodrome. The investigation determined that the flight crew completed the required communications during the approach and landing.
Communications on the MF in use at CAD4 are not recorded.
1.9.2 Airport vehicles
Operator 1 had been using Airport 2 and a skid steer for snow removal. The skid steer was not equipped with a VHF radio; therefore, Operator 1 relied on a hand-held VHF radio for communication while using the skid steer.
TC’s Aerodromes Standards and Recommended Practices (TP 312) sets out the communications standards for vehicles operating on the manoeuvring area Footnote 24 at an aerodrome, according to which, a vehicle
- broadcasts prior to entering, exiting or changing location on the manoeuvring area, stating the vehicle position and intentions on the MF or ATF, as applicable;
- broadcasts when on the manoeuvring area to advise pilots of vehicle positions and intentions;
- broadcasts when requested, to provide runway condition reports and the location of other known ground traffic present on the manoeuvring area; and
- gives way to aircraft at all times. Footnote 25
The airport vehicle operators at CAD4 generally work alone. However, during snowfalls or other periods of significant weather, 2 or more operators may be working at the same time. At the time of the occurrence, CAD4 did not have separate procedures or policies in place outlining how multiple vehicles operating at the same time should communicate.
Consequently, individual operators were required to follow the communications standards outlined in TP 312 and broadcast their intentions and position once they were on the manoeuvring area.
1.10 Aerodrome information
The City of Trail owns and operates CAD4 under a Civil Aviation Airport Certificate issued by TC on 15 February 2014, in accordance with CARs section 302.03.Footnote 26
The airport is located 3.5 NM south of Trail, in the Columbia River valley. There is a single asphalt runway (Runway 16/34) that is 4001 feet long and 75 feet wide and at an elevation of 1427 feet ASL.
The airport serves general aviation flights, scheduled commercial flights, and rotary-wing aircraft operations throughout the year during daylight hours.
1.11 Flight recorders
1.11.1 Cockpit voice recorder
The occurrence aircraft was equipped with a cockpit voice recorder (CVR), as required by regulation. The CVR was capable of recording only 30 minutes before it began to overwrite previously recorded material. The Pacific Coastal Airlines Ltd. Company Operations Manual instructs the flight crew to pull the CVR circuit breaker in the event of a TSB-reportable incident.Footnote 27 In this case, the flight crew did not isolate the recording before it was overwritten. Therefore, the CVR was not available for review, and information that could have been valuable to the investigation was lost.
184.108.40.206 TSB recommendation on cockpit voice recorder duration
On 09 March 1999, the TSB issued Recommendation A99-02 as part of its investigation into an accident involving Swissair Flight 111, a McDonnell Douglas MD-11 aircraft that struck water near Peggy’s Cove, Nova Scotia, after the crew diverted the flight to Halifax, Nova Scotia, because of smoke in the cockpit.Footnote 28
One of the shortcomings identified during the investigation was the limited recording capacity of the aircraft’s CVR. The CVR was able to record only 30 minutes, and therefore did not capture the timeframe when the fire started.
A lack of recorded voice and other aural information can inhibit safety investigations and delay or prevent the identification of safety deficiencies. Given the need for longer periods of recorded sound to capture the initiating events of aviation accidents, and the availability of 2-hour CVRs, the Board believed that such recorders should be mandated by regulatory authorities worldwide. However, it also recognized that a period of several years may be reasonably required for manufacturers and operators to implement this change. The Board believed that, with appropriate lead time, a retrofit program was warranted for aircraft already in service. Therefore, the Board recommended to both TC and the European Joint Aviation Authorities that:
As of 01 January 2005, all aircraft that require both an FDR and a CVR be required to be fitted with a CVR having a recording capacity of at least two hours.
Transportation Safety Recommendation A99-02
Since the latest reassessment of Recommendation A99-02 in March 2019, amendments to the regulations pertaining to CVRs have been published in Canada Gazette, Part II.Footnote 29 The new regulations require a CVR with a recording time of least 2 hours for all multi-engined turbine-powered aircraft that are configured for 6 or more passenger seats and for which 2 pilots are required by the aircraft type certificate or by the subpart under which the aircraft is operated. The new regulations will come into effect in May 2023, 4 years after their publication.
1.12 Wreckage and impact
There was no wreckage or impact.
1.13 Medical and pathological information
1.15 Survival aspects
1.16 Test and research
1.17 Organizational and management information
1.17.1 Pacific Coastal Airlines Ltd.
Pacific Coastal Airlines Ltd. is an air operator with operations approved under Subpart 704 (commuter operations) and Subpart 705 (airline operations) of the CARs. The company operates 20 aircraft, including 7 Beechcraft 1900Cs. Its main base of operations is at CYVR, in the South Terminal. The airline is privately owned and services communities throughout BC and Alberta.
220.127.116.11 Safety management system
As a CARs Subpart 705 air operator, Pacific Coastal Airlines Ltd. is required to implement a safety management system (SMS)Footnote 30 in accordance with section 107.02 of the CARs.Footnote 31 Pacific Coastal Airlines Ltd. first established its SMS in 2007.
1.17.2 Trail Airport
CAD4’s organizational structure consists of an accountable executive, a part-time airport manager, who is also the SMS manager, a full-time airport maintenance technician, and 2 part-time airport operation specialists. The airport maintenance technician works 4 days a week, and the 2 airport operation specialists split the remaining 3 days of the week.
From February 2014 to March 2016, the airport manager position had been full-time. In April 2016, a new airport manager was appointed in a part-time role. At the time of his appointment, the new airport manager had no aviation experience or aerodrome knowledge.
TC does not approve or set out experience requirements for the airport manager position at certified airports.
18.104.22.168 Safety management system
As a certified airport, CAD4 is required to implement an SMS in accordance with CARs section 107.02.Footnote 32 CAD4 established its SMS in 2014.
22.214.171.124.1 Proactive Hazard Review
According to the CAD4 Safety Management System Policy Manual, “[a] review of hazards is conducted at least annually, or when major changes occur at the Airport (i.e. changes to staff, equipment, air carrier frequency, aircraft type or destination).”Footnote 33 This type of review is proactive in nature and is used to identify hazards.
Pacific Coastal Airlines Ltd. has been offering 2 scheduled flights daily from CYVR to CAD4 since April 2006. In the winter of 2018, the airline added an extra flight to CAD4 on Sundays, Mondays, and Fridays.Footnote 34 Although this constituted a change in air carrier frequency, a hazard review was not completed at CAD4 before the extra Pacific Coastal Airlines Ltd. flights were added to the schedule.
126.96.36.199.2 Previous runway incursions at CAD4
Two SMS hazard reports were generated following runway incursions at CAD4 in 2017:
- In January 2017, a private aircraft taxied onto the runway while a Pacific Coastal Airlines Ltd. flight was on approach. The Pacific Coastal Airlines Ltd. crew recognized the conflict and completed a go-around while the private aircraft cleared the runway.
- In April 2017, a runway incursion occurred involving an airport vehicle and an inbound medical evacuation flight. The airport vehicle approached the runway and stopped at the runway holding position marking. The airport vehicle operator then broadcast his intention to enter the runway on the radio and received no reply. As the airport vehicle entered the runway, the operator saw the inbound aircraft and quickly left the runway area. The aircraft landed uneventfully.
The SMS manager had completed a safety investigation and risk assessment for both events; however, in a subsequent 2017 Management Review, the events were deemed unrelated to the airport operations.Footnote 35 Therefore, airport operations were not reviewed or changed based on these 2 occurrences. In addition, the safety goals and objectives for 2018, set out in the 2017 Management Review, did not include an objective related to preventing runway incursions.
1.18 Additional information
1.18.1 Guidelines and standards regarding vehicle conspicuity
TC’s Aerodrome Standards and Recommended Practices (TP 312) states that “[a]ll mobile objects to be marked are coloured or display flags.”Footnote 36 While operating at an airport, vehicles are considered mobile objects.
The U.S. Federal Aviation Administration’s Advisory Circular AC150/5210-5D provides guidelines and standards for airport vehicles based in the U.S. It notes that
[a]irport vehicle paint and markings are a safety of flight requirement. The approved colors/markings herein assure conspicuity of vehicles operating in the AOA [air operations area] from both the ground and air.Footnote 37
The truck involved in this occurrence was painted white, with a black front grill and black bumper (Figure 2).
The airport vehicle was equipped with an amber beacon affixed to a rack installed above the airport vehicle cab (Figure 2). The beacon met the applicable standard for lighting of mobile objects.Footnote 38 During the occurrence, the airport vehicle was operating with the beacon on and functioning.
The AVOP Study Guide states that vehicle headlights “must be turned on while operating on airside.”Footnote 39 In this occurrence, the airport vehicle’s headlights were not turned on when it was being operated on the runway. However, the airport vehicle was equipped with daytime running lights, which were on and functioning at the time of the occurrence.
1.18.2 Guidance on the prevention of runway incursions
188.8.131.52 International Civil Aviation Organization
ICAO published Doc 9870 AN/463, Manual on the Prevention of Runway Incursions, to specifically address “the subject of runway incursion prevention as it relates to the safe operation of aircraft, air traffic management, vehicle movement on the manoeuvring area and aerodrome management.”Footnote 40
The manual provides a systemic approach to examining contributory factors and offers recommendations to prevent runway incursions. The focus is not only on operational personnel and human limitations, but also on the operational system in its entirety. More specifically, Doc 9870 states the following:
Active failures by operational personnel are sometimes a consequence of flaws in the system, sometimes a result of well-known and documented human limitations, but usually are a combination of the two. A true systemic approach to safety must consider latent conditions in the system as well as active failures on the front lines of operations. Such a systemic approach underlies this manual.Footnote 41
ICAO Doc 9870 provides best practices to be used for communications by flight crews and airside vehicle drivers. It also provides tools for training and prevention programs and lists common pilot- and driver-related factors that can contribute to a runway incursion.
Common pilot-related factors that can contribute to a runway incursion include a breakdown in communications and performance of mandatory head-down tasks, which reduces situational awareness.Footnote 42 Common driver-related factors include failure to obtain clearance to enter the runway, communication errors, and inadequate training in airside vehicle operations.Footnote 43
184.108.40.206 Transport Canada
TC has a website dedicated to runway incursions. At the time of writing this report, 6 publications, 4 Aviation Safety Letter articles, and 7 Advisory CircularsFootnote 44 on runway safety and related matters were available to the public.
220.127.116.11 NAV CANADA
Runway incursions are one of NAV CANADA’s top 8 risks to operational safety, as identified by a risk assessment using information from a variety of sources, including frontline employees. NAV CANADA actively pursues the prevention of runway incursions, both internally and with other aviation stakeholders, through publications, information sharing, and safety forums, among other initiatives.
Given the critical role of phraseology in preventing runway incursions, NAV CANADA has published 2 guidance documentsFootnote 45,Footnote 46 on phraseology to be used by pilots flying VFR and by ground vehicle operators.
In 2019, NAV CANADA began providing information to TC in cases where NAV CANADA had safety concerns related to a perceived student pilot proficiency deficiency (e.g., related to language). Many of these safety concerns relate to runway incursions. TC has been able to use this information to assist in its oversight of flight training schools.
In 2019, NAV CANADA developed a national NAV CANADA flight school agreement template that can be tailored to the needs of individual flight schools. This template includes the key elements that have proven to be effective practices, some of which may assist with preventing runway incursions.
NAV CANADA has published a Runway Safety webpageFootnote 47 to help airport operators establish runway safety teams at their airports.
NAV CANADA facilitates the Canadian Aviation Safety Officer Partnership (CASOP), a safety forum held twice a year, with representation from all aviation stakeholder groups.Footnote 48 The intent of the forum is to discuss safety issues, and share safety-related information within Canada’s aviation community.
1.18.3 Human performance
18.104.22.168 Visual performance
The mountainous terrain surrounding CAD4 does not allow for a straight-in approach to Runway 16. The river valley in which the airport is located is narrow, and the final approach for Runway 16 is offset by 20°. Aircraft are required to join the final leg of the approach less than 1 NM from the runway threshold. In this occurrence, both pilots had lowered the aircraft’s sun visors (Figure 3) to combat solar glare during the approach and subsequent landing. Yet neither pilot saw the airport vehicle on the runway until after they had landed.
22.214.171.124 Solar glare
Solar glareFootnote 49 from direct or reflected sunlight affects visual performance by reducing visual acuity and contrast.
Generally speaking, there are 2 types of glare: discomfort glare and disability glare. Discomfort glare can affect visual performance by distracting people and making them look away from the source of the glare. Disability glare reduces the contrast of objects with their background and can vary in intensity.
Glare is most intense when the sun is low on the horizon. The degree of solar glare depends on the sun’s position and on the reflectivity of surfaces in relation to the field of view.
1.18.4 TSB Watchlist
The TSB Watchlist identifies the key safety issues that need to be addressed to make Canada's transportation system even safer. The TSB publishes the Watchlist to focus the attention of industry and regulators on the problems that need to be addressed today.
The risk of collisions from runway incursions is a 2018 Watchlist issue. Since this issue was first added to the Watchlist in 2010, the TSB has completed 10 investigationsFootnote 50 into runway incursions as well as a safety issues investigation focused on the south complex parallel runways at Toronto/Lester B. Pearson International Airport (CYYZ), Ontario.Footnote 51 In late 2018 and early 2019, the TSB initiated 3 additional investigations.Footnote 52 Although there has not been a recent accident as a result of a runway incursion in Canada, the potential consequences of such a collision could be catastrophic.
The Board is concerned that the rate of runway incursions in Canada and the associated risks of collision will remain until effective defences tailored to address previously identified hazards are implemented at airports and in aircraft, vehicles, and air traffic service facilities across Canada.
- This issue will remain on the TSB Watchlist until the rate of runway incursions, particularly the most severe ones, demonstrates a sustained reduction.
- Transport Canada and all sectors of the aviation industry must continue to collaborate and develop tailored solutions to identified hazards at Canadian airports. These solutions could include improvements in air traffic control procedures, surveillance and warning systems, runway and taxiway designs, holding position visual aids, and flight crew training and procedures.
- Modern technical solutions, such as in-cockpit electronic situational awareness aids, and direct-to-pilot warnings, such as runway status lights, should also be implemented.
1.19 Useful or effective investigation techniques
The runway incursion occurred during the hours of daylight in visual meteorological conditions, when the aircraft landed while the flight crew was unaware that an airport vehicle was still on the active runway.
The investigation found no indication that the aircraft’s systems, or the flight crew’s performance, played a role in this occurrence.
As a result, the analysis will focus on communications from the flight crew and the airport vehicle operators, visual conditions, and the effectiveness of the airport’s operations.
Mandatory frequency (MF) areas are established surrounding uncontrolled aerodromes to facilitate communication between aerodrome users. In this occurrence, the flight crew followed communication procedures, as per the Canadian Aviation Regulations (CARs), as they approached the airport.
Trail Airport (CAD4) had established communication procedures for ground operations. Several of these procedures were complied with on the day of the occurrence. However, although a radio functionality check was required before entering the manoeuvring area, per the Airport Vehicle Operator Permit (AVOP) Study Guide, the truck driver (Operator 1) did not conduct one. As a result, Operator 1 did not realize that the radio volume had been turned down to a level that prevented effective communication. Consequently, Operator 1 could not confirm that the flight crew or the other airport vehicle operator (Operator 2) had heard his broadcast stating that he was entering the active runway.
Effective communication in an MF area can prevent aerodrome users from making assumptions about the movements and intentions of others. For example, the snowplow driver (Operator 2) attempted to inform the truck driver (Operator 1) of the inbound aircraft, but this communication was not acknowledged. Operator 2 assumed that Operator 1 had heard the broadcast about the inbound aircraft’s estimated time of arrival and did not make any further attempts to communicate. If users of an MF are not required to confirm that their broadcasts are heard and understood in an airport environment, there is a risk that movements will be made without the knowledge of other users, which could lead to a collision.
In this occurrence, gaps in communication protocol and missed opportunities for communication between aerodrome users contributed to Operator 1 being unaware of the inbound aircraft and vice versa. The truck driver (Operator 1) did not broadcast the vehicle position or his intentions when changing location on the runway, contrary to what is required by Transport Canada’s Aerodrome Standards and Recommended Practices (TP 312). Broadcasting the vehicle’s position and the operator’s intentions would have greatly increased the chances of the flight crew becoming aware of his presence. The absence of a broadcast reinforced the flight crew’s assumption that the runway was clear, and they continued their approach to land.
This occurrence highlights that the lack of clear communication and coordination can introduce hazards when operating on or around active runways. Effective communication and coordination help ensure that all aerodrome users have a shared awareness of the current situation: flight crews are aware of vehicles operating in the vicinity of active runways, and airport operators are aware of aircraft departures and arrivals. As observed in this occurrence, if airport vehicle operators do not follow communication procedures, there is increased risk of a runway incursion due to inaccurate awareness of other aerodrome users.
2.3 Visual conditions
In this occurrence, the visual conditions made it more difficult for the flight crew to detect the airport vehicle on the active runway.
During the aircraft’s approach, the sun, low on the horizon, reflected off the wet runway, creating a solar glare condition that diminished the flight crew’s ability to detect the airport vehicle on the runway. Specifically, the glare made it difficult for the flight crew to see the entire length of the runway.
The paint colour and markings on airport vehicles help flight crews see them. The occurrence airport vehicle was painted white and had black accents, and the ground surrounding the runway was snow-covered. The airport vehicle’s flashing beacon and daytime running lights were on. However, under the prevailing visual conditions, the markings and colour were insufficient to make the vehicle conspicuous to the flight crew. It is unknown whether the flight crew would have been able to see the airport vehicle on the runway if it had had its full headlights on.
If airport vehicles are not conspicuous, they may not be seen by flight crew, increasing the risk of potential collisions.
2.4 Airport operations
The regulations and standards governing airport operations in Canada are general in nature. This places the onus on airports to develop a training program that ensures its airport vehicle operators are adequately prepared to perform the tasks they are assigned.
In this case, although CAD4 had established a training program for airport vehicle operators, the program did not provide guidance for operations with multiple vehicles on the manoeuvring area. In this occurrence, the 2 airport vehicle operators were unaware of each other’s location and intentions during the landing of the aircraft. If training programs for airport vehicle operators do not address common operational scenarios, there is increased risk that airport vehicle operators will lack the knowledge needed to safely conduct their duties.
As well, at the time of the occurrence, Operator 1 and Operator 2 had not completed all the requirements specified in the Airport Staff Training Manual. For example, training related to operating a vehicle on the critical portion of the runway had not been completed. When airport operators’ training plans are not fully implemented, there is increased risk that airport vehicle operators will miss important actions, compromising safety.
2.4.2 Safety management systems
An airport’s safety management system (SMS) must be able to proactively identify hazards and effectively manage the safety risks within the airport’s operation. Runway incursions create the potential for collision; therefore, corrective action taken following occurrences must address this risk.
There were 2 runway incursions at CAD4 in 2017. The SMS manager had completed a safety investigation and risk assessment for both events; the events were deemed unrelated to the airport operations and procedures were not reviewed or revised. The airport’s SMS goals and objectives for 2018 did not include an objective related to mitigating runway incursions.
If proactive hazard identification and mitigation strategies are not implemented under an airport’s SMS, the risk of incursions and collisions will remain.
3.1 Findings as to causes and contributing factors
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
- Although a radio functionality check was required before entering the manoeuvring area, per the Airport Vehicle Operator Permit (AVOP) Study Guide, the truck driver (Operator 1) did not conduct one. As a result, Operator 1 did not realize that the radio volume had been turned down to a level that prevented effective communication.
- The truck driver (Operator 1) did not broadcast the vehicle position or his intentions when changing location on the runway, contrary to what is required by Transport Canada’s Aerodrome Standards and Recommended Practices (TP 312). Broadcasting the vehicle’s position and the operator’s intentions would have greatly increased the chances of the flight crew becoming aware of his presence.
- The sun, low on the horizon, reflected off the wet runway, creating a solar glare condition that diminished the flight crew’s ability to detect the airport vehicle on the runway.
3.2 Findings as to risk
These are conditions, unsafe acts or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
- If users of an MF are not required to confirm that their broadcasts are heard and understood in an airport environment, there is a risk that movements will be made without the knowledge of other users, which could lead to a collision.
- If airport vehicle operators do not follow communication procedures, there is increased risk of a runway incursion due to inaccurate awareness of other aerodrome users.
- If airport vehicles are not conspicuous, they may not be seen by flight crew, increasing the risk of potential collisions.
- If training programs for airport vehicle operators do not address common operational scenarios, there is increased risk that airport vehicle operators will lack the knowledge needed to safely conduct their duties.
- When airport operators’ training plans are not fully implemented, there is an increased risk that airport vehicle operators will take inappropriate actions or miss important actions, compromising safety.
- If proactive hazard identification and mitigation strategies are not implemented under an airport’s safety management system, the risk of incursions and collisions will remain.
3.3 Other findings
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
- The flight crew did not isolate the cockpit voice recorder’s recording before it was overwritten. Therefore, the cockpit voice recorder was not available for review, and information that could have been valuable to the investigation was lost.
4.0 Safety action
4.1 Safety action taken
4.1.1 Pacific Coastal Airlines Ltd.
After this occurrence, internal safety management system (SMS) hazard reports were filed as required. An internal investigation was initiated to develop hazard mitigation.
4.1.2 Trail Airport
Since the occurrence, the Trail Airport (CAD4) has reported to have implemented the following safety actions:
- It developed site-specific, clear, workable very high frequency (VHF) radio check and operating procedures.
- It reviewed and amended Airport Vehicle Operator Permit (AVOP) procedures to include procedures for entering and exiting the runway.
- It developed procedures for airside operations to assist vehicle operators if they find themselves on a runway occupied by an aircraft.
- It identified communication protocols to improve safety at the airport (radio procedures among airport staff on duty and between shifts, as well as staff-to-supervisor and airport-to-airline communications). It made changes to procedures, where appropriate.
- It amended the Apron Management Plan.
- All employees reviewed the airport’s procedure for communicating a near-miss incident.
- The Airport Staff Training Manual was reviewed, and improvements were made.
- Employees were retrained and retested for AVOP and radio procedures. Individual learning plans were developed for employees to become confident operating a VHF aeronautical radio.
- Ground and aviation radios were mounted in the skid steer and Snowplow 2 to increase situational awareness. Ground radio speakers have now been installed in all airport equipment.
- All employees met to discuss informal radio operating procedures, including what to do if the other operator does not respond to a radio communication and shared responsibility for safety and communication.
- Procedures in the winter operations manual were revised with respect to staffing levels and airside snow clearing when a commercial air carrier is en route.
- The airport provided feedback to the airline requesting radio communication when the aircraft is on final approach (15 to 20 minutes) and on short final approach.
- The airport identified all duties superfluous to core responsibilities and determined how these tasks can be managed without affecting day-to-day operations. The airport manager published guidelines concerning these tasks in the Airport Staff Training Manual and trained staff in these guidelines.
This report concludes the Transportation Safety Board of Canada’s investigation into this occurrence. The Board authorized the release of this report on . It was officially released on .
- Date modified: