Runway incursion, Incident at Vaasa airport, Finland, on 15 December 1999

Similar documents
EFIS failure, Incident on board aircraft SE-LGX in the air space north-east of Stockholm/Arlanda Airport, AB county, 13 November 2002

AIRPROX incident between a Cessna 650, LN-NLD, and Airbus A320, HS- IPZ, approximately 20 NM north of Oslo.

Loss of separation west of Helsinki-Vantaa airport on

Pitch control problems, Boeing , March 27, 2001

Micro-summary: A failure of electronic flight instrumentation on this BAe-146 results in an altitude bust.

Risk of collision between two airliners southwest of Vihti VOR, Finland on 9 October 1998

Investigation Report. Identification. Factual information. German Federal Bureau of Aircraft Accidents Investigation. TX002-0/07 September 2008

Tire failure and systems damage on takeoff, Airbus A , G-JDFW, 10 July 1996

Near-miss between a DHC-8-311, LN-WFR, and Boeing

Air Accident Investigation Unit Ireland

Loss of separation over BALTI on

Air Accident Investigation Unit Ireland FACTUAL REPORT

Nosewheel stuck 90, Airbus A320, N536JB, September 21, 2005

Oostwold Airshow 2017

PRELIMINARY OCCURRENCE REPORT

Near-miss, Boeing 737, NZ 450 and Hawker Siddeley 748, ZQA 719, Wellington Airport, 2 July 1995

FINAL REPORT ON THE SERIOUS INCIDENT INVOLVING AIRCRAFT CIRRUS SR-20, OE-DDD OCCURRING ON AUGUST 17, 2012 AT SPLIT AIRPORT

PRELIMINARY KNKT

Air Accident Investigation Unit Ireland FACTUAL REPORT

Taxiway landing, Boeing , February 24, 2004

Runway incursion between Airbus A , G-SMTJ and Boeing 737-2E7, EI-CJI

Near-miss, Aircraft Incident at Lappeenranta TMA, Finland on 29 July 1999

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

Air Accident Investigation Unit Ireland. FACTUAL REPORT ACCIDENT Colibri MB-2, EI-EWZ ILAS Airfield, Taghmon, Co. Wexford

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

Final report on aircraft serious incident

Two s Too Many BY MARK LACAGNINA

GENERAL INFORMATION Aircraft #1 Aircraft #2

21 November 2016, 18:06 UTC Coordinates --- Altitude Approximately 1700 ft above mean sea level Air traffic service

REPORT IN-011/2012 DATA SUMMARY

FINAL REPORT. Ref. No 135/05/ZZ. Investigation into separation infringement between EEZ 1978 and OK-RMA. at CTR/TMA LKPR on 22 th of April 2005

AIRCRAFT INCIDENT REPORT

Turbulence injury, Boeing , G-BNLS, April 1, 2002

Time: 1111Z Position: 5049N 00016W Location: 1nm SE Brighton City Airport

FINAL REPORT. Ref. No 547/05/ZZ. Investigation separation minima infringement CSA 689 and DLH 2JC on 1 st of November Prague December 2005

VFR PHRASEOLOGY. The word IMMEDIATELY should only be used when immediate action is required for safety reasons.

Aircraft Incident Investigation Report on Ethiopian Airlines Aircraft B (ET-AMG) Runway Incursion. Addis Ababa Bole International Airport

MINISTRY OF INFRASTRUCTURE STATE COMMISSION ON AIRCRAFT ACCIDENT INVESTIGATION FINAL REPORT. Serious Incident No: 518/07

AI AIRCRAFT SERIOUS INCIDENT INVESTIGATION REPORT THAI AIRASIA X CO., LTD. H S X T C CHINA AIRLINES B

AIRCRAFT INCIDENT REPORT AND EXECUTIVE SUMMARY

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AI AIRCRAFT SERIOUS INCIDENT INVESTIGATION REPORT PRIVATELY OWNED J A T

BULLETIN. Serious incident involving BOMBARDIER INC. DHC OY-GRO. and RUNWAY SNOW CLEARING VECHICLES

SERIOUS INCIDENT. Aircraft Type and Registration: Boeing 737-8F2, TC-JKF. No & Type of Engines: 2 CFM 56-7B22 turbofan engines

Uncontained engine failure, Boeing , N107BV, August 2, 1993

Flight attendant fall off Boeing , May 4, 1997

In-Flight Fire/Emergency Landing, Federal Express Flight 1406 Douglas DC-10-10, N68055, Newburgh, New York September 5, 1996

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

Appendix F ICAO MODEL RUNWAY INCURSION INITIAL REPORT FORM

AIRPROX REPORT No

AIRCRAFT INCIDENT REPORT AND EXECUTIVE SUMMARY

Incident between an airliner and airport maintenance vehicle at Kuusamo airport on 29 January 2003

Aircraft Accident Investigation Report

AIRPROX REPORT No Date/Time: 7 Dec Z (Saturday)

AIRCRAFT INCIDENT REPORT AND EXECUTIVE SUMMARY

Training Department. GA Club Entry UKV-GA

Appendix A COMMUNICATION BEST PRACTICES

Flight Director Regulation for AIR SHOW in Mlada Boleslav, 16 June 2016

Date: 29 Jun 2018 Time: 1502Z Position: 5325N 00312W Location: 5nm NW Liverpool Airport

GOVERNMENT OF INDIA DIRECTORIATE GENERAL OF CIVIL AVIATION NEW DELHI

Air Accident Investigation Unit Ireland. FACTUAL REPORT INCIDENT Cameron N-105 Balloon, G-SSTI Mountallen, Arigna, Co. Roscommon 24 September 2013

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

Hard landing, ATR A, D-ANFH, September 17, 2005

Air Accident Investigation Unit Ireland

AIRCRAFT SERIOUS INCIDENT INVESTIGATION REPORT

FINAL REPORT BOEING B777, REGISTRATION 9V-SWH LOSS OF SEPARATION EVENT 3 JULY 2014

LETTER OF AGREEMENT. Between. and RELATING TO

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

National Transportation Safety Board Aviation Incident Final Report

RV6 800ft aal 24:27 24:39 25:03 24:51

Air Accident Investigation Unit Ireland

REPORT IN-038/2010 DATA SUMMARY

Air Accident Investigation Unit Ireland FACTUAL REPORT

AIRCRAFT SERIOUS INCIDENT INVESTIGATION REPORT

Galley lift injury, Boeing , June 9, 1999

A PILOT S GUIDE To understanding ATC operations at Lancaster Airport

REPORT A-024/2012 DATA SUMMARY

AA AIRCRAFT ACCIDENT INVESTIGATION REPORT PRIVATELY OWNED J A 2 5 C H

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

Fast level off produces broken leg, Boeing , June 2, 2002

Air Accident Investigation Unit Ireland SYNOPTIC REPORT

Second Interim statement A-029/2012

National Transportation Safety Board Aviation Incident Final Report

AA AIRCRAFT ACCIDENT INVESTIGATION REPORT FIRST FLYING CO., LTD. J A

Failure of retract actuator, Boeing , December 6, 1999

PRELIMINARY REPORT Accident involving DIAMOND DA40 N39SE

SECTION 4 - APPROACH CONTROL PROCEDURES

Flight control system failure, Airbus A320 EI-TLI, on

Date: 29 Apr 2017 Time: 1119Z Position: 5226N 00112W Location: 10nm ENE Coventry

Date: 01 Aug 2016 Time: 1344Z Position: 5441N 00241W

Air Accident Investigation Unit Ireland. FACTUAL REPORT INCIDENT TO BOMBARDIER DHC-8-402, G-JEDR Waterford Airport (EIWT), Ireland 05 June 2012

Air Accident Investigation Unit Ireland. PRELIMINARY REPORT ACCIDENT BRM Land Africa, EI-EOH Near Ballina, Co. Mayo 4 May 2018

AERONAUTICAL INFORMATION CIRCULAR Y 024/2015

Investigation Report

FINAL REPORT. Investigation into the incident of aircraft A , at LKPR on 12 February Prague April 2007

Contents. Subpart A General 91.1 Purpose... 7

Instrument failure, Airbus A , G-EUOB

Aircraft Attempted Takeoff from Taxiway

Transcription:

Runway incursion, Incident at Vaasa airport, Finland, on 15 December 1999 Micro-summary: Embraer taxis onto runway while it's being used for touch and gos. Event Date: 1999-12-15 at 1720 UTC Investigative Body: Finland Accident Investigation Board (AIB), Finland Investigative Body's Web Site: http://www.onnettomuustutkinta.fi/ Cautions: 1. Accident reports can be and sometimes are revised. Be sure to consult the investigative agency for the latest version before basing anything significant on content (e.g., thesis, research, etc). 2. Readers are advised that each report is a glimpse of events at specific points in time. While broad themes permeate the causal events leading up to crashes, and we can learn from those, the specific regulatory and technological environments can and do change. Your company's flight operations manual is the final authority as to the safe operation of your aircraft! 3. Reports may or may not represent reality. Many many non-scientific factors go into an investigation, including the magnitude of the event, the experience of the investigator, the political climate, relationship with the regulatory authority, technological and recovery capabilities, etc. It is recommended that the reader review all reports analytically. Even a "bad" report can be a very useful launching point for learning. 4. Contact us before reproducing or redistributing a report from this anthology. Individual countries have very differing views on copyright! We can advise you on the steps to follow. Aircraft Accident Reports on DVD, Copyright 2006 by Flight Simulation Systems, LLC All rights reserved. www.fss.aero

Investigation report C 23/1999 L Translation of the Finnish original report LN-TDY, Embraer 110 Bandeirante HW-334, Hawk Mk 51 According to Annex 13 of the Civil Aviation Convention, paragraph 3.1, the purpose of aircraft accident and incident investigation is the prevention of accidents. It is not the aim of aircraft accident investigation or the investigation report to apportion blame or to assign responsibility. This basic rule is also contained in the Investigation of Accidents Act, 3 May 1985 (373/85) and European Union Directive 94/56/EC. Use of the report for purposes other than the improvement of safety should be avoided.

C 23/1999 L CONTENTS SYNOPSIS...iii 1 FACTUAL INFORMATION... 1 1.1 Sequence of events... 1 1.2 Basic information... 1 1.2.1 Aircraft... 1 1.2.2 Type of operation... 1 1.2.3 Persons on board... 2 1.2.4 Injuries to persons... 2 1.2.5 Damage to aircraft... 2 1.2.6 Other damage... 2 1.2.7 Personnel information... 2 1.2.8 Weather... 3 2 ANALYSIS... 5 2.1 Incident in Vaasa... 5 2.2 Incident in Oulu on 25 January 2000... 5 2.3 Means for the ATC to prevent this kind of incidents... 5 3 Conclusions... 7 3.1 Findings... 7 3.2 Probable cause... 7 4 RECOMMENDATIONS...9 Appendices Other investigation material is stored at the Accident Investigation Board, Finland. i

C 23/1999 L SYNOPSIS A flight safety incident occurred at Vaasa airport on 15 December 1999 at 19.20 local time (17.20 UTC, Universal Co-ordinated Time), when an aircraft of type Embraer EMB- 110 Bandeirante, owned by Reguljair Ltd, registered LN-TDY, call sign REF901, taxied to runway 34 at the same time when a Hawk advanced jet trainer operated by the Finnish Air Force, registered HW-334, call sign H30, was making a touch-and-go landing on runway 16. The Hawk passed the E110 at a height of about 50 meters after the touchand-go landing. Neither pilot saw each other s aircraft because of darkness and occasional ground fog. The air traffic controller on duty in Vaasa tower and the Hawk pilot reported the incident to CAA Finland, Flight Safety Authority, as required by Aviation Regulation GEN M1-4. The Accident Investigation Board (AIB), Finland, decided to commence an investigation (C 23/1999 L) on 29 December 1999. Flight instructor Pekka Raine was appointed to investigate the incident. In addition, air traffic controller Ari Huhtala assisted in the examination of air traffic control operations. The investigation report was sent for comments to the Air Navigation Services department of the Finnish Civil Aviation Administration, Finnish Air Force, and the Swedish accident investigation authority (Statens Haverikommission). The comments received have been taken into account in the report. The statement of the Air Navigation Services department is annexed. Statens Haverikommission also reported that Reguljair Ab had gone into liquidation and ceased operations. The investigation was closed on 13 March 2001. iii

C 23/1999 L 1 FACTUAL INFORMATION 1.1 Sequence of events The Finnish Air Force Hawk, call sign H30, was approaching Vaasa airport on a night VFR navigation training flight. When the crew requested approach instructions for a touch-and-go landing, Vaasa TWR cleared it to join left downwind leg for runway 16. The radio communications were in Finnish. After a while the Reguljair EMB-110, call sign REF901, requested start-up, which the TWR accepted. The radio communications with REF901 were in English. H30 reported on downwind leg for runway 16, and was cleared for a touch-and-go landing on runway 16. Vaasa TWR then cleared REF901 to holding Bravo, which the crew acknowledged. While REF901 was taxiing towards the holding position, the controller gave a route clearance and the crew read it back. However, REF901 did not stop at holding Bravo, but continued taxiing to runway 34. At the same time, H30 was making a touch-and-go landing on runway 16, coming towards REF901 at a distance of about 600 meters. H30 was then about to lift off after the touch-and-go landing, and became airborne again near taxiway Alfa. While taxiing to the runway, REF901 crew asked the controller if they had been cleared to line-up. At that time, the controller realised what had happened and gave a negative answer. REF901 crew then reported that they would leave the runway, but the controller replied that it was no longer necessary. H30 had already passed REF901 at a height of about 50 meters. Thereafter the controller cleared REF901 to line up for runway 34. Because of the darkness and patches of ground fog, neither pilot saw each other s aircraft. The controller saw both aircraft from the tower at the time of the incident, but did not notice that REF901 had taxied past the clearance limit. A transcript of relevant radio communications on Vaasa TWR frequency 119,300 MHz is contained in Appendix 1. 1.2 Basic information 1.2.1 Aircraft Twin-engined non-pressurised turboprop aeroplane Embraer EMB-110 Bandeirante, registered LN-TDY, used in commuter operations. Two-seated advanced jet trainer Hawk Mk 51, registered HW-334. 1.2.2 Type of operation REF901 was on a ferry flight from Vaasa to Umeå, Sweden. 1

C23/1999 L H30 was conducting a night VFR navigation training flight from Kauhava to Vaasa and back to Kauhava. 1.2.3 Persons on board REF901 had a crew of two pilots. H30 had a flight instructor and a student pilot on board. 1.2.4 Injuries to persons There were no injuries. 1.2.5 Damage to aircraft Neither aircraft was damaged. 1.2.6 Other damage There was no other damage. 1.2.7 Personnel information Crew of REF901: Pilot-in-command: airline transport pilot licence, total flying experience 4878 hours, of which 1835 hours on EMB-110. Co-pilot: commercial pilot licence, total flying experience 665 hours, of which 443 hours on EMB-110. The crew had been off duty on the previous day. On the day of the incident, their first shift had commenced at 5.10 UTC and ended at 6.50 UTC. During that time they had flown one flight of 30 minutes and made one landing. Thereafter the crew had rested until 11.20 UTC, when a new shift was started. During the second shift, the crew had been flying for two hours and made four landings before the incident now under investigation. The crew felt themselves well rested and fit for duty at the time of the incident. Crew of H30: Pilot-in-command: flight instructor, total flying experience 1450 hours, of which 750 hours on Hawk. On the previous day, the flight instructor had worked during normal office hours. On the day of the incident his shift had commenced at 15.30 local time. The incident flight was the instructor s third flight on that day. The combined flight time of the two preceding flights was 1 h 41 min. 2

C 23/1999 L Student pilot: flying experience not relevant for the incident. Air traffic controller: The air traffic controller s licence was valid until 10 September 2001, ratings EFVA TWR/APP. The controller was on duty as scheduled and his alertness was normal. 1.2.8 Weather EFVA 15.12.1999 at 1720 UTC: wind 270º 2 kt, visibility more than 10 km, surface fog, clouds FEW 900 ft, temperature -16ºC, dewpoint -17ºC, QNH1006. There were occasional patches of ground fog. The air traffic controller was able to see both aircraft at the time of the incident. The pilot-in-command of H30 did not see the ground fog from the traffic circuit, but only during the touch-and-go landing. 3

C 23/1999 L 2 ANALYSIS 2.1 Incident in Vaasa H30 flew in accordance with the clearances issued. Because of the darkness and ground fog, the crew could not see REF901 taxiing towards the runway, and nothing in the radio communications alerted them either. The crew of REF901 forgot their clearance limit and taxied to the runway without clearance. Due to darkness and ground fog, they could not see H30. The crew of REF901 could not understand the radio communications between the TWR and H30, which were in Finnish, and therefore did not realize that H30 was making a touch-and-go landing. If the REF901 pilots had understood this, they probably would not have taxied to an active runway. When seen from the control tower, holding Bravo is situated at the front right side about 320 meters away. The controller did not notice REF901 taxiing past the clearance limit until the pilots asked him whether the plane had been cleared to the runway. For this reason, the controller could not prevent the incident. Radio communications were in accordance with applicable regulations. 2.2 Incident in Oulu on 25 January 2000 An incident similar to that in Vaasa occurred in Oulu on 25 March 2000. In that case, an Estonian Let 410 aircraft operated by EV Piirivalve Lennusalk, registered ES-PLY, took off without clearance when there was an airport maintenance vehicle on the runway. The aircraft passed the vehicle from a height of about 20-30 meters during the initial climb. The incident has been investigated by the Finnish AIB, and the following is an extract from investigation report No. C 2/2000 L (originally written in Finnish). There are means to prevent such situations. The controller on duty at the time of the incident suggested that the pilots could be informed of the expected delay and its cause. In the incident now under investigation, the controller said: ES-PLY line up runway 30. However, in his incident report, which was very comprehensive and useful for the investigation, he stated that a better clearance would have been: ES- PLY line up runway 30 and wait, will be 1 min delay before takeoff due to vehicle on runway. 2.3 Means for the ATC to prevent this kind of incidents The common factor for the incidents described above was that the pilots of the aircraft not complying with the clearance were not aware of the other essential traffic. In Vaasa, the pilots could not understand the radio communications between the Finnish Air Force 5

C23/1999 L Hawk and the controller, since they were conducted in Finnish. In Oulu, the airport maintenance vehicle was on a different frequency. In the investigator s opinion, the procedure suggested by the controller in the Oulu incident could have been used to prevent the Vaasa incident as well: the controller could have informed the Reguljair Bandeirante crew of the reason for the delay. It must, however, be emphasised that the current regulations on ATC operations do not require such information to be provided. The above solution, providing information on essential traffic, also has its drawbacks. It increases radio traffic on the frequency and adds to the controller s workload. Moreover, it is only suitable for quiet traffic situations. It is obvious that this kind of justification of clearances would not be possible at times of high traffic density. 6

C 23/1999 L 3 Conclusions 3.1 Findings 1. The pilots and the controller were properly licensed and qualified for their duties. 2. The crew of REF901 forgot their taxi clearance and taxied to the runway without clearance, at the same time when H30 was making a touch-and-go landing for which it had been cleared. 3. The crew of REF901 could not understand the radio communications between the controller and H30, which were in Finnish, and therefore did not realize that H30 was making a touch-and-go landing. 4. Because of darkness and ground fog, the crews of REF901 and H30 could not see each other. 5. H30 made the touch-and-go landing, for which it had been cleared, without knowing that another aircraft had taxied to the runway. 6. The air traffic controller noticed the traffic conflict, but too late to intervene in the situation. 7. H30 passed REF901 after the touch-and-go landing at a height of about 50 meters. 3.2 Probable cause The incident occurred because the crew of REF901 forgot their taxi clearance and taxied to an active runway without clearance. The actual reason why they forgot the clearance could not be determined. Contributing factors were the use of the Finnish language in radio communications besides English, and the prevailing conditions. 7

C 23/1999 L 4 RECOMMENDATIONS No recommendations are issued. Helsinki, 13 March 2001 Pekka Raine 9

Appendices 1. Radio communications on Vaasa TWR frequency 119,300 MHz Reference material The following investigation material is stored at AIB, Finland: 1. Decision of the Accident Investigation Board n:o C 23/1999 L 2. Reports filed by REF901 pilots to the airline company 3. GEN M1-4 report filed by the Hawk instructor 4. GEN M1-4 report filed by the air traffic controller on duty 5. Records of the Hawk instructor s telephone interview 6. Preliminary analysis of the incident by Vaasa airport 7. Correspondence between the investigator and Reguljair Ltd. 8. Correspondence with the Swedish accident investigation authority.

Appendix 1 Radio communications relating to the incident of 15 December 1999 at Vaasa (Translator s note: The conversations written in italics were originally in Finnish, and have been translated into English for the purpose of this report. The word Heikki is a name used in the Finnish phonetic alphabet, corresponding to Hotel in the international one.) H30: Heikki 30, downwind 16. Heikki 30, cleared for touch-and-go, runway 16, wind calm, after touch-and-go leave control zone via Laihia VFR. H30: Cleared for touch-and-go runway 16 and after touch-and-go will leave control zone via Laihia VFR, Heikki 30. H30: Heikki 30, gear pressure. Heikki 30 Reguljair 901, taxi to holding Bravo. REF901: Taxiing to holding Bravo, Reguljair 901. Reguljair 901, clearance is available. REF901: Go ahead, 901. Reguljair 901, cleared Umeå direct flight level 60, squawk 3650. REF901: Cleared to Umeå, flight level 60, squawking 3650, Reguljair 901. REF901: Vaasa. 901 cleared to line-up. Negative. REF901: I will leave runway, 901. Don t need anymore. Reguljair 901, it was to holding Bravo. REF901: Roger, 901. REF901: There was just one military Hawk making touch-and-go. Okay. And 901, you are now cleared line-up runway 34.

REF901: Lining up 34, 901. Vaasa. H30: Heikki 30, do you agree, at 350 meters on QFE 1007. Heikki 30, affirm at 350 meters in Vaasa TMA on QNH 1007. H30: Affirm at 350 meters in Vaasa TMA, Heikki 30. Heikki 30, you probably noticed that Reguljair coming to the runway from Bravo when you were making touch-and-go. H30: Please repeat, Heikki 30. And Heikki 30, did you notice that there was that Reguljair 901 coming to the runway from Bravo when you were making touch-and-go. H30: No, I did not notice. Heikki 30, roger, anyway it almost got to the runway when you were just going around. H30: Roger. Reguljair 901, cleared for takeoff runway 34, lefft turn, wind is calm. REF901: Left turn, cleared for takeoff, Reguljair 901. Vaasa.