NTSB Releases Preliminary Findings on Fatal Louisiana Crash

On October 21, 2025, a Raytheon Aircraft Company G58, a twin-engine aircraft registered as N16PV, crashed in a pasture near Carencro, Louisiana, while on approach to Lafayette Regional Airport. The accident resulted in the fatal injuries of the commercial pilot and two passengers. In the weeks following the tragic event, the National Transportation Safety Board (NTSB) has been conducting a thorough investigation to understand the sequence of events that led to the crash. The agency has now released its preliminary report, offering the first official, fact-based look into the aircraft’s final moments.

It is crucial to understand the role of a preliminary report in an aviation accident investigation. This document is not intended to provide a probable cause, that determination will come much later in a final, more comprehensive report. Instead, the preliminary findings serve to lay out the established facts gathered from the accident site, air traffic control communications, witness statements, and initial examinations of the wreckage. It provides a timeline and a factual foundation upon which the rest of the investigation will be built. The information is subject to change as more evidence is analyzed.

The flight, operated by Align Aviation LLC under Part 91 for business purposes, had departed from David Wayne Hooks Memorial Airport in Houston, Texas. Its destination was Lafayette, a routine flight that ended tragically just miles from the runway. The NTSB’s initial findings focus on the pilot’s last communication, physical evidence from the engines, and the aircraft’s configuration at the time of impact, painting a complex picture that investigators are now working to decipher.

The Final Moments of Flight N16PV

The sequence of events in the final minutes of the flight provides critical clues for investigators. The pilot’s communication with air traffic control, combined with video evidence of the crash, establishes a timeline that pinpoints when the emergency began and how it progressed. These moments, from the initial report of trouble to the final impact, are the central focus of the NTSB’s preliminary analysis.

An Unspecified Engine Issue

The flight appeared to be proceeding normally until it was approximately nine nautical miles northwest of Lafayette Regional Airport. At an altitude of 1,300 feet, the pilot contacted air traffic control to report an “unspecified engine issue.” This communication is a pivotal point in the accident timeline. The pilot did not detail the exact nature of the problem but immediately requested a direct route to the airport, a clear indication that the situation required an expedited landing. ATC responded by clearing the flight to proceed directly to runway 11.

Following this exchange, there were no further transmissions from the aircraft. This radio silence suggests the pilot was likely dealing with a rapidly escalating situation that demanded his full attention. For investigators, the lack of further detail about the engine issue means they must rely entirely on the physical evidence from the wreckage to understand what was happening in the cockpit. The flight was operating in Visual Meteorological Conditions (VMC), with 10 miles of visibility and scattered clouds, ruling out weather as a primary factor in the accident.

The aircraft’s position at 1,300 feet and nine miles from the airport provided limited time and altitude to manage a critical emergency. While a twin-engine aircraft like the Raytheon G58 is designed to fly with one engine inoperative, controlling it requires a specific and timely sequence of actions from the pilot. The “unspecified” nature of the reported issue leaves open a range of possibilities, from a partial power loss to a complete engine failure.

The Crash Sequence

Evidence from the ground helped fill in the gaps left by the radio silence. A surveillance video captured the airplane’s final moments, showing it in a right spin before it disappeared from view and impacted the terrain. An aerodynamic spin is an aggravated stall condition where one wing is stalled more deeply than the other, causing the aircraft to descend in a corkscrew-like path. At low altitudes, recovering from a spin is extremely difficult, if not impossible.

Adding another layer to the investigation, a sound consistent with an operating engine was also recorded around the time of the crash. This audio evidence, paired with the visual of a spin, points away from a scenario where both engines had completely failed. Instead, it suggests a possible asymmetric thrust condition, where one engine was producing power while the other was not. This imbalance can create significant control challenges, and if not managed correctly, can lead to a loss of control and a spin.

The combination of a reported engine issue, a subsequent spin, and the sound of a running engine provides investigators with a clear direction. The focus shifts to why the aircraft lost aerodynamic control. The investigation will now delve deeper into the performance of a G58 Baron during single-engine operations and what could have led to this catastrophic loss of control so close to its destination.

Analyzing the Evidence on the Ground

Once on site, NTSB investigators began the meticulous process of examining the wreckage. The physical condition of the engines, propellers, and flight controls provides a tangible record of the aircraft’s state at the moment of impact. These findings are compared against the pilot’s report and other data to build a cohesive understanding of the accident sequence.

Engine and Propeller Findings

The post-accident examination of the aircraft’s two engines and their propellers revealed a significant discrepancy. The left engine’s propeller blades showed clear signs of being under power at impact, exhibiting “torsional bending and twisting.” This type of damage occurs when the propeller is rotating with significant force as it strikes the ground. This finding aligns with the recorded sound of an operating engine.

In stark contrast, the right engine’s propeller blades were found to be relatively straight. This suggests the right engine was not producing significant power, if any, at the time of the crash. Critically, the NTSB noted that the blades were not in the “feathered” position. In a multi-engine aircraft, feathering a propeller involves turning the blades to be parallel with the airflow after an engine failure. This action dramatically reduces drag and is a critical step in maintaining control. An unfeathered, windmilling propeller on a failed engine creates substantial drag, making the aircraft much more difficult to fly.

The discovery that the right engine’s propeller was not feathered is a key piece of evidence. It raises questions about the sequence of events in the cockpit and whether the pilot had sufficient time or control to perform the necessary emergency procedures.

Further examination of the cockpit controls showed that the propeller levers for both engines were in similar, unfeathered positions. This finding complicates the picture. It could indicate that the pilot was unable to feather the prop, that the failure was so sudden there was no time, or that the nature of the “unspecified engine issue” was not a straightforward failure. This is a central question that the NTSB will seek to answer through more detailed analysis.

Aircraft Configuration and Systems

Investigators also documented the overall state of the aircraft. The landing gear and wing flaps were both found in the retracted position. This is consistent with the phase of flight, as the aircraft was still several miles from the airport and had not yet been configured for landing. This detail helps confirm that the emergency began before the final approach sequence was initiated.

Perhaps one of the most important preliminary findings is that an initial examination of the flight control system and both engines found “no mechanical anomalies that would have prevented normal operation.” This statement means that, upon initial inspection, investigators did not find any obvious pre-impact failures, such as a broken control cable or a disconnected engine part. The search for the root cause will therefore require a much deeper, more forensic level of investigation.

The absence of obvious mechanical failures does not mean the aircraft was perfectly healthy. It simply means the cause of the engine issue was not immediately apparent from the wreckage. The investigation will now proceed to a more detailed phase, which will likely include a complete teardown of both engines, analysis of fuel samples, and a thorough review of the aircraft’s maintenance records to search for more subtle clues that could explain the events of October 21.

An Ongoing Investigation

The preliminary report from the NTSB provides a clear but incomplete picture of the final moments of N16PV. The key takeaways are centered on the pilot’s report of an engine issue, followed by a loss of control resulting in a spin at low altitude. The physical evidence strongly suggests an asymmetric thrust condition, with the left engine operating and the right engine not, compounded by the fact that the right propeller was not feathered. The lack of any obvious pre-impact mechanical failures points to a complex scenario that demands further scrutiny.

The NTSB’s work is far from over. The path forward involves a methodical and detailed analysis of every component of the aircraft, its maintenance history, and the pilot’s records. Investigators will conduct engine teardowns at their laboratory facilities, looking for internal failures or operational issues that would not be visible during an on-site examination. This process can take many months. The final report, which will likely not be released for 12 to 24 months, will aim to provide a probable cause for the accident, offering answers to the victims’ families and valuable safety lessons for the aviation community.

FAQ

Question: What is a preliminary NTSB report?
Answer: A preliminary report is an initial summary of facts collected by investigators in the immediate aftermath of an accident. It outlines the timeline of events and the initial findings from the wreckage but does not determine a probable cause. The information is subject to change as the investigation continues.

Question: What does it mean if an engine propeller is “not feathered”?
Answer: In a multi-engine aircraft, if an engine fails, the pilot is trained to “feather” the propeller, which means turning the blades to be parallel with the direction of flight. This minimizes drag. A non-feathered propeller on a failed engine acts like a large airbrake, creating significant drag that can make the aircraft difficult to control, especially at low speeds.

Question: What are the next steps in the NTSB’s investigation?
Answer: The NTSB will continue its investigation by performing detailed teardowns and analysis of the engines and other aircraft systems. They will also review maintenance records, the pilot’s training and medical history, and any other relevant data. The goal is to produce a final report that identifies a probable cause for the accident.

Sources

• NTSB Preliminary Report CEN26FA026