Regulations & Safety
Angara Airlines Antonov An-24 Crash in Russia Highlights Aging Fleet Risks
Angara Airlines Flight 2311 crashed near Tynda, Russia, killing 48. The incident raises concerns about aging Soviet-era aircraft and aviation safety in remote regions.
Tragedy in the Skies: Angara Airlines Crash in Russia’s Far East
On July 24, 2025, a domestic flight operated by Angara Airlines ended in tragedy when an Antonov An-24 Commercial-Aircraft crashed during a second landing attempt near Tynda, in Russia’s Amur Oblast. All 48 people aboard, including 42 passengers and 6 crew members, lost their lives. The crash site, discovered hours later in a mountainous forested area, revealed a burning wreckage with no survivors.
This incident has reignited concerns over the continued use of aging Soviet-era aircraft in Russia’s remote regions, particularly under current geopolitical and economic constraints. It also raises broader questions about aviation safety, regulatory oversight, and the challenges of maintaining older fleets in isolated areas with limited infrastructure.
As investigators work to determine the precise cause of the crash, the tragedy has prompted national mourning, international condolences, and a renewed focus on the risks inherent in operating vintage aircraft under modern conditions.
Background: The Aircraft and the Airline
The Antonov An-24: A Soviet Workhorse
The Antonov An-24, a twin-turboprop aircraft developed in the late 1950s, was designed for rugged conditions and short takeoff and landing capabilities. It became a staple of Soviet regional aviation, with over 1,300 units produced. Despite its durability and simplicity, the aircraft’s design and technology are now considered outdated by modern aviation standards.
The plane involved in the crash, tail number RA-47315, was manufactured in 1976, making it nearly five decades old. According to public records, it had a documented history of at least four incidents since 2018. Nevertheless, it passed a technical inspection in 2021 and held an airworthiness certificate valid until 2036. This raises questions about the effectiveness and rigor of maintenance and inspection protocols for aging aircraft still in service.
While the An-24 is no longer produced, it remains operational in parts of Russia and Africa, largely due to its ability to handle unpaved runways and extreme weather, features that are critical in remote regions. However, its safety record is mixed, with over 60 accidents involving An-24s reported since 2000, according to aviation safety databases.
“The Antonov An-24 was built for resilience, not comfort or modern safety standards. Its continued use reflects necessity more than choice.”, Aviation Historian, Aviamuseum Ukraine
Angara Airlines: Serving the Remote Corners
Angara Airlines, based in Irkutsk, operates a fleet primarily consisting of Soviet-era aircraft, including multiple An-24s built between 1972 and 1976. The Airlines serves remote Siberian and Far Eastern destinations where alternative transport options are limited or non-existent.
Despite its crucial regional role, Angara Airlines has faced scrutiny over its safety record. Notable incidents include a 2011 ditching in the Ob River that resulted in seven fatalities and a 2019 runway overrun that killed two people. The airline’s reliance on older aircraft has been a point of concern for aviation analysts, especially given the challenges of maintaining such planes amid limited access to spare parts.
In the aftermath of the 2025 crash, the company has pledged full cooperation with investigators and expressed condolences to the victims’ families. It also announced internal reviews of its maintenance and training procedures, although public trust may take time to rebuild.
Crash Details and Investigation
The Flight and the Fatal Descent
The ill-fated flight originated in Khabarovsk and made a scheduled stop in Blagoveshchensk before heading to its final destination in Tynda. The aircraft experienced a 95-minute delay due to adverse weather conditions before departing for the final leg of the journey.
At approximately 1:00 PM local time, the plane disappeared from radar during its second attempt to land at Tynda Airport. No distress signal was received from the crew, which is unusual for a crash of this nature. Search and rescue operations commenced promptly, and by 5:30 PM, a helicopter located the burning wreckage approximately 16 kilometers south of the airport in a mountainous and densely forested area.
Rescue teams reached the site several hours later and confirmed that all 48 individuals on board had perished. Among the victims were five children and one Chinese national. A local woman, who missed the flight due to her granddaughter falling ill, later shared her story, a poignant reminder of fate’s unpredictability.
Preliminary Findings and Official Response
Initial reports from Russia’s Emergency Situations Ministry and the Investigative Committee suggest that poor visibility and possible pilot error were contributing factors. The aircraft was on its second landing attempt under difficult weather conditions, and the lack of a distress call suggests a sudden loss of control or situational awareness.
Flight recorders, commonly known as black boxes, were recovered from the site and are currently undergoing analysis. Investigators are exploring multiple angles, including technical malfunction, crew performance, and air traffic control communication. A criminal case has been opened under Russian law for alleged violations of air safety regulations.
In response to the tragedy, authorities declared three days of mourning in the Amur region. Financial compensation of 5 million rubles (approximately $63,000) per victim has been promised to the families. International condolences poured in from neighboring countries, including China and Belarus.
Broader Implications and Industry Challenges
Aging Aircraft and Sanction Pressures
The crash has brought renewed attention to the challenges of operating aging aircraft in Russia’s vast and often inaccessible regions. With Western sanctions restricting access to spare parts and new aircraft acquisitions, Russian airlines have increasingly relied on older Soviet-era models like the An-24 and An-26.
Experts warn that while these aircraft are robust, they are not immune to wear and tear. Maintenance becomes increasingly complex and costly as parts become harder to source. Additionally, training pilots to handle these older systems, which lack modern avionics, adds another layer of operational risk.
The aviation industry in Russia is at a crossroads. Without significant investment in fleet modernization or the development of reliable domestic alternatives, incidents like the Angara crash may become more frequent. The situation underscores the broader impact of geopolitical tensions on public Safety and infrastructure.
“Sanctions don’t just affect governments, they trickle down to impact safety in the skies. This crash is a tragic example of that reality.”, Aviation Analyst, DW News
Regional Dependency and Safety Trade-Offs
In regions like Amur Oblast, aviation is often the only viable form of transportation due to vast distances and limited road or rail access. This makes aircraft like the An-24 indispensable, despite their age and associated risks.
Local governments and airlines face a difficult balancing act: ensuring connectivity while managing safety and cost. The lack of infrastructure investment in remote areas further exacerbates the problem, leaving few alternatives to these aging airframes.
Some aviation experts advocate for the development of newer, rugged aircraft tailored to remote operations. However, such initiatives require long-term planning, funding, and international cooperation, all of which are currently constrained by Russia’s political and economic isolation.
Conclusion
The crash of Angara Airlines Flight 2311 is a sobering reminder of the risks associated with operating outdated aircraft in challenging environments. While the An-24 has served reliably for decades, its continued use underlines systemic issues within Russia’s aviation sector, from regulatory oversight to infrastructure limitations and geopolitical constraints.
As investigations proceed, the focus must shift toward long-term solutions that prioritize passenger safety without compromising regional connectivity. Modernizing fleets, improving pilot training, and reassessing maintenance protocols are essential steps to prevent future tragedies. The world will be watching how Russia responds, not just with words, but with meaningful action.
FAQ
What type of aircraft was involved in the crash?
The aircraft was an Antonov An-24, a Soviet-era twin-turboprop plane built in 1976.
How many people were on board?
There were 48 people on board, including 42 passengers and 6 crew members. All perished in the crash.
What caused the crash?
Preliminary findings suggest poor visibility and possible pilot error during a second landing attempt. Investigations are ongoing.
Is Angara Airlines considered safe?
Angara Airlines has a mixed safety record, with previous incidents in 2011 and 2019. It operates older aircraft, which raises safety concerns.
What steps are being taken after the crash?
Authorities have launched a criminal investigation, recovered flight recorders, and declared a period of mourning. Compensation has been promised to victims’ families.
Sources:
Photo Credit: Wikidata
Regulations & Safety
FAA Investigates Southwest Airlines Ground Collision at PVD
Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.
This is a developing story. Information may change as official details are released.
This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.
The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.
The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.
Details of the ground collision
At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).
Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.
“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”
the airline stated in remarks provided to local media, adding that safety remains its highest priority.
Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.
Regulatory response and recent precedent
The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.
This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.
AirPro News analysis
We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.
Sources: WPRI
Photo Credit: Zachary Reis
Regulations & Safety
Turkish Airlines 777-300ER Wing Strike at Antalya Airport
A Turkish Airlines Boeing 777-300ER struck a radar antenna pole taxiing at Antalya Airport, prompting evacuation and a formal investigation.
This is a developing story. Information may change as official details are released.
This article summarizes reporting by Hürriyet.
A Turkish Airlines (TK) Boeing 777-300ER sustained damage and prompted a passenger evacuation after its right wing struck a ground radar antenna pole while taxiing at Antalya Airport (AYT) on June 11, 2026.
The incident, which occurred at approximately 20:00 local time following Flight TK2430 from Istanbul, resulted in minor injuries among the passengers. According to official statements reported by Hürriyet, the widebody aircraft was maneuvering toward its parking position on Apron-1 when the collision occurred, leading to an immediate evacuation on the tarmac.
Conflicting passenger and injury reports
Following the evacuation, official sources provided conflicting figures regarding the number of passengers on board and the extent of injuries. In a public statement, Turkish Airlines Senior Vice President of Communications Yahya Üstün confirmed the evacuation, stating that 267 passengers were safely removed from the aircraft. The airline reported that one passenger sustained minor injuries and was in good health.
Conversely, the Turkey Ministry of Transport released a separate statement indicating a higher passenger count. The ministry reported that the aircraft was carrying 284 adult passengers and four infants. Furthermore, the government authority stated that three passengers suffered minor injuries during the event. Both entities confirmed that the aircraft, registered as TC-LKD, was towed to a parking area after the necessary safety checks and passenger removal were completed.
Investigation into the ground collision
A technical investigation into the ground collision has been initiated by the Turkey Ministry of Transport and the General Directorate of State Airports Authority (DHMI). The official cause of the incident remains under investigation.
While the airline noted the aircraft was approaching its parking position, preliminary remarks from the Ministry of Transport suggested the Boeing 777-300ER made contact with the radar pole after entering an incorrect taxiway line. Final determinations regarding the aircraft routing, ground control instructions, and the sequence of events will be established by the investigating authorities.
AirPro News analysis
Ground collisions involving widebody aircraft like the Boeing 777-300ER often highlight the tight tolerances required when maneuvering large airframes around airport infrastructure. While we await the official investigation findings, safety reviews following such events typically examine airport taxiway markings, lighting, and the clarity of ground control communications. The discrepancy in passenger manifests between the operator and the regulator is a notable detail, though initial reporting conflicts frequently occur in the immediate aftermath of an evacuation before final reconciliations are completed.
Sources: X.com
Photo Credit: X
Regulations & Safety
NTSB Final Report: Southwest Flight 4273 Turbulence Encounter
NTSB cites ATC communication delays and sector overload in Southwest Airlines turbulence event over Gulf of Mexico.
This is original reporting and analysis by AirPro News.
The National Transportation Safety Board (NTSB) has released its final report on a severe turbulence encounter involving a Southwest Airlines Boeing 737-700, detailing how rapidly developing convective weather and air traffic control communication delays factored into an event that seriously injured two people.
The April 3, 2024, incident aboard Southwest Airlines Flight 4273 over the Gulf of Mexico highlights the operational risks when severe weather systems intersect with technical limitations at air traffic control facilities. According to the NTSB investigation, the aircraft was navigating complex weather en route from New Orleans to Orlando when the encounter occurred, resulting in serious injuries to one flight attendant and one passenger, alongside minor injuries to a second flight attendant.
Weather conditions and the turbulence encounter
Flight 4273, operated by a Boeing 737-700 (registration N567WN) with 140 passengers and five crew members on board, was traveling from Louis Armstrong New Orleans International Airport (MSY) to Orlando International Airport (MCO).
At 11:55 UTC, a Convective Significant Meteorological Information (SIGMET) advisory was issued for the region, warning of cloud tops exceeding 45,000 feet.
At approximately 08:20 Eastern Daylight Time, the aircraft encountered severe turbulence over the Gulf of Mexico. The NTSB confirmed the aircraft itself sustained no damage during the event and the flight crew was able to continue the flight.
Air traffic control workload and technical limitations
The NTSB report outlines compounding factors at the Jacksonville Air Route Traffic Control Center (JAX ARTCC) that affected the flight routing through the weather system.
During the incident, the specific JAX ARTCC sector was managing a traffic volume that exceeded its target capacity of 20 aircraft.
This high workload was exacerbated by a technical limitation involving the facility communication infrastructure. The primary VHF antenna at JAX ARTCC had been rendered inoperative following a fire in October 2023. As a result, controllers were utilizing a temporary satellite relay connection to communicate with aircraft in the sector.
The NTSB determined this satellite relay introduced a 600-millisecond round-trip transmission delay, complicating timely communication between controllers and flight crews navigating the dynamic weather environment.
AirPro News analysis
We note that the findings in this final report underscore a critical vulnerability in the National Airspace System. When primary communication infrastructure fails, the fallback systems must be robust enough to handle high-stress, time-critical scenarios like severe convective weather deviation. A 600-millisecond delay might seem negligible in routine operations, but in a saturated sector where controllers are issuing rapid heading changes to keep aircraft clear of building storm cells, that latency degrades situational awareness and increases the risk of weather encounters. The NTSB documentation of this technical shortfall will likely prompt further scrutiny of contingency communication systems at major en route centers.
Photo Credit: NTSB
-
Technology & Innovation2 days agoAirbus Vision Landing Application Enables AI Autoland
-
Route Development5 days agoDubai International Airport to Close in 2035 for Al Maktoum
-
Defense & Military6 days agoWhisper Aero Launches Collaborative Logistics Aircraft for US Military
-
Commercial Aviation5 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
MRO & Manufacturing5 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog