Regulations & Safety
NTSB Preliminary Report on Cirrus SR22 Crash in Lexington SC
NTSB reports engine failure caused fatal Cirrus SR22 crash in Lexington, South Carolina. Investigation continues with engine and fuel system analysis.

This article is based on an official preliminary report from the National Transportation Safety Board (NTSB) and public records regarding the investigation.
NTSB Issues Preliminary Findings on Fatal Cirrus SR22 Crash in Lexington, South Carolina
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal aviation accident that occurred on February 6, 2026, in Lexington County, South Carolina. The crash of the Cirrus Design Corp SR22 Commercial-Aircraft, registered as N705CD, resulted in the death of the passenger and serious injuries to the pilot. The Investigation is ongoing, with initial findings pointing to a complete loss of engine power during the cruise phase of the flight.
According to the NTSB’s preliminary document, the single-engine aircraft was attempting an emergency diversion to a nearby private airfield when it impacted terrain short of the runway. The report provides the first official timeline of the events leading up to the tragedy, confirming that the pilot explicitly communicated an engine failure to air traffic control moments before the descent.
While the preliminary report establishes the factual circumstances of the flight, it does not yet determine a probable cause. Investigators have recovered key Avionics data and are proceeding with a detailed examination of the engine and fuel systems.
Flight History and Sequence of Events
Departure and Initial Climb
The flight originated from Columbia Metropolitan Airport (CAE) in South Carolina, with a planned destination of Decatur, Alabama. The NTSB report notes that the pilot and passenger arrived at the aircraft at approximately 8:00 AM EST. In an effort to prepare the aircraft for flight, they reportedly moved the plane into the sunlight to “warm it up and melt the frost” before departure.
The aircraft took off at approximately 9:05 AM. Investigators described the initial climb and the early portion of the flight as “unremarkable.” The aircraft reached a cruising altitude of 8,000 feet mean sea level (MSL) and had traveled approximately 13 nautical miles from Columbia when the emergency began.
Engine Failure and Emergency Descent
Data indicates that shortly after establishing cruise altitude, the pilot declared a “Mayday” to air traffic control. The NTSB report highlights the pilot’s direct communication regarding the mechanical state of the aircraft.
“We just lost our engine.”
, Pilot communication cited in the NTSB Preliminary Report
Following the loss of power, the pilot attempted to divert to White Plains Airport (SC99), a private airfield located in Gilbert, South Carolina. Flight tracking data and security footage reviewed by investigators showed the aircraft’s propeller was “windmilling,” spinning solely due to airflow rather than engine power, during the descent.
Despite maneuvering toward the landing strip, the aircraft could not maintain sufficient altitude to reach the runway threshold. The report states that the plane crashed approximately 1,800 feet short of the runway, impacting trees and terrain.
Wreckage Examination and Recovery
Impact and Scene Conditions
The impact sequence caused the aircraft to tumble and roll for approximately 200 feet before coming to rest in an inverted position. Significantly, the NTSB noted there was no post-crash fire. The absence of fire often preserves critical evidence, allowing investigators to better analyze fuel lines, tanks, and avionics systems for potential blockages or failures.
Local law enforcement and the Lexington County Coroner’s Office identified the deceased passenger as Andrew Frederick Nichols, 30, of Huntsville, Alabama. The pilot survived with serious injuries and was transported for medical treatment.
Parachute System Status
The Cirrus SR22 is equipped with the Cirrus Airframe Parachute System (CAPS), a ballistic parachute designed to lower the entire aircraft to the ground in emergencies. The NTSB investigation confirmed that the CAPS was not deployed during the incident.
Because the system was not activated, the rocket-propelled parachute remained armed within the wreckage. This presented a safety hazard for first responders and investigators at the scene. Technical experts from Cirrus Aircraft were dispatched to the site to safely disarm the mechanism before the wreckage could be fully examined or moved.
AirPro News Analysis
The non-deployment of the CAPS system is likely to be a focal point of the ongoing investigation. While the system is a hallmark Safety feature of Cirrus aircraft, its effective use depends on altitude, airspeed, and pilot decision-making timeframes. In this instance, the pilot opted for an emergency landing at a nearby Airports rather than a parachute deployment. The NTSB will likely analyze whether the altitude and position relative to the airport influenced this decision.
Furthermore, engine failure at cruise altitude (8,000 feet) is statistically less common than failures during high-stress phases like takeoff or climb. This suggests the investigation will look closely at fuel delivery issues, mechanical breakage, or oil starvation, rather than low-altitude maneuvering errors.
Next Steps in the Investigation
The NTSB has emphasized that the current report is preliminary and subject to change as new information becomes available. The wreckage has been recovered for a more granular inspection.
Focus Areas
- Engine Teardown: The engine will undergo a complete disassembly to identify any internal mechanical failures, such as fractured components or lubrication issues.
- Fuel Analysis: Investigators will test fuel samples and delivery systems to rule out contamination or blockage.
- Weather and Environment: Although the flight reached cruise altitude, the pre-flight mention of “melting frost” will be reviewed to ensure no residual ice contamination affected the airframe, though the nature of the engine failure makes this a secondary line of inquiry.
- Data Recovery: The recovery of the aircraft’s flight display systems (avionics) will provide investigators with precise data logs, similar to a “black box,” revealing engine parameters and flight control inputs leading up to the crash.
A final factual report and a determination of probable cause are expected to take between 12 and 18 months to complete.
Sources:
NTSB Preliminary Report (ERA26FAxxx)
Lexington County Coroner’s Office
Photo Credit: NTSB
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
Regulations & Safety
Sinkhole Closes Primary Runway at Tri-Cities Airport
A 20-ft-wide, 17-ft-deep sinkhole forced closure of Runway 5/23 at TRI on June 9, 2026, disrupting airline operations.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by WSMV by Li Cohen, Kingsport Times News, and official statements from the Tri-Cities Airport Authority.
A massive sinkhole measuring 20 feet wide and 17 feet deep forced the immediate closure of the primary commercial runway at Tri-Cities Airports (TRI) in East Tennessee on June 9, 2026, disrupting airline operations. The subsurface void was discovered beneath Runway 5/23, prompting airport officials to halt traffic on the strip while engineering teams assess the structural integrity of the pavement.
Airport personnel initially identified a surface condition requiring evaluation on the runway on Tuesday. Subsequent investigation by the Tri-Cities Airport Authority revealed the extensive 20-by-20-by-17-foot void, leading to an extended closure through at least June 10, 2026, according to official airport updates.
Operational impact and airline response
Runway 5/23 serves as the primary long runway for commercial flights at the Blountville facility. Its sudden closure has shifted the burden of operational decisions to individual air carriers, who must evaluate their ability to operate at the airport under current conditions.
Tri-Cities Airport Authority President and CEO Gene Cossey stated that airlines will determine whether to delay or cancel their scheduled flights. According to reporting by Kingsport Times News, Cossey advised passengers to check directly with their respective airlines for status updates before traveling to the terminal.
While the primary commercial strip is out of service, the airport’s secondary runway, Runway 9/27, remains open for operations. However, the shift in runway availability has required dispatchers and flight crews to recalculate performance data to ensure safe operations on the alternate surface.
Infrastructure repairs and geological context
Repair efforts commenced immediately on the evening of June 9. The airport authority emphasized that safety remains the primary concern during the restoration process and that the runway will remain closed until repairs meet regulatory standards.
“The airport will work to fix this problem as quickly as possible, but we always ensure the safety of the traveling public is our primary concern, and we will ensure that the repairs are made as quickly as we can while also ensuring complete safety,” Cossey said, as reported by Kingsport Times News.
Sinkholes are a documented geological hazard in East Tennessee. The region is characterized by karst topography, which consists of highly soluble carbonate rocks that can dissolve and create underground voids over time.
Similar infrastructure challenges have affected other major aviation facilities recently. On May 20, 2026, a sinkhole discovered near Runway 4/22 at New York’s LaGuardia Airport (LGA) forced a runway closure and caused widespread flight disruptions, according to reporting by WBIR.
AirPro News analysis
We note that runway closures due to sudden geological subsidence present unique challenges for airport operators, particularly at regional facilities with limited runway redundancy. While TRI’s Runway 9/27 remains active, its dimensions and weight-bearing capacity may restrict certain commercial operations or require payload penalties compared to the primary Runway 5/23. The rapid identification of the 17-foot-deep void highlights the critical importance of routine daily runway inspections in preventing potential aircraft incidents during takeoff or landing rolls. The timeline for reopening Runway 5/23 will likely depend on the stability of the surrounding soil and the extent of the required fill and repaving work.
Sources: Tri-Cities Airport, WSMV, Kingsport Times News, WBIR
Photo Credit: Kingsport Times News
-
Technology & Innovation1 day agoAirbus Vision Landing Application Enables AI Autoland
-
Commercial Aviation7 days agoEuropean Cargo Limited Enters Administration Grounding Airbus A340 Fleet
-
Commercial Aviation4 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
Route Development4 days agoDubai International Airport to Close in 2035 for Al Maktoum
-
MRO & Manufacturing5 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog
