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.
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.
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
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:
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.
Authorities and the NTSB have confirmed the identities of the seven individuals lost in the Accident:
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.
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
NTSB Releases Preliminary Report on Statesville Cessna Citation Crash
Flight Sequence and “Rough Engine” Report
Crash Circumstances and Weather Conditions
Crew Certification and Single-Pilot Investigation
Victim Identification
AirPro News Analysis
Next Steps
Photo Credit: NTSB
Regulations & Safety
Air India Grounds Boeing 787 Dreamliner Over Fuel Control Switch Defect
Air India grounds Boeing 787-8 after pilot reports fuel control switch issue on flight from London to Bengaluru, prompting investigation by DGCA and Boeing.
This article summarizes reporting by The Times of India and Saurabh Sinha.
Air India has grounded one of its Boeing 787-8 Dreamliners after a pilot reported a potential mechanical defect involving the aircraft’s fuel control switch. The incident occurred on Monday, February 2, 2026, following the arrival of flight AI132 in Bengaluru from London Heathrow.
According to reporting by The Times of India, the aircraft, registered as VT-ANX, was withdrawn from service immediately upon landing. The crew identified an issue where the fuel control switch for the left engine reportedly failed to remain locked in the “RUN” position, slipping instead toward “CUTOFF.” This specific mechanism is critical for maintaining fuel flow to the engines during operation.
Flight AI132, carrying over 250 passengers, landed safely at Kempegowda International Airport (BLR) at approximately 11:54 AM IST. The Times of India reports that the defect was noted by the crew either during post-flight procedures or while preparing the jet for its subsequent leg. Consequently, the airline has notified the Directorate General of Civil Aviation (DGCA) and engaged Boeing to assist with a priority investigation.
In a statement regarding the incident, an Air India spokesperson confirmed the grounding:
“We are aware that one of our pilots has reported a possible defect on the fuel control switch of a Boeing 787-8 aircraft. After receiving this initial information, we have grounded the said aircraft and are involving the OEM [Boeing] to get the pilot’s concerns checked on a priority basis.”
Boeing has also acknowledged the situation, stating they are in contact with the airline to support the review process.
This mechanical report has drawn significant industry attention due to its similarity to a fatal accident involving the same airline and aircraft type less than a year ago. As detailed in safety reports surrounding the June 12, 2025 crash of Air India Flight AI171 (VT-ANB) in Ahmedabad, preliminary investigations implicated the fuel control switches in that disaster.
In the 2025 incident, investigators found that the switches for both engines moved from “RUN” to “CUTOFF” shortly after takeoff, leading to a total loss of thrust. The recurrence of a similar “RUN to CUTOFF” slip on VT-ANX, an aircraft delivered to Air India in January 2014, raises questions regarding the locking mechanisms on the 787 fleet’s throttle quadrant. The grounding of VT-ANX represents a critical moment for Air India and Boeing. While the safe conclusion of flight AI132 is a relief, the reported failure mode mimics the exact technical flaw suspected in the tragic loss of AI171. We anticipate that regulators will face immense pressure to determine if this is a systemic wear-and-tear issue affecting aging Dreamliners or a fundamental design vulnerability in the switch’s detent mechanism.
Until the DGCA and Boeing release their findings on VT-ANX, scrutiny on the maintenance protocols for these switches will likely intensify across operators of the 787-8 variant.
Sources: The Times of India
Air India Grounds Dreamliner Following Fuel Control Switch Defect
Incident Details and Immediate Grounding
Context: Parallels to Previous Safety Events
AirPro News Analysis
Photo Credit: Anna Zvereva
Regulations & Safety
FAA Admits Systemic Failures Led to Deadly 2025 DCA Collision
FAA Administrator Bryan Bedford accepts NTSB findings on systemic failures causing the 2025 DCA mid-air collision that killed 67, prompting FAA reforms.
In a significant admission of agency culpability, Federal Aviation Administration (FAA) Administrator Bryan Bedford has publicly accepted the findings of the National Transportation Safety Board (NTSB) regarding the catastrophic mid-air collision near Washington, D.C., last year. Speaking at an aviation conference in Singapore on February 2, 2026, Bedford acknowledged that internal failures within the FAA contributed to the accident that claimed 67 lives.
The collision, which occurred on January 29, 2025, involved an American Airlines regional jet and a U.S. Army Black Hawk helicopter. It stands as the deadliest commercial aviation disaster in the United States since 2009. According to reporting by Reuters, Bedford stated that the agency accepts the NTSB’s conclusion that “systemic failures” rather than isolated pilot error were the primary drivers of the tragedy.
This statement marks a pivotal moment for the agency as it attempts to rebuild public trust following a year of intense scrutiny. The FAA has subsequently announced a series of sweeping reforms, including a reduction in flight volume at Ronald Reagan Washington National Airport (DCA) and a massive internal reorganization.
The NTSB’s final report, released just days prior to Bedford’s comments, painted a damning picture of the safety culture surrounding the capital’s airspace. The investigation concluded that the FAA permitted helicopters to operate in dangerous proximity to commercial fixed-wing traffic without adequate separation protocols.
Addressing reporters in Singapore, Administrator Bedford did not attempt to deflect the blame assigned to his agency. Instead, he signaled a readiness to overhaul the FAA’s approach to airspace management.
“We don’t disagree with anything that the NTSB has concluded from their investigations. Many of the recommendations have already been put into action.”
, Bryan Bedford, FAA Administrator (via Reuters)
Bedford, who was confirmed in 2025, noted that the agency’s systems ultimately “failed to protect” the victims. This aligns with the NTSB’s assessment that the crash was “100% preventable.”
One of the most troubling aspects of the investigation was the revelation that air traffic controllers had previously raised red flags about helicopter traffic near DCA. According to the NTSB, these concerns were effectively ignored by leadership. NTSB Chair Jennifer Homendy stated that safety concerns raised by frontline controllers were “squashed by management,” preventing necessary changes that could have averted the disaster. The accident on January 29, 2025, ended a remarkable era of safety in U.S. commercial aviation. The collision occurred at an altitude of approximately 300 feet as the American Eagle regional jet was on approach to DCA. It collided with a U.S. Army Black Hawk that had deviated from its route.
The crash resulted in 67 fatalities, comprising all passengers and crew on both aircraft. The investigation highlighted that the helicopter was operating on a route with a maximum altitude of 200 feet but had risen into the path of the descending jet. While the Army unit involved was cited for a poor safety culture and the pilot’s failure to “see and avoid,” the NTSB emphasized that the FAA failed to act on prior recommendations to reroute such traffic away from commercial flight paths.
In response to the tragedy and the subsequent investigation, the FAA has initiated what officials describe as the largest reorganization in the agency’s history. These changes aim to break down data silos and prioritize safety over capacity.
To immediately mitigate risk in the congested airspace around Washington, D.C., the FAA has reduced the hourly arrival rate at DCA. The rate has been cut from 36 to 26 arrivals per hour. This reduction is intended to give controllers more margin for error and reduce the complexity of managing mixed civilian and military traffic.
Administrator Bedford and Transportation Secretary Sean Duffy have announced the creation of a new “Airspace Modernization Office.” Additionally, the agency is implementing a single Safety Management System (SMS) across all divisions to ensure that safety data is shared effectively and that warnings from frontline employees are not lost in bureaucracy.
The End of the “Perfect” Era
The admission by Administrator Bedford is politically and operationally significant. For over a decade, the U.S. aviation system was the gold standard, with zero fatal commercial crashes. This accident has shattered that perception, forcing a reckoning between capacity and safety.
Bedford’s willingness to accept “systemic failure” suggests a departure from the defensive posture often seen in government agencies. By validating the NTSB’s harsh critique, the FAA leadership appears to be leveraging the crisis to push through modernization efforts that might otherwise have faced bureaucratic resistance. However, the reduction of slots at DCA, a highly coveted airport for lawmakers and lobbyists, indicates that the agency is finally prioritizing operational margins over political convenience. What caused the collision near DCA? How many people died in the accident? What is the FAA doing to prevent this from happening again? Who is Bryan Bedford?
FAA Administrator Accepts “Systemic Failures” Led to Deadly DCA Collision
NTSB Findings and FAA Admission
“We Don’t Disagree”
Ignored Warnings
The Crash: A Shattered Safety Record
Operational Overhaul and Reforms
Immediate Traffic Reductions
Structural Changes
AirPro News Analysis
Frequently Asked Questions
The NTSB determined the cause was a combination of systemic failures by the FAA, including poor airspace design and ignored warnings from controllers, alongside pilot error and a poor safety culture within the U.S. Army unit involved.
The crash resulted in 67 fatalities, killing everyone on board both the American Eagle jet and the Black Hawk helicopter.
The FAA has reduced the arrival rate at DCA from 36 to 26 flights per hour, established a new Airspace Modernization Office, and is implementing a unified Safety Management System to better track and act on risks.
Bryan Bedford is the current FAA Administrator, confirmed in 2025. He is the former CEO of Republic Airways and was nominated by President Trump to modernize the agency.
Sources
Photo Credit: Taylor Bacon – US Coast Guard – Reuters
Regulations & Safety
FAA Funding Lapse Amid Government Shutdown in Early 2026
The FAA faces a funding lapse starting January 31, 2026, due to a government shutdown from a House-Senate scheduling gap, impacting aviation operations.
This article summarizes reporting by Politico and Sam Ogozalek.
A partial government shutdown officially began at midnight on Saturday, January 31, 2026, triggering a funding lapse for the Federal Aviation Administration (FAA) and other key agencies. As reported by Politico, this latest disruption follows a chaotic period for the U.S. aviation sector, which is still recovering from widespread operational failures experienced late last year.
The lapse is technically the result of a scheduling disconnect between the two chambers of Congress. While the Senate successfully passed a “minibus” spending package (H.R. 7148) on Friday night by a vote of 71-29, the House of Representatives had already adjourned for the weekend. Consequently, the FAA lacks appropriated funds until the House returns to vote on the measure, which is currently scheduled for Monday, February 3.
While immediate travel disruptions are expected to be minimal over the weekend, the aviation industry remains on high alert. This anxiety stems from the lingering trauma of the record-breaking 43-day shutdown in the fall of 2025, which caused billions in losses and thousands of flight cancellations.
According to legislative reports, the current funding battle is not centered on aviation policy but rather on the Department of Homeland Security (DHS). Negotiations reportedly collapsed following a controversial incident in Minneapolis on January 24 involving Immigration and Customs Enforcement (ICE) agents.
In response to the deadlock, the Senate passed a compromise bill that fully funds the Department of Transportation and the FAA for the fiscal year but restricts DHS to a two-week stopgap extension. This maneuver is intended to allow a “cooling off” period for immigration policy disputes while keeping the rest of the government running. However, because the House did not remain in session to ratify this amendment, the funding gap occurred automatically at midnight.
The Office of Management and Budget (OMB) has directed federal employees to prepare for shutdown procedures, though officials remain optimistic about a quick resolution. In a statement regarding the lapse, OMB Director Russell Vought emphasized the administration’s intent to resolve the issue quickly.
“The Administration will continue working with Congress to address recently raised concerns… it is our hope that this lapse will be short.”
, Russell Vought, OMB Director
Despite the funding lapse, the immediate impact on passengers this weekend is expected to be limited. Under federal law, air traffic controllers and Transportation Security Administration (TSA) agents are classified as “essential” workers. They are required to report for duty even when their agencies are technically unfunded.
According to industry analysis, the following operations remain active:
However, non-essential activities, such as pilot and controller training programs and non-critical aviation research, have been suspended. The National Air Traffic Controllers Association (NATCA) expressed frustration at the recurring uncertainty facing its members.
“It would be incredibly unfair to the hardworking, patriotic American air traffic controllers… to face another pay disruption just three months after the last one.”
, National Air Traffic Controllers Association (NATCA)
FAA employees are still scheduled to receive their full paychecks on Tuesday, February 3, as that pay period concluded prior to the lapse. However, if the shutdown extends beyond the immediate weekend, future pay cycles would be jeopardized.
The aviation sector’s heightened sensitivity to this shutdown is directly linked to the events of late 2025. As noted in the Politico report, the industry is still reeling from “widespread airport disruption last fall.”
Data from that 43-day shutdown, the longest in U.S. history, illustrates the potential risks if the current lapse is not resolved quickly:
Airlines for America, the trade group representing major U.S. carriers, issued a statement urging Congress to avoid repeating history.
“We implore Congress to protect the FAA… Their jobs are too important to the safety and modernization of our National Aviation System to be used as political leverage.”
, Airlines for America
While the current lapse appears to be a procedural hiccup rather than a deeply entrenched standoff regarding the FAA itself, the frequency of these funding gaps poses a long-term threat to the U.S. aviation system. The “essential” designation for controllers and TSA agents relies on the workforce’s willingness to work without immediate pay. The Fall 2025 shutdown demonstrated that this willingness has a breaking point. Furthermore, even if the House passes the Senate package on Monday, the underlying dispute regarding DHS remains unresolved. With only a two-week extension for Homeland Security on the table, the aviation industry, specifically the TSA, could face another shutdown threat in mid-February. The separation of FAA funding from DHS funding in the Senate bill offers some protection for air traffic control, but security screening operations remain tethered to the volatile immigration debate.
Will my flight be canceled this weekend? Are air traffic controllers getting paid? When will the shutdown end?
FAA Funding Lapses as House Adjourns; Aviation Industry Braces for Uncertainty
The Legislative Impasse: DHS at the Center
White House Response
Operational Impact on Air Travel
Context: The Shadow of Fall 2025
AirPro News Analysis
Frequently Asked Questions
It is unlikely. Air traffic controllers and TSA agents are working. Unless the shutdown drags on for weeks, causing absenteeism to spike, schedules should remain normal.
They will receive their paycheck on Tuesday, February 3, for work completed before the shutdown. Pay for work performed this weekend is delayed until funding is restored.
The House is expected to vote on the Senate-passed funding package on Monday, February 3. If passed, normal operations would resume by Tuesday.
Sources
Photo Credit: National Affairs
-
Business Aviation4 days agoBombardier Responds to U.S. Tariff and Certification Threats
-
Business Aviation5 days agoUS Threatens to Decertify Bombardier Jets in Canada Trade Dispute
-
Regulations & Safety7 days agoNTSB Attributes Fatal 2025 DCA Mid-Air Collision to Systemic Failures
-
Aircraft Orders & Deliveries7 days agoDelta Air Lines Orders 31 Airbus Widebody Aircraft for Fleet Expansion
-
Regulations & Safety6 days agoChallenger 650 Crash in Maine Linked to De-Icing Limits and Wing Sensitivity
