Description of the Occurrence

Similar documents
REPORT IN-038/2010 DATA SUMMARY

REPORT A-024/2012 DATA SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

PRELIMINARY OCCURRENCE REPORT

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

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

PRELIMINARY REPORT Accident involving DIAMOND DA40 N39SE

Investigation Report

AIRCRAFT INCIDENT REPORT AND EXECUTIVE SUMMARY

AVIATION INVESTIGATION REPORT A01Q0165 LOSS OF CONTROL AND STALL

REPORT ULM A 005/2018. Accident involving a FLIGHT DESIGN CTSW, registration EC-LXE, in Gurrea de Gállego (Huesca, Spain) on 3 March 2018

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

F I N A L R E P O R T

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

REPORT IN-011/2012 DATA SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

PRELIMINARY ACCIDENT REPORT

FINAL REPORT ON ACCIDENT

BULLETIN Serious incident involving BEECH 33 E33A G-GMCT

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

FINAL REPORT. of civil aviation safety investigation. No. I Date: Artem Avia, Ucraine. Genex Ltd., Belarus

Aircraft Accident Investigation Report

AVIATION INVESTIGATION REPORT A06Q0181 FLIGHT IN WEATHER CONDITIONS UNFAVOURABLE FOR VISUAL FLIGHT AND COLLISION WITH TERRAIN

REPORT IN-017/2011 DATA SUMMARY

AVIONS ROBIN DR400 HB-KFV

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AIRCRAFT ACCIDENT REPORT OCCURRENCE NUMBER 03/249 PIPER TOMAHAWK PA ZK-USA RAUMATI SOUTH 31 JANUARY 2003

AIRCRAFT SERIOUS INCIDENT REPORT

TECHNICAL REPORT IN-018/2005 DATA SUMMARY

AIRCRAFT INCIDENT REPORT AND EXECUTIVE SUMMARY

PARACHUTEACCIDENT REPORT AND EXECUTIVE SUMMARY

AI AIRCRAFT SERIOUS INCIDENT INVESTIGATION REPORT PRIVATELY OWNED J A T

REPORT A-038/2011 DATA SUMMARY

Foreword. This report was originally issued in Spanish. This English translation is provided for information purposes only.

REPORT A-042/2007 DATA SUMMARY

Investigation Report

Investigation Report. Bundesstelle für Flugunfalluntersuchung. Identification. Factual information

AVIATION INVESTIGATION REPORT A02P0290 GEAR-UP LANDING

TECHNICAL REPORT IN-038/2001 DATA SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

DEPARTMENT OF AIR ACCIDENT INVESTIGATION

AIRCRAFT INCIDENT REPORT AND EXECUTIVE SUMMARY

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

Safety Investigation Report Ref. AAIU Issue date: 22 March 2016 Status: Final

AIRCRAFT INCIDENT REPORT

Newcastle Airport. 36 years

Accident to the Piper PA34-200T Seneca III registered HB-LSD on 7 December 2016 at Basel Mulhouse airport (68)

Second Interim statement A-029/2012

AIRPROX REPORT No Date: 17 Apr 2015 Time: 1345Z Position: 5243N 00253W Location: Nesscliff PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

Commercial Pilot Total Flying Hours

F I N A L R E P O R T ON SERIOUS INCIDENT OF THE AIRCRAFT SR-20, REGISTRATION D-ELLT, WHICH OCCURED ON MAY , AT ZADAR AIRPORT

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

FACTUAL REPORT AVIATION

AVIATION OCCURRENCE REPORT A97Q0250 MID-AIR COLLISION BETWEEN CESSNA 172M C-GEYG OF CARGAIR LTD. AND CESSNA 150H C-FNLD MASCOUCHE AIRPORT, QUEBEC

F I N A L R E P O R T

PRELIMINARY REPORT. Serious Incident. Occurrence No: 1860/14

GOVERNMENT OF INDIA INVESTIGATION REPORT

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

REPORT ULM A-006/2013 DATA SUMMARY

AIRCRAFT INCIDENT 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 OCCURRENCE NUMBER 03/1675 RAND KR-2 ZK-CSR 25 KM SOUTH WEST OF WOODBOURNE 8 JUNE 2003

FACTUAL REPORT AVIATION

National Transportation Safety Board Aviation Accident Final Report

Cirrus SR22 registered F-HTAV Date and time 11 May 2013 at about 16 h 20 (1) Operator Place Type of flight Persons on board

Two s Too Many BY MARK LACAGNINA

Microlight Accident and Incident Summary 01/2012

Interim Report. Identification. Factual Information. History of the Flight. Bundesstelle für Flugunfalluntersuchung.

FACTUAL REPORT AVIATION

AIRPROX REPORT No

This space for binding 04/24/1990. Occurrence Date: Accident. Occurrence Type: Off Airport/Airstrip. Model/Series. Air Medical Transport Flight:

GENERAL INFORMATION Aircraft #1 Aircraft #2

ACCIDENT. Aircraft Type and Registration: Piper PA Cherokee, G-BRWO. No & Type of Engines: 1 Lycoming O-320-E3D piston engine

National Transportation Safety Board Aviation Accident Final Report

Airmen s Academic Examination

Date: 12 January Two pilots and two passengers fatally injured. Open wire, forest and crop damages

PRELIMINARY OCCURRENCE REPORT

FINAL KNKT Aircraft Accident Investigation Report

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

Flight Review Written Exam

Informal translation of the BEA (Bureau d Enquêtes et d Analyses) report on the accident involving Cirrus SR22GTS N224AG on 16 November 2008

CAA Safety Investigation Brief. Yakovlev Yak 3M ZK-YYY Collision with ground equipment Warbirds over Wanaka Air show 31 March 2018

FACTUAL REPORT AVIATION

Date: 20 October Manufacturer / Model: The Boeing Company / B Minor damage to aircraft

MINISTRY OF TRANSPORT AND COMMUNICATIONS OF THE REPUBLIC OF LITHUANIA CHIEF INVESTIGATOR OF AIRCRAFT ACCIDENT AND INCIDENT

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

FACTUAL REPORT AVIATION

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

FINAL REPORT ON THE ACCIDENT OCCURRED ON 10 MAY 2008 AT HARVENG ON A AVIAT HUSKY A-1 REGISTERED OO-HUS

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

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

CLASS D CONTROLLED AIRSPACE GUIDE

FACTUAL REPORT AVIATION

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

National Transportation Safety Board Aviation Accident Final Report

Loss of separation west of Helsinki-Vantaa airport on

AVIATION INVESTIGATION REPORT A09O0159 TREE STRIKE DURING CLIMB-OUT

Transcription:

Registration: F-GLKF Year of manufacture: 1992 Category/Weight: 0-2.250 Kgs. Aircraft manufacturer and model: ROBIN DR-400 / 120 Number of engines/ Manufacturer and model: 1 / LYCOMING O-235-LA Date: 03-APR-2002 Local time: 16:25 Province: ALMERÍA Location: KM. 19,800 ROAD A-347 OF ADRA TO LAUJAR DE ANDARAX, T.M. BERJA Injuries Fatal Serious Minor/none Pilot in command: Private Pilot's Licence Flight crew 1 Age: 37 Total flight hours: 125 HOURS Passengers 2 Operation type: GENERAL AVIATION - PRIVATE On ground Phase of flight: ON ROUTE Aircraft damage: MINOR Event type: EMERGENCY LANDING Description of the Occurrence The aircraft was part of a group of six, belonging to the Union Aerienne Lille-Roubaix- Tourcoing Flying Club, that were flying together. They left the French town of Lille on Saturday, 30 th March, reaching Clermont-Ferrand on the first leg. The following day they flew to Le Lignon and, on Monday, 1 st April, from there to the Aerodrome of Ampuriabrava in Spain. On Tuesday, 2 nd April, they left Ampuriabrava for the Aerodrome of Castellón. On 3 rd April, the day of the occurrence, the six aircraft took off from the aerodrome of Castellón at around 12:30 hours, local time, heading for Almería Airport, with flight plans under VFR conditions. The estimated time of the leg was two hours and thirty minutes. The aircraft involved in the incident refuelled at the aerodrome of Castellón to fill its 110-litre tanks, providing it with four hours flight autonomy. Before starting the flight, they obtained information on current and forecast weather conditions, METAR and TAFOR, on the destination airport, as transcribed below, and on the alternatives. METAR LEAM 030900Z 25017KT 9999 SCT025 SCT055 15/12 Q1007 This means: observation made at 09:00 hours UTC on 3 rd April, wind direction 250º and intensity 17 Kt, visibility over 10 Km, scattered clouds at 2,500 feet, scattered clouds at 5,500 feet, temperature 15º C, dew point 12º C and QNH 1007 Hpa. 1

TAFOR LEAM 030800Z031019 26025KT 9999 SCT020 BKN030 TEMPO 1019 26035G45KT This means: TAFOR made at 8:00 hours UTC on 3 rd April, valid between 10:00 and 19:00 hours on 3 rd April, wind direction 260º and intensity 25 Kt, visibility over 10 Km, scattered clouds at 2,000 feet, heavy cloud at 3,000 feet, temporarily between 10:00 and 19:00 hours, wind direction 260º and intensity 35 Kt, with gusts of 45 Kt. According to the Metar data of Almería Airport, between 12:00 and 12:30 hours UTC (between 30 and 60 minutes prior to the arrival of the aircraft at the airport), the wind changed direction by around 90º, i. e., it changes direction from 230º-240º to 330º-340º, whilst increasing its intensity. When the first three aircraft, corresponding to versions with improved features, reached entry point E of the Almería Airport CTR, they established contact with the Airport control tower, which informed that that the duty runway was number 26 and that the wind was blowing at 350º (transversal to the runway), at an intensity of between 25 and 30 Kt, with gusts of 30 to 35 Kt. Despite this, the front three aircraft landed at Almería Airport. Once they had landed, one of the pilots, at the time the Head Pilot of the Flying Club, made radio contact with the three approaching aircraft, recommending that they divert to Malaga or Granada Airport. The three pilots decided to head for Granada. After passing over the town of Órgiva, in the province of Granada, the pilot of aircraft F-GLKF encountered strong turbulence and saw that the way out of the valley was closed off by a thick layer of clouds, making it impossible to continue the flight under VFR conditions. He made several attempts through different places to try to continue towards Granada, without finding any areas free of clouds for VFR flight, forcing him to turn round. Later, and due to his lack of fuel, he chose to descend in order to locate a site where he could land. At 16:25 hours, local time, three hours and fifty-five minutes after having taken off, he located a road with a stretch running at 300º-310º. He flew low overhead to ensure no vehicles were travelling along it and eventually landed. 2

The aircraft suffered damage to its left wing when it hit a tree during the run after landing, none of the three occupants being injured. Analysis The average consumption of this aircraft is around 25 litres/hour. Given that the flight lasted around three hours, fifty-five minutes, it can be estimated that around 98 litres of fuel were consumed. Once the aircraft had landed, the fuel tanks were drained, to find they contained a quantity of approximately 10 litres that, added to the 98 litres consumed, leads to a total of 108 litres. Given that the tank capacity is 110 litres, the previous data shows that the aircraft had taken off with its tanks full. When the aircraft reached entry point E of the Almería Airport CTR, at around 15:00 hours, local time, it found that the existing wind conditions, in terms of its direction, differed to those reflected in the TAFOR that the crew had obtained before taking off. At that time, the wind was blowing 350º perpendicular to the runway, oriented 08-26, and at an intensity of between 25 and 30 knots, with gusts of 30 to 35 knots. Under these conditions, landing the aircraft was completely unfeasible. The pilot, following the recommendations of the Flying Club Head Pilot, decided not to land and to head for another airport. According to his statement, he chose to head for Granada airport because it was closer than Malaga, as well as because the runway is practically parallel to that of Almería. This last piece of information is not entirely correct, given that the Malaga runway is oriented 14-32, whereas that of Almería is 08-26. On the other hand, it is important to note that Valencia had been assigned on the flight plan as the alternative airport. However, the pilot must have had doubts as to the suitability of the alternative airport chosen, as he asked Almería Control Tower for information on the military aerodrome of Armilla, the controller informing him that it was a military installation that only admitted civilian flights in the event of an emergency. However, in this communication the pilot did not request meteorological information on Granada Airport. 3

Regarding the flight to Granada Airport, the pilot indicated in his statement that, bearing in mind the orography of the land, he plotted the most direct route possible from his position (point E) to said airport. Therefore, he is most likely to have flown first along the valley of the river Andarax and then along the valley of the river Guadalfeo. During this distance, he tried on numerous occasions to establish contact with Granada Control Tower, without any success. He then decided to contact the Malaga ATIS to obtain meteorological information on Granada, but was also unable to make contact, possibly due to the flight altitude and to the orography of his current position. He later came across visibility conditions that made it impossible to continue flying towards Granada Airport under VFR conditions. At that time he had no fuel to reach any other airport or aerodrome, which led the pilot to make the decision to turn round and look for a suitable landing site. The decision to land before coming into pressing fuel problems was reasonable, although it is possible that the choice of landing site was not the most appropriate, given that there were obstacles nearby that he crashed into. To summarise, we can highlight the following as the most significant facts of this event: o Although the group of pilots had planned an alternative airport (Valencia) in the event of problems arising during the first part of the route, no alternative had been foreseen in the event of the destination airport not being accessible for landing, as was the case. Therefore, when they came across this situation they had to select an alternative field there and then. In this sense, the Head Pilot of the Flying Club offered two possibilities to the three approaching aircraft: Malaga or Granada. The pilot of the affected aircraft rejected heading for Malaga Airport, based on erroneous information concerning the orientation of its runway. Likewise, he must have had some doubts as to the suitability of Granada Airport, given that he requested information on a third site, Armilla. o The weather conditions at Almería Airport were slightly different to those forecast, with the crew having no prior knowledge of such. 4

o When the pilot came across weather conditions that made it impossible for him to continue flying towards Granada under VFR conditions, he decided to turn round and look for a landing site without waiting for pressing fuel problems, instead of trying to continue with the flight by entering the clouds. Conclusions In view of the above, it can be concluded that this incident was almost certainly caused by an unsuitable flight plan, especially in terms of the choice of alternative airports. 5