Cessna Citation 550 Crash on Approach Near Statesville, NC (N257BW)

On December 18, 2025, a Cessna Citation 550 crashed near Statesville, North Carolina. The aircraft was destroyed during an approach sequence back toward Statesville Regional Airport, and all seven occupants were fatally injured. Federal investigators are examining the accident, recorded data, and the aircraft’s systems and operations.

Accident Summary

What Happened

The aircraft was positioned on the south parking ramp at Statesville Regional Airport (SVH) for passenger loading and preflight, and ground personnel reported it was fully fueled before departure. Cockpit voice recorder audio indicates that after an initial unsuccessful start of the left engine, both engines were started around 0953, and the airplane taxied to runway 10 for departure. During taxi, the pilot and two pilot-rated passengers discussed an inoperative thrust reverser indicator light for an unspecified engine, while stating the thrust reverser itself was working properly.

The flight departed runway 10 under visual flight rules around 1006, with the pilot intending to activate an IFR flight plan to SRQ once airborne. During the takeoff roll, a passenger in the cabin commented that the left engine appeared to be producing more power than the right and suggested a gauge issue; the takeoff continued. Preliminary GPS data described a climbing left turn after departure, and a right-seat passenger attempted to contact ATC to activate the IFR flight plan but did not establish contact.

CVR audio captured later remarks indicating the pilot believed his altitude indicator was not working properly and that additional left-side flight instruments may not have been working properly. The recorded GPS/navigation data also included gaps in certain parameters during portions of the flight. Around 1011, control was reportedly transferred to the right-seat passenger at approximately 4,500 feet msl; the recording did not capture comments indicating malfunctions with the right-side flight instruments.

After additional maneuvering and discussion about seeing the ground, the airplane turned toward runway 28. The right-seat passenger reported acquiring the runway visually and provided directional guidance, followed shortly by the pilot indicating he had the runway in sight. The recorded navigation data showed decreasing airspeed and altitude on final approach, with the final data ending around 1015:23.

Investigators documented the first identified point of impact as the first light station of the runway 28 approach lighting system (MALSR) approximately 1,380 feet from the runway threshold, followed by additional impacts along the approach/overrun area and a debris path leading to the main wreckage in the runway blast area. A post-impact fire consumed much of the fuselage and heat-damaged the wings, empennage, and both engines.

Aircraft and Operational Context

The aircraft was a Cessna 550 operated under 14 CFR Part 91 as a personal flight, with an airline transport pilot-rated pilot in the left seat. The pilot held multiple type ratings, and his CE-500 type rating included a limitation stating “CE-500 Second in Command Required.” The right-seat occupant held a private pilot certificate with an instrument rating and had about 175.3 total hours logged as of late November 2025; the preliminary report states he was not qualified to perform second-in-command duties under 14 CFR 61.55.

The preliminary report describes additional pilot-rated passengers seated in the cabin area near the cockpit. It also documents the taxi discussion regarding a thrust reverser indicator light being inoperative, and the cabin comment during takeoff about a perceived left/right engine power difference and a possible faulty gauge. In documented wreckage findings, both thrust reversers were found in the stowed position, investigators reported no evidence of uncontained engine failure, and no observed evidence of pre-impact structural separation.

Weather information in the preliminary report includes earlier automated observations showing ceilings in the several-thousand-foot range, and a 1015 report describing reduced visibility with heavy drizzle and broken ceilings as low as 1,200 feet above ground level. The preliminary report lists conditions at the accident site as instrument meteorological conditions.

Accident Investigation

NTSB investigations develop in stages—from initial scene documentation and recorded-data review to component examinations, systems testing, and follow-on factual reports—before conclusions are reached, as outlined at /aviation-insights/ntsb-investigation-process/. In this case, the NTSB reported it traveled to the scene and recovered a Fairchild GA-100 tape-based cockpit voice recorder. Portions of the recording required extraordinary measures to make intelligible due to a poor signal-to-noise ratio, and the aircraft was not equipped with (nor required to have) a flight data recorder.

The NTSB also recovered a Garmin GTN-750 unit capable of recording certain parameters, and the preliminary report describes how recorded data were used to summarize the flight path and key sequence points. The agency’s documented wreckage path included approach lighting impacts, damaged trees, ground impressions, and fire-related ground scorching leading to the main wreckage location.

Parties to the investigation listed in the preliminary report include the FAA, Textron Aviation, and Pratt & Whitney Canada. As the investigation continues, investigators typically evaluate aircraft records and maintenance history, cockpit avionics and electrical distribution, flight instruments and pitot-static systems, engine indications and performance evidence, and the operational decision-making reflected in available communications and recorded data.

Operational and Regulatory Issues

Based on the preliminary report, investigators will likely scrutinize the operational context of a Part 91 personal flight that departed VFR with an intention to activate an IFR flight plan once airborne, including the timing of ATC contact attempts and the reported inability to obtain an IFR clearance during the departure/return sequence. They will also evaluate how deteriorating ceilings and visibility reported around the time of the accident related to flight planning, workload, and approach execution, without assuming a cause.

The preliminary report highlights a qualification issue that may be examined as part of the broader operational picture: the pilot’s type rating limitation indicating a second-in-command requirement and the report’s statement that the right-seat occupant was not qualified to perform second-in-command duties under 14 CFR 61.55. Investigators commonly examine crew roles, task-sharing, checklist execution, and decision points as reflected in CVR audio and available avionics data, particularly when abnormal indications or instrument concerns are described.

Aviation Accident Litigation

When a fatal aviation accident occurs, civil litigation often proceeds in parallel with (but separate from) the NTSB’s safety-focused investigation, with different standards, discovery tools, and objectives described at Aviation Accident Litigation. In cases involving complex aircraft systems, recorded-data issues, and operational questions, parties may seek to preserve evidence, obtain maintenance and component histories, and evaluate how the factual record develops over time.

Potential civil issues that are commonly evaluated—depending on the facts established—can include aircraft and component condition, inspection and maintenance practices, avionics and instrument functionality, operational oversight, and the roles of multiple entities involved with ownership, leasing, maintenance, or manufacturing, similar to matters summarized at Representative Aviation Verdicts. Any such analysis is fact-dependent and should track the investigative record as it becomes publicly available.

Where cases proceed to resolution, outcomes typically turn on detailed technical proof, causation analysis, and damages evidence, consistent with the kinds of case records reflected at Selected Settlements and Verdicts. Early-stage reporting is often incomplete, so definitive conclusions should be avoided until the factual record is developed.

Over time, broader patterns in aviation civil outcomes are sometimes discussed in terms of aircraft category, operational context, and injury severity, as summarized at Aviation Crash Verdict Trends. For this accident, the NTSB preliminary report provides an initial factual framework, and additional public documentation may clarify systems status, performance evidence, and operational circumstances.