AIRES Flight 8250
AIRES Flight 8250
Main page
hub-image

AIRES Flight 8250

logo
Community Hub0 subscribers
Read side by side
AIRES Flight 8250
View on Wikipedia
from Wikipedia

AIRES Flight 8250 was a domestic scheduled passenger flight that on 16 August 2010 crashed on landing at night in poor weather on the Colombian island of San Andrés, killing two of the 131 people on board. The aircraft, an AIRES-operated Boeing 737-700, was arriving from the Colombian capital Bogotá when it heavily touched down short of the runway, breaking up in three sections.

Key Information

The official investigation concluded that the crash was caused by the misjudgment by the crew of the aircraft's altitude during the last phase of the approach.[1]

History of the flight

[edit]

Flight 8250 was operated by the local, privately owned Colombian airline AIRES.[2][3] The aircraft was on a flight from Bogotá to the Colombian island of San Andrés, in the Caribbean.[3] A popular tourist destination, San Andres Island is about 190 kilometres (120 mi; 100 nmi) east of the Nicaraguan coast.[3]

The flight took off from Bogotá's El Dorado International Airport at 00:07 en route to Gustavo Rojas Pinilla International Airport with 125 passengers and six crew. Captain Wilson Gutierrez (43) was the pilot flying (PF) while First Officer Camilo Piñeros Rodriguez (25) was the pilot monitoring (PM).[4]

Accident

[edit]

The crash occurred as the aircraft landed at San Andrés at 1:49 am local Western Caribbean Time (UTC−05:00).[3][5] The Boeing 737 broke up into three main sections.[6] The impact occurred about 260 feet (80 m) before the start of the runway, with wreckage spread about another 328 feet (100 m).[5] The aircraft skidded along the runway; the landing gear collapsed and one engine was ripped off the wing.[7] The aircraft's nose and first eight rows of seating came to rest on the runway pointing in a different direction from the rest of the wreckage.[5] Airport fire crews quickly doused a small fire that had started on a wing.[7] As a result of the accident, the Regional Committee for Disaster Prevention and Attention (Spanish: Comité Regional de Prevención y Atención de Desastres) was mobilized.[8]

Aircraft

[edit]

The aircraft involved was a Boeing 737-73V,[Notes 1] registration HK-4682, with serial number (MSN) 32416, construction number 1270.[9] The aircraft was built in 2003 and was first delivered to EasyJet registered as G-EZJU. It was then sold to AIRES in March 2010.[9] Investigators said the day after the crash that the aircraft's maintenance log was up to date.[7]

Passengers and crew

[edit]
Passenger fatality chart

There were contradictory reports as to how many people were aboard the aircraft.[5] Reports range from 121 passengers and six crew members,[2] 131 passengers and crew,[3] and at least 127 people aboard.[5] The report of 131 people was further broken down as 121 adult passengers and four minors.[5] Reports the day after the accident settled on 131 people aboard: 125 passengers and six crew.[7][10][11][12]

One early report stated that 114 people were injured in the crash, and that of 99 passengers taken to the Amor de Patria Hospital on San Andrés, only four had had major injuries.[3] Reports a day later settled on a figure of 119 people being taken to local hospitals, mostly with minor injuries.[7][12] Thirteen survivors, including four with serious injuries, were flown to Bogotá for treatment.[7]

Initial reports indicated one fatality, an elderly lady dying of a heart attack.[13] The final fatality count was two. Autopsy revealed that a 68-year-old woman had a ruptured aorta and ruptured liver.[6] She died on the way to the hospital.[2][3] The second fatality was a 10-year-old girl;[14] she sustained substantial brain damage[15] and died 16 days after the accident.[16]

One report stated that the passenger list included six Americans, five Mexicans, four Brazilians, four Ecuadorians, and two Germans with the rest being Colombians.[5] Another report stated there were three Americans aboard.[17] A later report put the number of non-Colombians aboard as "at least 16."[11]

Investigation

[edit]

Colombia's civil aviation authority, Special Administrative Unit of Civil Aeronautics, and the Colombian Air Force opened an investigation into the accident.[8] The airport was closed as investigators examined the wreckage.[2] The closure was expected to last until 06:00 on 17 August.[8]

The aircraft reportedly crashed in bad weather while a storm was reported in the area, but not at the airport.[5] The METAR (aviation routine weather observation message) report in force at the time of the accident indicated that the wind was from the east north east at 6 knots (11 km/h; 6.9 mph), visibility was good and that the runway was wet.[Notes 2][6] The aircraft "landed in the middle of an intense electrical storm" according to Colonel Barrero.[2]

Passenger accounts the day after the crash detailed how the approach appeared to have been going normally, with the flight attendants having made the passengers ready for landing, when the crash occurred suddenly and without warning.[7][10][11] The pilot did not report an emergency to the tower.[12] There were conflicting reports over what caused the crash, suggesting that the landing was disrupted after the aircraft was hit by a downdraft, or struck by lightning.[5] The pilot said that the aircraft was struck by lightning. Officials refused to comment on the reports of a lightning strike,[3][5][8] although subsequent research proved that[specify] was not true. No aircraft has had an accident caused by lightning since 1971. The airport was not fitted with equipment to detect wind shear, such as a Doppler radar.[7]

Both the flight data and cockpit voice recorders were recovered from the wreckage.[7] Based on the pattern of wreckage, investigators concluded that the aircraft had broken up on impact and not while in the air.[7]

The U.S. National Transportation Safety Board sent a team to support the Colombian-led investigation as representatives of the manufacturer's state.[18]

Almost one year after the accident, on 15 July 2011, the Security Council of Aeronáutica Civil concluded that the cause of the accident was the execution of the final approach below the glide path, due to an error of judgment by the crew who believed they were much higher. This is typical of a "black hole" illusion, which is experienced during a night approach to a low contrast runway environment surrounded by bright lights, aggravated by heavy rain.[1] Aeronaútica Civil recommended retraining of the crew. Although the accident was caused by human error, Aeronaútica representative Colonel Carlos Silva reminded that the purpose of the investigation was not to apportion blame but to prevent aircraft accidents that may occur in the future.[19]

[edit]

The accident is featured in the fifth episode of Season 20 of Mayday, also known as Air Crash Investigation. The episode is titled "Runway Breakup."[20]

Notes

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

AIRES Flight 8250

View on Grokipedia
from Grokipedia
AIRES Flight 8250 was a scheduled domestic passenger flight operated by the Colombian airline AIRES, departing from Bogotá's El Dorado International Airport bound for Gustavo Rojas Pinilla International Airport on San Andrés Island, that crashed on 16 August 2010 at 01:47 local time while attempting to land in heavy rain and poor visibility conditions.[1] The aircraft, a Boeing 737-700 registered as HK-4682, impacted the ground approximately 49 meters short of runway 06 threshold, breaking into three pieces upon touchdown and coming to rest with the forward fuselage on the runway.[2] The flight carried 125 passengers and 6 crew members, totaling 131 occupants; two passengers were fatally injured—one from impact trauma and the other from complications days later—while 33 others sustained injuries ranging from minor to serious, with four requiring surgery.[2] The accident occurred amid a thunderstorm, following a four-hour departure delay due to adverse weather en route, and the crew reported challenges with turbulence and visibility during the approach.[1] The investigation, led by Colombia's Aeronautical Civil Authority (Aerocivil) under report COL-10-18-GIA, concluded that the probable cause was the flight crew's erroneous perception of the aircraft's altitude, leading to a low approach path, primarily due to a black hole illusion—a visual misjudgment common in night operations over dark terrain with limited ground references and heavy precipitation reducing contrast.[1] Contributing factors included the absence of precision approach aids at the airport, inadequate runway lighting, and the crew's decision to continue the visual approach despite deteriorating conditions, though a reported lightning strike was not determined to be causal.[2] The incident highlighted vulnerabilities in low-visibility landings at regional airports and prompted recommendations for enhanced pilot training on optical illusions and infrastructure improvements at San Andrés.[1]

Background

AIRES Línea Aérea

AIRES Línea Aérea was established on October 2, 1980, and commenced operations on February 23, 1981, as a regional carrier headquartered in Bogotá, Colombia, initially focusing on domestic short-haul routes using turboprop aircraft such as the Embraer EMB-110 Bandeirante and Fokker F27 Friendship.[3] Over the subsequent decades, the airline grew by modernizing its operations and expanding its route network, transitioning from a monopoly-like position in regional services in the early 1990s to competing in a liberalized market; by 2010, it served a substantial share of Colombia's domestic market and had begun introducing international flights to destinations in Central and South America, including plans for routes to Brazil, Canada, Mexico, Paraguay, and Peru.[4][5] Later in 2010, AIRES was acquired by LAN Airlines, and it began operating as LAN Colombia in December 2011. In 2010, AIRES operated a fleet of 18 aircraft tailored for short-haul efficiency, comprising eight Boeing 737-700 jetliners for higher-capacity domestic and emerging international segments, alongside eleven de Havilland Canada DHC-8-200 turboprops for regional connectivity across Colombia's diverse terrain.[6] This composition reflected the airline's strategy to balance speed and accessibility in serving underserved areas, with the Boeing 737-700 marking AIRES as the first Colombian operator of this type for domestic flights.[6] Prior to 2010, AIRES maintained an exemplary safety record, with no fatal accidents or major hull-loss incidents reported in its operations.[7] Minor occurrences, such as runway excursions or technical delays, were infrequent and resolved without injuries, underscoring the airline's adherence to international standards amid Colombia's evolving aviation oversight.[7] The late 2000s marked a period of recovery and expansion for Colombian aviation, following economic turbulence in the late 1990s and early 2000s that included high unemployment and political instability, which had temporarily constrained growth.[8] Deregulation policies initiated in the early 1990s continued to drive competition by easing entry barriers for new carriers and modernizing infrastructure, while the 2000 U.S.-Colombia open skies agreement liberalized bilateral routes, boosting international traffic and supporting airlines like AIRES in their network development.[9][10] This regulatory environment, overseen by the Civil Aviation Authority (Aerocivil), emphasized safety enhancements and economic integration, positioning Colombia as a regional aviation hub despite lingering challenges like fuel costs and security concerns.[11]

Flight details

AIRES Flight 8250 was a domestic scheduled passenger flight operated by AIRES Línea Aérea from El Dorado International Airport (BOG) in Bogotá, Colombia, to Gustavo Rojas Pinilla International Airport (ADZ) on San Andrés Island. The flight departed at 00:07 local time on August 16, 2010, as part of the airline's regular night operations on this route.[1] The planned flight duration was approximately 1 hour 35 minutes, covering the roughly 1,200-kilometer distance over the Caribbean Sea. This route was a key domestic connection for AIRES, with multiple daily flights typically scheduled to serve tourist and business travel between the mainland and the island, including evening and overnight services to maximize capacity.[1][12] The aircraft carried 125 passengers and 6 crew members, achieving a load factor of about 88% based on the Boeing 737-700's standard seating for 149 occupants. Pre-flight weather forecasts for the destination indicated calm winds initially but anticipated deteriorating conditions, including thunderstorms and reduced visibility due to heavy rain.[1][2]

Aircraft

Design and specifications

The Boeing 737-73V is a variant of the 737-700 Next Generation narrow-body airliner, designed as a twin-engine jet for efficient short- to medium-haul operations. It accommodates up to 149 passengers in a high-density single-class layout, with a typical two-class configuration seating 126. The aircraft is powered by two CFM International CFM56-7B20 high-bypass turbofan engines, providing thrust ratings between 20,000 and 27,300 lbf each, depending on the specific subvariant, enabling reliable performance on routes like intra-Colombian flights.[13][14][1] Key dimensions include a length of 33.6 meters (110 ft 4 in), a wingspan of 35.8 meters (117 ft 5 in), and a height of 12.5 meters (41 ft 3 in). The maximum takeoff weight is 70,080 kg (154,500 lb), with an operating empty weight around 41,318 kg (91,135 lb) and a maximum fuel capacity of 20,392 liters (5,390 US gallons). Performance specifications suit short-haul missions, offering a range of approximately 3,060 nautical miles (5,665 km) at Mach 0.78 cruise speed and a service ceiling of 41,000 feet, while maintaining low operating costs through improved aerodynamics and winglets installed on later models like the involved aircraft.[13][15] For landing operations, the 737-700 incorporates advanced avionics systems, including dual Rockwell Collins autopilots integrated with the flight management computer for precise approach guidance, supporting Category III instrument landings in low-visibility conditions. The nose-mounted weather radar, a Rockwell Collins WXR-700X unit, detects precipitation and turbulence up to 320 nautical miles ahead, aiding pilots in navigating adverse weather. Altitude measurement relies on redundant systems: a barometric altimeter for pressure-based readings and a radio altimeter that uses radar signals to measure height above terrain, providing critical data below 2,500 feet during final approach.[13][16][17] The 737-700 received FAA type certification on November 7, 1997, following extensive testing that validated its enhanced efficiency over earlier 737 models. Up to 2010, the series had accumulated over 100 million flight hours with an exemplary safety record, underscoring its reliability in global operations.[18][19]

Operational history

The Boeing 737-700 involved in the accident, registered as HK-4682, was constructed in 2003 with its first flight occurring on January 10 of that year.[20] It was initially delivered to EasyJet on February 21, 2003, under the registration G-EZJU, where it served primarily on European short-haul routes until being withdrawn from use and stored in January 2010.[14] The aircraft was then acquired by AIRES Línea Aérea and reregistered as HK-4682, entering service with the airline on March 7, 2010, following a ferry flight from Europe to Colombia.[20] By the time of the August 16, 2010, accident, HK-4682 had accumulated approximately 23,485 total flight hours.[21] During its brief tenure with AIRES, spanning about five months, the aircraft was utilized almost exclusively on domestic passenger flights within Colombia, including routes such as Bogotá to San Andrés.[14] Maintenance records for HK-4682 were reported as valid and up to date in the immediate aftermath of the accident, with no outstanding defects noted prior to the flight.[22] The aircraft had undergone a recent major inspection shortly before the incident, confirming compliance with all required airworthiness standards.[23]

Crew and passengers

Flight crew

The flight crew of AIRES Flight 8250 consisted of a captain and a first officer, both Colombian nationals employed by AIRES Línea Aérea. The captain, Wilson Rafael Gutiérrez, aged 43 at the time of the accident, served as the pilot flying and held an Airline Transport Pilot License; he accumulated 7,643 total flight hours, including 343 hours on the Boeing 737 aircraft type, with prior experience at AIRES dating back to 2004.[2][24] The first officer, Camilo José Piñeros Rodríguez, aged 25 at the time of the accident, acted as the pilot monitoring and possessed a Commercial Pilot License; he had logged 1,900 total flight hours, of which 800 were on the Boeing 737, having been hired by AIRES earlier in 2010.[2][24]

Cabin crew and passengers

AIRES Flight 8250 was serviced by four cabin crew members, who were responsible for passenger safety and comfort during the flight. The flight carried 125 passengers, consisting of 121 adults and 4 minors, with the majority being Colombian nationals traveling as tourists to the island of San Andrés.[25][26] Five American citizens were also among the passengers.[26] The Boeing 737-700 was configured with 12 first-class seats and 117 economy seats, accommodating the 125 passengers on board.

Accident

Departure and en route

AIRES Flight 8250 departed from Bogotá-El Dorado International Airport (BOG) at 00:07 local time on August 16, 2010, following a four-hour delay from its scheduled departure. The Boeing 737-700, registration HK-4682, conducted a normal takeoff and climbed without incident to its assigned cruising altitude of Flight Level 360 (FL360), approximately 36,000 feet.[27][2] During the en route phase, the flight proceeded along standard airways toward San Andrés Island, maintaining FL360 with no deviations from the planned route or reported issues in navigation or air traffic communications. The approximately 1-hour-18-minute cruise was uneventful, with the aircraft systems functioning normally.[27][2] Mid-flight, the crew obtained an updated weather briefing for the destination, which reported calm winds and visibility exceeding 10 kilometers, but noted that poor weather, including potential heavy rain and gusty winds, was expected at arrival. At 01:25 local time, after contacting San Andrés approach control, the flight was cleared to descend from FL360 to FL240, initiating the descent phase with all systems nominal.[27][2]

Approach and crash sequence

The aircraft began its descent toward Gustavo Rojas Pinilla International Airport in San Andrés at approximately 01:40 local time, amid deteriorating weather conditions including heavy rain and winds of around 10 knots. Visibility had reduced to 4,000 meters due to the precipitation.[2] Cleared for a VOR approach to runway 06, the crew extended the landing gear at 01:40 and progressively set the flaps to 15 degrees by 01:42 and 30 degrees by 01:44. The crew reported "gear down and full flaps" to air traffic control during this configuration. The aircraft remained 50 to 300 feet below the 3-degree glideslope as indicated by the precision approach path indicator lights.[2] As the aircraft continued its final approach, the first officer called for a go-around, but 0.5 seconds later, it impacted an upward-sloping terrain area 49 meters short of the runway 06 threshold at a vertical speed greater than 1,100 feet per minute. The impact occurred at 01:47 local time. Cockpit voice recorder data captured heavy rain sounds 12 seconds prior, followed by a ground proximity warning system alert of "50" and "40" four seconds before impact, with the first officer exclaiming "Ayyy, cap..." and beginning to say "captain, could..." two seconds prior; no thrust increase was applied beyond a brief engine adjustment 15 seconds earlier.[2] Upon striking the ground, the Boeing 737-700 broke into three main sections, with the main landing gear and both engines separating from the fuselage. The forward fuselage section came to rest on the runway after sliding along it, while the tail section remained short of the threshold.[2]

Casualties and response

Fatalities and injuries

The crash of AIRES Flight 8250 resulted in two fatalities, both among the passengers. The first was a 72-year-old woman who died from impact trauma sustained during the initial collision with terrain short of the runway, suffering ruptures to vital organs such as the aorta and liver, during transport to the hospital. The second passenger, an 11-year-old girl, succumbed to post-crash injuries including severe traumatic brain injury and multiple organ failure on September 1, 2010, 16 days later while receiving treatment in a Bogotá hospital.[2] In total, 33 people sustained injuries ranging from minor to serious, with four requiring surgery. These injuries were predominantly caused by the intense deceleration forces from the aircraft's sudden impact and breakup, as well as from flying debris and the ensuing slide across the runway surface. No crew members were fatally injured, though several passengers required surgical intervention for head trauma and fractures.[2][21] Of the 129 survivors, which included all 6 crew members and 123 passengers (among them 4 minors), the cabin crew assisted in the rapid evacuation from the fractured fuselage. Initial medical triage at the scene, conducted by responding emergency personnel, classified injuries into serious (requiring immediate hospitalization and potential surgery) and minor (treatable on-site or with observation) categories to prioritize care for those with life-threatening conditions. Approximately 119 survivors were evaluated at local hospitals, though many had no or minor injuries.[21][2]

Rescue operations

Following the crash of AIRES Flight 8250 at approximately 1:47 a.m. local time on August 16, 2010, the airport's fire crews from Gustavo Rojas Pinilla International Airport responded immediately to the site, where the Boeing 737-700 had broken into three sections upon impacting terrain short of the runway. Ruptured fuel tanks ignited a fire, which the fire crews contained to prevent further escalation, while also supporting the extraction of occupants from the wreckage. The Colombian Air Force, local police, and emergency medical teams coordinated the initial response, assisting in securing the area and aiding survivors amid the ongoing thunderstorm.[28][2][29] Survivors primarily self-evacuated through emergency doors and evacuation slides, with some passengers helping others despite sustaining injuries such as fractures and lacerations. Local police and military personnel from the Colombian Air Force provided on-site assistance, helping to guide evacuees away from the hazardous wreckage and potential fuel ignition risks. The effort was bolstered by a combination of official responders and community members, who used available vehicles to facilitate movement from the crash site.[29][28][30] Medical transport was rapidly organized, with ambulances from San Andrés conveying the injured to local facilities including Hospital Amor de Patria and Clínica Villareal for initial treatment; in cases of limited capacity, taxis and police vans supplemented the ambulances to transport patients. Serious cases, totaling around 13 to 17 individuals requiring advanced care (including the four who needed surgery), were airlifted via two dedicated ambulance aircraft operated by the Colombian Air Force to Bogotá on the mainland, where they received further evaluation and surgery from specialized teams.[28][31][30][32] The operations faced significant challenges from the prevailing poor weather, characterized by heavy rain, low visibility, and thunderstorms that had persisted since the flight's approach, delaying the mobilization of additional external resources from the mainland. The nighttime conditions further complicated the search and evacuation, as darkness and adverse weather reduced operational efficiency at the remote island location, though local responders mitigated risks effectively to ensure the survival of 129 out of 131 on board.[29][2]

Investigation

Inquiry process

The investigation into the crash of AIRES Flight 8250 was led by Colombia's Unidad Administrativa Especial de Aeronáutica Civil (Aerocivil), the national civil aviation authority responsible for probing domestic accidents.[1] A team of investigators from the United States National Transportation Safety Board (NTSB) was dispatched shortly after the incident to assist the Colombian authorities in accordance with international aviation protocols under ICAO Annex 13.[33] Boeing, the manufacturer of the Boeing 737-700 involved, provided technical expertise on aircraft systems and wreckage examination as part of the collaborative effort.[34] Wreckage recovery operations commenced on August 17, 2010, the day following the accident, with the aircraft debris secured and transported to a hangar for detailed analysis overnight into August 18.[2] Both the flight data recorder (FDR) and cockpit voice recorder (CVR) were recovered intact from the crash site within hours of the event, allowing for the extraction of critical flight parameters and audio data essential to the probe.[2] The scope of the inquiry focused on key areas including meteorological conditions at the time of the approach, the aircraft's maintenance history and technical condition, and human factors influencing crew performance, conducted strictly as a safety-oriented technical investigation without any criminal proceedings.[2] Aerocivil's Grupo de Investigación de Accidentes Aéreos (GIA) coordinated the multifaceted review, incorporating inputs from international partners to ensure a comprehensive procedural framework.[1] The final report, designated as COL-10-18-GIA, was issued by Aerocivil on July 15, 2011, marking the conclusion of the 11-month process.[2]

Findings and cause

The investigation by Colombia's Unidad Administrativa Especial de Aeronáutica Civil (Aerocivil) concluded that the probable cause of the accident was the crew's execution of the final approach below the proper glide path angle, resulting from a misjudgment of the aircraft's altitude, which led to a controlled flight into terrain short of the runway threshold.[2] This error was attributed to the pilots experiencing a "black hole" illusion, a visual misperception common during night approaches in low-contrast environments with scattered bright lights and heavy rain, causing them to perceive the aircraft as higher than it actually was.[21] The black hole illusion led the crew to descend below the intended glide path as they believed the aircraft was higher than its actual position.[2] Contributing factors included the crew's inadequate use of available resources, such as the radio altimeter and cross-checks between pilots, as well as the captain's prior experience primarily on turboprop aircraft, which influenced an inappropriate landing technique for the jet, including a tendency to flare too early.[2] Weather conditions played a role, with poor visibility due to heavy rain and thunderstorms; a moderate increase in headwinds approximately 30 seconds before impact further complicated the approach, though no wind shear was determined to be causal.[2] The airport's lack of precision approach aids, such as an instrument landing system (ILS), limited the options for safer navigation in low-visibility conditions, forcing reliance on visual cues that were compromised by the environmental factors.[2] No mechanical failures were identified as contributing to the accident; the Boeing 737-700 underwent a pre-flight inspection and was found to be in full operational condition, with all systems, including engines, flight controls, and landing gear (except for impact damage), functioning normally.[2] The primary responsibility was assigned to pilot error, with no evidence of structural or technical deficiencies in the aircraft.[21] In response to the findings, the report recommended enhanced pilot training on recognizing and mitigating visual illusions like the black hole effect, as well as improved procedures for non-precision approaches at airports lacking advanced navigation aids.[1] These measures aimed to address the human factors that predominated in the incident.[2]

Aftermath

Safety improvements

The investigation report (COL-10-18-GIA) included recommendations for enhanced pilot training on optical illusions such as the black hole effect during night approaches in poor visibility, as well as improvements to airport infrastructure, including better runway lighting and installation of precision approach aids at facilities like Gustavo Rojas Pinilla International Airport.[1] The accident contributed to heightened safety scrutiny of AIRES, culminating in its acquisition by LAN Airlines in late 2010 for approximately $32.5 million, with the carrier rebranded as LAN Colombia in 2011 and integrated into the LATAM Airlines Group following the 2016 merger of LAN and TAM.[35][36]

Cultural depictions

The crash of AIRES Flight 8250 has been depicted in the television documentary series Air Crash Investigation (also known as Mayday or Air Disasters), specifically in the episode titled "Runway Breakup," which first aired on March 12, 2020.[37] This episode reconstructs the sequence of events during the flight's approach to San Andrés Island amid severe weather, highlighting the role of visual illusions and pilot decision-making, and has served as an educational tool for illustrating the hazards of night landings in thunderstorms.[38] The incident has also inspired numerous online animations and recreations, often drawing from the Air Crash Investigation footage to simulate the crash dynamics for aviation enthusiasts and trainees. These depictions emphasize the educational value of the accident in demonstrating spatial disorientation risks, contributing to broader discussions in post-2010 aviation safety literature on perceptual errors during instrument approaches.[39] The event's portrayal in media has influenced the development of training simulations that replicate thunderstorm conditions and runway illusions to better prepare pilots for similar scenarios.

References

  1. https://aviation-safety.net/database/record.php?id=20100816-0
  2. Aires B737 at San Andres Island on Aug 16th 2010, landed short of ...
  3. Aires Fleet Details and History - Planespotters.net
  4. Aires Colombia - AirlineDecals.com
  5. Aires looks to launch several new international routes - FlightGlobal
  6. Aires: Featured Airline | Aviation Week Network
  7. ASN Aviation Safety Database
  8. [PDF] Impact of US Low Cost Carriers Entrance to the Airline Market in ...
  9. Impact of airport policies on regional development. Evidence from ...
  10. 3/16/00: U.S. and Colombia Expand Aviation Ties - State Department
  11. [PDF] Evolution of the airport and air transport industry in Colombia and its ...
  12. Flights from Bogotá to San Andrés: BOG to ADZ ...
  13. https://www.boeing.com/commercial/737ng/
  14. HK-4682 Aires Boeing 737-73V(WL) - Planespotters.net
  15. BOEING 737-700 | SKYbrary Aviation Safety
  16. https://pilotjohn.com/a/boeing/737-700
  17. CFM56-7-Powered 737-700 Receives FAA Certification
  18. Boeing 737-7H4 (WL) - Aviation Safety Network
  19. Boeing 737 NG / Max - MSN 32416 HK-4682 - Airfleets
  20. Accident Boeing 737-73V (WL) HK-4682, Monday 16 August 2010
  21. Authorities partially re-open San Andres runway | News | Flight Global
  22. Boeing – Page 2 - Flightstory.net – Aviation Blog
  23. [PDF] Aires-Airlines-Colombian-Crash-8250.pdf
  24. Colombian Plane Crash: 'Miracle' Accident? - ABC News
  25. Accident Boeing 737-73V (WL) HK-4682, Monday 16 August 2010
  26. [PDF] INFORME FINAL DE ACCIDENTE - Aviation Safety Network
  27. Colombian 'Miracle' Plane Crash: Inside the Story of Survival
  28. Salvados, de milagro, 130 ocupantes de avión de Aires - El Tiempo
  29. Evacúan a primeros heridos de accidente de avión en San Andrés
  30. Fuerza Aérea transportó heridos del accidente aéreo hacia Bogotá
  31. NTSB Team Assisting Investigation of Aires Boeing 737 Crash on ...
  32. [PDF] A-12-1 through -6 - National Transportation Safety Board
  33. Aires airline plane crash caused by human error - Colombia News
  34. NTSB team dispatched to San Andres in Aires crash investigation
  35. LAN to acquire Colombia's Aires | News | Flight Global
  36. Lan Agrees to Buy Colombia's Aires for ... - Bloomberg.com
  37. "Air Crash Investigation" Runway Breakup (TV Episode 2020) - IMDb
  38. Air Crash Investigation - National Geographic
  39. AIRES Flight 8250 - Crash Animation - YouTube
User Avatar
No comments yet.