航空 发表于 2010-8-3 09:43:39

AVIATION INVESTIGATION REPORT 11 FEBRUARY 2003

<P>Transportation Safety Board of Canada </P>
<P>**** Hidden Message *****</P>

航空 发表于 2010-8-3 09:43:50

AVIATION INVESTIGATION REPORT<BR>A03O0034<BR>RUNWAY EXCURSION<BR>SKYSERVICE AIRLINES INC.<BR>AIRBUS A320-212 C-GJUP<BR>WINDSOR, ONTARIO<BR>11 FEBRUARY 2003<BR>Transportation Safety Board<BR>of Canada<BR>Bureau de la sécurité des transports<BR>du Canada<BR>The Transportation Safety Board of Canada (TSB) investigated this occurrence for the<BR>purpose of advancing transportation safety. It is not the function of the Board to assign fault<BR>or determine civil or criminal liability.<BR>Aviation Investigation Report<BR>Runway Excursion<BR>Skyservice Airlines Inc.<BR>Airbus A320-212 C-GJUP<BR>Windsor, Ontario<BR>11 February 2003<BR>Report Number A03O0034<BR>Summary<BR>Skyservice Airlines Flight 0045, an Airbus A320-212, registration C-GJUP, serial number 645, was<BR>on a regularly scheduled instrument flight rules (IFR) flight. The flight had departed<BR>Toronto/LBPIA at 1257 eastern standard time, flew to Windsor where additional passengers<BR>were picked up, and then continued to Cancun, Mexico. For the return leg, Flight 0045 departed<BR>Cancun at 1910 and arrived at Windsor at 2243.<BR>At the time of the occurrence, the aircraft was back-taxiing to position on Runway 25 in<BR>preparation for departure from Windsor. The aircraft radio control of aerodrome lighting<BR>(ARCAL) system was in use as the tower had closed during passenger deplaning at the terminal.<BR>The airfield lighting extinguished while the aircraft was taxiing to the runway and was not reactivated<BR>by the copilot until the aircraft neared the end of the runway. The captain observed<BR>the runway end lights after the ARCAL lighting system was activated and applied heavy<BR>braking. Because of the aircraft’s proximity to the end of the runway and the speed at which it<BR>was being taxied, the aircraft did not remain within the confines of the runway. After the aircraft<BR>stopped, at approximately 2327 eastern standard time, the flight crew shut down the engines<BR>and advised London Flight Information Centre (FIC) of their position. There were no injuries to<BR>the passengers or crew. The passengers and flight crew deplaned the aircraft and were bused<BR>back to the airport terminal.<BR>Ce rapport est également disponible en fran&ccedil;ais.<BR>- 2 -<BR>1 All times are eastern daylight time (Coordinated Universal Time (UTC) minus four<BR>hours) unless otherwise noted.<BR>Other Factual Information<BR>The captain and first officer had not flown together as a crew prior to the day of the occurrence.<BR>The captain held a valid airline transport pilot licence (ATPL). He had accumulated over 11 000<BR>hours total flight time of which over 6600 hours were on Airbus A320 aircraft. He was certified<BR>and qualified for the flight under existing regulations. He had been awake for 17 hours and had<BR>been performing duties as a flight crew member for 12 hours prior to the occurrence. The<BR>captain was seated in the aircraft left seat and was the designated pilot flying (PF).<BR>The first officer was an employee of My Travel Airways Ltd., United Kingdom (UK) and was<BR>flying for Skyservice Airlines for the winter season as part of a crew sharing arrangement<BR>between Skyservice and My Travel. He held a valid UK, Civil Aviation Authority (CAA), ATPL.<BR>This licence had been appropriately attached to a Transport Canada, foreign licence validation<BR>certificate and was being properly exercised in accordance with the privileges of his UK licence.<BR>He had accumulated over 2200 hours total flight time of which 450 hours were on Airbus A320<BR>aircraft. He was certified and qualified for the flight under existing regulations. He had been<BR>awake for 16 hours and had been performing duties as a flight crew member for 12 hours prior<BR>to the occurrence. The first officer was seated in the aircraft right seat and was the designated<BR>pilot not flying (PNF).<BR>On arrival at Windsor, the air traffic controller advised the flight crew that the control tower<BR>would be closed by the time the flight was ready to depart. Five minutes later, the tower closed<BR>and the aircraft radio control of aerodrome lighting (ARCAL) system was activated. While the<BR>tower is closed, runway and taxiway lighting is controlled by the pilot. The system employed at<BR>Windsor airport is defined as a “K” type ARCAL system. This system is activated by pressing the<BR>transmit button on the aircraft’s very high frequency (VHF) aeronautical radio seven times while<BR>tuned to the airport tower frequency of 124.7 MHz. Once activated, the airfield lights stay on for<BR>fifteen minutes. At any time during the activation time period, the lights may be reset for<BR>another 15 minutes by pressing the radio transmit button an additional seven times.<BR>The current automatic terminal information service (ATIS) stated that the tower was closed and<BR>advised vehicles operating on the manoeuvring area to broadcast their intentions on 124.7 MHz<BR>and to monitor that frequency. En route flight service would be provided by London Flight<BR>Service on 126.7 MHz. At 23151, the aircraft taxied via Golf and Foxtrot taxiways in preparation<BR>for departure from Runway 25. The crew followed the movement instructions and requested the<BR>IFR clearance from London Radio on 126.7 MHz. The flight crew did not broadcast their<BR>intentions on the aerodrome traffic frequency (ATF) on 124.7 MHz.<BR>The captain gave a traffic advisory announcing that the aircraft was taxiing on Foxtrot taxiway<BR>crossing Runway 12; however, this advisory was not communicated on the ATF, 124.7 MHz.<BR>While the aircraft was taxiing on Foxtrot taxiway, the airfield lighting extinguished and the flight<BR>crew continued to taxi the aircraft without activating the ARCAL system. The first officer was<BR>unfamiliar with operations at uncontrolled aerodromes, including ARCAL lighting procedures,<BR>which resulted in the captain attempting to assist the first officer with his PNF duties.<BR>- 3 -<BR>He directed the first officer to contact London Radio and inform the flight service specialist that<BR>they did not observe any snow removal activity and to advise him that nobody was responding<BR>to either the tower or ground frequency.<BR>The first officer attempted to contact London Radio several times before the flight service<BR>specialist asked Flight 0045 to please standby. Shortly after, the flight service specialist contacted<BR>the flight crew to relay the IFR departure clearance. It took over three minutes for the first officer<BR>to receive the clearance and read it back correctly. The captain then mistakenly broadcast a<BR>traffic advisory on 126.7 MHz announcing that the aircraft was positioning onto the runway.<BR>As the aircraft back-taxied on the runway, the flight crew reviewed the departure clearance,<BR>actioned the before take-off checklist, and discussed the lack of runway lighting and the means<BR>of activating the ARCAL lighting system. The first officer changed the radio frequency to the<BR>ATF 124.7 MHz and activated the ARCAL lighting system; the runway edge lights and the<BR>threshold end lights illuminated. The captain then saw the end of the runway and applied<BR>heavy braking. The aircraft overran the runway, ran over a lighting bar standard damaging a<BR>main wheel tire, travelled down a gentle slope, and stopped at a large drainage ditch running<BR>perpendicular to the runway.<BR>After the aircraft came to a stop, the flight crew communicated with London Radio to apprise<BR>the flight service specialist of their situation. The London flight service specialist relayed the<BR>flight crew’s request for maintenance assistance to the Windsor Airport Security Operations<BR>Centre (SOC). SOC requested London FIC to direct the flight crew to communicate on the ATF,<BR>124.7 MHz.<BR>A digital, ground-speed readout is displayed in front of each pilot in the upper left corner of the<BR>navigation display (ND) cathode ray tube (CRT).<BR>The flight data recorder (FDR) and cockpit voice recorder (CVR) were secured and forwarded to<BR>the TSB Engineering Branch in Ottawa. The FDR revealed that the aircraft ground speed<BR>increased to approximately 35 knots during the runway back-taxi and remained at that speed for<BR>approximately one minute prior to the aircraft exiting the end of the runway. Three seconds<BR>after activation of the ARCAL lighting system, the aircraft brake pedals were deflected to a<BR>maximum angle of 80 degrees. Tire skidmarks were evident at the centre end of the runway. The<BR>aircraft heading was relatively constant until the application of brakes.<BR>A review of the Windsor ATF recorded transmissions indicated that Staff 28, an airport ground<BR>vehicle, attempted to contact the flight crew on the ATF as the aircraft was holding short of<BR>Runway 25. The flight crew did not respond to this communique. After communicating with the<BR>firehall and Staff 29, Staff 28 attempted to contact the flight crew again; however, again there<BR>was no response. Moments later, Staff 28 observed the aircraft proceed onto the unlit runway<BR>and back-taxi. There was no broadcast message for this aircraft movement from the flight crew<BR>on the ATF.<BR>The aircraft was operating within the manufacturer’s specifications for both weight and centre<BR>of gravity limitations, and records indicate that the aircraft was properly maintained in<BR>accordance with existing regulation. There were no operational or mechanical defects involving<BR>either the braking, hydraulic, or nose wheel steering systems. The aircraft’s anti-skid system was<BR>activated and was functioning properly at the time of the occurrence.<BR>- 4 -<BR>The Skyservice A320 Flight Crew Operating Manual (FCOM), Standard Operating Procedures (SOPs),<BR>includes a directive that ground speed during taxi should be monitored by the flight crew. It<BR>further provides guidance to pilots regarding maximum speeds for taxiing and ground<BR>manoeuvring. Skyservice FCOM, SOP, Section 3.03.10, Page 2, states: “The normal maximum<BR>taxi speed should be 30 knots in a straight line, 10 knots for a sharp turn. As the ground speed is<BR>difficult to assess, monitor ground speed on the ND”.<BR>Skyservice Airlines company Flight Operations Manual (FOM) enables a document entitled<BR>“Briefing and Airport Notes”. This document is part of the on-board library and contains<BR>comprehensive information for flight crews operating into airports that require additional<BR>airport specific information. Windsor Airport is not included in this section as an airport<BR>requiring extra attention by flight crews.<BR>Transport Canada’s Aeronautical Information Publication (AIP) includes specific guidance for<BR>aircraft operations at uncontrolled aerodromes. AIP, RAC 4.5.1, states, in part: “An uncontrolled<BR>aerodrome is an aerodrome without a control tower, or one where the tower is not in operation.<BR>There is no substitute for alertness while in the vicinity of an uncontrolled aerodrome. It is<BR>essential that pilots be aware of and look for other traffic, and exchange traffic information when<BR>approaching or departing from an uncontrolled aerodrome, particularly since some aircraft may<BR>not have communication capability. To achieve the greatest degree of safety, it is essential that<BR>all radio-equipped aircraft monitor a common designated frequency, such as the published<BR>mandatory frequency (MF) or ATF, and follow the reporting procedures specified for use in an<BR>MF area while operating on the manoeuvring area or flying within an MF area surrounding an<BR>uncontrolled aerodrome.”<BR>The AIP provides further specific guidance for pilots operating IFR departures from<BR>uncontrolled airports. AIP, RAC 7.9, states: “Where a pilot-in-command intends to take-off from<BR>an uncontrolled aerodrome, the pilot shall:<BR>(a) obtain an ATC clearance if in controlled airspace;<BR>(b) report on the appropriate frequency his/her departure procedure and<BR>intentions before moving on to the runway or before aligning the aircraft on the<BR>take-off path; and<BR>(c) ascertain by radio on the appropriate frequency and by visual observation that<BR>no other aircraft or vehicle is likely to come into conflict with the aircraft during<BR>take-off”.<BR>Skyservice does not include operations at uncontrolled airports in either initial or recurrent<BR>ground training for flight crews.<BR>The Windsor Airport is a certified controlled airport between the hours of 0630 and 2230 hours<BR>local time. Outside of these hours of operation, the airport is uncontrolled, meaning the ATC<BR>tower is not staffed. Ground and air movements are facilitated by traffic advisories made over a<BR>common radio frequency by the pilots of each aircraft operating on, or in the vicinity of the<BR>airport. IFR clearances, en route flight information, and other aviation services are provided by<BR>London FIC via remote communication outlet (RCO).<BR>- 5 -<BR>Runway edge lighting comprised variable intensity white lights, spaced at 200-foot intervals, at<BR>the runway edges along the full length of the runway. There are runway threshold end lights<BR>along the width of each runway end. These are variable intensity lights, each of which is<BR>coloured red and green. The red is visible while within the confines of the runway and the green<BR>is visible while on approach to the runway. The airport has two asphalt-covered runways:<BR>runway 12/30 is 5150 feet long and 150 feet wide, and runway 07/25 is 9000 feet long and 200 feet<BR>wide.<BR>A runway condition report for runway 07/25 taken at 2230 indicated that the runway was<BR>100 per cent bare and dry. According to the routine aviation weather report (METAR) for 2300,<BR>Windsor Airport reported an overcast cloud layer at 2000 feet above ground level (agl). Visibility<BR>was reported to be 1 statute mile (sm) in light snow/ drifting snow. The wind was 240°M at<BR>23 knots gusting to 31 knots. The observation recorded at 2349 reported an overcast cloud layer<BR>at 2600 feet agl, visibility one and a half sm in light snow/blowing snow and wind 290°M at<BR>35 knots gusting to 47 knots.<BR>During taxi and ground manoeuvring operations, blowing and drifting snow can create false<BR>impressions of speed and movement. Hawkins, F.H. (1987), Human Factors In Flight, Hants, UK:<BR>Ashgate on Illusions In Taxiing writes that in winter, blowing snow may be sweeping across an<BR>airfield, giving a false impression of relative movement. Inappropriate control action can be<BR>initiated based on this illusion. For instance, an impression can be given that the aircraft is<BR>stationary when it is still moving, and a pilot could apply the brakes in a more abrupt manner<BR>than he would if he knew the aircraft was moving. Alternatively, the aircraft could slowly creep<BR>forward, colliding with an obstruction, when it was thought to be stationary.<BR>Analysis<BR>In this occurrence, a number of factors combined, resulting in the runway excursion. This<BR>analysis will examine those factors, including the flight crew’s unfamiliarity with and nonadherence<BR>to uncontrolled aerodrome procedures, the flight crew’s failure to activate the<BR>ARCAL lighting system in a timely manner, the illusions created by drifting snow during low<BR>visibility taxi and ground manoeuvring, and lastly, the flight crew’s non-conformance with<BR>company SOPs.<BR>The first officer was unfamiliar with procedures at uncontrolled aerodromes. He transmitted the<BR>initial aircraft manoeuvring on the apron on the appropriate ATF and then, in error, requested<BR>the IFR departure clearance on this frequency. He then contacted London FIC on the<BR>appropriate radio frequency to obtain the departure clearance. The first officer made it known to<BR>the captain that he was not familiar with uncontrolled aerodrome procedures and as a result the<BR>captain assisted the first officer in his PNF duties, thereby increasing his own workload. The<BR>captain made the subsequent appropriate radio calls while manoeuvring on the taxiways and<BR>prior to back-taxiing on the runway; however, these radio calls were transmitted on radio<BR>frequencies other than the ATF. This non-use of the ATF and the captain’s expectancy to receive<BR>a response on either the tower or ground frequency indicated that he was not fully aware of the<BR>environment in which he was operating. The flight crew did not monitor the published ATF,<BR>and, as a result, they did not hear any of the radio transmissions directed to them by Staff 28.<BR>During the runway back-taxi and after conducting the before take-off check, the flight crew<BR>discussed the lack of runway lighting and the means of activating the ARCAL lighting system.<BR>Skyservice Airlines does not specifically address the operational use of ARCAL lighting systems<BR>- 6 -<BR>in either its initial or recurrent ground school for flight crew members. It likewise does not<BR>address operations at night at uncontrolled aerodromes in either company SOPs or the company<BR>operations manual. There is no Transport Canada regulation requiring them to do so; however,<BR>instructions for using ARCAL lighting exist in the Canada Flight Supplement (CFS) as well as the<BR>Air Canada Route Manual Supplement, which is Skyservice’s primary source of airport<BR>supplementary information. Both of these documents are part of the on-board library and were<BR>available to the flight crew.<BR>The flight crew back-taxied the aircraft on the runway in conditions of rear quarterly gusting<BR>winds and blowing snow at night without the benefit of runway lighting. During the low<BR>visibility taxi, both flight crew members indicated that they could visually reference the end of<BR>the runway; however, they did not consider the illusions of relative movement to which they<BR>were being subjected. The strong tailwind with blowing snow conditions would have given the<BR>crew the illusion of moving slower than they were actually moving. Activation of the ARCAL<BR>lighting system prior to entering the runway is not only good airmanship, as it indicates to other<BR>airport vehicles that the runway is in use, but it also would have provided the flight crew with a<BR>visual cue as to the aircraft’s relative movement as it back taxied about 5500 feet of runway. It<BR>also would have clearly indicated the end of the runway to the flight crew.<BR>Contrary to company SOPs, the flight crew did not monitor the aircraft ground speed to ensure<BR>a safe taxi speed while back-taxiing on the runway. The aircraft exceeded the normal maximum<BR>straight line taxi speed of 30 knots and exited the end of the runway at approximately 35 knots.<BR>The following TSB Engineering Branch report was completed:<BR>LP010/2003 - FDR/CVR Examination<BR>Findings as to Causes and Contributing Factors<BR>1. The flight crew continued to taxi at night in low visibility conditions after the airfield<BR>lighting had extinguished, which deprived the crew of important visual cues to clearly<BR>identify the end of the runway and cues as to the taxi speed of the aircraft.<BR>2. The flight crew did not monitor the aircraft’s ground speed to ensure a safe taxi speed<BR>while back-taxiing on the runway. The aircraft exceeded the normal maximum<BR>straight line taxi speed of 30 knots and exited the end of the runway at approximately<BR>35 knots.<BR>3. The flight crew did not consider the illusion of relative movement caused by the<BR>tailwind and blowing snow on the runway. This contributed to the aircraft ground<BR>speed inadvertently increasing to 35 knots.<BR>4. The captain observed the runway end lights after the ARCAL lighting system was<BR>activated and applied heavy braking; however, because of the aircraft’s proximity to<BR>the end of the runway and the speed at which the aircraft was taxied, it failed to<BR>remain within the confines of the runway.<BR>5. The first officer was unfamiliar with procedures for operating at uncontrolled<BR>aerodromes and in the use of ARCAL lighting and, as a result, the captain conducted<BR>both PF and PNF duties, which increased his workload.<BR>- 7 -<BR>Findings as to Risk<BR>1. The captain made the appropriate radio calls while manoeuvring the aircraft on the<BR>taxiways and prior to proceeding onto the runway; however, these transmissions<BR>were not made on the ATF of 124.7 MHz.The flight crew did not adhere to<BR>uncontrolled aerodrome procedures and as a consequence were not aware of any<BR>communiques directed to them on the ATF.<BR>2. Skyservice does not include operations at uncontrolled aerodromes in either initial or<BR>recurrent ground training for flight crews.<BR>Safety Action<BR>As a result of this occurrence, Skyservice Airlines identified 10 safety actions that were<BR>implemented in 2003. They are as follows:<BR>1. Operations at uncontrolled airports in Canada to be addressed during company<BR>indoctrination training for all Skyservice pilots.<BR>2. Use of ARCAL airfield lighting systems to be addressed during company<BR>indoctrination training for all Skyservice pilots.<BR>3. Winter operations training now includes a discussion of the illusion effects created by<BR>drifting snow during ground operations.<BR>4. Operations at uncontrolled airports and/or where ARCAL lighting is in use to be<BR>addressed in the Briefing and Airport Notes manual. Such information could be<BR>addressed in a summary section with a list of applicable airfields included.<BR>5. Special airspace and ATC procedures unique to Windsor Airport and the surrounding<BR>airspace to be addressed in the Briefing and Airport Notes manual.<BR>6. The role of the PNF as a monitoring pilot during all flight phases will be emphasized<BR>in ground and simulator training and during line training and checking. Special<BR>emphasis of monitoring of taxiing path and ground speed during ground operations<BR>to be included.<BR>7. Low visibility taxiing and ground operations in conditions involving surface<BR>contamination will be addressed in simulator training.<BR>8. Develop a set of “best practices” techniques which serve as an enhancement to SOP’s.<BR>Best practices include methods for maintaining an appropriate level of flight discipline<BR>during dynamic phases of flight.<BR>9. Pilots involved in any reportable accident or incident where damage is incurred or<BR>suspected must not operate as flight crew until a thorough assessment of the<BR>accident/incident has been made by the VP flight operations in accordance with<BR>FOM DIV 111, 17.10.3.<BR>- 8 -<BR>10. Any movement of aircraft following an excursion from a paved surface will be<BR>conducted only under the guidance of Skyservice maintenance, who will ensure that<BR>the aircraft manufacturer’s guidelines are followed.<BR>This report concludes the Transportation Safety Board’s investigation into this occurrence. Consequently,<BR>the Board authorized the release of this report on 25 February 2004.<BR>- 9 -<BR>Appendix A - Windsor Aerodrome Chart
页: [1]
查看完整版本: AVIATION INVESTIGATION REPORT 11 FEBRUARY 2003