全球空难事件数据简介
飞机作为20世纪以来最伟大的发明之一，极大的便利了人们的交通出行，拉近了世界各地的距离，但也因为其空中飞行的特点给人们带来更多未知性。随着科技的进步和航空业的发展，航空安全也在不断进步，通过采用先进的技术设备、制定严格的规章制度、加强人员培训和安全文化建设等措施，航空安全水平得到了显著提升。然而，航空安全仍面临诸多挑战，如人为因素、技术故障、恐怖活动等，需要各方共同努力，持续改进和创新，以保障航空运输的安全和可持续发展。
从统计数据来看，人类历史上飞机失事的第一个高峰是在二战时期，在上世纪40年代，飞机作为重要飞行工具被大量应用到二战中，1944年和1945年事故量分别达到1505起和1444起，平均每天都有4架飞机发生事故，之后随着战争结束事故量逐渐降低。进入21世纪以来，随着航空安全技术的发展，事故量明显下降。2024年全球共发生了190起飞行事故（截至12月29日），是近三年内事故量最少的一年。
该网站全球空难事件数据整理了自1902年以来的客机、气球、滑翔机、旋翼机、直升机、超轻型飞机、无人机事故等详细信息，分为3张表：全球客机事故数据、全球航空器事故数据、全球无人机事故数据，包含时间、机型、所有者/经营者、飞机号、死亡人数、飞机损坏情况、事件类型、地理位置、出事阶段、飞机用途、始发/到达机场、飞行次数、事件说明、调查报告、调查进度等字段。
时间区间
全球客机事故数据：1919-2024
全球航空器事故数据：1906-2024
全球无人机事故数据：1936-2024
数据规模
字段展示
| 全球客机事故数据-英文字段 | 全球客机事故数据-中文字段 | 全球航空器事故数据-英文字段 | 全球航空器事故数据-中文字段 | 全球无人机事故数据-英文字段 | 全球无人机事故数据-中文字段 |
|---|---|---|---|---|---|
| Year | 年份 | Year | 年份 | Sort | 无人机类型 |
| Date | 日期 | Date | 日期 | Year | 年份 |
| Time | 时间 | Time | 时间 | Date | 日期 |
| Type | 机型 | Type | 机型 | Time | 时间 |
| Owner/operator | 所有者/经营者 | Owner/operator | 所有者/经营者 | Type | 机型 |
| Registration | 飞机号 | Registration | 飞机号 | Owner/operator | 所有者/经营者 |
| MSN | MSN | MSN | MSN | Registration | 飞机号 |
| Year of manufacture | 制造年份 | Year of manufacture | 制造年份 | MSN | MSN |
| Engine model | 发动机型号 | Engine model | 发动机型号 | Year of manufacture | 制造年份 |
| Fatalities | 死亡人数 | Fatalities | 死亡人数 | Engine model | 发动机型号 |
| Other fatalities | 其他死亡人数 | Other fatalities | 其他死亡人数 | Fatalities | 死亡人数 |
| Aircraft damage | 飞机损坏情况 | Aircraft damage | 飞机损坏情况 | Other fatalities | 其他死亡人数 |
| Category | 事件类型 | Category | 事件类型 | Aircraft damage | 飞机损坏情况 |
| Location | 地理位置 | Location | 地理位置 | Category | 事件类型 |
| Phase | 出事阶段 | Phase | 出事阶段 | Location | 地理位置 |
| Nature | 飞机用途 | Nature | 飞机用途 | Phase | 出事阶段 |
| Departure airport | 始发机场 | Departure airport | 始发机场 | Nature | 飞机用途 |
| Destination airport | 到达机场 | Destination airport | 到达机场 | Departure airport | 始发机场 |
| Confidence Rating | 信用评级 | Confidence Rating | 信用评级 | Destination airport | 到达机场 |
| narrative | 事件说明 | narrative | 事件说明 | Confidence Rating | 信用评级 |
| notes | 备注 | notes | 备注 | narrative | 事件说明 |
| Cycles | 飞行次数 | Cycles | 飞行次数 | notes | 备注 |
| Total airframe hrs | 总飞行时长 | Total airframe hrs | 总飞行时长 | Total airframe hrs | 总飞行时长 |
| Report number | 报告编号 | Report number | 报告编号 | Report number | 报告编号 |
| Investigating agency | 调查机构 | Investigating agency | 调查机构 | Investigating agency | 调查机构 |
| Download report | 下载报告 | Download report | 下载报告 | Download report | 下载报告 |
| Accident investigation PDF | 调查报告 | Accident investigation PDF | 调查报告 | Accident investigation PDF | 调查报告 |
| Status | 调查进度 | Status | 调查进度 | Status | 调查进度 |
| Duration | 调查时长 | Duration | 调查时长 | Duration | 调查时长 |
样本数据
全球客机事故数据
| Year | Date | Time | Type | Owner/operator | Registration | MSN | Year of manufacture | Engine model | Fatalities | Other fatalities | Aircraft damage | Category | Location | Phase | Nature | Departure airport | Destination airport | Confidence Rating | narrative | notes | Cycles | Total airframe hrs | Report number | Investigating agency | Download report | Accident investigation PDF | Status | Duration |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 年份 | 日期 | 时间 | 机型 | 所有者/经营者 | 飞机号 | MSN | 制造年份 | 发动机型号 | 死亡人数 | 其他死亡人数 | 飞机损坏情况 | 事件类型 | 地理位置 | 出事阶段 | 飞机用途 | 始发机场 | 到达机场 | 信用评级 | 事件说明 | 备注 | 飞行次数 | 总飞行时长 | 报告编号 | 调查机构 | 下载报告 | 调查报告 | 调查进度 | 调查时长 |
| 2019 | Thursday 7 March 2019 | 19:30 | Learjet 35A | Baires Fly | LV-BNR | 35-373 | 1981 | Fatalities: 0 / Occupants: 4 | 0 | Substantial, written off | Accident | Buenos Aires-Jorge Newbery Airport, BA (AEP) - Argentina | Landing | Passenger - Non-Scheduled/charter/Air Taxi | Rosario-Islas Malvinas International Airport, SF (ROS/SAAR) | Buenos Aires-Jorge Newbery Airport, BA (AEP/SABE) | Accident investigation report completed and information captured | Upon landing on runway 13 at Buenos Aires-Jorge Newbery Airport in severe weather conditions (wind gusts at 23 Kt, heavy rain and thunderstorms) at touchdown, the aircraft veered off to the left, running into the grass and stopping 400 m from the runway threshold, close of the terminal building. Conclusions regarding factors related to the accident - At the time of the event, weather conditions were severe thunderstorms with rain and gusty winds. - Visual references could be reduced due to the heavy rains. - The aircraft was displaced from the runway axis at the time of contact with the terrain. - The aircraft made contact with the left landing gear off the runway due to strong wind gusts. - The lateral runway excursion over the green cloth occurred due to the impossibility of recovering the aircraft's trajectory, once it was displaced by the action of the wind. | JIAAC | Final report | f88c8d2d43465de160725d4bb89a9a13 | Investigation completed | 1 year and 4 months | |||||
| 2019 | Friday 3 May 2019 | 21:42 | Boeing 737-81Q (WL) | Miami Air International | N732MA | 30618/830 | 2001 | CFMI CFM56-7B26 | Fatalities: 0 / Occupants: 143 | 0 | Substantial, written off | Accident | Jacksonville Naval Air Station, FL (NIP) - United States of America | Landing | Passenger - Non-Scheduled/charter/Air Taxi | Guantánamo NAS (NBW/MUGM) | Jacksonville NAS, FL (NIP/KNIP) | Accident investigation report completed and information captured | A Miami Air Boeing 737-800, registration N732MA, operating as Flight 293 from Cubas Leeward Point Field at Guantánamo Bay experienced a runway overrun upon landing at Jacksonville Naval Air Station/Towers Field (KNIP), Florida. The airplane came to rest in the shallow waters of St. Johns River, sustaining substantial damage. The 143 passengers and crew survived. The aircraft was engaged in a charter flight to bring military personnel and family members home. The No. 1 (left) thrust reverser was not operational and deferred for the flight in accordance with the airplanes minimum equipment list. The captain was the pilot flying for the accident flight, and the first officer was the pilot monitoring. The captain was also performing check airman duties for the first officer who was in the process of completing operating experience training. Flight 293 departed Guantánamo Bay at 23:19 UTC. At 21:22 local time the pilot checked in with a Jacksonville approach (JAX) controller while level at 13,000 ft mean sea level and was provided the JAX altimeter setting; the controller advised the pilot to expect the RNAV runway 28 approach and moderate-to-heavy precipitation on the final approach to runway 28 (9000 ft/2743 m long). At 21:23, the JAX controller advised the pilot that the winds at KNIP were from 350° at 4 knots; the pilot then asked if there was any chance of getting runway 10 because it looked a little better. The JAX controller responded that he was showing moderate-to-heavy precipitation building over runway 10 starting about 5 miles on final. The pilot acknowledged and said he would stick with runway 28. He was then instructed to descend and maintain 5,000 ft. At 21:25, the controller provided additional weather information to the flight crew, stating that moderate-to-heavy precipitation was present east and west of the airport. The pilot elected to continue for an approach to runway 28. At 21:30, the JAX controller advised the pilot that the flight was heading northbound and the precipitation was moving eastbound; the controller then asked the pilot if he would like to try runway 10 since it might be better. The pilot acknowledged "yeah go ahead, lets do it." The controller then instructed the pilot to turn left to a heading of 270°, and the pilot acknowledged. Over the next several minutes, the flight was vectored for the approach to runway 10. At 21:37, the JAX controller cleared the flight for the RNAV runway 10 approach, and the pilot acknowledged. Shortly after, the flight was transferred to the KNIP radar controller. The pilot contacted the KNIP radar controller, and, at 21:39, the KNIP radar controller indicated the winds were from 240° at 10 knots; he then cleared the flight to land on runway 10. As the airplane descended through 1,390 ft mean sea level (msl), the pilots configured it for landing with the flaps set at 30° and the landing gear extended; however, the speedbrake handle was not placed in the armed position as specified in the Landing checklist. At an altitude of about 1,100 ft msl and 2.8 nm from the runway, the airplane was slightly above the glidepath, and its airspeed was on target. Over the next minute, the indicated airspeed increased to 170 knots (17 knots above the target approach speed), and groundspeed reached 180 knots, including an estimated 7-knot tailwind. At an altitude of about 680 ft msl and 1.6 nm from the threshold, the airplane deviated further above the 3° glidepath such that the precision approach path indicator (PAPI) lights would have appeared to the flight crew as four white lights and would retain that appearance throughout the rest of the approach. Eight seconds before touchdown, multiple enhanced ground proximity warning system alerts announced "sink rate" as the airplanes descent rate peaked at 1,580 fpm. The airplane crossed the displaced threshold 120 ft above the runway and 17 knots above the target approach speed, with a groundspeed of 180 knots and a rate of descent about 1,450 ft per minute (fpm). The airplane touched down about 1,580 ft beyond the displaced threshold, which was 80 ft beyond the designated touchdown zone as specified in the operators standard operating procedures (SOP). After touchdown, the captain deployed the No. 2 engine thrust reverser and began braking; he later reported, however, that he did not feel the aircraft decelerate and increased the brake pressure. The speedbrakes deployed about 4 seconds after touchdown, most likely triggered by the movement of the right throttle into the idle reverse thrust detent after main gear tire spinup. The automatic deployment of the speedbrakes was likely delayed by about 3 seconds compared to the automatic deployment that could have been obtained by arming the speedbrakes before landing. The airplane crossed the end of the runway about 55 ft right of the centerline and impacted a seawall 90 ft to the right of the centerline, 9,170 ft beyond the displaced threshold, and 1,164 ft beyond the departure end of runway 10. After the airplane came to rest in St. Johns River, the flight crew began an emergency evacuation. The airplane was mostly intact, but both main landing gear had separated from the airplane and were also located in the river. Probable Cause and Findings An extreme loss of braking friction due to heavy rain and the water depth on the ungrooved runway, which resulted in viscous hydroplaning. Contributing to the accident was the operators inadequate guidance for evaluating runway braking conditions and conducting en route landing distance assessments. Contributing to the continuation of an unstabilized approach were 1) the captains plan continuation bias and increased workload due to the weather and performing check airman duties and 2) the first officers lack of experience. | 15610 flights | 38928 hours | DCA19FA143 | NTSB | Final report | 9fdb370c9b0370ea87c3203bf35eeb45 | Investigation completed | 2 years and 3 months | |
| 2019 | Monday 28 January 2019 | 17:25 | ATR 72-500 (72-212A) | Air Europa, opb Swiftair | EC-LYJ | 468 | 1996 | Pratt & Whitney Canada PW127F | Fatalities: 0 / Occupants: 65 | 0 | Substantial, repaired | Accident | Palma de Mallorca Airport (PMI) - Spain | Landing | Passenger - Scheduled | Valencia Airport (VLC/LEVC) | Palma de Mallorca Airport (PMI/LEPA) | Accident investigation report completed and information captured | Air Europa flight 4014, an ATR 72-500, suffered a partial runway excursion during landing rollout on runway 24L at Palma de Mallorca Airport, Spain. The aircraft departed the right side of the runway and hit one of the runway edge lights. The landing could be completed without further incident and the aircraft rolled on its own to the apron. The aircraft sustained significant damage to the right side of the fuselage that affected the airframe, the hydraulic system and the landing gear. Causes/Contributing factors: The investigation has determined that the accident was caused by the loss of control of the aircraft on the ground in conditions close to the maximum demonstrated cross wind limit due to the fact that this maneuver was not performed according to the procedure published by the manufacturer. The following are considered to be contributing factors: - The absence of communication between crew members on cross wind landing technique during the approach briefing. - The surprise and shock effect on the crew produced by the behaviour of the aircraft in the first moments after the landing, which affected negatively their subsequent actions and caused them to react instinctively instead of applying the procedure published by the manufacturer. | 32100 hours | A-004/2019 | CIAIAC | Final report | 2703123694318798a582a7ac62af8e9f | Investigation completed | 11 months | ||
| 2019 | Wednesday 13 February 2019 | 15:55 LT | Embraer ERJ-175LR (ERJ-170-200 LR) | Delta Airlines, opb Compass Airlines | N613CZ | 17000203 | 2008 | General Electric CF34-8E5 | Fatalities: 0 / Occupants: 64 | 0 | Minor | Accident | near Reno-Tahoe International Airport (KRNO), Washoe County, NV - United States of America | En route | Passenger - Scheduled | Santa Ana-John Wayne International Airport, CA (SNA/KSNA) | Reno/Tahoe International Airport, NV (RNO/KRNO) | Accident investigation report completed and information captured | On February 13, 2019 about 1232 PST, Compass Airlines flight 5763, an Embraer ERJ 175, N613CZ, encountered turbulence while in cruise flight at flight level (FL) 340 and subsequently diverted to Reno-Tahoe International Airport (KRNO), Reno, Nevada. Of the 75 passengers and crew onboard, one flight attendant sustained serious injuries while two flight attendants and two passengers received minor injuries. The airplane sustained minor damage. The flight was operating under the provisions of 14 Code of Federal Regulations Part 121 as a regularly scheduled passenger flight from the John Wayne-Orange County Airport (KSNA), Santa Ana, California to Seattle-Tacoma International Airport (KSEA), Seattle, Washington. According to the flight crew, about 40 minutes into the flight when the airplane was in smooth air and 'between cloud layers', the captain informed the flight attendants that they could begin cabin service but left the seatbelt sign illuminated for passengers because there was a report of 'occasional light chop'. About 20 minutes later, the flight encountered an area of severe turbulence that lasted about 8 seconds and caused the airplane to rapidly gain altitude and the traffic collision avoidance system (TCAS) to issue a resolution advisory (RA) for opposite-direction traffic 1,000 ft above them. The first officer (FO) , who was the flying pilot, disengaged the autopilot and applied forward control pressure to comply with the RA. The FO could not obtain the target flight path vector directed by the TCAS, so the captain assisted on the controls to obtain the desired pitch attitude. After the airplane descended back to its assigned altitude, the TCAS RA cleared, and the captain informed air traffic control of the turbulence and TCAS RA. According to the flight attendants (FA), the turbulence was encountered as they were beginning the beverage service. Two of the FAs impacted the ceiling before falling to the floor and one passenger, who had been in the lavatory at the time of the encounter had a small head laceration. As a result of the injuries, the captain declared an emergency and the flight diverted to KRNO. The FA in the aft galley was assisted by a medically qualified passenger and remained on the floor until landing due to her injuries. She was transported to the hospital and diagnosed with a broken arm. Post accident examination of the weather satellite data depicted cloud patterns aloft consistent with the presence of a convective updraft coincident with the flight's location at the time of the turbulence encounter. The convection appeared to be “embedded†with stratiform clouds and may not have been visually identifiable by the flight crew. Probable Cause: an inadvertent encounter with convective turbulence that resulted in a TCAS RA, which required an abrupt control input by the flight crew to resolve the conflict. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | 30469 hours | DCA19CA081 | NTSB | Final report | 74ccdf7f2f948ff1536bad3efd686c60 | Investigation completed | ||
| 2019 | Thursday 11 April 2019 | 23:16 LT | Boeing 737-924ER (WL) | United Airlines | N31412 | 30129/1112 | 2002 | CFMI CFM56 | Fatalities: 0 / Occupants: 108 | 0 | Accident | Fort Myers, FL - United States of America | Landing | Passenger - Scheduled | Houston-George Bush Intercontinental Airport, TX (IAH/KIAH) | Fort Myers, FL | Accident investigation report completed and information captured | On April 11, 2019, about 2316 eastern daylight time, United Airlines flight 2260, a Boeing 737-924, N31412, the aft galley oven dislodged during landing at Southwest Florida International Airport(KRSW), Fort Myers, Florida. Of the 107 passengers and crew onboard, one flight attendant sustained serious injuries. The airplane was not damaged. The flight was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 121 as a regularly scheduled passenger flight from the George Bush Intercontinental Airport (KIAH), Houston, Texas, to KRSW. After touchdown on runway 24, the aft galley oven became dislodged, and the aft galley flight attendant attempted to restrain it causing her injury. After taxiing to the gate and deplaning, the flight attendant was treated by emergency medical personnel and transported to the hospital where she was diagnosed with a fractured left forearm. Post flight examination found multiple attach screws on the bottom of the oven were missing, which allowed the oven to slide out of its compartment during the landing. Subsequent to the accident, the operator conducted a fleet inspection of the oven housing attach screws. Probable Cause: missing attach screws on the aft galley oven, which allowed it to become dislodged landing, injuring a flight attendant. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | 52524 hours | DCA19CA137 | NTSB | Final report | 8fddd7ede22851ce67f32d4ee662ca1f | Investigation completed | 2 years and 10 months | ||
| 2019 | Friday 18 January 2019 | 23:19 UTC | Boeing 777-212ER | Singapore Airlines | 9V-SQL | 33370/451 | 2003 | Fatalities: 0 / Occupants: 261 | 0 | Accident | en route Melbourne-Wellington - Australia | En route | Passenger - Scheduled | Melbourne-Tullamarine Airport, VIC (MEL/YMML) | Wellington International Airport (WLG/NZWN) | Accident investigation report completed and information captured | The Boeing 777-200 aircraft encountered turbulence while enroute from Melbourne, Australia to Wellington, New Zealand. As a result of the turbulence encounter, a passenger sustained a fractured right femur (thighbone). The flight continued to Wellington. Due to the nature of the injury, the passenger had to remain on the aisle during the landing in Wellington. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | TSIB Singapore | Final report | 22d30055f43f0be381acc298dbf76d7a | Investigation completed | 9 months | |||||
| 2019 | Monday 11 February 2019 | 10:06 | Raytheon Beechjet 400A | Stein's Aircraft Services | N750TA | RK-226 | 1999 | Pratt & Whitney Canada JT15D-5 | Fatalities: 0 / Occupants: 3 | 0 | Substantial | Accident | Richmond Municipal Airport, IN (RID) - United States of America | Landing | Executive | Waukesha Airport, WI (UES/KUES) | Richmond Municipal Airport, IN (RID/KRID) | Accident investigation report completed and information captured | The Beech 400A airplane, N750TA, collided with ground objects and terrain following a landing overrun on runway 24 at the Richmond Municipal Airport (RID), Indiana, USA. The three occupants were uninjured. The airplane sustained substantial wing and fuselage damage. After reviewing the weather at the destination airport the pilots decided they would be landing on runway 24 using the GPS approach. They reviewed weather at least "4 or 5 times" on the installed avionics display and the pilot stated that the displayed information indicated conditions of 1.5 miles visibility, ceiling of 1,500 ft, wind 090 at 4 knots, with fog and mist. The crew discussed the approach and talked about having a 4 knot quartering tailwind. When the airplane was near Richmond, the first officer listened to the automated weather observing system recording and it was reporting 3/4 mile visibility and 1,500 ft ceiling, scattered 300, wind 090 at 4 knots, temp 0C, dew point 0 C, altimeter 30.13 inches of mercury. The pilot indicated, "All this information said we had the numbers to make the approach to runway 24, (5,500 feet long)." The pilot used the autopilot fly the approach to just before minimums. The airplane was about "300 ft" and the first officer called the runway to the left. The pilot looked up and saw the precision approach path indicator lights to the left and the runway straight ahead. However, the runway appeared to have a "very light coating of snow on it." The pilot elected to land and apply full thrust reverse and braking. The pilot also queried the first officer about the spoilers and the first officer confirmed the spoilers were out. A few seconds later the pilot felt the airplane was not slowing much and advised the first officer that the airplane was going to go off the end. At that point, the first officer said that he saw the 2,000 ft marker ahead of the airplane. Both pilots were pushing the brakes as hard as they could and full reverse was applied. The airplane went off the end of the runway and ended up across a road near the runway. Probable Cause: The flight crew's decision to continue an unstable approach under conditions that exceeded the airplane's landing performance capabilities, which resulted in a runway overrun and impact with terrain. | 6224 hours | CEN19LA090 | NTSB | Final report | 03e7cdfe0dc550b72c0e41027fe36894 | Investigation completed | 2 years and 2 months | ||
| 2019 | Saturday 9 February 2019 | Embraer ERJ 190AR (ERJ-190-100 IGW) | Kenya Airways | 5Y-KYR | 19000468 | 2011 | General Electric CF34-10E6 | Fatalities: 0 / Occupants: | 0 | Substantial, written off | Other | Nairobi-Jomo Kenyatta International Airport (NBO) - Kenya | Standing | - | - | - | A Kenya Airways Embraer ERJ-190AR (5Y-KYR) was being serviced on the apron at Nairobi-Jomo Kenyatta International Airport in Kenya. Chocks were placed at the wheels. As the engine were powered, the aircraft jumped the chocks. It collided with another parked Kenya Airways Embraer ERJ-190AR (5Y-FFF). Both aircraft suffered serious damage. | |||||||||||
| 2019 | Saturday 9 March 2019 | 10:36 | Douglas DC-3 | LASER Aéreo Colombia | HK-2494 | 33105/16357 | 1945 | Pratt & Whitney R-1830-92 | Fatalities: 14 / Occupants: 14 | 0 | Destroyed, written off | Accident | Finca La Bendición, San Martín - Colombia | Approach | Passenger - Non-Scheduled/charter/Air Taxi | San Jose del Guaviare-Jorge E. González T. Airport (SJE/SKSJ) | Villavicencio Airport (VVC/SKVV) | Accident investigation report completed and information captured | The DC-3 aircraft with registration HK-2494, operated by LASER, was prepared to make a non-scheduled passenger flight between Taraira Airport (SKTR) and the aerodrome Villavicencio (SKVV) in Colombia. The aircraft took off at 06:13 hours local time with a crew of three, eight passengers and 500 kgs of cargo. Adverse weather conditions were encountered en route and the crew decided divert to Miraflores (SKMF) where it landed at 07:39. There two more passengers boarded the flight for Villavicencio. At 08:34 the aircraft took off from Miraflores and flew to San Jose del Guaviare (SKSJ) to refuel, where it landed at 09:14. The aircraft was fueled and the crew submitted a flight plan to Villavicencio with a total flight time of 45 minutes an altitude of 8,500 feet. Prior to departure one more passenger boarded the flight. The aircraft took off at 09:55. At 10:15, when the aircraft was climbing through 8,100 feet and approximately 59NM (109 km) from Villavicencio, the flight reported engine problems and their failure to feather the propeller. At the crew's request, ATC provided information on the location of several aerodromes in the area and the crew chose to proceed to La Rinconada aerodrome. The aircraft lost altitude and last radio contact was at 10:32 when the crew radioed that they had a runway in sight, with no further information. At 10:34 the aircraft hit the ground of a palm plantation with a high angle of descent and low speed. Flaps and undercarriage were retracted at the time of the accident. The aircraft slid across a gravel road and burst into flames. Probable Cause(s). The investigation determined that the accident was caused by the following probable causes: - Loss of control in-flight as a consequence of the decrease in minimum in-flight control speed and drag generated by the impossibility of performing the No. 1 engine propeller feathering in the face of engine failure. - Malfunction of the lubrication system of engine No. 1, evident in the abundant oil leakage from the engine, in flight, and in the governor of the left propeller; although discrepancies were found in the maintenance of the propeller feathering pressure line, it was not possible to determine the origin of the oil leakage. - Weaknesses in the aircraft Operator's operational procedures, lacking a standard that would facilitate a crew's decision making to act in the event of critical failures, in matters such as making an emergency landing on unprepared field or the selection of an alternate airfield. Contributing Factors: - Deficiencies in standard maintenance practices during repairs performed on the No. 1 engine's propeller propeller feathering oil pressure line. - Non-compliance with an effective and reliable maintenance program, which did not verify the operating conditions of the aircraft components; it was not possible to determine compliance with the last 50-hour service, Phase A, to engine No. 1 according to the company's maintenance program, since there are no records of that service in the Flight Log. - Inefficient safety management system of the Operator for not detecting errors in the maintenance processes and in the conduct and control of operations. | 27308 hours | COL-19-10-GIA | Aerocivil | Final report | dd0ee7db7d33509a9984d15148e78163 | Investigation completed | 1 year and 9 months | ||
| 2019 | Wednesday 8 May 2019 | 18:51 | de Havilland Canada DHC-8-402Q Dash 8 | Biman Bangladesh Airlines | S2-AGQ | 4367 | 2011 | Pratt & Whitney Canada PW150A | Fatalities: 0 / Occupants: 34 | 0 | Destroyed, written off | Accident | Yangon-Mingaladon Airport (RGN/VYYY) - Myanmar | Landing | Passenger - Scheduled | Dhaka-Shahjalal International Airport (DAC/VGHS) | Yangon-Mingaladon Airport (RGN/VYYY) | Accident investigation report completed and information captured | A Biman Bangladesh Airlines DHC-8-400 suffered an accident during an attempted landing on runway 21 at Yangon-Mingaladon Airport, Myanmar. The aircraft departed Dhaka-Shahjalal International Airport, Bangladesh, as Biman flight 060 about 15:15 hours local time with destination Yangon-Mingaladon Airport in Myanmar. Weather at Yangon was poor due to the presence of a thunderstorm in the area. While the flight crew was performing an ILS approach, the controller instructed them to go around as the airport was closed due to weather. When the weather condition got better, the flight was cleared for an RNP approach to runway 21 because only the localizer was available at that moment. The co-pilot was Pilot Flying and the captain was Pilot Monitoring. The aircraft was higher than the 3 degree approach path and the airspeed fluctuated between 136 and 151 kts, which was than the 122 kts target airspeed. The captain said "continue, continue" to the copilot and the approach was continued. At an altitude of 22 feet over the runway, the captain began pushing the control column forward, while the PF was attempting to pull on the control column. At 1828 m down the runway, with 1585 m remaining, the aircraft briefly skipped a few times before getting airborne again. The captain then stated: "I have control", which was confirmed by the co-pilot. While in the air, the captain applied the brake pedal several times. At a height of 44 feet, the captain put the propellers in beta range and reduced the power lever angle to 18 degrees. The aircraft sank again and collided with runway 03 and slid forward. It left the runway and came to a complete stop in the over-run area. The aircraft fuselage broke in just behind the forward passenger door and just behind the rear service door. The undercarriage collapsed and the right hand wing broke at the attachment point with the fuselage. There was no fire. All occupants survived, but twelve suffered serious injuries. Primary Cause: While the aircraft was unstablized on approach, the pilot did not execute a go-around. | 8115 hours | Final report | AAIB Myanmar | Final report | da09983b09a09680658559b1429e83a4 | Investigation completed | 8 months | ||
| 2019 | Sunday 10 March 2019 | 09:45 | Bombardier CL-600-2D24 Regional Jet CRJ-900LR | PSA Airlines, opf American Eagle | N569NN | 15356 | 2015 | General Electric CF34-8C5B1 | Fatalities: 0 / Occupants: 70 | 0 | Substantial, repaired | Accident | Charlotte-Douglas International Airport, NC (CLT/KCLT) - United States of America | Taxi | Passenger - Scheduled | Charlotte-Douglas International Airport, NC (CLT/KCLT) | Nashville International Airport, TN (BNA/KBNA) | Accident investigation report completed and information captured | PSA Airlines flight 5366, a CRJ-900LR, N569NN, collided with PSA Airlines flight 5141, a CRJ-702ER, N530EA while pushing back from gate E31 at the Charlotte Douglas International Airport (KCLT), North Carolina, USA. There were no injuries the passengers and crew onboard either airplane, and both airplanes received substantial damage. The CRJ-700 had pushed back from gate E14B and was waiting for taxi by spot 29W. The CRJ900 requested push back from gate E31, and the north ramp controller initially instructed them to "10 and hold". The push back was approved about 2 minutes later and the flight crew coordinated with ground crew. After pushing back about 30 feet, the tail of the CRJ-900 impacted the tail of the CRJ-700. After feeling the impact, the CRJ-900 crew aborted their engine start procedure and set the parking brake, while the CRJ-700 crew started their auxiliary power unit and shut down both engines after receiving damage reports from ATC and neighboring airplanes. An emergency evacuation was not performed on either aircraft. Post-accident examination revealed substantially damaged to the horizontal and vertical stabilizers and left elevator of the CRJ-900, and the horizontal stabilizer and left elevator of the CRJ-700. Probable Cause: "Failure of the ground crew to maintain visual separation and avoid the holding aircraft." | DCA19CA102B | NTSB | Final report | 6962b6a6184a2b785f30d9fcbfa734d9 | Investigation completed | 2 years and 11 months | |||
| 2019 | Wednesday 13 February 2019 | 14:52 | de Havilland Canada DHC-6 Twin Otter 300 | Winair | PJ-WII | 682 | 1980 | Pratt & Whitney Canada PT6A-27 | Fatalities: 0 / Occupants: 6 | 0 | Accident | Saint-Barthélémy-Rémy de Haenen Airport (SBH/TFFJ) - Saint Barth�lemy | Standing | Passenger - Scheduled | Sint Maarten-Juliana Airport (SXM/TNCM) | Saint-Barthélémy-Rémy de Haenen Airport (SBH/TFFJ) | Accident investigation report completed and information captured | At the arrival at the parking, a gate agent is hit in the head by the right engine spinning propeller. Contributing factors: - the ground handler's failure to comply with safety measures designed to protect personnel from the hazards inherent around an operating aircraft; - the probable state of fatigue of the ground handler due to his late bedtime and his probable consumption of psychoactive substances; - the habit taken, during short rotations, by a part of the ground handling personnel, to disregard certain safety measures in order to gain time, which could have encouraged him to leave his position at the nose of the aircraft without waiting for the complete stop of the propellers. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | BEA | Final report | 7d9f853fcdacabc68330b0ab40cf8efd | Investigation completed | 3 years and 10 months | ||||
| 2019 | Tuesday 5 February 2019 | 09:47 LT | Boeing 737-823 (WL) | American Airlines | N852NN | 40581/3396 | 2010 | CFM56-7B | Fatalities: 0 / Occupants: 119 | 0 | Accident | Bluefields - Costa Rica | Initial climb | Passenger - Scheduled | San José-Juan Santamaria International Airport (SJO/MROC) | Miami International Airport, FL (MIA/KMIA) | Accident investigation report completed and information captured | American Airlines flight AA1204, a Boeing 737-823, encountered severe turbulence during climb. Of the 119 passengers and crew onboard, one flight attendant received a serious injury and another flight attendant received minor injuries. The airplane was not damaged. The captain was the pilot flying and the copilot was pilot monitoring. The flight was climbing through FL310 to the planned cruising altitude when the flight encountered moderate to severe clear air turbulence. According to the flight crew, the seatbelt sign was on when the turbulence occurred The turbulence subsided after about one and a half minutes and occurred during daylight, in visual meteorological conditions, and with no indications of convective weather in the area. At the time of the turbulence, two flight attendants (FA) had just started to prepare for beverage service in the aft galley when they were thrown to the floor. Both FAs crawled to the last row of seats as the turbulence continued. The two FAs were then assisted for the remainder of the flight by to passenger medical professionals. After landing, the FAs were transported to the hospital where one was diagnosed with a broken foot and the other with minor bruises. Probable Cause: An inadvertent encounter with clear air turbulence. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | DCA19CA075 | NTSB | Final report | 3b37028df71de7761c75c7a58cbcf024 | Investigation completed | 3 years | |||
| 2019 | Monday 13 May 2019 | 16:07 | Boeing 737-9B5 | Korean Air | HL7726 | 30001/1729 | 2005 | CFMI CFM56-7B | Fatalities: 0 / Occupants: 85 | 0 | Accident | 30NM W of Incheon International Airport - South Korea | En route | Passenger - Scheduled | Tianjin International Airport | Seoul-Incheon International Airport (ICN/RKSI) | Accident investigation report completed and information captured | Korean Air flight KE864, a Boeing 737-9B5, encountered turbulence at about 17,000ft. One cabin crew member fell in the galley and suffered 12 fractures of the thoracic vertebrae. The Air and Rail Accident Investigation Committee, hereinafter referred to as the Committee, determines the cause of this accident Unexpected clear air turbulence during approach descent for landing I decide that it is.” Approach for landing as a contributing factor Landing “ON” “with seat belt” during descent It is decided due to the lack of self-protection of the cabin crew who were preparing beforehand.” Based on the results of the accident investigation, the committee issued safety advisories to Korean Air. The Aviation and Railway Accident Investigation Committee determines the cause of this accident as “clear air turbulence during the approach descent for landing.” As a contributing factor “It is determined by the lack of self-protection of the cabin crew who were preparing before landing with the seat belts turned “ON” during the descent.” | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ARAIB | Final report | 8bebd583ef85702e76c866139b9b2d46 | Investigation completed | 1 year and 3 months | ||||
| 2020 | Thursday 23 January 2020 | 13:15 | Lockheed EC-130Q Hercules | Coulson Aviation | N134CG | 4904 | 1981 | Allison T56-A-15 | Fatalities: 3 / Occupants: 3 | 0 | Destroyed, written off | Accident | near Cooma, NSW - Australia | Manoeuvring (airshow, firefighting, ag.ops.) | Fire fighting | Richmond RAAF Base, NSW (XRH/YSRI) | Richmond RAAF Base, NSW (XRH/YSRI) | Accident investigation report completed and information captured | A Lockheed C-130 Hercules firefighting aircraft impacted terrain and burst into flames near Cooma, north-east of the Snowy Mountains in Australia. All three crew members died in the accident. The aircraft, contracted to the New South Wales Rural Fire Service, departed Richmond RAAF Base, Australia at 12:05 local time. The crew had been tasked with a fire retardant drop over the Adaminaby Complex bush fire. After approaching the Adaminaby complex fire, the drop was unable to be completed and the aircraft was diverted to a secondary tasking, to drop retardant on the Good Good fire. Witnesses reported seeing the aircraft complete a number of circuits, prior to completing the retardant drop. The drop was conducted on a heading of about 190°, at about 200 ft above ground level, with a drop time of approximately 2 seconds. The crew released about 1,200 US gallons (4,500 L) of fire retardant during the drop. Witness videos taken of the aircraft leading up to the accident showed a number of passes conducted at varying heights prior to the retardant drop. Following the retardant drop, the aircraft was observed to bank left, before becoming obscured by smoke after about 5 seconds. A further 15 seconds after this, the aircraft was seen flying at a very low height above the ground, in a left wing down attitude. Shortly after, at about 13:16, the aircraft collided with terrain and a post-impact fuel-fed fire ensued. The three crew were fatally injured and the aircraft was destroyed. Contributing factors: - Hazardous weather conditions were forecast and present at the drop site near Peak View, which included strong gusting winds and mountain wave activity, producing turbulence. These conditions were likely exacerbated by the fire and local terrain. - The Rural Fire Service continued the B134 tasking to Adaminaby when they learned that no other aircraft would continue to operate due to the environmental conditions. In addition, they relied on the pilot in command to assess the appropriateness of the tasking to Adaminaby without providing them all the available information to make an informed decision on flight safety. - The pilot in command of B134 accepted the Adaminaby fire-ground tasking, which was in an area of forecast mountain wave activity and severe turbulence. After assessing the conditions as unsuitable, the crew accepted an alternate tasking to continue to the Good Good (Peak View) fire-ground, which was subject to the same weather conditions. The acceptance of these taskings were consistent with company practices. - Following the partial retardant drop and left turn, the aircraft was very likely subjected to hazardous environmental conditions including low-level windshear and an increased tailwind component, which degraded the aircrafts climb performance. - While at a low height and airspeed, it was likely the aircraft aerodynamically stalled, leading to a collision with terrain. - Coulson Aviation's safety risk management processes did not adequately manage the risks associated with large air tanker operations. There were no operational risk assessments conducted or a risk register maintained. Further, as safety incident reports submitted were mainly related to maintenance issues, operational risks were less likely to be considered or monitored. Overall, this limited their ability to identify and implement mitigations to manage the risks associated with their aerial firefighting operations. (Safety issue) - Coulson Aviation did not provide a pre-flight risk assessment for their firefighting large air tanker crews. This would provide predefined criteria to ensure consistent and objective decision-making with accepting or rejecting tasks, including factors relating to crew, environment, aircraft and external pressures. (Safety issue) - The New South Wales Rural Fire Service had limited large air tanker policies and procedures for aerial supervision requirements and no procedures for deployment without aerial supervision. (Safety issue) - The New South Wales Rural Fire Service did not have a policy or procedures in place to manage task rejections, nor to communicate this information internally or to other pilots working in the same area of operation. (Safety issue) | 11888 hours | AO-2020-007 | ATSB | Final report | dbbcc9746c9cd4c5e9701353d0e7770f | Investigation completed | 2 years and 7 months | ||
| 2020 | Wednesday 5 February 2020 | 18:19 | Boeing 737-86J (WL) | Pegasus Airlines | TC-IZK | 37742/2796 | 2009 | CFMI CFM56-7B24 | Fatalities: 3 / Occupants: 183 | 0 | Destroyed, written off | Accident | Istanbul-Sabiha Gökçen International Airport (SAW) - Türkiye | Landing | Passenger - Scheduled | Izmir-Adnan Menderes Airport (ADB/LTBJ) | Istanbul-Sabiha Gökçen International Airport (SAW/LTFJ) | Information is only available from news, social media or unofficial sources | Pegasus Airlines flight 2193, a Boeing 737-800, suffered a runway excursion after landing on runway 06 at Istanbul-Sabiha Gökçen International Airport, Turkey. There were 183 occupants on the aircraft. Three passengers died, the remaining 180 occupants were injured. The aircraft departed Izmir Airport at 17:22 hours. At the time the flight arrived in the vicinity of Istanbul-Sabiha Gökçen Airport, a thunderstorm was passing. Runway in use was 06. About 18:17 the Tower controller cleared another flight for takeoff from runway 06, reporting wind 300 degrees at 11 knots, gusting to 21 knots. The subsequent arrival was flight 2193, which was cleared to land with wind information given as 270 degrees at 22 knots, gusting to 30 knots. This translates to a 19 knot tailwind. Since the wind was shifting the controller reported to a flight on the ground that it was to expect a runway change for departure. At 18:19 Pegasus 2193 touched down, but failed to come to a complete stop on the runway. It overran and went down an embankment, breaking in three. The aircraft came to rest about 30 m below runway elevation. Data from flight tracking website Flightradar24 suggest that the aircraft was steered to the left at the end of the runway, likely as there was an antenna array just past the stopway. The last recorded ground speed was 63 knots as the aircraft crossed the perimeter road. Runway 06 is a concrete runway with a Landing Distance Available (LDA) of 3000 m. At the runway end there is a 65 m long stopway, followed by antenna array, perimeter road and a downslope. In March 2020 Turkish media reported on a preliminary report, issued by authorities. According to this report the aircraft was struck by lightning six minutes before landing. During the approach one of the preceding aircraft reported a sudden tailwind of 37 knots below 600 feet. This report was communicated in Turkish by the Tower controller. The Dutch first officer, who was Pilot Monitoring, did not understand this. Subsequent clearances and weather information were in English. After touchdown the speedbrake and autobrake activated. The thrust reversers were selected manually. After passing taxiway F at an airspeed of 57 knots, the speed brake and thrust reverser were switched off. The ground speed was reported to be 84 knots due to the effect of the wind. Six seconds later manual braking was resumed. The aircraft failed to stop on the runway, hit ILS antennas and a small building before it fell 30 m down the embankment. | |||||||||
| 2020 | Friday 7 February 2020 | 04:18 | Cessna 208B Super Cargomaster | Mountain Air Cargo, opf FedEx | N988FX | 208B2400 | 2012 | Pratt & Whitney Canada PT6A-114A | Fatalities: 0 / Occupants: 1 | 0 | Substantial, repaired | Accident | Baltimore/Washington International Thurgood Marshall Airport, MD (BWI) - United States of America | Landing | Cargo | Newark-Liberty International Airport, NJ (EWR/KEWR) | Baltimore/Washington International Thurgood Marshall Airport, MD (BWI/KBWI) | Accident investigation report completed and information captured | The pilot of a Cessna 208B Super Cargomaster was conducting an instrument landing system approach in night instrument meteorological conditions to runway 10 at Baltimore/Washington International Thurgood Marshall Airport, MD (BWI). The pilot was utilizing the autopilot for the approach and disengaged it when he had the runway and airport lighting system in view. As he approached the runway, the pilot heard a sound and thought the airplane had hit a bird. He felt the airplane pitch up so he increased engine power and pitched down in order to reach the runway. After the pilot landed and taxied to the ramp, he saw that a large piece of an approach light was caught on the airplane's right main landing gear. Further inspection revealed that the airplane's empennage, right horizontal stabilizer, right wing strut, and front cargo pod were also damaged. The operator reported that the airplane had struck four separate approach light towers as well as a localizer antenna. Probable cause: "The pilot's failure to maintain clearance from the approach lights during an instrument approach." | 3497 hours | ERA20CA095 | NTSB | Final report | b4ccfe03a34625bbf9f4c49be95eadd3 | Investigation completed | 6 months | ||
| 2020 | Tuesday 28 January 2020 | 17:35 LT | Boeing 737-6CT | WestJet | C-GWJU | 34289/1956 | 2006 | CFMI CFM56-7B | Fatalities: 0 / Occupants: 85 | 0 | Substantial, repaired | Accident | Vancouver International Airport, BC (YVR/CYVR) - Canada | Standing | Passenger - Scheduled | Edmonton International Airport, AB (YEG/CYEG) | Vancouver International Airport, BC (YVR/CYVR) | Information verified through data from accident investigation authorities | WestJet flight WJA141, a Boeing 737-600 (C-GWJU) and WestJet flight WJA717, a Boeing 737-700 (C-FZWS) were involved in a ground contact accident at Vancouver International Airport, BC (YVR/CYVR). WJA141 stopped short of the lead-in line for gate B15, with engines running, awaiting ground crew to marshal the aircraft to the gate. Meanwhile, WJA717 was taxing eastbound on the apron towards the lead-in line for gate B13. The left winglet of C-FZWS contacted the right-hand horizontal stabilizer of C-GWJU. There were no injuries. Both aircraft sustained substantial damage. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||
| 2020 | Sunday 5 January 2020 | de Havilland Canada DHC-8-202Q | US Special Operations Command (USSOCOM) | N8200L | 455 | 1997 | Pratt & Whitney Canada PW123D | Fatalities: 0 / Occupants: 0 | 0 | Destroyed, written off | Manda Bay-Camp Simba Air Base - Kenya | Standing | Military | - | - | The airplane damaged beyond repair during an attack on the air base by Shabab fighters. | ||||||||||||
| 2020 | Tuesday 3 March 2020 | 00:35 | Cessna 560 Citation Encore | private | N43NC | 560-0698 | 2006 | Pratt & Whitney Canada PW535A | Fatalities: 0 / Occupants: 0 | 0 | Substantial, written off | Other | Nashville-John C. Tune Airport, TN (KJWN) - United States of America | Standing | - | - | - | The aircraft was substantially damaged when a tornado struck Nashville-John C. Tune Airport, Tennessee, USA. | ||||||||||
| 2020 | Monday 9 March 2020 | 06:25 | Gulfstream G-IVSP | Platinum Jet Co., Ltd. | M-YWAY | 1486 | 2002 | Fatalities: 0 / Occupants: 0 | 0 | Substantial, repaired | Accident | Vientiane-Wattay Airport (VTE) - Laos | Standing | - | - | - | A Thai Airways Airbus A330-343 (HS-TEU), performing flight TG575, struck a parked Gulfstream G-IVSP business jet (M-YWAY) at Vientiane-Wattay Airport in Laos. | |||||||||||
| 2020 | Sunday 23 February 2020 | 14:30 | Bombardier CL-600-2B16 Challenger 605 | Canadian Pacific Railway Company | C-GKCP | 5945 | 2013 | General Electric CF34-3B | Fatalities: 0 / Occupants: 13 | 0 | Substantial, repaired | Accident | Calgary International Airport, AB (YYC) - Canada | Landing | Passenger - Non-Scheduled/charter/Air Taxi | West Palm Beach International Airport, FL (PBI/KPBI) | Calgary International Airport, AB (YYC/CYYC) | Accident investigation report completed and information captured | A privately registered Bombardier Challenger 605, was conducting a flight from Palm Beach International Airport, Florida USA (KPBI) to Calgary Intl., AB (CYYC), with three crew members and 10 passengers on board. During the final descent into CYYC, the flight crew selected flaps 20 and immediately received a flaps fail caution message. The decision was made to abandon the approach, and the crew received clearance from ATC to proceed NW of the CYYC airport and troubleshoot the issue. The crew executed the applicable QRH procedure and subsequently received clearance from ATC to proceed with the landing. A flaps 0 landing was then executed. During the landing roll, after ground spoiler and thrust reverser deployment, the nose of the aircraft attained a significant nose high attitude. The rear fuselage of the aircraft struck the runway, and during the recovery, the nose landing gear subsequently impacted the runway. The aircraft taxied clear of the runway and to the intended parking area. Subsequent inspection revealed that the aircraft sustained significant structural damage to the forward fuselage and minor damage to the rear fuselage. There were no injuries. Findings as to causes and contributing factors 1. Moisture entered the flap flexible drive shaft casing, likely through the undetected puncture holes and the drive shaft casing to flap actuator interface, which led to the subsequent corrosion and failure of the inner drive shaft. 2. As the occurrence aircrafts actual annual utilization was approximately half of that expected by the manufacturer, the calendar time interval between maintenance inspections increased. As a result, the corrosion that developed was not detected because the shaft had not yet reached the 2400 flight-hour maintenance interval. 3. The Challenger 605 flight simulator used for recurrent training did not accurately represent the zero-flap handling characteristics of the aircraft when the thrust reversers are deployed, nor was it required for certification. As a result, the flight crew was inadequately prepared to prevent, or recover from, the nose pitch-up that occurred when the thrust reversers were deployed. 4. The pilot monitoring did not read the cautions included on the flaps fail checklist out loud to the pilot flying during the completion of the Quick Reference Handbook procedure. As a result, information critical to the safe operation of the aircraft was not brought to the pilot flyings attention. 5. Insufficient pressure was applied to the control column to maintain the nose on the runway while using maximum reverse thrust; as a result, the nose pitched up, the aft fuselage contacted the runway, and the aircraft transitioned to a partial weight-off-wheels state. 6. When the left main wheel left the runway surface and the angle of attack reached 28.9°, the stick pusher activated and commanded a rapid nose-down pitch input. As a result of this rapid nose-down pitch, the forward section of the aircraft was damaged when the nose wheel contacted the runway. | 920 flights | 1699 hours | A20W0016 | TSB | Final report | abcad67f6b2331682b8ec4a4927ae332 | Investigation completed | 1 year and 2 months | |
| 2020 | Saturday 29 February 2020 | 12:37 | Learjet 35A | East Coast Jets | N721EC | 35A-355 | 1980 | Garrett TFE731-2C-2B | Fatalities: 0 / Occupants: 2 | 0 | Substantial, repaired | Accident | Altoona Airport, PA (AOO) - United States of America | Landing | Ferry/positioning | Allentown-Lehigh Valley International Airport, PA (ABE/KABE) | Altoona Airport, PA (AOO/KAOO) | Accident investigation report completed and information captured | The flight crew reported that, after an instrument landing system approach and during the landing flare, the airplane encountered a strong wind gust that pushed the airplane toward the edge of the runway, so they initiated a go-around. During the go-around, the left-wing tip tank struck the runway. The flight crew diverted to another airport where the weather conditions were more favorable, and after landing, examination of the airplane revealed that the left wing had sustained substantial damage. The calculated crosswind component was 18 knots at the time of landing. According to the Airplane Flight Manual, the maximum demonstrated crosswind component was 24.7 knots. PROBABLE CAUSE: "The pilot flying's improper lateral bank control during a go-around in gusting wind conditions, which resulted in the left-wing tip tank striking the runway." | 14859 hours | ERA20CA120 | NTSB | Final report | baf2917d1cc64988e34e5cd54fa666ef | Investigation completed | 6 months | ||
| 2020 | Monday 4 May 2020 | Learjet 25D | Dos Mil Aerosistema SA | LV-WOC | 25-269 | 1979 | Fatalities: 0 / Occupants: 0 | 0 | Substantial | Other | San Fernando Airport, BA (FDO) - Argentina | Standing | - | - | - | An explosion occurred on a Learjet 25D ambulance jet while being serviced on the apron at San Fernando Airport, Argentina. The aircraft was being prepared for emergency medical flights on behalf of the Tierra del Fuego government with the servicing of the oxygen system when the explosion took place in the rear fuselage. | ||||||||||||
| 2020 | Tuesday 3 March 2020 | 00:35 | Cirrus SF50 Vision Jet | BBR Air | N217CB | 0032 | 2018 | Williams International FJ33-5A | Fatalities: 0 / Occupants: 0 | 0 | Substantial, written off | Other | Nashville-John C. Tune Airport, TN (KJWN) - United States of America | Standing | - | - | - | The aircraft was substantially damaged when a tornado struck the airport. The corporate hangar where the aircraft was being stored collapsed. A beam fell onto the rear side of the aircraft, damaging the aft structure and the V tail stabilizers and tail flight controls. | 134 hours | |||||||||
| 2020 | Friday 3 January 2020 | 10:40 | Hawker 900XP | Million Air San Juan | N805D | HA-0113 | 2009 | Honeywell TFE731-50R | Fatalities: 0 / Occupants: 5 | 0 | Substantial, written off | Accident | San Juan-Fernando Luis Ribas Dominicci Airport (SIG) - Puerto Rico | Landing | Unknown | La Romana-Casa de Campo International Airport (LRM/MDLR) | San Juan-Fernando Luis Ribas Dominicci Airport (SIG/TJIG) | Accident investigation report completed and information captured | As the pilot and copilot of the business jet were conducting an instrument approach to runway 09 at San Juan-Fernando Luis Ribas Dominicci Airport, Puerto Rico. As the airplane was about to touch down, the pilot reduced the engine power. The airplane then descended and landed hard on a grassy area short of the runway threshold. The fuselage sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane what would have precluded normal operation. Probable Cause: The pilot's failure to maintain a proper descent rate during landing, which resulted in a hard landing short of the runway. | 2198 hours | ERA20CA073 | NTSB | Final report | 1ab4a39d671bc3cae334bb820c00d354 | Investigation completed | 5 months | ||
| 2021 | Saturday 23 January 2021 | Canadair CL-600 Challenger 600 | Global Avionics LLC | N275JP | 1036 | 1981 | Lycoming ALF502L-2 | Fatalities: 0 / Occupants: 2 | 0 | Unknown | Accident | Los Mochis-Federal Airport (LMM) - Mexico | Take off | Unknown | Los Mochis-Federal Airport (LMM/MMLM) | Information is only available from news, social media or unofficial sources | Canadair CL-600S Challenger N275JP, suffered a runway excursion at Los Mochis Airport (LMM/MMLM), Sinaloa, Mexico. One of the two pilots received minor injuries. The aircraft, which had undergoing repairs for a month, was trying to conduct a test flight when directional control was lost on takeoff. | |||||||||||
| 2021 | Friday 16 April 2021 | 18:45 | Beechcraft B99 Airliner | Lake Clark Air | N991AK | U-189 | 1982 | Pratt & Whitney Canada PT6A-36 | Fatalities: 0 / Occupants: 9 | 0 | Substantial, repaired | Accident | Chignik-Lagoon Airport, AK (KCL) - United States of America | Landing | Passenger - Non-Scheduled/charter/Air Taxi | Anchorage-Merrill Field, AK (MRI/PAMR) | Chignik-Lagoon Airport, AK (KCL) | Accident investigation report completed and information captured | A Beechcraft B99 Airliner, registration N991AK, sustained substantial damage when it struck a chunk of ice and frozen gravel during a landing attempt at Chignik Lagoon Airport (KCL), Alaska. The pilot reported to the NTSB that, during final approach to land, he noticed a road grader operating on the far end of the runway. He made a radio transmission stating that the flight was 4 miles out on final approach and observed the road grader pull over at the opposite end of the airport and park. Believing that the operator of the road grader heard his call and parked, he proceeded with a normal approach and landing. After touchdown, he applied reverse with moderate braking. When the airplane was fully out of reverse and had slowed to about 35 mph, he noticed a large piece of foreign object debris (FOD) on the runway centerline. The FOD appeared to be about 18 inches wide and about 12 inches tall. He veered to the left in an effort to straddle the FOD with main landing gear. Subsequently, the right main landing gear struck the FOD, the right main landing gear collapsed, and the airplane slid about 75 ft down the runway centerline before coming to a stop. A postaccident inspection revealed that the FOD was a chunk of ice. Probable Cause: The pilots failure to visually inspect the runway condition before landing, which resulted in a collision with an ice chunk and main landing gear separation during landing. | 27917 hours | ANC21LA030 | NTSB | Final report | 35e703027ea6718db94bab87c9d5b6db | Investigation completed | 6 months | ||
| 2021 | Saturday 13 March 2021 | 17:22 | Antonov An-26 | Kazakhstan Border Guards | 02 white | 7201 | Ivchenko AI-24 | Fatalities: 4 / Occupants: 6 | 0 | Destroyed, written off | Accident | Almaty Airport (ALA) - Kazakhstan | Landing | Military | Nursultan Nazarbayev International Airport (NQZ/UACC) | Almaty Airport (ALA/UAAA) | Information is only available from news, social media or unofficial sources | A Kazakh Border Service Antonov An-26 crashed at Almaty Airport, killing four of the six occupants. The aircraft crashed about 600 m short of the threshold of runway 23R and burst into flames. Weather at the time of the accident was poor with overcast clouds at 300 feet (91 meters), a visibility of 5 km with light freezing drizzle and mist. | ||||||||||
| 2021 | Friday 25 June 2021 | 21:31 LT | Airbus A321-231 | American Airlines | N926UW | 6618 | 2015 | IAE V2533-A5 | Fatalities: 0 / Occupants: 194 | 0 | Accident | New Orleans, Louisiana - United States of America | En route | Passenger - Scheduled | Dallas/Fort Worth International Airport, TX (DFW/KDFW) | Tampa International Airport, FL (TPA/KTPA) | Accident investigation report completed and information captured | American Airlines flight 2401 encountered severe turbulence while in cruise flight at FL310 and a flight attendant fractured his ankle. The captain was the pilot flying (PF) and the first officer was monitoring. Ride conditions were smooth with no reports of turbulence in the area and the crewmembers had the weather radar turned off. The flight was in day visual meteorological conditions (VMC) with the visibility greater than 20 miles. About 20 miles NW of the REDFN waypoint, near airway Q105, the flight experienced a single 'jolt†of severe turbulence, which caused the autopilot to disconnect, and the airplane to roll about 30 degrees to the right and climb about 300 feet. The PF took control and returned the airplane to its assigned altitude and reengaged the autopilot. When the turbulence occurred beverage service had recently concluded, and two flight attendants were in the aisle collecting trash. One flight attendant was in the aft galley securing service items and was thrown to the ceiling and fell, fracturing his left ankle. Ten passengers who were not seated or who were not using their seatbelts sustained minor injuries. The fasten seatbelt indication to passengers was turned off. Probable Cause: An inadvertent encounter with severe turbulence during cruise flight that caused a flight attendant to fall and fracture his ankle. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | DCA21LA164 | NTSB | Final report | 62bc5dc3d0497fd852984eb06fe148dd | Investigation completed | 1 year | |||
| 2021 | Sunday 4 July 2021 | 07:00 | Antonov An-2R | ELISA | UP-A0135 | 1G143-48 | 1973 | Shvetsov ASh-62IR | Fatalities: 0 / Occupants: 2 | 0 | Substantial | Accident | 12 km from Karaultobe, Kyzylorda - Kazakhstan | Manoeuvring (airshow, firefighting, ag.ops.) | Agricultural | Information is only available from news, social media or unofficial sources | An Antonov An-2 force landed in a field after an engine malfunction and flipped over. Both pilots survived the crash and were taken to a hospital. The aircraft was spraying a rice field at the time of the accident. | |||||||||||
| 2021 | Thursday 3 June 2021 | Cessna 208B Grand Caravan EX | Dabi Air Nusantara | PK-DPT | 208B5025 | 2013 | Pratt & Whitney Canada PT6A-140 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed, written off | Unlawful Interference | Ilaga Airport (ILA) - Indonesia | Standing | - | Information is only available from news, social media or unofficial sources | A Cessna 208B Grand Caravan EX, registration PK-DPT was set on fire by Papua separatists at Ilaga Airport (ILA/WABL), Papua. The airplane was destroyed. | ||||||||||||
| 2021 | Thursday 24 June 2021 | 09:00 | Antonov An-2R | private | RA-01430 | 1G231-10 | 1988 | Shvetsov ASh-62IR | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | 3,5 km W of Zaboyskiy, Slavyansky district - Russia | Take off | Agricultural | Accident investigation report completed and information captured | The An-2 struck a mound of earth during takeoff from a temporary agricultural airstrip near Zaboyskiy, Krasnodar region, Russia. The right-hand main gear collapsed. The pilot was planning to conduct an aerial application flight on a rice field. It appeared that the pilots licence of the captain had expired in 2010. The accident with the An-2 RA-01430 aircraft occurred during takeoff from a landing strip with a non-uniform surface, which led to the aircraft yawing during the takeoff run. Correcting the directional sway, the PIC allowed a sharp operation of the brakes and wheels, which, in turn, led to an uncontrolled turn to the left, as a result of which the aircraft rolled out of the landing area and collided with a bunker. The contributing factors were most likely: - the PIC's interruptions in flight work and, as a consequence, the loss of flight skills in aircraft piloting; - failure to comply with the operator's RPM requirements in terms of training flight personnel on the An-2 aircraft; - lack of a tail wheel locking mechanism on the An-2 RA-01430 aircraft; - takeoff using the rated engine power with the flaps extended to the 20° position, which does not correspond to the Airplane Flight Manual of the An-2 aircraft, when taking off from a site with a non-uniform surface (take off at the engine takeoff power with the flaps deflected by 30°). | 2867 hours | MAK | Final report | d1391258d963dca8be93a3913824a2ec | Investigation completed | 6 months | |||||
| 2021 | Monday 21 June 2021 | Rockwell Sabreliner 65 | private | XB-OXV | 465-11 | 1980 | Honeywell TFE731-3R-1D | Fatalities: 0 / Occupants: 0 | 0 | Destroyed, written off | Other | within Jesús María Semprún - Venezuela | Standing | Illegal Flight | Little or no information is available | A Rockwell Sabreliner 65 was destroyed by Venezuelan law enforcement officers in Jesús María Semprún, Zulia. The aircraft had been used for transporting drugs and was located on an illegal airstrip, 8 km from the Colombian border. | ||||||||||||
| 2021 | Sunday 21 February 2021 | 11:48 | Beechcraft B300 King Air 350 | Nigerian Air Force - NAF | NAF201 | FL-585 | 2008 | Fatalities: 7 / Occupants: 7 | 0 | Destroyed, written off | Accident | NE of Abuja-Nnamdi Azikiwe International Airport (ABV) - Nigeria | Approach | Military | Abuja-Nnamdi Azikiwe International Airport (ABV/DNAA) | Minna Airport (MXJ/DNMN) | Information is only available from news, social media or unofficial sources | A Nigerian Air Force Beechcraft B300 King Air 350 airplane was destroyed when it impacted terrain shortly after takeoff following a reported loss of engine power near Nnamdi Azikiwe International Airport (ABV/DNAA), Abuja, Nigeria. The aircraft crashed on the final approach path of Abuja Airport runway 22. The seven people onboard perished. | ||||||||||
| 2021 | Saturday 5 June 2021 | 10:16 | Cessna 208B Supervan 900 | Paraclub Wiener Neustadt | N103AN | 208B0928 | 2001 | Honeywell TPE331-12JR | Fatalities: 0 / Occupants: 1 | 0 | Substantial, repaired | Accident | Wiener Neustadt West Air Base - Austria | Taxi | Parachuting | Wiener Neustadt West AB (LOXN) | Wiener Neustadt West AB (LOXN) | Information is only available from news, social media or unofficial sources | A Cessna 208B Supervan 900, registration N103AN, suffered a nose landing gear collapse while taxiing after landing at Wiener Neustadt West Air Base, Austria. All 5 propeller blades separated after the prop struck the ground. The aircraft was engaged in dropping skydivers and had just returned. | |||||||||
| 2021 | Friday 19 March 2021 | 13:25 | Antonov An-2T | Venezuela Flight Canaima | YV3312 | 1G157-07 | 1974 | Fatalities: 0 / Occupants: | 0 | Substantial | Accident | Kapaure - Venezuela | Landing | Cargo | La Paragua Airport (SVPU) | Information verified through data from accident investigation authorities | An Antonov An-2T, YV3312, sustained serious damage in an accident in Bolívar State, Venezuela. The right-hand main gear leg collapsed as the aircraft landed on an unprepared strip. Damage was sustained to the right-hand lower wing and propeller blades. The Civil Aviation Accident and Incident Investigation Board (JIAAC), as part of the investigations initially conducted, determined that the probable cause of the incident was the explosion of the right main gear shock absorber; the weight of the aircraft, as well as the inadequate operation of the aircraft in the landing maneuver on unprepared runways are considered as contributing factors. | 005/2021 | JIAAC Venezuela | Preliminary report | 956c68c243c701d812ce9ec00ea93839 | Preliminary report | ||||||
| 2021 | Tuesday 29 June 2021 | Airbus A350-941 | Air France | F-HTYH | 488 | 2021 | Rolls-Royce Trent XWB-84 | Fatalities: 0 / Occupants: | 0 | Accident | Paris-Charles de Gaulle Airport (CDG/LFPG) - France | Standing | Passenger - Scheduled | Toronto-Pearson International Airport, ON (YYZ/CYYZ) | Paris-Charles de Gaulle Airport (CDG/LFPG) | Accident investigation report completed and information captured | The aircraft arrived at a peak time for long-haul flight arrivals, which stretches emergency care and assistance resources. The distribution of persons with reduced mobility on board the aeroplane, between the different specialist vehicles upon arrival was not shared with the crew prior to the landing and the matter was only addressed after the other passengers had disembarked. The cabin crew then had to manage an unplanned situation involving a number of passengers wanting to board a specialist vehicle beyond the vehicle?s capacity, when all of the aeroplane?s occupants were fatigued from the flight.A PRM and her travel companion did not want to be separated and chose to use the disembarkation steps to stay together. The heavy workload associated with the confused situation, as well as the behaviour (described as aggressive) of the travel companion, prevented the crew members, the arrival agent and the assistance personnel from spotting in time that the passenger was descending the steps alone and unaided. She subsequently tripped during her descent and fell to the bottom of the steps.The emergency services were alerted in compliance with the procedures in force. The public emergency services took longer to arrive than the average response time for this type of intervention at Paris-Charles de Gaulle. The crew members considered the response time to be too long, likely due to the perceived severity of the medical emergency and to their knowledge of the usually very quick response times of the ARFF in the aeronautical domain.Due to the lack of updates on the expected arrival time of the emergency services, the captain decided to issue a MAYDAY to put an end to his uncertainty. This alert, which was issued several minutes before the arrival of the emergency services mobilised first, led to the subsequent mobilisation of substantial fire fighting resources. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | BEA | Final report | e14c3e7a356e8d1cbcbd3140afa93b3d | Investigation completed | ||||||
| 2021 | Sunday 14 February 2021 | 07:32 | de Havilland Canada DHC-6 Twin Otter 300 | Manta Air | 8Q-RAE | 617 | 1979 | Pratt & Whitney Canada PT6A-27 | Fatalities: 0 / Occupants: 9 | 0 | Substantial, repaired | Accident | Malé-Velana International Airport (MLE) - Maldives | Landing | Passenger - Scheduled | COMO Maalifushi Resort | Malé-Velana International Airport (MLE/VRMM) | Accident investigation report completed and information captured | The float-equipped DHC-6 aircraft operated by Manta Air was on a domestic passenger flight from Como Maalifushi Resort to Velana International Airport. The aircraft touched down on the water at Velana International Airport and veered right, causing the right-hand wing to dug into the water. The aircraft swung and flipped upside down. Causes / Contributing Factors: The AICC determines that the causes / contributing factors of this accident were: a. FO maintained a flatter than normal attitude of the aircraft at touch down; b. FO released the controls too early for an aircraft operated on floats due to his flying motor skills on a land aircraft which require release of the control at touchdown; c. Loss of control of the aircraft immediately after touchdown; d. PIC did not take over the controls from FO in a timely manner. | 78854 flights | 43932 hours | 2021/01 | AICC Maldives | Final report | 8d19661f21f2b4cf55e7ef459615452a | Investigation completed | 1 year 1 month | |
| 2021 | Saturday 19 June 2021 | 10:00 | Let L-410UVP-E | DOSAAF | RF-94603 | Fatalities: 5 / Occupants: 19 | 0 | Destroyed, written off | Accident | near Tanay Airfield - Russia | Unknown | Parachuting | Tanay Airfield | Tanay Airfield | Information is only available from news, social media or unofficial sources | A Let L-410UVP aircraft was destroyed in an accident after takeoff from Tanay Airfield, Kemerovo Region, Russia. The aircraft was operating the fourth flight of the day, carrying skydivers. Preliminary information suggests the no.2 engine failed shortly after takeoff. The aircraft impacted a field when the pilot attempted to turn back. | ||||||||||||
| 2021 | Wednesday 10 February 2021 | Airbus A320-214 (WL) | Flyadeal | HZ-FAB | 7867 | 2017 | CFMI CFM56-5B4/3 | Fatalities: 0 / Occupants: | 0 | Substantial, repaired | Unlawful Interference | Abha International Airport (OHB) - Saudi Arabia | Standing | Passenger - Scheduled | Little or no information is available | An Airbus A320-214, registration HZ-FAB, sustained substantial damage following a Houthi attack at Abha International Airport (OHB/OEAB), Saudi Arabia. | ||||||||||||
| 2021 | Friday 26 March 2021 | 16:30 | Beechcraft B200 Super King Air | West Wind Aviation Ltd. | 5Y-NJS | BB-837 | 1981 | Pratt & Whitney Canada PT6A-42 | Fatalities: 0 / Occupants: 3 | 0 | Destroyed, written off | Accident | Nairobi - Kenya | Approach | Private | Eldoret Airport (EDL/HKEL) | Nairobi-Wilson Airport (WIL/HKNW) | Information verified through data from accident investigation authorities | The aircraft made a forced landing on the Ngong Racecourse, located about 7 km west of Nairobi-Wilson Airport. The flight with one passenger and one pilot was on a private mission to from Nairobi to Kisumu, Eldoret and back to Nairobi. The aircraft departed Wilson Airport (HKNW) at 04:20 UTC and landed at Kisumu Airport (HKKI) at 05:02. It then departed HKKI to Eldoret (HKEL) at 11:42 and landed at 12:00 where it picked up one passenger. The flight then departed Nairobi at 12:47 with an estimated flight time of 40 minutes. The aircraft reached flight level 250 42NM from Eldoret VOR. The flight was then cleared to fly direct to GV VOR by Nairobi Area Control Centre. During descend to flight level 100 they encountered bad weather and the wings developed heavy icing. The captain activated the de-icing systems on the wings but the problem persisted. The situation prompted the captain to request Wilson Control to descend to the 'Monstry fix' for landing at HKNW which was approved. As the flight continued descending the left engine failed. The captain requested Wilson Tower for assistance. After 30 seconds, the right engine also failed. The captain elected to make an emergency landing at Ngong Racecourse. On landing, the left wing collided with trees, broke-off and separated together with the left engine and the left main landing gear. The aircraft turned clockwise through 180° and came to a full stop. All three onboard escaped unhurt but the aircraft was destroyed. | 12177 hours | ||||||||
| 2021 | Sunday 28 February 2021 | 15:07 | Douglas DC-3C | ALIANSA Colombia | HK-2006 | 43086 | 1946 | Pratt & Whitney R-1830-92 | Fatalities: 0 / Occupants: 3 | 0 | Substantial | Accident | Monfort Airport (MFB) - Colombia | Landing | Cargo | Mitú-Fabio Alberto León Bentley Airport (MVP/SKMU) | Monfort Airport (MFB) | Accident investigation report completed and information captured | The Douglas DC-3 of Aliansa had an accident while landing at Monfort Airport, Colombia. All three on board were unhurt. During the final approach to runway 17 at Monfort, the right landing gear hit the ground hard, causing the aircraft to substantially change its trajectory and skid on the left side. The two engines impacted the ground and the propellers became detached. The aircraft finally came to rest on the runway with substantial damage. The three occupants were unharmed and left the aircraft under their own power. Probable Cause(s): Abnormal contact of the aircraft before the runway, as a result of an approach made at too low a landing angle, in an attempt by the crew to make a short landing. Contributing Factors The investigation process determined that the accident was caused by a combination of the following factors: - Loss of situational awareness of the crew, who neglected the position of the aircraft in relation to the terrain during the approach, when attempting to make a short landing, probably caused by overconfidence and by the Pilot in Command's maladjustment to flying, who was making his first flights after a 70-day inactivity, caused by health problems. - Deficient condition of the safety zone and runway thresholds, without demarcation and with unevenness, which contributed to the initial damage to the aircraft, fracture of the right landing gear and which triggered other damages to the aircraft. - Deficient airfield conditions, as it lacked the minimum signage, such as demarcation of the beginning, end and margins of the usable runway, airfield limits and wind indication; these limitations increased the crew's workload as they lacked basic guidance to perform the landing in a limited field. - Lack of supervision by the operator, who did not have a flight readjustment procedure for crews after a significant inactivity, and, instead, scheduled the Pilot to perform a demanding operation to a runway with limited conditions on the first day of his return to flight. - Lack of risk management on the part of the operator, who despite knowing the risk conditions of the Monfort runway, did not have the necessary defenses for an acceptably safe operation on it, nor did it take the necessary steps to improve its conditions with the aerodrome operator, the government of the department of Vaupés. - Absence of surveillance of crews under stressful conditions, high workloads, taking into account that the company operates on restricted runways with a high probability of accidents, conditions that increase the risk considerably during the operation. - Absence of minimum signage on the runway, increasing the workload for the crew, considering that they never had a reference point to perform calculations or correct estimates during approach and landing. | 29968 hours | COL-21-08-GIA | Aerocivil | Final report | a13387d354beaa74b19889125a74cc9f | Investigation completed | 10 months | ||
| 2021 | Wednesday 12 May 2021 | 21:30 UTC | Boeing 737-8AS (WL) | Ryanair | EI-EGA | 38490/3096 | 2009 | CFMI CFM56-7B | Fatalities: 0 / Occupants: 168 | 0 | Accident | Alicante Airport (ALC/LEAL) - Spain | Standing | Passenger - Scheduled | Göteborg-Landvetter Airport (GOT/ESGG) | Alicante Airport (ALC/LEAL) | Accident investigation report completed and information captured | Ryanair flight FR4013, a Boeing 737-8AS, had departed from Gothenburg Airport (ESGG), landed at Alicante Airport (LEAL), and was parked on stand 16 of the apron. At approximately 23:30 h, the passengers began to disembark via the aircraft’s forward stairs. While disembarking, one of the passengers got one of the two suitcases he was carrying caught on the stairs and lost his balance. Being unable to grab the handrail, he fell from the top of the stairs and hit another passenger at the bottom of the stairs. The passenger who fell sustained serious injuries. The crew stopped the disembarkation via the forward stairs and redirected the rest of the passengers towards the rear exit of the aircraft. The ground personnel immediately assisted the injured passenger, and the dispatcher called for an ambulance, which took approximately 10 minutes to arrive and transferred the wounded passenger to hospital. At the hospital, the injured passenger received stitches to his head, and it was confirmed that he had broken his arm. The investigation has determined that the cause of the accident was the passenger’s decision to disregard the disembarkation instructions and descend the stairs with one suitcase in each hand. The stairs are approximately 0.62 m2 wide, which is sufficient for passengers to carry a single suitcase. However, as was shown in this case, it may not be enough to carry two suitcases, especially if they are separated a certain distance from the body. Moreover, anyone carrying two suitcases would be unable to grasp the handrail should they lose their balance. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | A-020/2021 | CIAIAC | Final report | cd70a53fc631010ebf94c24c20995eb8 | Investigation completed | ||||
| 2021 | Sunday 13 June 2021 | 23:21 | Boeing 737-8AS (WL) | Ryanair | EI-EVE | 35035/3920 | 2012 | CFMI CFM56-7B | Fatalities: 0 / Occupants: 155 | 0 | Accident | Málaga-Costa del Sol Airport (AGP/LEMG) - Spain | Standing | Passenger - Scheduled | Bruxelles-Sud Charleroi Airport (CRL/EBCI) | Málaga-Costa del Sol Airport (AGP/LEMG) | Accident investigation report completed and information captured | The Boeing 737-8AS aircraft, with registration EI-EVE, coming from the Belgian airport of Charleroi (EBCI), landed at Malaga airport (LEMG) and was parked at stand 48 on the apron. At 23:21 h, during the passenger disembarkation process, one of the passengers fell down the aircraft's forward stairs while disembarking. According to the testimonies collected from the aircraft crew, the passenger fell from the penultimate step and could not explain how it happened. The passenger's companion reported that sometimes the medications the passenger takes for his heart condition cause him to feel dizzy and he believed that this was the cause of his fall. The passenger was treated by the airport medical services. The airport medical service subsequently indicated that from the examination of the passenger there was no evidence and it could not be deduced that the fall was caused by the medication. The passenger was taken by ambulance to a hospital for further care and had to undergo surgery for a broken hip. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | A-025/2021 | CIAIAC | Final report | edc85aacb5315918f2e8101237579eaa | Investigation completed | ||||
| 2021 | Monday 1 March 2021 | 15:19 | Beechcraft B300 King Air 350i | Beidahuang General Airlines, opf China Met, Administration | B-10GD | FL-1014 | 2016 | Pratt & Whitney Canada PT6A-60A | Fatalities: 5 / Occupants: 5 | 0 | Destroyed, written off | Accident | Shanghu, Ji'an County - China | En route | Agricultural | Ganzhou Airport (KOW/ZSGZ) | Ganzhou Airport (KOW/ZSGZ) | Accident investigation report completed and information captured | A Beechcraft B300 King Air 350 on a cloud seeding flight crashed into a residential area in Ji'an County, China. All five occupants of the King Air were killed. Three houses were damaged, and one villager suffered minor injuries. The aircraft had departed Ganzhou Airport at 14:40 and crashed 39 minutes later. Findings: The investigation concluded that the cause of the accident was that the aircraft was flying in icy conditions for a long period of time during an artificial rainfall operation and the wings and propellers became seriously iced up. The aircraft was unable to effectively control the risk of icing, which resulted in the aircraft losing speed and entering a spin, eventually crashing to the ground and catching fire. Based on the casualties and damage to the aircraft, the incident constituted a major general aviation accident of aircraft crew origin. The investigation also found that the aircraft had been modified in such a way that the relevant data was not available and that the crew did not handle the spin properly. | 398 flights | 672 hours | 20210301TFSQ01 | CAAC | Final report | 105659f87494bc8a8842548572f79179 | Investigation completed | 7 months | |
| 2021 | Wednesday 12 May 2021 | 10:23 | Swearingen SA226-TC Metro II | Key Lime Air | N280KL | TC-280 | 1978 | Garrett TPE331-10UA-511G | Fatalities: 0 / Occupants: 1 | 0 | Substantial, written off | Accident | 5,9km N of Denver-Centennial Airport, CO (APA) - United States of America | Approach | Ferry/positioning | Salida Airport, CO (SLT/KANK) | Denver-Centennial Airport, CO (APA/KAPA) | Accident investigation report completed and information captured | A privately registered Cirrus SR22 (N416DJ) and a Key Lime Air Swearingen Metro II (N280KL) collided on approach to Denver-Centennial Airport, Colorado, USA. The Cirrus departed Denver-Centennial Airport (APA) for a local flight about 09:21, and the Metro II departed the Salida Airport (SLT) about 09:56. The Cirrus was performing a right-hand traffic pattern for runway 17R at APA, and N280KL was on final approach for runway 17L at APA, when the collision occurred. Both airplanes were in communication with air traffic control during their respective approaches to the airport. About 10:22:43, the Metro II was about 5.5 nm from APA and had completed a right turn to align with the final approach course to runway 17L. At this same time, the Cirrus was on the downwind leg of the right-hand traffic pattern for runway 17R just before he commenced a right turn to the base leg of the traffic pattern. The Metro continued its approach and remained aligned with runway 17L. The Cirrus continued the right-hand traffic pattern through the base leg, and then began to turn toward the final approach course for the runway. The airplanes collided at 10:23:53 when they were about 3.2 nm from APA. The Metro was aligned with runway 17L while the Cirrus was turning from base to final and heading about 146° when the collision occurred. After the impact, N280KL declared an emergency, continued to APA, and landed successfully on runway 17L without further incident. The Cirrus pilot reported that the airplane was not controllable after the impact and he deployed the Cirrus Airframe Parachute System (CAPS). The aircraft came to rest about 3 nm north of APA. Probable Cause and Findings: The Cirrus pilots failure to maintain the final approach course for the assigned runway, which resulted in a collision with the Swearingen which was on final approach to the parallel runway. Contributing to the accident was the failure of the controller to issue a traffic advisory to the Swearingen pilot regarding the location of Cirrus, and the Cirrus pilots decision to fly higher than recommended approach speed which resulted in a larger turn radius and contributed to his overshoot of the final approach course. | 37895 flights | 29525 hours | CEN21FA215A | NTSB | Final report | 35cd9586bf05336ca42646cf14c46ad3 | Investigation completed | 1 year and 10 months | |
| 2021 | Sunday 4 July 2021 | 11:30 | Lockheed C-130H Hercules | Hukbong Himpapawid ng Pilipinas (Philippine Air Force) | 5125 | 5125 | 1988 | Fatalities: 50 / Occupants: 96 | 3 | Destroyed, written off | Accident | Patikul, Sulu - Philippines | Landing | Military | Cagayan de Oro-Lumbia Airport (CGY/RPML) | Jolo Airport (JOL/RPMJ) | Information is only available from news, social media or unofficial sources | A Philippine Air Force Lockheed C-130H Hercules crashed and caught fire while during an attempted landing at Jolo Airport, Philippines. The Hercules transport plane originated from Villamor Air Base, located at the Manila International Airport and flew to Cagayan de Oro-Lumbia Airport in order to fly troops from there to Jolo Airport. The aircraft touched down on runway 09, which is 1800 m long and apparently overshot the runway. It struck at least two houses and burst into flames as it came to rest in a coconut plantation. Of the 96 occupants, 49 were killed. Additionally, three civilians are reported to have died on the ground. | ||||||||||
| 2021 | Monday 8 February 2021 | 10:30 LT | Airbus A320-271N | Spirit Airlines | N918NK | 9259 | 2019 | Pratt & Whitney PW1127G-JM | Fatalities: 0 / Occupants: 96 | 0 | Accident | Fort Lauderdale, Florida - United States of America | En route | Passenger - Scheduled | Accident investigation report completed and information captured | The airplane experienced an abrupt maneuver during initial descent and a flight attendant fractured their ankle. According to the flight crew, just prior to top of descent the captain informed the flight attendants to prepare the cabin early because there was weather in the vicinity of the arrival airport. Shortly after that, the first officer (FO), who was the pilot flying, initiated the descent. Air traffic control then cleared the flight to a lower altitude and requested they increase their descent. The FO complied, and increased their vertical speed, however, at some point, he engaged "open descent" mode. The FO saw the airspeed increasing towards red line and he pulled back on the stick and the autopilot disengaged. The captain said he then took control using the autopilot disconnect/priority switch and applied aft stick pressure to return the airplane to a normal descent pitch attitude to prevent an overspeed. According to the flight crew, the airplane was in clear air and smooth flight conditions when the event occurred. Two flight attendants (FA) in the aft galley, were thrown into the air and onto the floor. The captain was notified that one of the FAs had been injured and would need assistance when they got to the gate. A deadheading FA assumed the injured FAs duties for the remainder of the flight. After landing, the FA was transported to a local hospital and diagnosed with a fractured ankle. Probable Cause: An abrupt flight control input by the flight crew during descent that caused a flight attendant to fall and fracture their ankle. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | DCA21LA082 | NTSB | Final report | 4d4819343d441f982eaf8ed190b0638c | Investigation completed | 1 year and 5 months |
全球航空器事故数据
| Year | Date | Time | Type | Owner/operator | Registration | MSN | Year of manufacture | Engine model | Fatalities | Other fatalities | Aircraft damage | Category | Location | Phase | Nature | Departure airport | Destination airport | Confidence Rating | narrative | notes | Cycles | Total airframe hrs | Report number | Investigating agency | Download report | Accident investigation PDF | Status | Duration |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 年份 | 日期 | 时间 | 机型 | 所有者/经营者 | 飞机号 | MSN | 制造年份 | 发动机型号 | 死亡人数 | 其他死亡人数 | 飞机损坏情况 | 事件类型 | 地理位置 | 出事阶段 | 飞机用途 | 始发机场 | 到达机场 | 信用评级 | 事件说明 | 备注 | 飞行次数 | 总飞行时长 | 报告编号 | 调查机构 | 下载报告 | 调查报告 | 调查进度 | 调查时长 |
| 2020 | Saturday 25 April 2020 | 12:15 | Aeronca 7AC Champion | Private | N83216 | 7AC-1877 | 1946 | Continental A65-8F | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Enosburg, VT - United States of America | Landing | Private | South Hero, VT (VT26) | Enosburg, VT | Accident investigation report completed and information captured | The pilot reported that, during the landing roll on a private grass airfield, the main landing gear dug into soft grass, and the airplane nosed over. The airplane sustained substantial damage to the right-wing lift strut. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Probable Cause: The pilot's improper decision to land on unsuitable terrain, which resulted in a nose-over. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 4573 hours | ERA20CA159 | NTSB | Final report | dba924a4b33c6d6359c9baa63c062249 | Investigation completed | 3 months | |
| 2020 | Wednesday 5 August 2020 | Javelin Wichawk | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Lismore Airport, NSW (YLIS) - Australia | Unknown | Private | Lismore Airport, NSW (YLIS) | Information verified through data from accident investigation authorities | During landing in wet grass parallel to the runway, the wheels dug into soft ground and the aircraft pitched over coming to rest inverted. The aircraft was substantially damaged and the pilot sustained minor injuries. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ATSB | ||||||||||||||
| 2020 | Sunday 16 August 2020 | 14:54 UTC | Aerotechnik L-13SEH Vivat | Private | N334BA | 940517 | 1994 | Fatalities: 0 / Occupants: 2 | 0 | Substantial | Accident | William 'Tiny' Zehnder Field Airport (66G), Saginaw County, MI - United States of America | Take off | Private | Frankenmuth, MI (66G) | Frankenmuth, MI (66G) | Accident investigation report completed and information captured | The pilot reported that following a landing and back-taxi in a motor glider, he failed to stow the speed brake prior to attempting a subsequent takeoff. During the takeoff attempt, the glider would not climb out of ground effect. The motor glider departed the end of the runway and impacted terrain which resulted in substantial damage to the fuselage. Probable Cause: The pilot's failure to stow the speed brake prior to attempting takeoff. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | CEN20CA337 | NTSB | Final report | 333be449d713f47f063f5d8eb3392e47 | Investigation completed | ||||
| 2020 | Tuesday 27 October 2020 | 10:33 LT | Hughes 369D | Windward Aviation Inc | N58251 | 880317D | 1978 | Rolls Royce 250-C20B | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | near Nuuanu Reservoir, Honolulu, Oahu, HI - United States of America | En route | Cargo | Oahu-Dillingham Airfield, HI (HDH/PHDH) | Kahului Airport, HI (OGG/PHOG) | Accident investigation report completed and information captured | During longline operations, the helicopter lost partial power and the main rotor rpm decreased. The pilot jettisoned the external load and the helicopter impacted trees, resulting in substantial damage. The engine continued to run after impact, and the pilot performed an emergency engine shutdown. Examination revealed that the start fuel pump was damaged. The circlip and pin that held the flapper valve in place in the bypass inlet were missing, and the flapper valve was wedged against the sidewall of the bypass inlet, obstructing about 50% of the discharge port. The pin was located in the fuel line between the start fuel pump and the engine-driven fuel pump; the circlip was not found. No other mechanical malfunctions were found that would have precluded normal operation. The pin found in the fuel line and obstruction from the flapper valve located in the start fuel pump likely induced restricted fuel flow from the engine-driven fuel pump to the engine, which resulted in a partial loss of engine power. Based on the available evidence, the reason for the separation of the circlip from the pin could not be determined. Probable Cause: A partial loss of engine power due to an obstructed fuel line as a result of the separation of the circlip from the pin used on the fuel start pump. The reason for the circlip separation could not be determined based on the available evidence. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 20345 hours | ANC21LA003 | NTSB | Final report | 21e3d60d08948f010ee098e5ac7f175f | Investigation completed | 1 year and 8 months | |
| 2020 | Friday 21 August 2020 | Pilatus PC-12/45 | Fat City Air Service LLC | N8YU | 413 | 2001 | P&W Canada PT6A-67 | Fatalities: 0 / Occupants: | 0 | Unknown | Aspen Pitkin County Airport (ASE/KASE), CO - United States of America | Taxi | Unknown | Information is only available from news, social media or unofficial sources | Aircraft struck Raytheon Hawker 800, N489BM, while taxiing. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||||
| 2020 | Thursday 2 January 2020 | 10:25 | Cirrus SR22 GTS | Cornerstone Aviation LLC | N323SR | 2271 | 2006 | Continental IO-550-N | Fatalities: 0 / Occupants: 2 | 0 | Substantial | Accident | Kenansville, NC - United States of America | En route | Private | Worcester Airport, MA (ORH/KORH) | Elizabethtown-Curtis L Brown Jr Field, NC (KEYF) | Accident investigation report completed and information captured | The pilot reported that, during a cross-country flight, he heard a pop from the engine, and it subsequently stopped producing power; however, the engine continued to run, and the propeller continued to rotate. The pilot attempted to troubleshoot the loss of power; however, power was not restored. Subsequently, the pilot activated the airplane’s parachute system and the airplane impacted trees and terrain, resulting in substantial damage to the airframe. Postacccident examination of the engine revealed that the camshaft fractured at one of its four oil transfer holes. As a result, camshaft continuity was lost, and the engine was partially unable to produce power. Forensic examination of the fracture surface revealed that the fracture occurred due to fatigue that initiated from a burr at the corner of an oil transfer hole. The extent of fatigue crack growth through the cross-section suggested the overall torsion load on the camshaft was relatively low as the crack grew. However, a burr at the edge of a hole is a feature that is known to reduce component fatigue life. The burr was deformed and coated, consistent with forming during a peening operation and before the manganese phosphate coating had been applied. A similar burr was also observed on the adjacent oil transfer hole in the camshaft. The presence of a burr suggests the corner of the hole was not properly broken before the part was peened during manufacturing, leading to deformation of a sharp corner during the peening operation. Probable Cause: A fatigue failure of the camshaft due to a manufacturing defect, which resulted in a partial loss of engine power. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | 3774 hours | ERA20LA064 | NTSB | Final report | 9bb962bf5514931a56ca757cc4cd45ca | Investigation completed | 2 years and 3 months | |
| 2020 | Saturday 9 May 2020 | 11:10 LT | Ayres S-2R-G1 Turbo Thrush | Farmers Services | N2245S | G1-106 | Airesearch TPE331 | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Imperial County Airport (KIPL/IPL), CA - United States of America | Landing | Agricultural | Imperial County Airport, CA (IPL/KIPL) | Imperial County Airport, CA (IPL/KIPL) | Accident investigation report completed and information captured | Shortly after landing, the airplane veered left. The pilot used right rudder and applied right brake to counteract the turn, and the airplane began to straighten out. Immediately after, he felt that the right brake was not working, and the airplane again made an immediate turn to the left. The airplane exited the left side of the runway, the left-wing tip impacted the ground, and the airplane spun to the left, which resulted in a collapse of the left main landing gear and substantial damage to the left wing. An examination of the right brake assembly revealed that the center piston O-ring was damaged, and the right brake hydraulic fluid reservoir was empty. These discrepancies resulted in the loss of brake pressure and subsequent failure of the right brake. Probable Cause: The pilot's loss of control during a landing roll due to a failure of the main O-ring in the right brake assembly, which resulted in a loss of brake pressure and subsequent brake failure. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | WPR20LA172 | NTSB | Final report | b5c6b969882f429aca48aedaaf224c9a | Investigation completed | 2 years 1 month | |||
| 2020 | Thursday 17 September 2020 | c. 10:21 | Cessna 152 II | Lahore Flying Club (LFC) | AP-BEO | 15285762 | Fatalities: 0 / Occupants: 1 | 0 | Minor | Accident | Lahore/Walton Airport (OPLH) - Pakistan | Landing | Training | Allama Iqbal International Airport Lahore | Lahore/Walton (OPLH) | Information is only available from news, social media or unofficial sources | The nose landing gear collapsed on touchdown. The first solo student pilot was not injured. Preliminary information suggests the pilot was making video/taking photos of the flight including landing. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||
| 2020 | Monday 8 June 2020 | Airbus A350-941 | LATAM Brasil | PR-XTI | 250 | 2018 | Rolls-Royce Trent XWB-84 | Fatalities: 0 / Occupants: | 0 | Minor | São Paulo-Guarulhos International Airport, SP (GRU/SBGR) - Brazil | Standing | Passenger | Information is only available from news, social media or unofficial sources | A LATAM Airlines Brasil Airbus A350-900 suffered minor damage to the no.2 engine fan cowl when a vehicle impacted the nacelle during ground operations. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||||
| 2020 | Friday 10 January 2020 | 12:40 LT | Mil Mi-8T | KrasAvia | RA-22901 | 98420092 | 1984 | Fatalities: 0 / Occupants: 17 | 0 | Incident | Krasnoyarsk Krai, Siberia - Russia | En route | Passenger | Syndassko | Khatanga | Information verified through data from accident investigation authorities | The helicopter made an emergency landing after engine failure. There are said to be no fatalities. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||
| 2020 | Monday 5 October 2020 | 11:15 | Cessna 180 Skywagon | Fatalities: 0 / Occupants: | 0 | Substantial | Accident | Saarmund Airport (EDCS) - Germany | Take off | Unknown | Saarmund | Information verified through data from accident investigation authorities | During takeoff roll, the aircraft collided with a deer running across the runway. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | BFU | |||||||||||||
| 2020 | Sunday 29 March 2020 | Luscombe 8A | Private | N71899 | 3326 | Fatalities: 0 / Occupants: 1 | 0 | Unknown | 24330 Snake River Rd, Asotin, WA - United States of America | Landing | Unknown | Information is only available from news, social media or unofficial sources | The aircraft experienced a loss of directional control and subsequent runway excursion upon landing at Snake River Rd, Asotin, Washington. The airplane came to rest inverted, sustaining unspecified damage, and the sole pilot onboard was not injured. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| 2020 | Tuesday 4 August 2020 | Harbin Y-12-II | Kenya Air Force - KAF | KAF128 | 0097 | 1997 | Fatalities: 0 / Occupants: 10 | 0 | Substantial | Accident | Dhobley Airstrip - Somalia | Take off | Military | Dhobley Airstrip | Nairobi-Moi Air Base (HKRE) | A Kenya Air Force Harbin Y-12-II suffered an accident at Dhobley Airstrip in Somalia. There were no serious injuries to the 10 people on board but the aircraft was seriously damaged. The landing gear as well as the left-hand wing have collapsed. The accident happened after the aircraft had taken off from Dhobley Airstrip after delivering supplies to U.N. Amisom forces. | ||||||||||||
| 2020 | Monday 20 January 2020 | 12:20 | Cessna 150G | Private | N4763X | 15064813 | 1966 | Continental O-200 SERIES | Fatalities: 1 / Occupants: 1 | 0 | Destroyed | Accident | near Cherokee County Airport (JKV/KJSO), Jacksonville, TX - United States of America | En route | Private | Jacksonville-Cherokee County Airport, TX (JKV/KJSO) | Accident investigation report completed and information captured | On January 20, 2020, about 1220 central standard time, a Cessna 150G airplane, N4763X, was substantially damaged when it was involved in an accident near Jacksonville, Texas. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Radar information showed that, after departing in day visual meteorological conditions, the pilot climbed the airplane to a maximum altitude of about 1,600 ft mean sea level (msl) before entering a gradual descent. The last radar return showed the airplane at a speed of 92 knots and altitude about 900 ft msl. The wreckage was found in the vicinity of a 1,586-ft-tall television tower, and its distribution was consistent with the left wing contacting one of the tower’s guy wires, resulting in a separation of the outboard section of the left wing. The airplane subsequently impacted terrain in a nose-down, near vertical attitude and was destroyed by impact. Examination revealed no evidence of mechanical malfunctions or anomalies that would have precluded normal operation of the airplane or engine. The circumstances of the accident are consistent with the pilot’s failure to maintain clearance from tower guy wires while flying at low altitude. Probable Cause: The pilot’s failure to maintain clearance from guy wires associated with a tower while maneuvering at low altitude. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | WPR20FA067 | NTSB | Final report | b085a33513575b2602831c2fc024b777 | Investigation completed | 2 years and 4 months | |||
| 2020 | Friday 25 September 2020 | 17:30 LT | Piper PA-46R-350T Matrix | Coadmere Inc | N920X | 4692206 | 2014 | Lycoming TIO-540-AE2A | Fatalities: 0 / Occupants: 2 | 0 | Substantial | Accident | near Rogers Municipal Airport (ROG/KROG), Benton County, AR - United States of America | En route | Training | Rogers Municipal Airport-Carter Field, AR (ROG/KROG) | Rogers, AR | Accident investigation report completed and information captured | The pilot reported that while practicing slow flight and approach-to-stall maneuvers at 5,500 ft msl with the landing gear and flaps fully extended, the stall warning horn sounded, and the airplane began buffeting. The pilot advanced the throttle and lowered the nose of the airplane to recover from the maneuver, when the right wing dropped, the airplane rolled over inverted, and subsequently entered a right spiral dive. The pilot reported that after 5 to 7 turns he regained control of the airplane leveling at 500 to 700 ft agl. The pilot returned to the airport and landed without further incident. Postaccident examination revealed the airplane sustained substantial damage to the fuselage above the left wing's trailing edge, below and forward of the empennage, above the right horizontal stabilizer, and at the tail cone below the right and left horizontal stabilizers. The pilot reported there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Probable Cause: The pilot's inadvertent loss of aircraft control, resulting in substantial damage to the airframe during the spin recovery. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 815 hours | CEN20LA430 | NTSB | Final report | b19d985dc8ac7e587ad33e7ec2946c1f | Investigation completed | 12 months | |
| 2020 | Saturday 25 April 2020 | 11:00 | Fly Synthesis Storch | Aeroklub “Josip Križaj” Ajdovščina | S5-PFA | F1BC4940C32K | Fatalities: 0 / Occupants: 2 | 1 | Destroyed | Ajdovščina - Slovenia | En route | Private | Ajdovšcina Airport (LJAJ) | Ajdovšcina Airport (LJAJ) | Information is only available from news, social media or unofficial sources | A paraglider collided with a Fly Synthesis Storch ultralight. Both crashed. The aeroplane pilot pulled the rescue parachute however they were flying to low for the parachute to fully deploy. The two occupants of the ultralight plane suffered heavy casualties but survived the crash. The paraglider died in the crash. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | |||||||||||
| 2020 | Wednesday 2 December 2020 | 09:25 | Boeing 737-529 | Air Djibouti | EY-560 | 26538/2298 | 1992 | CFMI CFM56-3B1 | Fatalities: 0 / Occupants: 39 | 0 | Substantial, repaired | Accident | Garowe Airport (GGR) - Somalia | Landing | Passenger - Scheduled | Hargeisa Airport (HGA/HCMH) | Garowe Airport (GGR/HCMW) | Information verified through data from accident investigation authorities | An Air Djibouti Boeing 737-529, EY-560, suffered a right-hand main landing gear collapse on landing at Garowe Airport, Puntland, Somalia. The aircraft operated on a flight from Djibouti to Mogadishu, Somalia, with en route stops at Hargeisa and Garowe. The pilot conducted a visual approach and the aircraft was stable. At low altitude the aircraft experienced a windshear and hit the runway hard. The root cause of the accident is loss of control of aircraft. The contributory factor was windshear. | 42964 hours | ||||||||
| 2020 | Tuesday 7 July 2020 | 14:35 | Schleicher ASW-19B | OK-7984 | 19420 | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Hodkovice (LKHD) - Czech Republic | Landing | Private | Hodkovice nad Mohelkou Airport (LKHD) | Hodkovice nad Mohelkou Airport (LKHD) | Accident investigation report completed and information captured | On landing, the aircraft bounced several times and then touched down hard. This caused damage to the nose, the cockpit glazing and the tail. The cause of the accident was most likely the pilot changing the control lever of the aerodynamic brakes and the landing gear lever. As a result, the approach and landing took place at high speeds. The pilot did not successfully solve this situation. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | UZPLN | Final report | 13201a6d9baf3a4335cefcbd0a8e9e8d | Investigation completed | 8 months | ||||||
| 2020 | Saturday 30 May 2020 | 19:32 | Cessna 182C Skylane | SkyConcept | D-EYST | 52478 | 1959 | Fatalities: 0 / Occupants: 1 | 0 | Destroyed | Accident | Langenhahn, Rhineland-Palatinate - Germany | Approach | Parachuting | Ailertchen Airfield (EDGA) | Ailertchen Airfield (EDGA) | Accident investigation report completed and information captured | After dropping four parachutists, the engine failed during descent. Subsequently, the aircraft collided with an overhead power line and crashed into the roof of a residential building. The pilot was injured and the aircraft destroyed. Also the electricity of 50.000 people was cut off. Conclusions: The accident was caused by the pilot experiencing an engine failure due to an interrupted fuel supply, and the aircraft colliding with obstacles during the subsequent emergency landing. The following factors contributed to the accident: - Non-compliance with the manual requirements for the descent procedure with the low fuel quantity present in the wing tanks - Attempts to start the engine without first selecting and approaching an emergency landing area - Too low an altitude at the time of engine failure to safely reach the airport in a glide | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | BFU | Final report | bc49249ed207b196706bd1d8da40f09e | Investigation completed | 3 years and 3 months | ||||
| 2020 | Sunday 11 October 2020 | 14:42 | Cessna FRA150L Aerobat | Private | G-CIIR | FRA15000187 | 1973 | Continental O-240-A | Fatalities: 1 / Occupants: 1 | 0 | Destroyed | Accident | North of Troutbeck, between Keswick and Penrith, Cumbria - United Kingdom | Take off | Private | Troutbeck Airfield, Keswick, Cumbria | Repton/Gamston Airport (EGNE) | Accident investigation report completed and information captured | The aircraft, a Cessna FRA150L Aerobat (G-CIIR) landed at Troutbeck Airfield with its pilot and a passenger without the required permission. As the conditions on the day meant the aircraft’s takeoff performance from Troutbeck would be marginal, the airfield owner instructed the pilot to depart solo in order to improve the aircraft’s performance by reducing its takeoff weight. On the subsequent takeoff the aircraft was seen to depart controlled flight seconds after getting airborne and strike the ground. The pilot was fatally injured. The investigation identified a number of shortcomings with the preparation for the flight that contributed to the accident. In addition, opportunities were missed to prevent the accident because the pilot did not heed the advice not to operate into grass, performance-limiting airfields, did not obtain PPR and was probably not on the correct radio frequency on arrival. It is likely that the pilot did not fasten his shoulder harness, against the strong advice of his instructor, and this action may have meant the accident became unsurvivable. Flying for any pilot is a continual learning process whether they are newly qualified or very experienced. However, newly qualified pilots should be very careful to make sure they fly within the limits of their experience. This accident highlights the fact that thorough preparation is essential for every flight, and accidents can happen if short cuts are taken or good advice is not heeded. =Damage sustained to airframe= Per the AAIB Report the airframe was "Destroyed". The CAA agreed with this conclusion, as the registration G-CIIR was cancelled, and the airframe de-registered, on 18 May 2021 as "destroyed" | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | AAIB-26991 | AAIB | Final report | 117fca6eda4446b661c31e1c7c2016b0 | Investigation completed | 1 year 1 month | ||
| 2020 | Wednesday 18 March 2020 | 13:30 | Boeing 737-33A | Aerolínea Estelar | YV-642T | 27267/2600 | 1994 | CFMI CFM56 | Fatalities: 0 / Occupants: 118 | 0 | Cacique Aramare Airport (SVPA), Puerto Ayacucho, Amazonas - Venezuela | En route | Passenger - Scheduled | Buenos Aires/Ezeiza-Ministro Pistarini Airport, BA (EZE/SAEZ) | Caracas-Simón Bolívar International Airport (CCS/SVMI) | Information is only available from news, social media or unofficial sources | Estelar Flight ES-8568 with 118 passengers on board, (crew members not available) was diverted to Puerto Ayacucho’s Cacique Aramare Airport due pressurisation system issues, according to airline statements. Landed safely at 13:30 local time (17:30 Z). | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||
| 2020 | Friday 28 August 2020 | c. 1045 UTC | de Havilland Canada DHC-8-402Q Dash 8 | SpiceJet | VT-SUL | 4400 | P&W Canada PW150 | Fatalities: 0 / Occupants: | 0 | Serious incident | Cochin International Airport (COK/VOCI) - India | Approach | Passenger - Scheduled | Bengaluru (Bangalore) International Airport (BLR/VOBL) | Cochin International Airport (COK/VOCI) | Information verified through data from accident investigation authorities | SpiceJet flight SG7077, a DHC-8-402Q (VT-SUL) and Qatar Airways flight QR7477, an Airbus A320-232 (A7-AHA) were involved in a serious airprox incident while on approach to Cochin Airport, India. Minimum separation was reduced to 2 NM horizontally and 500 feet vertically. Probable Cause of the Incident. Non adherence to ATC instructions by the crew of SEJ7077. Contributory factor: During descent to 3000 ft , pilot flying did not engage ‘ALT SEL’ and the same was not monitored by Pilot monitoring also. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | AAIB India | Final report | c59c52e0ef151797c749880cb481ef46 | Investigation completed | 6 months | |||||
| 2020 | Monday 28 December 2020 | 20:45 LT | Beechcraft B80 Queen Air 8800 | Bemidji Aviation Services | N134BA | LD-202 | 1964 | Lycoming IGSO-540-B1A | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Chandler Field Airport, Alexandria, MN - United States of America | Take off | Unknown | Chandler Field (AXN/KAXN), Alexandria, MN | Minneapolis-St. Paul International Airport, MN (MSP/KMSP) | Accident investigation report completed and information captured | The pilot reported that the takeoff was conducted below the airplane's maximum gross weight. Although his written statement and interviews indicated that there was no frost on the airplane during his preflight examination, the police report of the accident stated that the pilot told the responding officer immediately after the accident that there could have been frost on the wings of the airplane. The airport manager who responded to the accident scene reported that all airplane surfaces were covered with frost when he arrived a short time after the accident. The pilot reported that during the takeoff the rotation speed was between 82 and 85 knots. The pilot's reports of what happened after rotation were consistent, indicating that the airplane began to veer to the right and began shaking. The pilot stated that he did not hear a stall warning and that the airplane did not feel like it was in a stall. While the pilot tried to correct the veering to the right, the airplane pitched down, turned left, and the left wing struck the ground. The airplane then bounced, the right wing struck the ground, and the right main landing gear collapsed. The left wing sustained substantial damage. Airplane performance data indicated that the proper rotation speed for a maximum gross weight takeoff was 96 knots. The power-on stall speed at maximum gross weight for the airplane with landing gear extended and flaps retracted was not specifically listed but would have been between 78 and 91 knots based on available performance data from the airplane owner's manual. In addition, the performance data would have been for an airplane without frost on it; frost would have increased the speed. Based on the available evidence it is likely that the airplane had frost contamination, which the pilot ignored. He then rotated the airplane during the maximum gross-weight takeoff at a speed below the airplane manufacturer's recommended rotation speed. The slower speed in combination with degraded performance due to frost contamination of the airplane's flying surfaces resulted in exceedance of the critical angle of attack, resulting in an aerodynamic stall and subsequent impact with the ground. Probable Cause: The pilot's decision to attempt takeoff with frost covering the airplane and rotating below the published rotation speed, which led to exceedance of the airplane's critical angle of attack and an aerodynamic stall. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 18126 hours | CEN21LA101 | NTSB | Final report | 501eed514ef6664c97e0abb0c88f6acf | Investigation completed | ||
| 2020 | Saturday 31 October 2020 | 14:00 | Robin DR.400/140B | Vliegclub Rotterdam (VCR) | PH-NSC | 2611 | 2006 | Fatalities: 0 / Occupants: | 0 | Minor | Accident | Rotterdam/The Hague Airport (RTM/EHRD) - Netherlands | Landing | Unknown | Rotterdam/The Hague Airport (RTM/EHRD) | Rotterdam/The Hague Airport (RTM/EHRD) | Information verified through data from accident investigation authorities | During landing the pilot lost control of the aeroplane, whereupon it veered off the runway and hit a PAPI light unit with the left wing, before it came to a stop. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | Dutch Safety Board | ||||||||
| 2020 | Sunday 14 June 2020 | Schempp-Hirth Ventus 2B | OY-HXB | 72 | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Hammer (EKHM)r - Denmark | Take off | Private | Hammer (EKHM) | Hammer (EKHM) | Information verified through data from accident investigation authorities | During the winch launch for a thermal flight the glider got a strong crosswind shortly after take off in about 2 meters height. One wing got ground contact and the glider turned and hit the ground hard. The AIBN has identified the following factors that are presumed to have influenced the course of events: - A language barrier, between the winch driver (who was of foreign origin and had limited Danish skills) and the pilot, may have resulted in a misunderstanding about the pilot's intention of a good acceleration at the beginning of the start but a minor move later. - The winch manager's current training condition is estimated during the course of events to have affected the winch operator's operation of the winch. - The glider had a smaller rear rudder effect at low speeds compared to other types of gliders. - Poor acceleration resulted in a long starting run at low speed. The fact that the glider got into the air, at a relatively low speed, may have made it more difficult for the pilot to control the glider. - The glider may have been in lateral imbalance. The center of gravity of the left wing was possibly further located than the center of gravity of the right wing, due to water that had moved outwards in the wing. - A markedly variable headwind component, due to offensive winds from changing directions, probably caused the glider to unexpectedly lose lift. - A subsequent skewed winch move led to loss of control of the glider from low flight altitude. - The pilot did not interrupt the start of the winch launch in time and disconnected from the starting wire. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | HCLJ | Final report | 30d3a195c0d482dc124d0c32666dc73e | Investigation completed | 8 months | |||||||
| 2020 | Wednesday 30 September 2020 | 16:28 | Robinson R22 | Private | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Hawkwood, W of Maryborough, QLD - Australia | En route | Agricultural | Information verified through data from accident investigation authorities | During aerial mustering operations, the engine lost power and the helicopter was unable to maintain height. The helicopter made contact with trees and subsequently collided with terrain resulting in substantial damage. The pilot was uninjured. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ATSB | |||||||||||||
| 2020 | Saturday 31 October 2020 | Cessna TU206C Super Skywagon | private | C-FMQG | U2061101 | 1968 | Continental TSIO-520-C | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | 28 nm NNW of Bella Coola (CYBD), BC - Canada | En route | Private | Anahim Lake (CAJ4), BC | Bella Coola (CYBD), BC | Information verified through data from accident investigation authorities | A privately operated Cessna 206 aircraft, was conducting a flight from Anahim Lake (CAJ4), BC to Bella Coola (CYBD), BC with a sole pilot on board. While the aircraft was flying at approximately 2000 feet ASL, over the Dean Channel, the engine (Teledyne Continental TSIO-520 -C) experienced a complete power loss. The aircraft was ditched into the channel near the mouth of the Dean River. Upon entry into the water the aircraft began to sink and the pilot quickly exited. The pilot was wearing a manual inflation PFD which he inflated upon exit from the aircraft. The aircraft then sank below the water surface while the pilot, wearing his PFD, swam to the shore line where he was able to summon assistance from a nearby cabin. The pilot sustained minor injuries. An ELT signal was not received. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | TSB | ||||||||
| 2021 | Tuesday 24 August 2021 | 10:09 LT | Pilatus PC-21 | Pilatus Flugzeugwerke | HB-HZD | 102 | 2005 | Fatalities: 0 / Occupants: 2 | 0 | Serious incident | Emmen - Switzerland | Unknown | Training | Buochs Airport (BXO/LSZC) | Buochs Airport (BXO/LSZC) | Information verified through data from accident investigation authorities | A Pilatus PC-21 (HB-HZD) and a Cessna 182T (HB-TLM) were involved in a serious airprox incident near Emmen, Switzerland. The two aircraft were at approximately the same altitude with converging flight paths, leading to a dangerous airprox. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | STSB | |||||||||
| 2021 | Thursday 10 June 2021 | 19:10 | Piper PA-32-260 Cherokee Six | G&M Aircraft Inc | N3793W | 32-720 | 1966 | Lycoming O-540-E4B5 | Fatalities: 0 / Occupants: 2 | 0 | Substantial | Accident | near Lafayette, CO - United States of America | En route | Training | Broomfield-Rocky Mountain Metropolitan Airport, CO (BJC/KBJC) | Lafayette, CO | Accident investigation report completed and information captured | The purpose of the instructional flight was for the pilot to receive a checkout in the airplane. Before the flight, the right wing main fuel tank contained 16-18 gallons of fuel, the left wing main fuel tank contained less than 10 gallons of fuel, and both wingtip tanks were completely full (17 gallons each). The pilot and his flight instructor discussed the fuel status before departure and had agreed to operate the engine on the right wing main tank to correct the fuel imbalance between the tanks during the flight. The flight consisted of visual flight rules maneuvers and touch-and-go landings, and about 1.1 hour into the flight the airplane had a loss of engine power about 1,000 ft above the ground while in cruise flight. A forced landing was completed to a nearby field, but shortly after touchdown the airplane collided with a berm that caused the airplane to become airborne again. The nose landing gear collapsed and both wings were substantially damaged when the airplane landed hard the second time. The pilot and his flight instructor both reported that the entire flight had been flown using fuel from the right wing main fuel tank. Neither the pilot nor his flight instructor switched fuel tanks after the loss of engine power because they were focused on the forced landing. The pilot stated that based on the airplane’s performance data, the loss of engine power was likely due to fuel starvation. An onsite examination of the wreckage revealed that the right wing main fuel tank was intact and contained less than ¼ gallon of fuel. According to the airplane’s owner’s handbook, there was about 1 pint of unusable fuel in each of the 4 fuel tanks. The remaining 3 fuel tanks contained usable fuel. Additionally, there were no mechanical malfunctions identified with the airplane’s fuel system or the engine that would have precluded normal operation. Probable Cause: The flight crew’s improper fuel management that resulted in fuel starvation and the loss of engine power. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 3420 hours | CEN21LA261 | NTSB | Final report | c9c2c7383592781ec2676b5075225098 | Investigation completed | 6 months | |
| 2021 | Thursday 30 December 2021 | 22:00 UTC | ATR 72-202 (QC) | Calm Air | C-FJCQ | 311 | P&W Canada PW124B | Fatalities: 0 / Occupants: | 0 | Unknown | 150 nm WSW of Rankin Inlet (CYRT), NU - Canada | En route | Unknown | Gjoa Haven Airport, NU (YHK/CYHK) | Thompson Airport, MB (YTH/CYTH) | Information verified through data from accident investigation authorities | An ATR 72-200 operated by Calm Air, was conducting flight CAV468 from Goa Haven (CYHK), NU to Thompson (CYTH), MB. When the flight was approximately 150 nm west southwest from Rankin Inlet (CYRT), NU, the crew observed an intermittent low oil pressure warning light on the left engine (Pratt & Whitney Canada PW124B). The crew referred to the QRH and decided to divert to CYRT. While enroute to CYRT, the master caution light for the engine low oil pressure illuminated. The crew shut down the left engine as a precautionary measure and continued to CYRT where they carried out an uneventful landing. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | TSB | |||||||||
| 2021 | Thursday 24 June 2021 | 11:15 LT | Piper PA-28-161 Warrior II | Trident Aircraft Inc | N2143G | 28-7916176 | 1978 | Lycoming O-320-D3G | Fatalities: 0 / Occupants: 1 | 0 | Destroyed | Accident | near Easton/Newnam Field Airport (ESN/KESN), Easton, MD - United States of America | Approach | Training | Easton/Newnam Field Airport (ESN/KESN), Easton, MD | Easton/Newnam Field Airport (ESN/KESN), Easton, MD | The student pilot was conducting his first solo flight. After his second takeoff, while turning onto the downwind leg of the airport traffic pattern, he heard the engine lose power. At an altitude of 700 ft above ground level, he did not think he could make it back to the airport, so he maneuvered the airplane for a forced landing to a field. During the approach, the airplane stalled and impacted a construction area before reaching the field. A postcrash fire ensued. Flight control cable continuity for the aileron, stabilator, and rudder cables were continuous from the cockpit to the respective control surfaces, except for separations consistent with recovery cuts near the wing roots and the tailcone. The engine cylinders were examined with a borescope and minor scoring was noted. No anomalies were noted with the airframe or engine that would have precluded normal operation; however, due to the extent of the postcrash fire damage, the ignition and fuel systems could not be examined or tested, and the reason for the loss of engine power could not be determined. Probable Cause: A total loss of engine power for reasons that could not be determined. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 8649 hours | ERA21LA267 | NTSB | Final report | 01d79b500e2f2db5408f291583367dff | Investigation completed | |||
| 2021 | Thursday 15 April 2021 | 10:00 LT | Piper PA-22-160 Pacer | Private | N3551Z | 22-7462 | 1960 | Lycoming O-320 SERIES | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Cottonwood Airport (P52), Cottonwood, AZ - United States of America | Landing | Private | Calnevar, NV (1L4) | Cottonwood, AZ | Accident investigation report completed and information captured | The pilot of a tailwheel equipped airplane reported that, during the landing roll, while adjusting the flap handle, he briefly stepped on the right rudder and the airplane veered to the right. While attempting to correct with left rudder input, the airplane continued to veer to the right, exited the runway, ground looped to the right and collapsed the left main landing gear. The airplane sustained substantial damage to the left wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Probable Cause: The pilot's failure to maintain directional control during landing, which resulted in a ground loop. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 3400 hours | WPR21LA160 | NTSB | Final report | afa529e4c143c5bf50ea9a6ae1168f91 | Investigation completed | 5 months | |
| 2021 | Thursday 4 February 2021 | 13:20 UTC | Diamond DA62 | Private | PS-EBI | 62.089 | 2018 | Fatalities: 0 / Occupants: 2 | 0 | Substantial | Accident | Fazenda Chapadão, Barreiras, BA - Brazil | Landing | Private | Fazenda Vitória (SITH) Aerodrome, Luís Eduardo Magalhães, BA | Fazenda Chapadão, Barreiras, BA | Accident investigation report completed and information captured | The aircraft took off from the Fazenda Vitória (SITH) Aerodrome, Luís Eduardo Magalhães, BA, bound for the Agricultural Landing Area of Fazenda Chapadão, Barreiras, BA, at approximately 13:05 (UTC), with one pilot and one passenger on board. During the rollout after landing, while trying to divert from a mud puddle, the left wing collided with a corn field, resulting in loss of aircraft control. After a yaw of approximately 90 degrees to the left, the aircraft came to a stop with its front end in the cornfield.The aircraft had substantial damage. All on board were unharmed. Contributing factors. - Control skills – undetermined. It is possible that, during the reported deviation attempt, an inadequacy in the use of the controls resulted in the contact of the left-wing tip with the existing vegetation on the side of the runway, which caused an abrupt left turn, whose correction could not be performed because of the conditions prevailing at the time of landing (soft, wet, slippery terrain with accumulations of water). - Piloting judgment – a contributor. The fact that it had rained the day before and the slippery condition of the runway, in which there were still puddles of water, as well as the non-compliance with the requirements established in the RBACs 91 and 137, led the investigators to conclude that the inadequate assessment of the risks associated with the operation conducted under such conditions contributed to this accident. In addition, the requirements established in the RBACs 91 and 137 which prevented the operation in that location, were not considered. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | CENIPA | Final report | 279bfaa2d75a874f10032e694c195a9a | Investigation completed | 1 year and 8 months | ||||
| 2021 | Monday 8 November 2021 | 16:15 LT | Cub Crafters CC18-180 Top Cub | U.S. Department of the Interior | N413CC | CC18-0065 | 2013 | Lycoming O-360-C4P | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Yukon Charlie River, AK - United States of America | Landing | Unknown | Eagle Airport, AK (EAA/PAEG) | Yukon Charlie River, AK | Accident investigation report completed and information captured | The pilot reported that he had completed one high to mid-level reconnaissance flight over the snow-covered runway in his tundra tire tailwheel-equipped airplane. Before landing, he intended to fly a low pass and drag the main landing gear along the surface of the runway to determine the depth of the snow. As the main landing gear wheels touched down atop the snow, he stated it initially felt okay but also felt deeper than what he had anticipated. He applied full power and began to apply back stick pressure, but he felt the snow consistency change to a punchy feeling, and the airplane's tail began to rise. Subsequently, the airplane nosed over and sustained substantial damage to the rudder and right-wing lift strut. The pilot reported that there were no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. Probable Cause: The pilot's selection of an unsuitable landing site, which resulted in a nose-over. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 1388 hours | ANC22LA006 | NTSB | Final report | 2b2c26ccaa4c02318a4719ab5e388cd1 | Investigation completed | ||
| 2021 | Monday 14 June 2021 | day | Gulfstream American AA-5B Tiger | Private | G-BIPV | AA5B-0981 | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Sandown Airport, Sandown, Isle of Wight - United Kingdom | Landing | Private | Sandown Airport (EGHN) | Information verified through data from accident investigation authorities | Gulfstream American AA-5B Tiger G-BIPV substantially damaged 14 June 2021 in a landing accident at Sandown Airport, Sandown, Isle of Wight. The incident was the subject of an AAIB Correspondence-only investigation, published on 14 October 2021 and the following is the summary from that... "14 Jun 2021 Gulfstream AA-5B G-BIPV Sandown Airport, Isle of Wight, Hampshire Following an uneventful approach to land in very little wind, with full flap deployed, the aircraft floated over the grass strip for an “unusually long” time before touching down. The brakes were applied but the pilot was unable to bring the aircraft to a safe stop. It overran the end of the runway into rough terrain and gravel, during which the nose gear collapsed". | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||||
| 2021 | Wednesday 14 July 2021 | Cessna U206G Stationair 6 II | Aero Jomacha | XA-KCH | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Morelos, Chihuahua - Mexico | En route | Ferry/positioning | Information is only available from news, social media or unofficial sources | A Cessna U206G Stationair 6 II crashed under unknown circumstances in Morelos, Chihuahua. The pilot was not injured. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| 2021 | Wednesday 30 June 2021 | c. 18:45 UTC | Piper PA-23-250 Aztec F | Pacific Fleet Aviation LLC | N1715Y | 27-7654096 | 1976 | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | Kona-Keahole Airport, HI (KOA/PHKO) - United States of America | Taxi | Private | Kona-Keahole Airport, HI (KOA/PHKO) | Information is only available from news, social media or unofficial sources | A Piper PA-23-250 Aztec F sustained substantial damage when it collided with Dassault Falcon 900C N917JF at Kona-Keahole Airport (KOA/PHKO), Hawai, USA. There were no injuries. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | NTSB | |||||||||
| 2021 | Monday 29 March 2021 | 16:03 UTC | Progressive Aerodyne SeaRey LSA | Progressive Aerodyne Inc | N847SR | 1096 | Fatalities: 0 / Occupants: 1 | 0 | Unknown | Flagler County Airport, FL (FIN/KFIN) - United States of America | Landing | Private | Flagler County Airport, FL (FIN/KFIN) | Information is only available from news, social media or unofficial sources | Aircraft landed and veered off runway into the grass, became airborne again, returned to land and veered off the runway into the grass. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||||
| 2021 | Monday 15 November 2021 | Van's RV-3 | Private | I-1174 | Fatalities: 1 / Occupants: 1 | 0 | Destroyed | Accident | near Ano Amygdali, Larissa - Greece | En route | Private | Drama | Athens | Little or no information is available | The aircraft crashed into a heavily wooded steep ravine, killing the pilot. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||||
| 2021 | Friday 10 December 2021 | 13:10 | Air Tractor AT-802 | Fatalities: 0 / Occupants: | 0 | Substantial | Accident | 49.8 km 286 degrees from Wee Waa, NSW - Australia | Unknown | Agricultural | Information verified through data from accident investigation authorities | During agricultural spraying operations, the aircraft struck a powerline and the pilot diverted the aircraft to Moree. The aircraft sustained substantial damage. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ATSB | ||||||||||||||
| 2021 | Saturday 3 April 2021 | c. 15:21 | Robinson R22 Beta | Spitzer Helicopter LLC | N74347 | 3759 | 2005 | Fatalities: 0 / Occupants: 2 | 0 | Unknown | Martin State Airport (MTN/KMTN), Baltimore, MD - United States of America | Manoeuvring (airshow, firefighting, ag.ops.) | Private | Baltimore-Glenn L. Martin Airport, MD (MTN/KMTN) | Baltimore-Glenn L. Martin Airport, MD (MTN/KMTN) | Information is only available from news, social media or unofficial sources | The aircraft experienced a tail rotor strike during hover at Martin State Airport (MTN/KMTN), Baltimore, Maryland. The helicopter sustained unreported damage and the two pilots onboard were not injured during the incident. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||
| 2021 | Sunday 9 May 2021 | 09:04 | Airbus A320-214 | Trade Air | 9A-BTH | 1454 | 2001 | CFMI CFM56-5B4/P | Fatalities: 0 / Occupants: | 0 | Unknown | Ljubljana Airport (LJU/LJLJ) - Slovenia | Take off | Passenger | Ljubljana-Brnik Airport (LJU/LJLJ) | Madeira-Cristiano Ronaldo International Airport (FNC/LPFU) | Information is only available from news, social media or unofficial sources | Trade Air flight C3125, a Airbus A320-214, returned to land at Ljubljana Airport after suffering a bird strike. The Ljubljana Tower controller reported that airport operations located a harrier on the runway. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | |||||||||
| 2021 | Wednesday 13 January 2021 | Mil Mi-24? | Sudan Armed Forces | Fatalities: 0 / Occupants: 3 | 0 | Destroyed | Wad Zayed Airport, al-Showak, al-Qadarif province - Sudan | Take off | Military | Wad Zayed Airport, al-Showak, al-Qadarif province | Information is only available from news, social media or unofficial sources | The Sudanese military helicopter crashed upon takeoff under unknown circumstances. All three crew members survived the crash. *media reported an Apache helicopter. Impossible as the SAF has not this helicopter and it can't carry 3 POB! | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| 2021 | Wednesday 13 October 2021 | 07:55 | Boeing 737-8AS (WL) | Ryanair | EI-EKR | 38503/3202 | 2010 | CFMI CFM56-7B | Fatalities: 0 / Occupants: | 0 | Minor | near Manchester Airport, Ringway, Manchester - United Kingdom | Take off | Passenger - Scheduled | Manchester International Airport (MAN/EGCC) | Lanzarote Airport (ACE/GCRR) | Information is only available from news, social media or unofficial sources | Ryanair flight FR2131, a Boeing 737-8AS, suffered a bird strike on departure from Manchester Airport, U.K. The flight crew stopped the climb at 3625 feet and entered a holding pattern over Warrington, north of Liverpool before safely diverting to Liverpool Airport, where it landed safely on runway 27 about 55 minutes after departure. Ground observers at Manchester reported the engines (CFM56) sounded rough, almost like a helicopter, as the aircraft climbed out. A spokesperson for Ryanair said: "“This flight from Manchester to Lanzarote (13th Oct) diverted to Liverpool airport following a minor bird strike. The aircraft landed normally, and customers were transferred to a replacement aircraft which departed to Lanzarote following a short delay of approximately one hour. "Ryanair sincerely apologised to all affected customers." A Liverpool John Lennon Airport confirmed the Ryanair flight's unscheduled landing: "A Ryanair flight that took off from Manchester Airport bound for Arrecife (Lanzarote) requested to land here at Liverpool John Lennon Airport at 08:45 this morning landing safely and without incident at 08:53." | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | |||||||||
| 2021 | Wednesday 12 May 2021 | 15:30 | Aérospatiale AS 350B2 Ecureuil | US Customs and Border Protection (CBP) | N841BP | 2036 | 1987 | Turbomeca Arriel 1D1 | Fatalities: 0 / Occupants: 2 | 0 | Destroyed | Accident | Clarence E Page Municipal Airport (RCE/KRCE), Oklahoma City, OK - United States of America | Manoeuvring (airshow, firefighting, ag.ops.) | Training | Oklahoma City-Will Rogers Airport, OK (OKC/KOKC) | Clarence E Page Municipal Airport, OK (RCE/KRCE) | Accident investigation report completed and information captured | On May 12, 2021, about 1530 central daylight time, an Aerospatiale (Airbus) AS350 B2 helicopter, N841BP, was destroyed when it was involved in an accident near Yukon, Oklahoma. The pilot receiving instruction and the flight instructor were not injured. The helicopter was operated as a 14 CFR Part 91 public aircraft instructional flight. The pilot receiving instruction (pilot) and the flight instructor were conducting a training flight in the helicopter. They performed several simulated emergencies, each of which required the helicopter’s hydraulic system to be turned off and then turned back on at the conclusion of the procedure. The hydraulic system was turned off and on using the hydraulic cut-off switch, an unguarded push-button switch mounted on the end of the pilot’s collective stick. After completing the emergency procedures, the pilot performed four quick stop maneuvers. The flight instructor reported that on the last quick stop, the helicopter slowed normally but then started a left yaw about 25 ft above ground level. The pilot noted the left yaw and attempted to correct it, but his pedal inputs did not stop the yaw. As the pilot tightened his grip on the collective, the hydraulic system turned off, likely due to the pilot inadvertently pressing the hydraulic cut-off switch, and the left yaw rapidly increased to a left spin. According to the flight instructor, the control loads “instantly became excessive,” and he noticed the hydraulic light on the caution warning panel was illuminated. The pilot intentionally pressed the hydraulic cut-off switch a total of three times, but hydraulic pressure was never restored. The flight instructor told the pilot that he was taking control of the helicopter. However, the pilot did not relinquish control. The flight instructor attempted to regain control of the helicopter but was unable to overcome the high control loads. The helicopter continued to spin, impacted the ground, rolled over, and came to rest on its right side. A postimpact fire consumed most of the helicopter. Although examination of the helicopter was limited due to fire damage, no preimpact abnormalities were identified with helicopter’s airframe and engine. The US Customs and Border Protection Air and Marine Operations Division reported that the agency’s selection process for the Air Interdiction Agent Program failed to properly identify that the pilot was not qualified for the program. Because the pilot did not have the qualifications and experience required for the Air Interdiction Agent Program, he did not have the prerequisite skill necessary to critically assess the situation given by the flight instructor. This resulted in the pilot applying improper corrective actions and failing to relinquish control of the helicopter to the flight instructor when directed, which contributed the accident. Probable Cause: The pilot receiving instruction’s untimely and unidentified inadvertent activation of the hydraulic cut-off switch, which turned off the hydraulic system while the helicopter was at slow airspeed followed by a rapid power increase, which resulted in a loss of control. Contributing was the pilot’s failure to relinquish control of the helicopter to the flight instructor when directed. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 15261 hours | CEN21LA216 | NTSB | Final report | 7baa4e156c49947f85e901d3a2db324c | Investigation completed | ||
| 2021 | Saturday 10 April 2021 | 14:30 LT | Cessna 150M | Private | N439WT | 15077917 | 1976 | Continental O-200 | Fatalities: 0 / Occupants: 2 | 0 | Substantial | Accident | Tishomingo, Oklahoma - United States of America | Take off | Private | Tishomingo, OK | Tishomingo, OK | Accident investigation report completed and information captured | The pilot reported he was taking off on personal flight when a gust of wind lifted the airplane's wing, and the airplane became airborne during his corrective control input. The pilot continued the climbout and attempted to gain airspeed, but the airplane did not accelerate and seemed to slow. The pilot elected to land the airplane to avoid trees that were ahead of him. The airplane touched down on a grass area just beyond the end of the runway but impacted in a drainage ditch about 100 ft. beyond the departure end of the runway that collapsed the nose landing gear. The airplane sustained substantial damage to the engine mounts at the nose landing gear. A Federal Aviation Administration inspector reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operations and that the engine was making power at impact. At the time of the accident, the pilot was taking off on runway 35 with a quartering wind from the northwest. The pilot reported that he may have encountered wind shear over the treetops which might have kept him low and slow to accelerate. Probable Cause: The pilot's decision to abort the takeoff on encountering a wind gust and his landing beyond the end of the runway that resulted in the airplane impacting a ditch collapsing the nose landing gear. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 5976 hours | CEN21LA188 | NTSB | Final report | 9ba0231e686c740160cb24824582fd89 | Investigation completed | 6 months | |
| 2021 | Tuesday 6 April 2021 | 11:30 | Beechcraft A36 Bonanza | 394 LLC | N18394 | E-1121 | 1977 | Continental IO520BA | Fatalities: 0 / Occupants: 1 | 0 | Substantial | Accident | near Arcadia Municipal Airport (X06), Arcadia, FL - United States of America | En route | Private | Arcadia Municipal Airport, FL (X06) | Venice Municipal Airport, FL (VNC/KVNC) | Accident investigation report completed and information captured | On April 6, 2021, about 1130 eastern daylight time, a Beech A36, N18394, was substantially damaged when it was involved in an accident near Arcadia, Florida. The pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Shortly after takeoff, the pilot noticed the engine rpm had increased and oil pressure was zero. While returning to the airport the engine lost all power and the pilot performed a forced landing to a field. About 8 months prior to the accident, all six cylinders were replaced. Examination of the engine revealed the engine was seized and would not rotate. The reason for the loss of power was not determined. The engine was not made available for an NTSB postaccident examination. Probable Cause: A total loss of engine power for underdetermined reasons. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | 5443 hours | ERA21LA174 | NTSB | Final report | dad9c97408df80d7ae86fa6fdacd236d | Investigation completed | 2 years 1 month | |
| 2021 | Sunday 30 May 2021 | 08:37 | Cessna A188A | Agrícola de Servicios Aéreos del Meta - ASAM | HK-1477 | 18800696 | Fatalities: 1 / Occupants: 1 | 0 | Destroyed | Accident | near El Dólar airfield, Paz de Ariporo - Colombia | Manoeuvring (airshow, firefighting, ag.ops.) | Agricultural | Accident investigation report completed and information captured | During the execution of aerial spraying activities to rice fields in the La Reforma field, located in the Municipality of Paz de Ariporo - Casanare, the Cessna A188A aircraft, registration HK-1477, lost altitude during the execution of a turn, colliding with the ground. As a result of the impact, the aircraft suffered substantial damage and its sole occupant sustained fatal injuries. The investigation determined that the accident was caused by the loss of control in flight due to the execution of a turn maneuver, which probably exceeded the aerodynamic limits of the aircraft, generating a loss of lift at low altitude and the subsequent collision with the terrain. To this cause, a contributing factor related to the existence in the area of low level wind shear (LLWS) and clear air turbulence (CAT) in the atmospheric surface layer during low altitude flights was assigned. Probable Cause(s). - Loss of control in flight originating from the execution of a turn maneuver, which probably exceeded the aerodynamic limits of the aircraft, generating a loss of lift at low altitude and the followed collision with the terrain. Contributing factors: - Existence in the area of low-level wind shear (LLWS) and clear air turbulence (CAT) in the atmospheric surface layer during low-altitude flight execution. | You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | COL-21-20-DIACC | Aerocivil | Final report | c708373bdd02cd6f0df247287d10620b | Investigation completed | 10 months | ||||||
| 2021 | Tuesday 27 April 2021 | 23:00 | Learjet 60 | Emergencias | LV-HXK | 60-316 | Fatalities: 0 / Occupants: | 0 | Minor | San Fernando Airport, BA (FDO/SADF) - Argentina | Pushback / towing | Executive | San Fernando Airport, BA (FDO/SADF) | Information is only available from news, social media or unofficial sources | The plane was being towed along taxiway "C" to a remote location at the San Fernando International Airport (FDO/SADF), when it was hit by a van belonging to the airport operator. No injuries were reported. Material damage to the wing tip and windshield of the truck. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description | ||||||||||||
| 2021 | Saturday 29 May 2021 | ultralight | Fatalities: 0 / Occupants: 1 | 0 | Minor | Dahlemer Binz Airfield (EDKV) - Germany | Landing | Training | Dahlemer Binz Airfield (EDKV) | Information is only available from news, social media or unofficial sources | The ultralight was caught by a gust of wind. A wing hit the ground and the aircraft swerved into a meadow. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. You can contribute by submitting additional or updated information. Corrections or additions? ... Edit this accident description |
全球无人机事故数据
| Sort | Year | Date | Time | Type | Owner/operator | Registration | MSN | Year of manufacture | Engine model | Fatalities | Other fatalities | Aircraft damage | Category | Location | Phase | Nature | Departure airport | Destination airport | Confidence Rating | narrative | notes | Total airframe hrs | Report number | Investigating agency | Download report | Accident investigation PDF | Status | Duration |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 无人机类型 | 年份 | 日期 | 时间 | 机型 | 所有者/经营者 | 飞机号 | MSN | 制造年份 | 发动机型号 | 死亡人数 | 其他死亡人数 | 飞机损坏情况 | 事件类型 | 地理位置 | 出事阶段 | 飞机用途 | 始发机场 | 到达机场 | 信用评级 | 事件说明 | 备注 | 总飞行时长 | 报告编号 | 调查机构 | 下载报告 | 调查报告 | 调查进度 | 调查时长 |
| Drone accidents (civilian only) | 2020 | Wednesday 4 March 2020 | Baykar Bayraktar TB2 | Türk Hava Kuvvetleri (Turkish Air Force) | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Idlib - Syria | Combat | Military | Little or no information is available | The Turkish drone was shot down by the Syrian Arab Army air defenses in the evening of 4 March 2020 in the Idlib Governorate. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2020 | Saturday 16 May 2020 | Wing Loong I | Libyan National Army (LNA) | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | near al-Watiyah Airbase - Libya | Combat | Military | al-Watiyah Airbase | al-Watiyah Airbase | Little or no information is available | A military drone (reported as a Wing Loong or TAI ANKA S) was shot down by fire. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||
| Drone accidents (civilian only) | 2020 | Thursday 24 September 2020 | General Atomics MQ-9A Reaper | USAF | 10-4108 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Accident | Ali Al Salem Air Base - Kuwait | Landing | Military | Ali Al Salem Air Base | Ali Al Salem Air Base | Accident investigation report completed and information captured | On 24 September 2020, at approximately 04:33 UTC, the MQ-9A (10-4108) departed the runway surface during landing rollout at Ali Al Salem Air Base, Kuwait. The aircraft was government-owned, contractor-operated and assigned to the 432d Wing with contractors for Remotely Piloted Solutions (RPS) flying it at the time of the mishap. The crew consisted of the pilot,sensor operator and safety observer. Another unit’s ground data terminal (GDT) and ground control station (GCS) and MQ-9 were in use during the landing of 10-4108 and were transmitting on the same frequency as the 10-4108’s uplink. The interfering GDT was transmitting on the wide beam during the landing then subsequently changed to the narrow beam. The MQ-9A entered the interfering GDT’s beam and lost uplink with its GDT. The nose wheel of 10-4108 maintained the last received command (slight left), and the aircraft veered left. The aircraft then departed the side of the runway. It was destroyed. The Abbreviated Accident Board President found by a preponderance of the evidence, the causes of the mishap, both of which were necessary, are: (a) the other unit's improperly using the MOSPORT uplink frequency to launch and land aircraft after the frequency allocation plan had been adjusted and distributed; and (b) during landing rollout, the mishap aircraft entered the beamwidth for the OU GDT, causing the mishap aircraft to receive two different uplink signals on the same frequency, preventing it from receiving data from its own GDT and resulting in the loss of uplink. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | USAF AIB | Final report | f284673335668a9f050f2809bb04e92a | Investigation completed | 1 year 1 month | ||||||
| Drone accidents (civilian only) | 2020 | Tuesday 27 October 2020 | Spaitech Sparrow | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Novogrigorovka, Donetsk Oblast - Ukraine | En route | Military | A Spaitech Sparrow of the Ukrainian Ground Forces was downed somewhere in Eastern Ukraine. Of note is that the drone contained a skull motif from the American comic book series "Punisher". | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2020 | Wednesday 24 June 2020 | 09:33 UTC | General Atomics MQ-9A Reaper | US Air Force (USAF) | 08-4051 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Accident | Africa - | Unknown | Military | Accident investigation report completed and information captured | The aircraft, an MQ-9A, crashed in an undisclosed location within the United States Africa Command (US AFRICOM) Area of Responsibility (AOR). Assigned to the 162d Wing, Arizona Air National Guard, the MA was operated by the 214th Attack Squadron Mission Control Element (MCE) located at Davis-Monthan AFB, Arizona, at the time of the mishap. The location of the crashed MA was confirmed, but the wreckage was not recovered. At approximately 0640Z, the Mishap Ground Control Station (MGCS) started to display warnings that the fuel level in the header tank was low. The pilot and sensor operator began to accomplish procedures to clear this fault. Soon thereafter, the pilot noted through fuel calculations that the measured fuel was well short of expected levels. The pilot enlisted the assistance of the mission crew commander to help diagnose the problem. As the pilot and mission crew commander worked the problem, the sensor operator used the primary camera to visually sweep the aircraft. During that sweep, the sensor operator found that the aircraft was severely leaking fuel from the fuselage. At 0723Z, the crew started to return to base at maximum airspeed. Without knowing exactly where in the fuel system the leak was occurring, the pilot concluded that if the leak was not affecting the aft tank and header tank, then a safe recovery was theoretically possible. After further analysis, the crew realized that the fuel leak was catastrophic. The pilot and mission crew commander, coordinating with Combined Air Operations Center (CAOC) Remotely Piloted Aircraft Liaison Officer (RPA LNO), started to plan to crash the aircraft. The CAOC directed mission crew commander and pilot to crash the aircraft, and to do so in a way that would minimize chances of a successful recovery effort. Fuel exhausted at 0914Z. The pilot then controlled the glide of the aircraft to optimize the impact point. As the aircraft lost altitude, the pilot increased the airspeed of the MA through the crash, which occurred at 0933Z. The Abbreviated Accident Investigation Board (AAIB) President found, by a preponderance of the evidence, the cause of the mishap was a fuel leak from the Forward Electric Fuel Heater that caused fuel exhaustion before the aircraft could be safely returned to the Launch and Recovery Element. Further, the AAIB President found, by a preponderance of the evidence, that each of the following factors substantially contributed to the mishap; (1) Delinquent Time Compliance Technical Order (TCTO) to correct a known MQ-9 deficiency (2) the design of the fuel leak detection system, and (3) lack of guidance and tolerances for the MQ-9 fuel system. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | USAF AIB | Final report | d20fe2c950064cad9661c4e93e199746 | Investigation completed | 11 months | |||||||
| Drone accidents (civilian only) | 2020 | Thursday 23 April 2020 | General Atomics MQ-1 | United States Air Force - USAF | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Aghalingharen, near Agadez - Niger | Combat | Military | Agadez AB | Agadez AB | Little or no information is available | The USAF military drone crashed after a technical malfunction near Agadez, Niger. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||
| Drone accidents (civilian only) | 2020 | Monday 30 March 2020 | Baykar Bayraktar TB2 | Government of National Accord (GNA) | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | South of Tripoli - Libya | Combat | Military | Little or no information is available | The military drone was shot down by LNA armed forces over Tripoli. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2020 | Saturday 18 April 2020 | Baykar Bayraktar TB2 | Government of National Accord (GNA) | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Al Ahira, South of Tripoli - Libya | Combat | Military | Mitiga military base | Little or no information is available | The Turkish military drone was downed by armed forces of the Libyan National Army (LNA). | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2020 | Wednesday 12 August 2020 | General Atomics MQ-1 | United States Air Force - USAF | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Tiguirwit, near Agadez - Niger | En route | Military | Niamey Airport | Niamey Airport | Information is only available from news, social media or unofficial sources | The US military drone crashed probably due to a technical malfunction. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||
| Drone accidents (civilian only) | 2020 | Wednesday 22 January 2020 | Baykar Bayraktar TB2 | Government of National Accord (GNA) | T92 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | near Mitiga Airport - Libya | En route | Military | Information is only available from news, social media or unofficial sources | The military drone with registration T92, was shot down by LNA armed forces. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2020 | Tuesday 25 August 2020 | AAI RQ-7 Shadow | Arkansas Army National Guard | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | near Lavaca - United States of America | En route | Military | Fort Chaffee | Fort Chaffee | Information is only available from news, social media or unofficial sources | The US military drone crashed under unknown circumstances during a training mission. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||
| Drone accidents (civilian only) | 2021 | Sunday 20 June 2021 | 12:55 UTC | General Atomics MQ-9A Reaper | USAF | 12-4203 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Accident | unknown - Afghanistan | En route | Military | Accident investigation report completed and information captured | An unmanned MQ-9A, 12-4203, was intentionally crashed into a mountain in an undisclosed location in Afghanistan. The mishap aircraft (MA) was operated remotely by a Mission Control Element (MCE) comprised of the mishap pilot (MP1) and the mishap sensor operator (MSO1). The MCE was assigned to the 138th Attack Squadron and belonged to the 174th Attack Wing. Both units are located at Hancock Field, an Air National Guard (ANG) Base near Syracuse, New York. The MA was not recovered after it was intentionally crashed in an unrecoverable location. The crash resulted in no reported damage to civilian property, no injuries, and no fatalities. The loss of government property was valued at $14,426,412. Approximately 30 minutes before deciding to crash the MA, MP1 noticed the oil level indication dropped to approximately 40%. The MA lost 100% of its indicated oil level between approximately 1219z and approximately 1224z. During this time, MP1 alerted MSO1 of the issue and turned the MA toward an Expeditionary Launch and Recovery Element (ELRE). Between 1225z and 1234z, oil pressure decreased from 100 psi to 5 psi. At roughly 1237z, the engine torque and propeller speed began to fluctuate and the exhaust gas temperature (EGT) spiked. MP1 determined the MA would suffer engine failure before reaching the ELRE, and at 1242z MP1 pulled the condition lever to the aft position, shutting down the engine. The supported unit then requested the MA be crashed in a location where it would be unrecoverable. At approximately 1254z, MP1 turned off all aircraft autopilot features, took a nose down attitude, and the MA impacted the ground at 1255z at 7,350 feet mean sea level (MSL). The Abbreviated Accident Investigation Board President (AAIB BP) found, by a preponderance of the evidence, MP1 shut down the engine after an oil leak reduced the indicated oil level to 0%, preventing the MA from returning safely to a recovery location. Moreover, the AAIB BP found, by a preponderance of evidence, the MA experienced an oil leak, reducing the indicated oil level to 0% substantially contributing to the mishap | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | USAF AIB | Final report | acb29e31fa9c39dae177a0e4b1a0716b | Investigation completed | 1 year | |||||||
| Drone accidents (civilian only) | 2021 | Sunday 7 March 2021 | Vestel Karayel | Saudi Armed Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Al-Jawf province, al-Marazeeq area - Yemen | Combat | Military | Little or no information is available | A Saudi military drone, manufactured in Turkey was shot down by Houthi air defense, in Al-Jawf province, al-Marazeeq area. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2021 | Saturday 22 May 2021 | Wing Loong II | SA AF | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Sa'dah prowince - Yemen | Combat | Military | Little or no information is available | Drone was shot down by Houtis close to border with SA province of Najran. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2021 | Sunday 20 June 2021 | Orlan-10 | Russian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Montef, Jabal al-Zawiya region - Syria | En route | Military | Information is only available from news, social media or unofficial sources | A Russian Air Force Orlan-10 UAV crashed in Montef, Jabal al-Zawiya region after a technical malfunction. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2021 | Tuesday 3 August 2021 | Wing Loong I | United Arab Emirates (UAE) | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Bani Walid, Libya - Libya | Combat | Military | UAE suplied Wing Loong I drone operated by LNA forces found destroyed in Bani Walid, Libya. Loss date unkown. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2021 | Friday 21 May 2021 | Baykar Bayraktar TB2 | Türk Hava Kuvvetleri (Turkish Air Force) | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Northern Iraq - Iraq | Combat | Military | Little or no information is available | Crasched in mountain and difficult to acces region. It was carry a MAM-C i MAM-L type munition under wings. Information about accident appears quickly but movie and pictures - around 16 of July | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | Saturday 28 May 2022 | Orlan-10 | Russian Ground Forces | 12302/12590 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | On the border of Kherson and Dnipropetrovsk oblasts - Ukraine | Combat | Military | Little or no information is available | A Russian Orlan-10 reconnaissance UAV was shot down by the Ukrainian forces on the border of Kherson and Dnipropetrovsk oblasts. It was assembled with parts from two different one, bearing two separate numbers on its wings. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2022 | Tuesday 19 April 2022 | Eleron-3 | Russian Air Force | Fatalities: 0 / Occupants: 0 | 0 | Minor | Chernihiv Oblast - Ukraine | Combat | Military | Little or no information is available | A crash landed Russian Eleron-3 light reconnaissance UAV was found by the forces of National Guard of Ukraine. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | Saturday 17 September 2022 | Leleka-100 | Ukrainian Ground Forces | 64 | Fatalities: 0 / Occupants: 0 | 0 | Minor | Donbass - Ukraine | Combat | Military | A Ukrainian Leleeka-100 was shot down and captured by Russian Forces. The incident was observed by journalists of Crimea24. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | Wednesday 28 September 2022 | Orlan-10 | Russian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Minor | Ukraine - Ukraine | Combat | Military | Little or no information is available | A Russian AF Orlan-10 military drone was captured by Ukrainian armed forces. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | Monday 23 May 2022 | 20:51 | CASC CH-4 Rainbow | Royal Saudi Air Force (RSAF) | 20325 | Fatalities: 0 / Occupants: 0 | 3 | Destroyed | Near Yemen Commercial Mall, Al Wahdah District, Sanaa Municipality - Yemen | En route | Military | Little or no information is available | On 23 May 2022, between 20:50 and 20:54 local time, a Royal Saudi Air Force CH-4 Rainbow of No. 203 Squadron crashed into a busy arterial street in Sanaa, near the location of the Yemen Commercial Mall, Al Wahdah District, Sanaa Municipality. As a result of the crash, three civilians were killed, and another three injured. A number of cars, motorcycles and merchant carts were also damaged or destroyed. Due to the lack of combat damage to the drone wreckage, it is likely that the vehicle crashed as a result of operational loss of control, as opposed to being lost as a result of combat. Sanaa is controlled by the Yemen Supreme Political Council, associated with the Ansar Allah (Houthi movement). | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||
| Drone accidents (civilian only) | 2022 | Tuesday 14 June 2022 | Orlan-10 | Russian Ground Forces | 20108 | Fatalities: 0 / Occupants: 0 | 0 | Minor | - Ukraine | Combat | Military | Little or no information is available | A Russian Orlan-10 reconnaissance UAV was shot down by the Ukrainian 58th Motorized Infantry Brigade. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2022 | Thursday 10 March 2022 | 23:01 | Tupolev Tu-141 Strizh | 383rd Unmanned Aircraft Regiment, Ukrainian Air Force | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Jarunska ulica, Trešnjevka – jug, Zagreb - Croatia | En route | Military | Information is only available from news, social media or unofficial sources | On the evening of 10 March 2022, 23:01 CET, a Tupolev Tu-141 unmanned reconnaissance aircraft crashed into a carpark located between the Adriatic Bridge (Jadranski most) and Stjepan Radić Student Dormitory (University of Zagreb) in Zagreb, the capital city of Croatia. As a result 96 cars were damaged, resulting in 600,000 kuna ($86,090 USD) worth of damage. Background The Tu-141 is a large reconnaissance drone produced at the Kharkov Aviation Factory in what was then the Ukrainian Soviet Socialist Republic, USSR from 1979 to 1989. It is designed to undertake many different operations with a variety of available payloads. It is launched form a specialised trailer using a rocket booster, flies using a KR-17A turbojet engine, and is recovered using a tail mounted parachute. The drone has a range of ~1000km. The Tu-141 was in service with the Soviet Union from 1979 to 1989, largely to carry out border reconnaissance flights along the Romanian, Hungarian, Slovakian and Polish frontier. In 2014, following the deteriorating situation in the Donbass region, the Ukrainian Air Force pressed the aircraft back into service, due to a lack of more modern platforms. Timeline 22:23 CET (23:23 EET) - Entered Romanian airspace- observed by the Romanian Air Force 22:26 CET - Entered Hungarian airspace at an altitude of 3,300 ft - observed by the Hungarian Air Force 22:54 CET - Entered Croatian airspace - observed by Croatian air defence systems at an altitude of 4,300 ft 23:01 CET - Crashed into a carpark located next to the Stjepan Radić Student Dormitory. Investigation On 13 April, officials confirmed that the drone was carrying an OFAB-100-120 aerial bomb. An explosives expert Ivana Bacic stated that: "The bomb was charged by unconventional organic powder which the explosion tore down to the gases so it was not possible to identify it". Since this event, a number of Ukrainian Tu-141 and Tu-143 aircraft have been used for reconnaissance purposes as well as an improvised cruise missile against Russian forces, with a number downed by Russian air defences. The aircraft contained a Soviet Air Force red star, which was defaced over with a blue and yellow roundel on its wings. This matches cases of other crashed Ukrainian Tu-141 and Tu-143 aircraft, which contained Soviet stars as a result of their Soviet inheritance. These were later covered with Ukrainian roundels and tryzubs, but remained underneath. As a result of fire damage, the original Soviet stars are revealed underneath. This is in comparison to aircraft operated by the Russian Federation, which utilise a modified version of the Soviet red star adding an additional blue border between the interior Red star and outer white border. On older aircraft these are painted within the Star and thus do not require overlaying the entire roundel. This has been observed on several other downed Tu-141 and Tu-143 drones. Reactions The slow reaction of NATO air defences caused controversy among the Croatian public. President of Croatia Zoran Milanovic stated that "In such situations you depend on NATO ... while there was obviously some failure there. The President stated that Croatia was aware of where the drone flew from, stating "evidently Ukraine to Zagreb." Croatian pilot Ivan Selak criticised NATO's Combined Air Operations Centre for not scrambling aircraft to intercept the aircraft. The Russian Embassy in Zagreb denied ownership of the crashed drone, stating that "the drone was produced on the territory of Ukraine" and that the modern Russian Armed Forces have not used this drone since 1991 when still a part of the Soviet Union. The Russian Federation is only publicly known to operate the much smaller derivative of the aircraft, the Tu-143. Ukrainian Ministry of Defence advisor Markiyan Lubkivsky denied that the UAV belonged to Ukraine. Ukraine maintains claims that the event was a Russian "false-flag" attack. NATO Secretary General Jens Stoltenberg stated that the drone did not constitute an armed attack as the drone was not armed. Croatian news outlet Nacional.hr reported that the Ministry of Defence had determined that the drone belonged to the Armed Forces of Ukraine, and had a bomb that had been intended to attack Russian positions. According to a source close to the Croatian MoD, the aircraft experienced a malfunction in mid-flight, possibly as a result of Russian electronic warfare measures, causing the aircraft to end up in Zagreb. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2022 | Wednesday 11 May 2022 | Orlan-10 | Russian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Minor | - Ukraine | Combat | Military | Little or no information is available | An Orlan-10 was downed with minor damage by the Ukraine Forces. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | Tuesday 23 August 2022 | Orlan-10 | Russian Ground Forces | 10997 + ? | Fatalities: 0 / Occupants: 0 | 0 | Minor | Zaporizhzhia Oblast - Ukraine | Combat | Military | Little or no information is available | A Russian Orlan-10 was downed in Zaporizhzhia Oblast by the Ukrainian 110th Separate Territorial Defense Brigade, with very few damage if any, so apparently using EW equipment. As regularly seen, it seems that it was a composite one with two different registration on its parts. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2022 | Sunday 12 June 2022 | Spectator-M1 | Ukrainian Ground Forces | 205 Blue | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | En route | Military | A Spectator-M1 of the Ukrainian Ground Forces was downed by forces of the Russian National Guard using electronic warfare. The drone was retrieved for further examination and study. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | Wednesday 19 October 2022 | Orlan-10 | Russian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Minor | Ukraine - Ukraine | Combat | Military | Little or no information is available | An Russian AF Orlan-10 military drone was captured by Ukrainian armed forces on 19 October 2022. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | unk. date 2022 | AeroVironment RQ-20 Puma | Ukrainian Ground Forces | Fatalities: / Occupants: | 0 | Destroyed | Popasnaya, Luhansk Oblast - | En route | Military | An RQ-20 Puma of the Ukrainian Ground Forces was downed in Popasnaya, Luhansk Oblast by forces of the Russian Federation. The wreckage of the drone was displayed as a trophy during the 9th International Military-Technical Forum by Russia. However, the date of actual capture is unknown. It is likely that the drone was captured during the Battle of Popasnaya, but no further information is available to verify this. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2022 | Tuesday 29 November 2022 | Baykar Bayraktar TB2 | Ukraine Air Force | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Ingulets river, Kirvoy Rog, Ukraine - Ukraine | Combat | Military | Little or no information is available | Ukrainian Bayraktar TB-2 destroyed near Ingulets River, Nikolaev-Krivoy Rog. Previously unseen loss. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | Tuesday 5 April 2022 | Orlan-10 | Russian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Popasna, Luhansk oblast - Ukraine | Combat | Military | Little or no information is available | A Russian Orlan-10 was shot down by the Ukrainian Border Guards in Popasna, Luhansk oblast. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2022 | xx Oct 2022 | Athlon Avia A1-SM Furia | Ukrainian Ground Forces | АСМ139201 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Kherson Oblast - Ukraine | En route | Military | An Athlon Avia A1-SM Furia of the AFU was shot down by forces of the Russian Federation in Fall 2022, in the area of Kherson Oblast. The exact date of the shootdown is unspecified. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Thursday 13 April 2023 | ASU-1 Valkyrja | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | En route | Military | A Ukrainian ASU-1 Valkyrja reconnaissance drone was downed by Russian forces of the 110th brigade of the 1st Donetsk Army Corps using a 2K22 Tunguska tracked self-propelled anti-aircraft system. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2023 | Monday 15 May 2023 | ASU-1 Valkyrja | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Donetsk Oblast - Ukraine | En route | Military | An ASU-1 Valkyrja of the Ukrainian Ground Forces was downed by forces of the 110th Brigade of the 1st Donetsk Army Corps (Formerly the 100th Brigade of the Donetsk People's Militia) of the Russian Federation. The drone was downed using a 2K22 Tunguska SPAAG. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2023 | Monday 6 November 2023 | WB Electronics FlyEye | Ukrainian Ground Forces | 670 | 23004758.06 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Novoprokopovka, Pologovsky Raion, Zaporozhye Oblast - Ukraine | En route | Military | A FlyEye reconnaissance UAV of the Ukrainian Ground Forces was downed by forces of the 76th Airborne Division of the Russian Federation. The UAV was complately destroyed as a result. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2023 | Friday 17 February 2023 | Ukrainian Aviation Systems Hawk | Ukrainian Ground Forces | NX-00103234 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | En route | Military | A Ukrainian Aviation Systems Hawk was downed by Russian forces. The drone sustained significant structural damage, but landed in one piece. Images of the downed drone were shared on the Russian Telegram channel "UAV Operator Chronicle". | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Sunday 26 March 2023 | 15:19 | Tupolev Tu-141 Strizh | 383rd Unmanned Aircraft Regiment, Ukrainian Air Force | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Kireyevsk, Kireyevsky Raion, Tula Oblast - Russia | Combat | Military | On the afternoon of 26 March 2023, a Ukrainian Air Force Tu-141 crashed into a residential area in Kireyevsk, Tula Oblast. Shortly after, the Russian Ministry of Defence released a statement: "On March 26, the Kiev regime attempted to launch an attack using a Tu-141 Strizh UAV. In particular, the electronic warfare complex "Polye-21" had an impact on the drone. As a result, the aircraft's navigation system was disabled. Having lost its orientation, the aircraft tell in the area of the village of Kireyevsk in Tula Oblast." It appears that after the drone was disabled through electronic warfare, the drone crashed into the town of Kireyevsk. The resulting crash and subsequent explosion left a large crater and damaged a large number of apartment buildings and private houses. Three civilians were reportedly injured by shrapnel. While the Tu-141 was originally developed for use as an unmanned reconnaissance drone, the aircraft has been used repeatedly by Ukrainian forces as an ersatz cruise missile. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Tuesday 31 October 2023 | Ukrspecsystems Shark | Ukrainian Ground Forces | 3230170 | SHRK-K11204-01 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | En route | Military | A Ukrspecsystems Shark of the Ukrainian Ground Forces was downed by forces of the Russian Federation. The drone was completely destroyed as a result. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||
| Drone accidents (civilian only) | 2023 | Thursday 4 May 2023 | Ukrspecsystems Shark | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Belgorod Oblast - Russia | En route | Military | A Ukrainian Shark reconnaissance UAV was shot down in Belgorod Oblast, Russia. The fuselage of the drone remained for the most part in one piece, but it's wings were destroyed. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2023 | Thursday 20 July 2023 | Leleka-100 | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | near Molodizhne Interchange, Kherson Oblast - Ukraine | Standing | Military | A Ukrainian Leleka-100 reconnaissance UAV was tracked by a Russian Zala UAV as it landed. Shortly after, the drone on the ground was destroyed by a drone assisted MLRS barrage. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2023 | Tuesday 31 January 2023 | Baykar Bayraktar Mini UAV | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | En route | Military | A Ukrainian Army Bayraktar Mini reconnaissance UAV was downed by Russian forces. The photo of the drone was first posted on 31 January 2023. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2023 | Monday 16 January 2023 | Leleka-100 | Ukrainian Ground Forces | 65 | Fatalities: 0 / Occupants: 0 | 0 | Minor | - Ukraine | En route | Military | A Leleka-100 reconnaissance UAV of the Ukrainian Ground Forces was downed by electronic warfare systems of the Russian Armed Forces. As a result, the drone sustained only minor damage, and was subsequently captured. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Wednesday 7 June 2023 | Leleka-100 | Ukrainian Ground Forces | 956 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Zaporozhye Oblast - Ukraine | En route | Military | A Ukrainian Leleka-100 reconnaissance drone was reportedly downed by Russian electronic warfare systems in Zaporozhye Oblast. However, photos posted on Russian Telegram channels show heavy damage to the captured drone, with significant damage to the vehicles wings, as well as scorch marks on the fuselage. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Friday 30 June 2023 | Athlon Avia A1-SM Furia | Ukrainian Ground Forces | ACM13131 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Zaporozhye Oblast - Ukraine | En route | Military | An A1-SM Furia reconnaissance UAV of the Ukrainian Ground Forces was downede by the 58th Combined Arms Army of the Russian Federation. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Sunday 26 March 2023 | Leleka-100 | Ukrainian Ground Forces | 896 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | Unknown | Military | A Leleka-100 UAV of the Ukrainian Ground Forces was downed in late March 2023. The destroyed remains of a Leleka-100 reconnaissance UAV of the Ukrainian Ground Forces was then later displayed by Russian forces, along with other destroyed drones. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Wednesday 15 March 2023 | ASU-1 Valkyrja | Ukrainian Ground Forces | 319 | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | Kremennaya, Luhansk Oblast - Ukraine | En route | Military | An ASU-1 Valkyrja of the Ukrainian Ground Forces was downed by forces of the Russian Federation in the vicinity of Kremennaya, located in the Russian controlled territory of the Luhansk People's Republic. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Monday 19 June 2023 | SuperCam S350 | Russian Air Force | Fatalities: 0 / Occupants: 0 | 0 | Substantial | Zaporizhzhia Oblast - Ukraine | Combat | Military | A Russian Air Force SuperCam S350 reconnaissance drone was shot down by Ukrainian soldiers from the 47th Brigade in Zaporizhzhia Oblast. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2023 | Thursday 5 October 2023 | Autel Dragonfish | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | En route | Military | An Autel Dragonfish of the Ukrainian Ground Forces was downed by forces of the Russian Federation, with the drone was completely destroyed as a result. The drone was equipped with an Autel DG-T3 triple camera payload, equipped with a 4K main camera, 640X512 thermal imager, and a 12MP wide angle lens. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | ||||||||||||||||
| Drone accidents (civilian only) | 2023 | Wednesday 31 May 2023 | Malloy Aeronautics TRV-150 | Territorial Defense Forces of Ukraine | 47 | Fatalities: 0 / Occupants: 0 | 0 | Substantial | Kursk Oblast - Russia | Combat | Military | On 31 May 2023, Russian sources reported that a British made T150 heavy cargo drone had been downed over the Kursk region. This was the first reported time the British vehicle was reported to have been operating within the internationally recognised borders of the Russian Federation. Russian Border Service forces took responsibility for its downing. Given the timing of the downing of the drone, it is evident that the aircraft was involved in supporting operations of Ukrainian backed anti-Russian insurgents in conducting cross border raids into Belgorod Oblast in Russia, taking place from 22 to 23 May. Ukrainian forces have acknowledged involvement with the Freedom of Russia Legion, but has denied affiliation with the far-right Russian Volunteer Corps, despite statements from the RVC itself. International observers consider these groups to be embedded within the International Legion of the Territorial Defense Forces of Ukraine. According to their data, this is the first time a British drone has flown into Russian territory. Until now, the Ukrainian Armed Forces have used such aircraft exclusively inside the country. The drone was shot down by border guards. The drone suffered damage from being shot down, in addition to dismounting its payload of an 82mm mortar shell. The drone is able to hold up to three of these shells. The shell could still be found located under the drone itself. T150 drones were originally supplied by the United Kingdom to Ukraine for logistics purposes. However, the downing of this drone shows that they are now additionally being used in a combat role as a drone bomber. In addition, a radio repeater was installed on the drone, with the intent to either extend the range of the drone, or act as a secondary means of communications. | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description | |||||||||||||||
| Drone accidents (civilian only) | 2023 | Monday 3 April 2023 | Athlon Avia A1-SM Furia | Ukrainian Ground Forces | Fatalities: 0 / Occupants: 0 | 0 | Destroyed | - Ukraine | En route | Military | An A1-SM Furia of the Ukrainian Ground Forces was downed by forces of the Russian Airborne Forces (VDV). | This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information. Corrections or additions? ... Edit this accident description |
数据更新频率
年度更新