Regulations & Safety
NTSB Preliminary Report on Statesville Cessna Citation Crash
NTSB releases preliminary findings on the December 2025 Cessna Citation crash in Statesville, NC, involving engine issues and pilot certification questions.
This article is based on an official preliminary report and investigation details released by the National Transportation Safety Board (NTSB) Preliminary Report.
NTSB Releases Preliminary Report on Statesville Cessna Citation Crash
The National Transportation Safety Board (NTSB) has issued its preliminary report regarding the December 18, 2025, crash of a Cessna Citation 550 in Statesville, North Carolina. The accident resulted in the fatalities of all seven occupants, including former NASCAR driver Greg Biffle and members of his family.
Released on January 30, 2026, the report (Investigation ID WPR26MA063) provides the first official factual account of the flight’s final minutes. According to investigators, the Private-Jets was attempting to return to Statesville Regional Airport (KSVH) shortly after takeoff due to a reported engine issue when it impacted ground obstacles significantly short of the runway threshold.
While the preliminary document does not determine a probable cause, it establishes critical data points regarding the weather conditions, the pilot’s credentials, and the aircraft’s configuration at the time of impact.
Flight Sequence and “Rough Engine” Report
The flight departed Statesville Regional Airport at approximately 10:05 AM EST, intended for Sarasota-Bradenton International Airport (KSRQ). The NTSB report indicates that the flight lasted only about 10 minutes.
Shortly after departure, the pilot contacted air traffic control to report an issue. According to the NTSB findings, witnesses described the problem as a “rough engine.” Consequently, the pilot requested an immediate return to Statesville.
Investigators confirmed that a passenger on board sent a text message to a family member during the brief flight. The message contained only two words:
“Emergency landing.”
, Text message sent by a passenger, as cited in the NTSB Preliminary Report
Crash Circumstances and Weather Conditions
The NTSB confirmed that the crash occurred under Instrument Meteorological Conditions (IMC). Weather reports from the time of the accident indicate low cloud ceilings and heavy drizzle, which would have required the pilot to rely heavily on aircraft instruments for the approach.
According to the preliminary data, the aircraft was configured for landing with its gear down and landing lights illuminated. However, the plane was flying below the standard glide path for the runway.
The report details the impact sequence:
- The aircraft struck a runway lighting stanchion approximately 1,800 feet short of the runway threshold.
- Following the initial impact, the jet collided with trees, additional lighting structures, and a perimeter fence.
- The debris field extended approximately 180 feet from the initial point of impact.
- A severe post-crash fire consumed the majority of the fuselage and inboard wing sections.
Crew Certification and Single-Pilot Investigation
A significant portion of the NTSB’s factual gathering has focused on the crew composition and certification. The Cessna Citation 550 is certified for a two-pilot crew, though it can be operated by a single pilot if that pilot holds a specific “Single Pilot Exemption” and the aircraft is equipped with the necessary Avionics.
The pilot in command, Dennis Dutton, held an Airline Transport Pilot (ATP) certificate and a type rating for the Cessna Citation (CE-500). He was a commercial captain for a major airline. Seated in the co-pilot seat was his son, Jack Dutton.
However, the NTSB noted that Jack Dutton was a student pilot and did not hold a multi-engine rating or a type rating for the Citation. Therefore, he was not legally qualified to serve as Second-in-Command (SIC) for this specific aircraft.
Investigators are currently verifying whether Dennis Dutton held the required Single Pilot Exemption. If he did not hold this specific exemption, the flight would have legally required a qualified second pilot, which was not present.
Victim Identification
Authorities and the NTSB have confirmed the identities of the seven individuals lost in the Accident:
- Greg Biffle: Retired NASCAR driver and owner of the aircraft via GB Aviation Leasing LLC.
- Cristina Biffle: Wife of Greg Biffle.
- Emma Biffle: Daughter.
- Ryder Biffle: Son.
- Dennis Dutton: The pilot in command.
- Jack Dutton: Student pilot and son of Dennis Dutton.
- Craig Wadsworth: A family friend and member of the NASCAR community.
AirPro News Analysis
The distinction between a “rough engine” report and the final impact location is likely to be a central focus of the ongoing investigation. While engine trouble precipitates an emergency return, it does not automatically result in a crash short of the runway. The presence of Instrument Meteorological Conditions (IMC) adds a layer of complexity.
In low-visibility approaches, altitude management is critical. The NTSB’s notation that the aircraft was stable but “lower than the standard glide path” suggests investigators will look closely at whether the engine issue affected the aircraft’s performance capabilities or if the high-workload environment of a single-pilot emergency return in bad weather contributed to spatial disorientation.
Furthermore, the regulatory scrutiny regarding the Single Pilot Exemption highlights the rigid Standards of corporate aviation. Even highly experienced airline captains must adhere to specific type-rating requirements when flying light jets alone. The absence of a qualified Second-in-Command, if an exemption was not in place, would be a significant regulatory finding.
Next Steps
The NTSB has recovered the Cockpit Voice Recorder (CVR) and transported it to their laboratory in Washington, D.C., for analysis. The aircraft was not equipped with a Flight Data Recorder (FDR), nor was it required to be.
A final report, which will determine the probable cause of the accident, is expected to take between 12 and 24 months to complete. Future investigative phases will include engine teardowns to verify the reported roughness and a detailed review of the pilot’s Training records.
Sources: NTSB Preliminary Report (WPR26MA063), NTSB
Photo Credit: NTSB
Regulations & Safety
FAA Completes Phase One of NOTAM System Cloud Modernization
The FAA finished phase one of the NOTAM system upgrade, migrating to cloud infrastructure to improve safety and reliability ahead of schedule.
The Federal Aviation Administration (FAA) has successfully completed the first phase of a major overhaul to its critical pilot alert system, moving the decades-old infrastructure to the cloud. According to an official press release from the FAA, U.S. Transportation Secretary Sean P. Duffy announced the milestone on May 12, 2026, noting that the project was finished more than a year ahead of its original schedule.
The modernized system, known as Notices to Airmen (NOTAM), is essential for commercial and general aviation. It provides pilots with real-time safety information, including runway closures, airspace restrictions, and potential hazards. The upgrade aims to prevent the kind of nationwide airspace shutdowns that have previously crippled U.S. air travel, while enhancing overall safety and communication reliability.
By transitioning the NOTAM system to a cloud-based architecture in April 2026, the Department of Transportation and the FAA hope to future-proof the nation’s aviation infrastructure. The rapid deployment was achieved through an innovative vendor challenge designed to bypass traditional bureaucratic delays, culminating in a partnership with IT contractor CGI Federal.
Accelerating the NOTAM Modernization
The legacy NOTAM system, which processes more than 4 million alerts annually, had long been a vulnerability in the National Airspace System. Its fragility was most notably exposed in January 2023, when a complete system failure forced a nationwide ground stop, halting thousands of flights and stranding passengers across the country.
Following that incident, initial projections from the previous administration estimated that a full modernization would not be completed until late 2027. However, the current Department of Transportation prioritized the overhaul to mitigate the risk of future collapses, accelerating the timeline significantly.
“The last administration handed us a 40-year old aviation alert system on the verge of complete collapse,” U.S. Transportation Secretary Sean P. Duffy stated in the FAA press release. “Instead of waiting for another nationwide ground stop, we moved at the Speed of Trump to build a brand new, modern system, and we did it years ahead of schedule.”
Technological Upgrades and Industry Impact
The successful completion of Phase One involved migrating the core NOTAM infrastructure into a secure cloud environment. This shift is expected to provide greater redundancy and scalability, ensuring that the system can handle the high volume of critical alerts without buckling under pressure.
The FAA collaborated with CGI Federal to develop the new service, utilizing a streamlined procurement process to accelerate the timeline. The agency also engaged directly with aviation stakeholders, including pilots, dispatchers, and flight planners, to ensure the modernized system meets the practical needs of its end users.
“Our transition to this state-of-the-art NOTAM system strengthens safety and reliability across the National Airspace System,” FAA Administrator Bryan Bedford noted in the official announcement. “We are focused on building a modern aviation system for the future, one that is resilient, efficient, and capable of meeting the demands of the world’s busiest airspace.”
AirPro News analysis
The accelerated timeline for the NOTAM overhaul reflects a broader push by the current Department of Transportation to expedite infrastructure projects through non-traditional procurement methods. By utilizing a “vendor challenge” rather than a standard multi-year bidding process, the FAA was able to rapidly deploy CGI Federal’s cloud solution.
While Phase One represents a significant technical milestone, the true test of the modernized NOTAM system will be its operational stability during peak travel seasons and severe weather events. Furthermore, the transition of the entire system remains ongoing. We will be watching closely to see if subsequent phases can maintain this accelerated pace without compromising the rigorous safety standards required for the National Airspace System.
Frequently Asked Questions
What is the NOTAM system?
The Notices to Airmen (NOTAM) system is a critical aviation alert network that communicates temporary changes, such as runway closures, airspace restrictions, and obstructions, to pilots and flight planners. Over 4 million NOTAMs are issued every year.
Why was the NOTAM system overhauled?
The legacy system was decades old and prone to technical failures. In January 2023, a complete shutdown of the NOTAM system led to a nationwide grounding of flights. The overhaul aims to move the infrastructure to the cloud to improve reliability and prevent future outages.
Who developed the new NOTAM system?
The Federal Aviation Administration (FAA) collaborated with CGI Federal to develop the modernized cloud-based service, utilizing a streamlined vendor challenge to accelerate the project.
Sources
Photo Credit: FAA
Regulations & Safety
Delta and Cirrus Planes Nearly Collide Near JFK Airport
A Delta Air Lines flight and a Cirrus plane came within 475-500 feet near JFK, raising concerns about air traffic safety at one of the busiest US airports.
This article summarizes reporting by New York Post and Daniel Cody.
Another Close Call in New York Skies
A commercial aircraft and a small propeller aircraft experienced a near-miss near John F. Kennedy International Airport (JFK) on Monday, marking the latest in a troubling series of aviation incidents in the New York area. The two planes came within approximately 500 feet of each other vertically, prompting immediate alerts from air traffic control.
According to reporting by the New York Post, the close call involved a Delta Air Lines flight and a smaller aircraft. This event adds to growing scrutiny over airspace safety and air traffic controller workloads at major United States hubs.
We continue to monitor these developments as federal regulators investigate the frequency of such airspace conflicts in one of the nation’s busiest flight corridors.
Flight Path Deviations and Air Traffic Control Response
The Incident Details
The incident occurred on Monday afternoon as a Delta flight, operated by regional subsidiary Endeavor Air, was on its approach to the Queens travel hub. Industry estimates from flight-tracking platforms indicate that the commercial jet was flying at an altitude of roughly 2,100 feet when its path crossed with a Cirrus propeller plane operating at approximately 2,575 feet.
Air traffic control audio revealed that a JFK controller quickly alerted the Endeavor Air pilot to the presence of the smaller aircraft flying less than 500 feet above them.
“An airliner approaching John F. Kennedy Airport and a small propellor plane came within 500 feet of each other on Monday.”
, Daniel Cody, New York Post
Data cited by secondary reporting suggests the vertical separation narrowed to just 475 feet at its closest point. Both aircraft managed to continue their respective flights without further conflict, and no injuries were reported.
A String of Aviation Incidents
Recent Near-Misses at JFK
This event is at least the second close call near JFK in recent weeks. On April 20, 2026, an American Airlines regional jet and an Air Canada Express flight came within 350 feet vertically of each other after a flight path deviation, triggering onboard collision-avoidance alarms and forcing both crews to execute go-around maneuvers.
Furthermore, the New York airspace has seen other unusual events in recent days. Just one day prior to the JFK near-miss, a United Airlines flight arriving from Venice, Italy, struck a light pole and damaged a bakery truck while descending into Newark Liberty International Airport.
AirPro News analysis
The frequency of these near-misses in the New York metropolitan area highlights the immense pressure on the region’s air traffic control infrastructure. JFK handled over 62 million passengers in 2025, making it one of the busiest international gateways in the country. When vertical separation drops below the Federal Aviation Administration’s standard minimums, it often triggers mandatory reviews and operational audits. If this pattern of runway incursions and mid-air close calls continues, federal regulators may be forced to implement temporary spacing restrictions, which could lead to increased arrival delays during the upcoming summer peak season.
Frequently Asked Questions (FAQ)
What planes were involved in the latest JFK close call?
The incident involved a Delta Air Lines flight, operated by its subsidiary Endeavor Air, and a small Cirrus propeller plane.
How close did the aircraft get?
Flight-tracking data indicates the two planes came within approximately 475 to 500 feet of each other vertically.
Are near-misses common at JFK?
While aviation remains highly safe, the New York area has experienced a string of close calls recently, including a notable incident in April 2026 where two commercial jets came within 350 feet of each other.
Sources
Photo Credit: FlightRadar24
Regulations & Safety
United Airlines Passenger Assaults Crew and Attempts Cockpit Breach
A United Airlines passenger assaulted a flight attendant and tried to breach the cockpit, leading to detention and psychiatric evaluation at Newark Airport.
This article summarizes reporting by NBC News and Doha Madani.
On May 2nd, a United Airlines flight experienced a severe security disruption when a passenger allegedly assaulted a crew member and attempted to breach the flight deck. The incident highlights ongoing concerns regarding in-flight safety and passenger behavior.
According to reporting by NBC News, the situation unfolded before the aircraft landed at its destination in New Jersey. Authorities quickly intervened once the plane was safely on the ground, securing the individual involved.
In-flight Altercation and Cockpit Breach Attempt
During the flight, a 48-year-old male passenger reportedly became unruly. Based on the NBC News report, the man allegedly assaulted a United Airlines flight attendant while the aircraft was airborne.
Following the alleged assault, the passenger then attempted to gain access to the aircraft’s cockpit. Flight deck security remains a top priority for airlines, and any attempt to breach the cockpit is treated as a critical security threat. The flight crew managed the situation until the aircraft could land safely.
Detention at Newark Airport
The flight arrived at Newark Liberty International Airport on Saturday evening. Upon arrival, law enforcement and medical personnel were prepared to respond to the in-flight disturbance.
NBC News reports that the 48-year-old man was immediately secured by authorities. Regarding the aftermath of the incident, the report notes that the passenger was:
“detained and taken to a hospital for psychiatric evaluation”
This evaluation took place shortly after the aircraft arrived at the Newark airport terminal.
AirPro News analysis
We note that incidents involving unruly passengers and attempted cockpit breaches represent significant safety risks for the commercial aviation industry. While reinforced flight deck doors, mandated across commercial aviation, effectively prevent unauthorized access, the physical assault of cabin crew members remains a persistent operational challenge. Airlines and federal authorities continue to enforce strict protocols to deter such dangerous behavior and protect the safety of both passengers and crew.
Frequently Asked Questions
What happened on the United Airlines flight?
According to reports, a 48-year-old male passenger allegedly assaulted a flight attendant and attempted to enter the cockpit during the flight.
Where was the passenger detained?
The individual was detained by authorities upon the flight’s arrival at Newark airport on Saturday evening and was subsequently taken to a hospital for a psychiatric evaluation.
Sources
Photo Credit: United Airlines
-
Regulations & Safety4 days agoFrontier Flight Hits Pedestrian on Denver Runway Causing Emergency Evacuation
-
MRO & Manufacturing4 days agoBoeing Proposes Fix for Grounded MD-11 Fleet with FedEx Return Plan
-
Regulations & Safety4 days agoDelta Worker Dies in Aircraft Tug Accident at Orlando Airport
-
MRO & Manufacturing4 days agoIAI Advances Airbus A330-300 Passenger-to-Freighter Conversion
-
Route Development6 days agoAustin-Bergstrom Airport Secures $1.18B Bond for Expansion