Regulations & Safety
Air India Express 737 MAX Hard Landing at Phuket Causes Runway Closure
Air India Express flight IX938 suffered a hard landing at Phuket Airport, collapsing nose gear after recent maintenance. All 140 evacuated safely.
On March 11, 2026, Air India Express flight IX938, operated by a Boeing 737 MAX 8, suffered a severe hard landing at Phuket International Airport (HKT). The incident resulted in the collapse of the nose landing gear and the detachment of both nose wheels, according to initial reporting from x.com and subsequent aviation research data.
Despite the structural failure and the aircraft sliding down the runway on its nose strut, all 140 individuals on board were safely evacuated without injury. The event prompted an immediate closure of Phuket’s single runway, causing significant regional flight disruptions for several hours.
Crucially, statements from India’s Directorate General of Civil Aviation (DGCA) indicate that the aircraft had undergone routine maintenance involving the replacement of its nose wheels just three days prior to the accident. This detail is expected to be a primary focal point in the upcoming investigation led by Thai authorities.
Flight IX938 was completing its scheduled route from Rajiv Gandhi International Airport in Hyderabad, India, to Phuket, Thailand. At approximately 11:24 AM local time, the six-year-old Boeing 737 MAX 8 (registration VT-BWQ) touched down on Runway 09.
According to aggregated research reports, the aircraft experienced a firm touchdown, bounced, and struck the tarmac a second time with excessive vertical force. This hard landing caused the nose gear strut to break, completely separating both nose wheels from the aircraft. The plane subsequently slid along the runway surface on its broken strut before coming to a complete stop, rendering it unable to taxi.
Initial reports from x.com cited 133 passengers and crew, but official flight tracking data later confirmed a total of 140 souls on board. This included 131 passengers, two infants, and seven crew members. Airport authorities and the airline confirmed that all occupants were safely evacuated to the terminal with no reported injuries.
Weather conditions at the time of the incident were highly favorable and are not currently suspected as a contributing factor. Meteorological Aerodrome Reports (METAR) indicated clear skies, visibility exceeding 10 kilometers, a temperature of 31°C, and a standard 10-knot headwind straight down the runway.
Because Phuket International Airport relies on a single runway (09/27), the immobilized Boeing 737 MAX 8 forced a complete halt to all flight operations. Airport authorities issued a Notice to Airmen (NOTAM) to close the runway for several hours. Emergency teams required this time to safely evacuate the passengers, inspect the runway surface for debris and damage, and tow the disabled aircraft to a hangar. The closure resulted in multiple diversions for inbound international flights, affecting carriers such as Emirates, AirAsia, Air Astana, and Bangkok Airways, which were rerouted to alternative airports like Krabi and Bangkok. Operations resumed after approximately six hours, as noted in the initial x.com report.
Following the incident, Air India Express issued a public statement acknowledging the event and praising the swift cooperation of Phuket airport authorities.
The airline confirmed an “issue with the nose wheel” upon landing, emphasizing that the flight crew followed all standard emergency protocols to ensure passenger safety.
A senior official from India’s Directorate General of Civil Aviation (DGCA) also confirmed the hard landing and the detachment of the wheels. Most notably, the DGCA official disclosed that maintenance crews had replaced both nose wheels on the aircraft (VT-BWQ) on March 8, 2026, a mere 72 hours before the accident.
In accordance with International Civil Aviation Organization (ICAO) Annex 13 protocols, the investigation will be led by the country where the incident occurred. Thailand’s Aircraft Accident Investigation Committee (AAIC) will spearhead the inquiry, working in close consultation with India’s DGCA.
Investigators are expected to analyze flight data recorders, pilot reports, and runway conditions. A primary focus will be scrutinizing the maintenance logs related to the recent nose wheel replacement to determine if the failure stemmed from a mechanical defect, a maintenance error, or strictly the operational force of the hard landing itself.
While any incident involving the Boeing 737 MAX family draws immediate public scrutiny due to the aircraft’s complex history and recent quality control controversies, current evidence points toward operational or maintenance factors rather than a manufacturing defect.
The revelation that the nose wheels were replaced just three days prior to the hard landing introduces a critical variable. Aviation investigations are meticulous, and authorities will need to determine whether the hard landing caused a properly installed wheel assembly to fail, or if an underlying maintenance error compromised the gear’s structural integrity prior to the excessive impact force. We will continue to monitor the AAIC’s findings as they become publicly available.
No. All 140 passengers and crew members were safely evacuated without injury, as confirmed by both the airline and airport authorities. The aircraft experienced a severe hard landing, bouncing before striking the runway with excessive force. Investigators are currently examining whether the impact force alone caused the structural failure or if recent routine maintenance on the nose wheels played a contributing role.
The airport’s single runway was closed for approximately six hours to facilitate passenger evacuation, aircraft recovery, and safety inspections of the tarmac.
Sources: X
Details of the Hard Landing and Evacuation
Flight IX938’s Approach and Impact
Passenger Safety and Weather Conditions
Operational Disruptions and Official Responses
Runway Closure at Phuket International
Statements from Air India Express and Regulators
Investigation and Next Steps
International Collaboration
AirPro News analysis
Frequently Asked Questions
Were there any injuries on Air India Express flight IX938?
What caused the nose gear to collapse?
How long was Phuket International Airport closed?
Photo Credit: X
Regulations & Safety
DHS Restarts Global Entry After 17-Day Suspension in 2026
The Department of Homeland Security resumed the Global Entry program on March 11, ending a 17-day suspension caused by a partial government shutdown.
The Department of Homeland Security (DHS) has officially reinstated the Global Entry program following a disruptive 17-day suspension tied to the ongoing partial government shutdown. According to reporting by the Associated Press, the service resumed early Wednesday morning, bringing much-needed relief to millions of international travelers who had been forced into standard customs queues.
The suspension, which began in late February 2026, caused significant bottlenecks at major U.S. Airports. Global Entry traditionally allows pre-approved, low-risk travelers to bypass standard passport control lines by using expedited automated kiosks. Without access to these kiosks, frequent flyers and business travelers faced severe delays, with industry research indicating wait times stretched up to three hours at key international hubs.
While the reactivation of Global Entry restores a critical expedited channel for arriving passengers, the broader impacts of the federal funding lapse continue to strain aviation infrastructure. As the busy spring travel season approaches, the travel industry remains on high alert regarding the stability of airport security and customs operations.
The disruption to airport security and customs services is rooted in a partial federal government shutdown that began on February 14, 2026. According to comprehensive industry research, the political impasse centers on disagreements between lawmakers and the White House over immigration enforcement operations and deportation policies. The shutdown has affected approximately 13 percent of the federal civilian workforce, requiring personnel within the Transportation Security Administration (TSA) and U.S. Customs and Border Protection (CBP) to work without pay.
On February 22, 2026, DHS Secretary Kristi Noem announced the nationwide suspension of both TSA PreCheck and Global Entry. The department cited the need to prioritize the general traveling public and conserve limited resources during the funding lapse. However, following immediate backlash from lawmakers and the travel industry, the DHS reversed its decision regarding TSA PreCheck the very next day, keeping the domestic expedited screening lanes operational. The suspension of Global Entry remained in effect, and CBP officers normally assigned to monitor the kiosks were reassigned to process all arriving international travelers.
According to the Associated Press, the DHS finally restarted the Global Entry program on Wednesday, March 11, 2026, at 5:00 a.m. EDT, a little over two weeks after it was initially halted.
The 17-day outage had a cascading effect on international arrivals. Industry data shows that the suspension forced the program’s estimated 12 to 13 million members into standard customs lines. Crowdsourced wait-time data indicated that bottlenecks at peak hubs, such as Miami International Airport and New York’s John F. Kennedy International Airport, ranged from 60 to 180 minutes. Furthermore, while TSA PreCheck remained open, the requirement for TSA officers to work without pay led to a spike in unscheduled absences. This staffing shortage resulted in domestic security wait times hitting three hours or more at airports such as William P. Hobby in Houston and Louis Armstrong New Orleans International, according to travel sector reports.
The travel and aviation sectors were highly vocal in their opposition to the suspension and expressed immense relief upon its restart. Industry leaders argued that halting a program funded largely by user fees compromised both efficiency and security.
Geoff Freeman, President and CEO of the U.S. Travel Association, applauded the program’s return. The association had previously pointed out that suspending Global Entry was illogical, given that the program is largely self-funded by a $120 application fee paid by members every five years.
“Trusted Traveler Programs enhance security while keeping travel moving,”
Freeman stated, according to industry reports.
Airlines for America (A4A) CEO Chris Sununu also strongly criticized the initial suspension, emphasizing the severe economic losses the travel industry faces during federal funding lapses.
Sununu argued that the traveling public was being “used as a political football amid another government shutdown.”
Lawmakers weighed in as well. Representative Bennie G. Thompson, the ranking Democrat on the House Homeland Security Committee, accused the administration of punishing air travelers and increasing the burden on unpaid DHS employees.
During the outage, travel advisors and CBP officials recommended alternative strategies to mitigate the chaos. CBP steered eligible travelers, including U.S. citizens, green-card holders, and Canadians, toward the free Mobile Passport Control (MPC) smartphone app. The app creates an expedited lane at roughly 40 participating airports and served as a crucial pressure valve during the suspension.
Corporate travel managers also advised executives to build in connection buffers of at least two to three hours between their U.S. arrival and onward domestic flights. In some cases, companies routed travelers through pre-clearance gateways, such as Dublin or Vancouver, where U.S. entry formalities are completed prior to departure. At AirPro News, we observe that the 17-day suspension of Global Entry highlights a critical vulnerability in U.S. aviation infrastructure. When essential travel facilitation programs are tethered to volatile federal funding cycles, the entire ecosystem, from airlines to corporate travel management, suffers immediate and measurable financial damage.
Although Global Entry has resumed, the underlying crisis remains unresolved. The ongoing partial shutdown continues to threaten the busy spring travel season. If TSA and CBP personnel are forced to continue working without pay, the resulting financial strain on these workers will likely lead to further unscheduled absences. This threatens to trigger a new wave of delayed flights, missed connections, and compromised airport security operations.
We note that these disruptions have renewed legislative and industry attention on how to insulate airport security from political impasses. Proposed solutions currently circulating in policy discussions include allowing more airports to outsource security screening to private contractors while maintaining federal TSA oversight. Until structural changes are made, the traveling public remains exposed to the collateral damage of Washington’s funding disputes.
When did the Global Entry program restart? Why was Global Entry suspended? Was TSA PreCheck affected by the suspension? What alternatives are available if Global Entry kiosks are offline?
The Shutdown and Global Entry Suspension
Timeline of the Disruption
Impact on Airport Operations
Industry Backlash and Workarounds
Travel Sector Reactions
How Travelers Adapted
Looking Ahead: Spring Break and Policy Shifts
AirPro News analysis
Frequently Asked Questions (FAQ)
The Department of Homeland Security officially restarted the Global Entry program at 5:00 a.m. EDT on Wednesday, March 11, 2026.
The program was halted on February 22, 2026, as a resource-conservation measure during a partial federal government shutdown. CBP officers normally assigned to the kiosks were reassigned to process all arriving international travelers.
TSA PreCheck was briefly suspended on February 22, 2026, but the DHS reversed that decision the following day, keeping the domestic expedited screening lanes operational. However, staffing shortages due to unpaid TSA agents have still caused significant delays at various airports.
Eligible travelers can use the free Mobile Passport Control (MPC) smartphone app, which provides an expedited customs lane at approximately 40 participating airports.
Photo Credit: U.S. Customs and Border Protection
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 & 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
