Regulations & Safety
FAA Temporarily Bans General Aviation at 12 US Airports Amid Shutdown
FAA halts general aviation flights at 12 key US airports to manage staffing shortages caused by a prolonged government shutdown and maintain airspace safety.
In a significant move to maintain the integrity of the U.S. airspace, the Federal Aviation Administration (FAA) has implemented a temporary ban on most general and business aviation flights at 12 of the nation’s most congested Airports. This decision, effective November 10, 2025, comes as a direct response to the escalating operational pressures caused by a prolonged government shutdown. The core of the issue lies with significant staffing shortages among air traffic controllers (ATCs), who have been working without pay, leading to a strained National Airspace System (NAS).
The restrictions are not an isolated event but rather the latest in a series of measures designed to ensure Safety above all else. Prior to this targeted ban, the FAA had already mandated a traffic reduction of up to 10% at 40 high-volume airports to alleviate the growing pressure on the system. FAA Administrator Bryan Bedford highlighted that air traffic data revealed a critical level of strain that, if left unaddressed, could compromise aviation safety. This ban, therefore, represents a calculated step to reduce controller workload by targeting non-scheduled flights at critical hubs, ensuring the system can continue to operate safely under duress.
The FAA’s directive was formalized through a series of Notices to Airmen (NOTAMs), which effectively halt most general and business aviation operations at the specified locations. Understanding the scope and specifics of these restrictions is crucial for anyone operating within the national airspace. The measure is designed as a temporary solution to a critical, but hopefully short-term, problem.
The ban officially commenced at 12:00 a.m. EST on Monday, November 10, 2025. While designated as temporary, the NOTAMs are set to expire on December 31, 2025. However, the FAA has been clear that this timeline is fluid; the restrictions could be lifted earlier if the government shutdown ends and staffing levels stabilize, or they could be extended if the operational challenges persist. This uncertainty adds another layer of complexity for flight planning and business operations.
The restrictions are concentrated on airports that are critical nodes in the national and international air travel network. The 12 airports impacted by this ban are:
By focusing on these specific hubs, the FAA aims to achieve the maximum reduction in system-wide strain while impacting the smallest number of airports. These locations handle a significant volume of traffic, and reducing non-scheduled operations provides substantial relief to the controllers managing these complex airspaces.
It is important to note that the ban is not absolute. The FAA has carved out several critical exemptions to ensure that essential services are not disrupted. The restrictions are primarily aimed at transient, non-scheduled flights that add to the complexity of air traffic management without serving an emergency or official function. These exemptions are a key part of balancing safety with public need.
The following operations are permitted to continue at the 12 affected airports: based aircraft (those permanently housed at the airport), emergency and medical flights, law enforcement and firefighting operations, military flights, and any other flights that receive specific authorization from the FAA. This ensures that life-saving medical transport, critical law enforcement missions, and national security operations can proceed without impediment.
These exemptions reflect a pragmatic approach from the FAA. The goal is not to shut down aviation but to manage risk. By allowing based aircraft to continue operating, the agency acknowledges the rights of tenants at these airports. By exempting emergency and official flights, it upholds its duty to support public safety and national interests, even in a time of operational crisis. The FAA’s decision, while rooted in safety, has generated significant concern and pushback from the aviation community, particularly from organizations representing general and business aviation. These groups argue that the ban unfairly singles out their sector, which they see as a vital contributor to the nation’s economy and transportation infrastructure.
The National Business Aviation Association (NBAA) has been at the forefront of the opposition. The organization argues that the ban places a disproportionate burden on general aviation, an industry that supports a vast economic ecosystem. The NBAA and its allies, including the Modern Skies Coalition, are not just challenging the restrictions but are also urging Congress to find a swift resolution to the government shutdown, which they identify as the root cause of the problem.
The economic stakes are high. General aviation is a significant driver of the U.S. economy, and limiting its access to major markets, even temporarily, can have cascading effects. The industry’s role extends beyond corporate travel to include humanitarian missions, cargo transport, and connecting communities that lack robust commercial airline service. The NBAA’s position is that these contributions are being overlooked in the FAA’s current strategy.
“Further restrictions were announced that will effectively prohibit business aviation operations at 12 of those airports, disproportionately impacting general aviation, an industry that creates more than a million jobs, generates $340 billion in economic impact, and supports humanitarian flights every day.” – Ed Bolen, NBAA President and CEO
In response to the operational hurdles, other industry groups like the National Air Transportation Association (NATA) are advising their members to adapt. The guidance is to be proactive in planning, which includes utilizing alternate airports near the restricted hubs and adjusting fuel and crew strategies to accommodate longer journeys or different operational bases. This reflects the industry’s resilience but also underscores the significant logistical and financial costs imposed by the ban.
The FAA’s temporary ban on general aviation at 12 major airports is a stark reminder of how deeply interconnected government functions and national infrastructure are. The measure is a direct, safety-oriented response to a critical shortage of air traffic controllers, a problem stemming directly from a political impasse. While the FAA’s primary mandate is the safety of the skies, its actions have created significant turbulence for the general and business aviation sectors, who feel they are shouldering an unfair share of the burden.
Looking ahead, the path to normalcy is tied directly to Washington. Transportation Secretary Sean Duffy has indicated that the restrictions will remain until data confirms the stability of the NAS. He also warned that if the situation deteriorates, further cuts, potentially as high as a 20% reduction in flights, could be on the table. The ultimate resolution lies not with the FAA, but with policymakers. Until the government shutdown ends and the agency is fully funded, the aviation industry and the flying public will likely continue to navigate a landscape of uncertainty and disruption.
Question: Why did the FAA implement this ban on general aviation flights? Question: Is this a permanent ban? Question: Are all general aviation flights banned at these 12 airports? Sources: Aviation Week
FAA Grounds General Aviation at 12 Key Airports Amid Shutdown
Breaking Down the Restrictions
Scope, Duration, and Affected Hubs
Exemptions and Permitted Operations
Industry Pushback and Future Outlook
A Disproportionate Burden?
Concluding Thoughts: An Uncertain Sky
FAQ
Answer: The ban was implemented to reduce the workload on air traffic controllers (ATCs) who are facing significant staffing shortages due to a prolonged government shutdown. The primary goal is to ensure the safety and integrity of the National Airspace System.
Answer: No, it is a temporary measure. The Notices to Airmen (NOTAMs) are set to expire on December 31, 2025, but they can be canceled or extended depending on the status of the government shutdown and FAA operational needs.
Answer: No, there are several exemptions. The ban does not apply to based aircraft, emergency and medical flights, law enforcement, firefighting, military operations, or flights specifically authorized by the FAA.
Photo Credit: AP
Regulations & Safety
NTSB Releases Preliminary Report on Arizona Helicopter Crash
NTSB reports on the February 4 crash of an Arizona DPS Bell 407 helicopter during an active shooter incident in Flagstaff, resulting in two fatalities.
This article is based on an official press release from the National Transportation Safety Board (NTSB).
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal February 4 crash of an Arizona Department of Public Safety (AZDPS) helicopters in Flagstaff, Arizona. The incident claimed the lives of two crew members who were providing tactical air support during an active shooter situation.
According to the official NTSB release, the ongoing investigation is examining the circumstances that led the Bell 407 helicopter to crash in a residential area. The preliminary findings offer initial data points, though a final determination of the probable cause is not expected for several months.
NTSB issues its preliminary report for the ongoing investigation of the Feb. 4 crash of a Bell 407 helicopter in Flagstaff, Arizona.
On the evening of February 4, 2026, the AZDPS helicopter was dispatched to assist the Flagstaff Police Department with an active shooter incident. The crew consisted of Pilot Robert Bruce Skankey and State Trooper/Paramedic Hunter R. Bennett. Both sustained fatal injuries when the aircraft went down at approximately 10:15 p.m. local time, according to timelines cited by Beaumont Enterprise.
The aircraft was operating in clear weather conditions with light winds. According to reporting by Red Rock News, the helicopter was a 2004 model with tail number N56AZ. The same outlet noted that Automatic Dependent Surveillance–Broadcast (ADS-B) data indicated the aircraft entered a rapid climb late in the flight, with groundspeeds dropping to as low as 4 knots, before entering an out-of-control spin. Witnesses on the ground reported hearing a loud pop prior to the descent.
The NTSB, assisted by the Federal Aviation Administration (FAA), is leading the federal investigation into the crash. Investigators are analyzing the aircraft’s maintenance records, flight data, and environmental factors. Beaumont Enterprise reported that the aircraft crashed approximately 50 feet from a BNSF Railway line, resulting in a post-crash fire.
While the NTSB preliminary report outlines the factual circumstances of the flight, it does not establish a causal chain. The suspect involved in the ground shooting, identified in media reports as Terrell Story, was taken into custody. He has been indicted on multiple charges, including two counts of first-degree felony murder related to the deaths of the flight crew during the commission of a felony.
The deployment of public-safety aviation units in urban environments at night introduces complex mission demands. Tactical air support requires sustained low-altitude maneuvering, frequent radio communications, and heightened situational awareness relative to terrain and obstacles. We anticipate the NTSB’s final report will likely focus heavily on the mechanical integrity of the helicopter’s tail rotor and transmission systems, given witness reports of a pop and video evidence of an out-of-control spin. Additionally, investigators will evaluate whether the ground threat directly impacted the aircraft, though current public releases have not confirmed if the helicopter sustained gunfire.
The aircraft was a Bell 407 helicopter, operated by the Arizona Department of Public Safety (AZDPS) under the call sign “Ranger 56.”
The National Transportation Safety Board (NTSB) is leading the investigation, with assistance from the Federal Aviation Administration (FAA) and local authorities.
No. Both crew members on board, Pilot Robert Bruce Skankey and State Trooper/Paramedic Hunter R. Bennett, were fatally injured in the crash.
Details of the Incident
The Investigation and Aftermath
AirPro News analysis
Frequently Asked Questions
What aircraft was involved in the Flagstaff crash?
Who is investigating the helicopter crash?
Were there any survivors?
Sources
Photo Credit: NTSB
Regulations & Safety
NTSB Finds No Mechanical Failure in Bangor Challenger 600 Crash
NTSB preliminary report on the Bangor Bombardier Challenger 600 crash cites severe winter weather and deicing as key factors, no mechanical faults found.
This article is based on an official preliminary report from the National Transportation Safety Board (NTSB).
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal crash of a Bombardier CL-600-2B16 airplane that occurred on January 25, 2026, at Bangor International Airport (KBGR) in Maine. The accident resulted in the deaths of all six individuals on board, including two crew members and four passengers.
According to the NTSB’s findings, investigators have found no evidence of flight control malfunctions or mechanical failures that would have precluded normal operation. Instead, the investigation is increasingly focusing on environmental factors, specifically the severe winter weather conditions and the deicing procedures conducted minutes before the aircraft attempted to take off.
The aircraft, registered as N10KJ and operated by KTKJ Challenger LLC, was en route to Châlons Vatry Airport in France after a refueling stop in Bangor. The flight originated from William P. Hobby Airport in Houston, Texas.
Data recovered from the Flight Data Recorder (FDR) and Cockpit Voice Recorder (CVR) provides a detailed timeline of the aircraft’s final movements. The NTSB report indicates that the jet arrived at the runway threshold during a severe winter storm characterized by falling snow and freezing temperatures.
The preliminary report states that the aircraft underwent deicing treatment with both Type I and Type IV fluids at approximately 7:20 PM local time. Following the application of the fluid, the plane remained stationary for about five minutes before beginning its taxi to the runway.
Investigators noted that the CVR captured a critical conversation between the flight crew regarding “holdover times.” Holdover time refers to the estimated length of time deicing fluid remains effective in preventing the accumulation of ice or snow on critical aircraft surfaces. This discussion suggests the crew was aware of the deteriorating conditions and the time sensitivity of their departure.
The aircraft reached Runway 33 at 7:40 PM and received clearance for takeoff. According to FDR data, engine power was increased for takeoff at 7:43:57 PM. The aircraft lifted off the runway approximately 30 seconds later. However, the flight was brief. Moments after becoming airborne, the aircraft veered off the right side of the runway. It scraped the ground, flipped over, and came to rest inverted in a grassy safety area. The debris field stretched approximately 1,270 feet long and 150 feet wide, with the wreckage sustaining significant damage from a prolonged post-crash fire.
The NTSB’s on-site examination and data analysis have ruled out several potential causes, narrowing the scope of the ongoing investigation.
A key finding in the preliminary report is the status of the engines. The NTSB states:
Data from the Flight Data Recorder indicates that both engines were producing takeoff power and continued to gain power until the recording stopped.
Furthermore, investigators found no evidence of anomalies with the flight controls prior to the impact. The wings remained attached to the fuselage despite the severity of the crash, and the landing gear was found in the extended position.
At the time of the accident, visibility was reported as approximately three-quarters of a mile due to snow. The presence of freezing precipitation is a critical factor in the investigation, particularly regarding the effectiveness of the deicing fluid used.
While the NTSB report focuses on technical details, local authorities and media have identified the six victims of the tragedy. According to reporting by the Bangor Daily News and other local outlets, the victims include Shawna Collins, Nick Mastrascusa, Tara Arnold, Jacob Hosmer, Shelby Kuyawa, and Jorden Reidel. The aircraft was linked to the Houston-based law firm Arnold & Itkin.
The Bombardier Challenger 600 series has a documented history regarding wing contamination. Aviation safety databases note that this aircraft type has a “hard wing” design that can be sensitive to even small amounts of ice or frost, which can disrupt airflow and lead to a stall during takeoff.
Previous incidents, such as the 2004 crash in Montrose, Colorado, and the 2002 crash in Birmingham, England, involved similar circumstances where wing contamination was cited as a contributing factor. The NTSB’s final report, expected in 12 to 24 months, will likely determine if the severe weather in Bangor exceeded the capabilities of the deicing fluid or if the holdover time was exceeded. The focus on “holdover times” in the cockpit voice recorder transcript is a significant detail. In severe winter operations, the window between deicing and takeoff is often measured in minutes. If the intensity of the snowfall increases, the effective time of the anti-icing fluid decreases rapidly. The fact that the engines were producing power and no mechanical faults were found strongly suggests that aerodynamic performance was compromised, a hallmark of icing accidents. This investigation will likely serve as a critical reminder of the strict limitations of deicing fluids in active precipitation.
Sources: NTSB Preliminary Report, Bangor Daily News, FAA Registry
NTSB Preliminary Report: No Mechanical Failure Found in Bangor Challenger 600 Crash
Sequence of Events
Deicing and Taxi
Takeoff and Impact
Investigation Findings
Engine and Systems Performance
Weather Conditions
Victims and Context
Aircraft History and Icing Sensitivity
AirPro News Analysis
Sources
Photo Credit: NTSB
Regulations & Safety
United Airlines Plane Collides with Deicing Truck at Denver Airport
United Airlines Flight 605 collided with a deicing truck at Denver International Airport amid a snowstorm, injuring the truck driver and delaying flights.
This article summarizes reporting by 9News, Richard Cote, CBS News and social platform X.
A United Airlines aircraft collided with a deicing truck Friday morning at Denver International Airport (DIA), resulting in injuries to the truck’s driver and forcing passengers to deplane on the tarmac. The incident occurred amidst a severe March snowstorm that has disrupted travel across the region.
United Airlines Flight 605, a Boeing 737-800 scheduled to depart for Nashville, struck the vehicle while exiting the deicing pad. According to the Federal Aviation Administration (FAA), the collision took place in a section of the airfield not controlled by air traffic towers.
The Incident occurred at approximately 8:26 a.m. local time as the aircraft was preparing for departure. According to reporting by 9News, the flight had been scheduled to leave Denver at 7:59 a.m. but was delayed due to winter weather conditions. The FAA confirmed that the aircraft was moving out of the deicing area when it struck the truck.
United Airlines confirmed the accident in a statement, noting that the aircraft “made contact with ground equipment” during the operation. Following the collision, the 122 passengers and six crew members on board were evacuated from the aircraft via stairs and transported by bus back to the terminal. No injuries were reported among those on the plane.
While the passengers and crew remained unharmed, the operator of the deicing truck sustained injuries. According to a United Airlines spokesperson cited by the Denver Gazette, the driver, an employee of a contractor used by the airport, was taken to a hospital. The extent of the driver’s injuries has not been publicly disclosed.
The collision occurred during a significant winter storm affecting Colorado’s Front Range. The adverse weather conditions had already severely impacted operations at Denver International Airports before the ground accident took place.
According to flight tracking data, more than 600 flights were delayed and scores were canceled at the airport by Friday morning. United Airlines and Southwest Airlines were among the carriers most heavily affected by the snow and ice. The FAA stated it would investigate the collision, specifically noting that the crash happened in a non-movement area where pilots and ground vehicles are responsible for maintaining visual clearance. United Airlines stated they were working to rebook customers on alternative flights to Nashville. In a statement regarding the safety of the operation, the airline said:
“United flight 605 made contact with the equipment… [We are] cooperating with airport officials and federal investigators.”
Ground collisions in deicing areas are relatively rare but can occur during periods of low visibility and high congestion, such as winter storms. In these “non-movement” areas, air traffic control does not provide separation instructions, placing the burden of safety on pilots and ground vehicle operators. The Investigation will likely focus on communication protocols and visibility factors present during the heavy snowfall.
Was anyone injured in the accident? What caused the collision? What happened to the passengers?
Collision on the Deicing Pad
Driver Hospitalized
Weather Context and Operational Impact
AirPro News Analysis
Frequently Asked Questions
Yes, the driver of the deicing truck was injured and transported to a hospital. No passengers or crew members on the aircraft were hurt.
The specific cause is under investigation by the FAA. The collision occurred while the aircraft was exiting a deicing pad during heavy snow.
Passengers were deplaned using stairs on the tarmac and bused back to the terminal to be rebooked on other flights.
Sources
Photo Credit: CBS News
-
Regulations & Safety6 days agoGreen Taxi Aerospace Gains FAA Approval for Electric Taxi System
-
Regulations & Safety5 days agoUnited Airlines Plane Collides with Deicing Truck at Denver Airport
-
Regulations & Safety5 days agoNTSB Finds No Mechanical Failure in Bangor Challenger 600 Crash
-
Aircraft Orders & Deliveries4 days agoBoeing Nears 500-Jet Order from China Ahead of Trump-Xi Summit
-
Aircraft Orders & Deliveries5 days agoBoeing 777-9 Vibration Testing Advances 2026 Certification Plans