Connect with us

Regulations & Safety

FAA Proposes $165,000 Fine Against Alaska Airlines for Intoxicated Passengers

FAA proposes a $165,000 fine against Alaska Airlines for allegedly allowing intoxicated passengers on 11 flights between 2024 and 2025.

Published

on

This article is based on an official press release from the Federal Aviation Administration (FAA).

The Federal Aviation Administration (FAA) has announced a proposed civil penalty of $165,000 against Alaska Airlines, citing allegations that the carrier repeatedly allowed passengers who appeared to be intoxicated to board its aircraft.

According to the official press release issued by the FAA on May 26, 2026, the alleged regulatory violations occurred across 11 separate flights over a one-year period, spanning from February 2024 to February 2025.

This enforcement action highlights the agency’s ongoing commitment to strict adherence to federal aviation safety protocols regarding passenger behavior and alcohol consumption, emphasizing the critical role airlines play in screening passengers before they reach the cabin.

Details of the Alleged Violations

The core of the FAA’s allegation centers on the airline’s failure to prevent impaired individuals from accessing the aircraft. Under federal aviation regulations, specifically 14 CFR § 121.575 governing alcoholic beverages, airlines are strictly prohibited from allowing any person to board an aircraft if that individual appears to be intoxicated.

The FAA has historically noted in its safety briefings that impaired passenger behavior introduces unpredictable risks to the flight environment. These risks can range from a passenger being non-responsive during an emergency to becoming physically disruptive, thereby creating unsafe conditions for both the flight crew and fellow travelers.

Regulatory Requirements and Next Steps

Beyond the strict prohibition on boarding, 14 CFR § 121.575 also mandates that airlines report any onboard disturbances caused by an intoxicated-appearing passenger to the FAA within five days of the incident. The agency relies on these reports to track safety trends and enforce compliance across the national airspace system.

Following the issuance of the enforcement letter, Alaska Airlines has a standard 30-day window to formally respond to the agency. During this period, the Seattle-based carrier may choose to pay the $165,000 penalty, dispute the FAA’s findings, or attempt to negotiate a settlement.

Broader Industry Context and Enforcement Trends

The proposed fine against Alaska Airlines is not an isolated incident but rather part of a wider regulatory crackdown by the FAA on alcohol and drug-related compliance across the commercial aviation sector.

In January 2026, the FAA issued an Information for Operators (InFO 26002) bulletin that specifically addressed the safety risks associated with carrying impaired passengers. While initially directed at charter and general aviation operators, the agency used the bulletin to underscore a universal safety principle regarding intoxication.

As noted in the FAA’s January guidance, “past aviation accidents have shown that carrying intoxicated or impaired passengers can be a contributing factor” to unsafe flight conditions.

Recent Actions Against Major Carriers

The agency has recently levied substantial fines against other major U.S. carriers for related infractions, demonstrating a zero-tolerance approach to substance-related regulations. In April 2026, the FAA proposed civil penalties of $304,000 against Southwest Airlines and $255,000 against American Airlines. According to the agency, those fines were related to alleged failures in conducting required follow-up drug and alcohol testing for employees in safety-sensitive roles, including pilots and flight attendants.

AirPro News analysis

At AirPro News, we observe that while a $165,000 fine represents a relatively minor financial penalty for a major corporation like Alaska Air Group, the reputational implications are far more significant. This enforcement action places a direct, public spotlight on the airline’s passenger safety management practices and internal training protocols.

Furthermore, this situation underscores the immense operational pressure placed on frontline aviation workers. Gate agents and flight crews are tasked with the difficult job of assessing a passenger’s level of intoxication during the highly time-sensitive and often chaotic boarding process. They must constantly balance the operational push for on-time departures with strict regulatory compliance. The string of recent FAA actions, from employee testing fines in April to this passenger screening fine in May, sends a clear message to the industry that the FAA expects safety and regulatory adherence to supersede operational speed.

Frequently Asked Questions

What regulation did Alaska Airlines allegedly violate?
The FAA alleges the airline violated 14 CFR § 121.575, which prohibits airlines from allowing any person to board an aircraft if they appear to be intoxicated.

How many flights were involved in the FAA’s allegations?
According to the FAA, the alleged violations occurred on 11 separate flights between February 2024 and February 2025.

What happens next for the airline?
Alaska Airlines has 30 days from the receipt of the FAA’s enforcement letter to respond. The airline can pay the fine, dispute the allegations, or negotiate with the agency.

Sources

Photo Credit: Alaska Airlines

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

FAA Investigates Southwest Airlines Ground Collision at PVD

Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.

The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.

The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.

Details of the ground collision

At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).

Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.

“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”

the airline stated in remarks provided to local media, adding that safety remains its highest priority.

Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.

Regulatory response and recent precedent

The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.

This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.

AirPro News analysis

We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.

Sources: WPRI

Photo Credit: Zachary Reis

Continue Reading

Regulations & Safety

Turkish Airlines 777-300ER Wing Strike at Antalya Airport

A Turkish Airlines Boeing 777-300ER struck a radar antenna pole taxiing at Antalya Airport, prompting evacuation and a formal investigation.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by Hürriyet.

A Turkish Airlines (TK) Boeing 777-300ER sustained damage and prompted a passenger evacuation after its right wing struck a ground radar antenna pole while taxiing at Antalya Airport (AYT) on June 11, 2026.

The incident, which occurred at approximately 20:00 local time following Flight TK2430 from Istanbul, resulted in minor injuries among the passengers. According to official statements reported by Hürriyet, the widebody aircraft was maneuvering toward its parking position on Apron-1 when the collision occurred, leading to an immediate evacuation on the tarmac.

Conflicting passenger and injury reports

Following the evacuation, official sources provided conflicting figures regarding the number of passengers on board and the extent of injuries. In a public statement, Turkish Airlines Senior Vice President of Communications Yahya Üstün confirmed the evacuation, stating that 267 passengers were safely removed from the aircraft. The airline reported that one passenger sustained minor injuries and was in good health.

Conversely, the Turkey Ministry of Transport released a separate statement indicating a higher passenger count. The ministry reported that the aircraft was carrying 284 adult passengers and four infants. Furthermore, the government authority stated that three passengers suffered minor injuries during the event. Both entities confirmed that the aircraft, registered as TC-LKD, was towed to a parking area after the necessary safety checks and passenger removal were completed.

Investigation into the ground collision

A technical investigation into the ground collision has been initiated by the Turkey Ministry of Transport and the General Directorate of State Airports Authority (DHMI). The official cause of the incident remains under investigation.

While the airline noted the aircraft was approaching its parking position, preliminary remarks from the Ministry of Transport suggested the Boeing 777-300ER made contact with the radar pole after entering an incorrect taxiway line. Final determinations regarding the aircraft routing, ground control instructions, and the sequence of events will be established by the investigating authorities.

AirPro News analysis

Ground collisions involving widebody aircraft like the Boeing 777-300ER often highlight the tight tolerances required when maneuvering large airframes around airport infrastructure. While we await the official investigation findings, safety reviews following such events typically examine airport taxiway markings, lighting, and the clarity of ground control communications. The discrepancy in passenger manifests between the operator and the regulator is a notable detail, though initial reporting conflicts frequently occur in the immediate aftermath of an evacuation before final reconciliations are completed.

Sources: X.com

Photo Credit: X

Continue Reading

Regulations & Safety

NTSB Final Report: Southwest Flight 4273 Turbulence Encounter

NTSB cites ATC communication delays and sector overload in Southwest Airlines turbulence event over Gulf of Mexico.

Published

on

This is original reporting and analysis by AirPro News.

The National Transportation Safety Board (NTSB) has released its final report on a severe turbulence encounter involving a Southwest Airlines Boeing 737-700, detailing how rapidly developing convective weather and air traffic control communication delays factored into an event that seriously injured two people.

The April 3, 2024, incident aboard Southwest Airlines Flight 4273 over the Gulf of Mexico highlights the operational risks when severe weather systems intersect with technical limitations at air traffic control facilities. According to the NTSB investigation, the aircraft was navigating complex weather en route from New Orleans to Orlando when the encounter occurred, resulting in serious injuries to one flight attendant and one passenger, alongside minor injuries to a second flight attendant.

Weather conditions and the turbulence encounter

Flight 4273, operated by a Boeing 737-700 (registration N567WN) with 140 passengers and five crew members on board, was traveling from Louis Armstrong New Orleans International Airport (MSY) to Orlando International Airport (MCO).

At 11:55 UTC, a Convective Significant Meteorological Information (SIGMET) advisory was issued for the region, warning of cloud tops exceeding 45,000 feet.

At approximately 08:20 Eastern Daylight Time, the aircraft encountered severe turbulence over the Gulf of Mexico. The NTSB confirmed the aircraft itself sustained no damage during the event and the flight crew was able to continue the flight.

Air traffic control workload and technical limitations

The NTSB report outlines compounding factors at the Jacksonville Air Route Traffic Control Center (JAX ARTCC) that affected the flight routing through the weather system.

During the incident, the specific JAX ARTCC sector was managing a traffic volume that exceeded its target capacity of 20 aircraft.

This high workload was exacerbated by a technical limitation involving the facility communication infrastructure. The primary VHF antenna at JAX ARTCC had been rendered inoperative following a fire in October 2023. As a result, controllers were utilizing a temporary satellite relay connection to communicate with aircraft in the sector.

The NTSB determined this satellite relay introduced a 600-millisecond round-trip transmission delay, complicating timely communication between controllers and flight crews navigating the dynamic weather environment.

AirPro News analysis

We note that the findings in this final report underscore a critical vulnerability in the National Airspace System. When primary communication infrastructure fails, the fallback systems must be robust enough to handle high-stress, time-critical scenarios like severe convective weather deviation. A 600-millisecond delay might seem negligible in routine operations, but in a saturated sector where controllers are issuing rapid heading changes to keep aircraft clear of building storm cells, that latency degrades situational awareness and increases the risk of weather encounters. The NTSB documentation of this technical shortfall will likely prompt further scrutiny of contingency communication systems at major en route centers.

Sources: National Transportation Safety Board (NTSB)

Photo Credit: NTSB

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News