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
NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure
NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.

The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.
The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.
Mechanical sequence and rejected takeoff
The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.
During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.
The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.
Emergency evacuation and passenger behavior
Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.
The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.
The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.
AirPro News analysis
The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).
When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
Marine One Loss of Separation at DCA: NTSB Preliminary Report
NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.

This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.
According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.
Incident timeline and separation data
The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.
President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.
Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.
No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.
Communication failure and FAA response
The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.
Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.
CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.
Regulatory context and prior airspace changes
The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.
Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.
Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.
AirPro News analysis
The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision
FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.
The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.
The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”
Disciplinary actions and union response
The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.
The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.
The March 22 collision and investigation
The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.
Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.
It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.
Regulatory response to surface safety
Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.
These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.
AirPro News analysis
We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.
Photo Credit: Mike Segar – Reuters
-
Technology & Innovation6 days agoSkyband Systems M100 LRU Validates GNSS Jamming Protection
-
MRO & Manufacturing5 days agoBoeing SPEEA Engineers Reject Contract, Authorize Strike
-
Military Technology6 days agoSaab Unveils A3-001 Supersonic Stealth Drone Concept
-
Business Aviation5 days agoFTAI Aviation Closes $2B Warehouse Financing for 2026 SPV
-
Business Aviation6 days agoSyberJet SJ30-2 Sets Transcontinental Speed Record
