ASN Aircraft accident ATR 42-300 YV1449 Mérida-A Carnevalli Airport (MRD)
ASN logo
 

Status:Accident investigation report completed and information captured
Date:Thursday 21 February 2008
Time:17:05
Type:Silhouette image of generic AT43 model; specific model in this crash may look slightly different
ATR 42-300
Operator:Santa Bárbara Airlines
Registration: YV1449
MSN: 028
First flight: 1986
Total airframe hrs:37138
Engines: 2 Pratt & Whitney Canada PW120
Crew:Fatalities: 3 / Occupants: 3
Passengers:Fatalities: 43 / Occupants: 43
Total:Fatalities: 46 / Occupants: 46
Aircraft damage: Destroyed
Aircraft fate: Written off (damaged beyond repair)
Location:ca 10 km NW of Mérida-A Carnevalli Airport (MRD) (   Venezuela)
Crash site elevation: 3810 m (12500 feet) amsl
Phase: En route (ENR)
Nature:Domestic Scheduled Passenger
Departure airport:Mérida-A Carnevalli Airport (MRD/SVMD), Venezuela
Destination airport:Caracas-Simón Bolívar International Airport (CCS/SVMI), Venezuela
Flightnumber: 518
Narrative:
An ATR-42-300 operating Santa Bárbara Airlines Flight 518 was destroyed when it impacted the side of a mountain shortly after takeoff from Mérida-A Carnevalli Airport in Venezuela. All 46 on board were killed.
Mérida Airport is located in a mountain valley at an elevation of 5010 feet. Terrain in the valley rises from 1000 to 19.500 feet. Arrivals and departures have to use the Rio Chama corridor to the west of the airport. Runway 07 is used for landings and takeoffs have to be performed in the opposite direction, from runway 25.
Santa Bárbara Airlines however used an unpublished approach and departure procedure which let the aircraft use a valley to the northeast of the airport. This procedure saved about 15 minutes of flying time on the route to Caracas.
After all passengers had boarded for flight 518 to Caracas, it took about 30 minutes for the pilots to arrive at the aircraft. Being late, they immediately started the engines while simultaneously asking for permission to do so.
Because an Avior Airlines flight was approaching the airport, the crew were told to expedite their departure or wait for the arrival of the Avior aircraft. The flight crew decided to go and began taxiing 2 minutes and 40 seconds after startup. Consequently the AHRS (attitude and heading reference) system of the airplane was unusable. The aircraft needed to remain still for 3 minutes after the battery is turned on so that all gyroscopes, accelerometers and magnetometers can be stabilized and synchronized.
The AHRS provides attitude information for aircraft, including roll, pitch and yaw. The captain possibly expected to re-initialize the system while they were at cruising altitude.
After departure from runway 25 the crew planned to use the unpublished procedure. Climbing through clouds a 180-degree turn was initiated. Using the unreliable magnetic compass, the flight made a 270 degree turn, heading towards rising terrain. The captain took over control from the copilot. When visual contact with terrain was regained, the crew noted they were heading for mountains. The captain tried to avoid rising terrain but the aircraft impacted the side of a mountain at 3810 m.

Probable Cause:

CONCLUSIONS
The attitude and heading reference system (AHRS) as a device was operational, however the initialization of the system was incomplete, so the standard mode was in a fault condition. This failure mode left the RMI or radio magnetic indicators and the autopilot inoperative.
The EGPWS or enhanced ground proximity warning system was inoperative in the "enhanced" functions, since the information is displayed on the EFIS system screens, therefore there was no early warning (Visual) of impact against the mountain range.
The GPS was the only instrument capable of providing heading information to within one degree of accuracy. Because it is located on the co-pilot's lower left panel, the information provided by the co-pilot was basically available for co-pilot observation. In addition, the size of the display is relatively small for the information it shows.
The crew was valid, qualified and certified by the National Institute of Civil Aeronautics (INAC). However, the crew was very unconcerned to learn that they were taking off with the AHRS system inoperative and the weather conditions were instrument or IMC.
The meteorological station in Merida was inoperative.
The control tower did not have an operational communications recording system.
According to the deformation shown on the low pressure compressor wheels, the engines had power at the time of impact.

Accident investigation:

cover
Investigating agency: JIAAC Venezuela
Status: Investigation completed
Accident number: 11-013/2008
Download report: Final report

Classification:

Controlled Flight Into Terrain (CFIT) - Mountain

Sources:
» LAGAD Aviation
» NotiSAR
» Instituto Nacional de Aeronáutica Civil (INAC)

METAR Weather report:
21:00 UTC / 17:00 local time:
SVMD 212100Z 29008KT 9999 SCT013 BKN100 XX/XX Q1018=

22:00 UTC / 18:00 local time:
SVMD 212200Z 25005KT 9999 BKN013 OVC100 20/12 Q1021=


Photos

photo of ATR-42-300-YV1449
3D terrain view and point of impact near Mérida Airport
photo of ATR-42-300-YV1449
accident date: 21-02-2008
type: ATR 42-300
registration: YV1449
 

Map
This map shows the airport of departure and the intended destination of the flight. The line between the airports does not display the exact flight path.
Distance from Mérida-A Carnevalli Airport to Caracas-Simón Bolívar International Airport as the crow flies is 507 km (317 miles).
Accident location: Exact; as reported in the official accident report.

This information is not presented as the Flight Safety Foundation or the Aviation Safety Network’s opinion as to the cause of the accident. It is preliminary and is based on the facts as they are known at this time.
languages: languages

Share

ATR 42

  • 457+ built
  • 19th loss
  • 7th fatal accident
  • The worst accident (at the time)
  • 3rd worst accident (currently)
» safety profile

 Venezuela
  • 8th worst accident
» safety profile

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org