Delta, United & JetBlue Face Federal Probe Over Using Passenger Data To Personalize Fares

Delta Air Lines, United Airlines and JetBlue are at the center of a federal inquiry in which the Federal Trade Commission has asked each carrier to explain how ticket prices are determined and whether personal data influence fare levels. The reporting indicates the FTC is examining whether personalized pricing practices are applied to airfares, with the commission seeking details on the pricing processes used by the three airlines. No findings, outcomes, or potential consequences have been disclosed in the available material, but the action signals formal scrutiny of how pricing decisions are made by these carriers. This summary draws on Simple Flying’s briefing, which outlines the scope of the FTC request and its focus on whether customers’ personal information may be used in setting fares.

In a separate development bundle, Westside Today reports a near-miss incident near Los Angeles International Airport involving two passenger jets, with authorities labeling the event as a near-miss. The FAA is conducting the investigation, and the near-miss is described as two aircraft coming within 400 vertical feet of each other near LAX. Westside Today notes that regulators are reviewing the incident but does not provide details such as aircraft types, exact timing, or subsequent operational actions. The broader Weather Channel commentary within the same coverage mentions wind-related stresses around the period and at Calgary, but does not append further specifics tied to the LAX near-miss.

The Weather Channel’s SmartMarty Sky segment adds context by pointing to a cluster of aviation disruptions around the same period, while clarifying that the Calgary wind conditions impacted landings but did not supply flight numbers or aircraft types for the LAX near-miss. Other outlets in the coverage bundle, including ClickOnDetroit (WDIV Local 4), WDSU, KRDO, Hoodline, and Quantisnow, similarly summarize aviation events without providing additional verifiable detail on the LAX near-miss beyond the general assertion that it occurred near Los Angeles International Airport. Hoodline and CBS News, in separate Ontario International Airport coverage, describe a parallel Frontier Airlines security incident in Southern California—an evacuation and security sweep in Terminal 2 after a language cue about bombs was overheard on FaceTime—though this is treated as a separate incident and not directly tied to the LAX near-miss in the supplied material.

Another strand of reporting in the coverage bundle centers on connectivity strategy in aviation. BigGo Finance relays United Airlines Chief Executive Scott Kirby’s praise for SpaceX’s Starlink as a major competitive advantage, with roughly 600 United aircraft outfitted and a plan to complete fleet-wide installations by the end of 2027. The rollout began with commercial Starlink flights in May 2025, marking a shift toward enhanced passenger connectivity as a differentiator for United in domestic and international markets. In contrast, Delta has chosen Amazon’s Leo as its connectivity platform and plans to begin installations in 2028, a strategic divergence that underscores an ongoing industry debate over the best satellite-enabled connectivity solution.

Within the same discourse, BigGo Finance references a broader industry backdrop from the Bureau of Transportation Statistics, noting that August 2026 U.S. airline traffic declined about 3.7 percent year over year, providing context for United’s Starlink investment amid softer demand. AeroXplorer contributes macro-level interpretation, tying the traffic dip to longer-run patterns in U.S. and global air travel, including manufacturing backlogs and capacity constraints that can influence schedule reliability. This framing helps readers understand the environment in which United’s Starlink rollout is proceeding, even as individual reported incidents circulate alongside connectivity discussions.

A separate thread in the material concerns a United Airlines flight that allegedly triggered a hijack alert, with the flight directed to divert and land safely after a passenger claimed to have a bomb. Simple Flying’s aggregation of coverage from the New York Post describes the Newark Liberty International Airport origin for the flight, with the aircraft reportedly landing safely at Louis Armstrong New Orleans International Airport (MSY). The reporting notes that ACARS messaging was used to alert other United departures, and that there were no reported injuries or detailed actions beyond the safe landing and the lack of disclosed information about the passenger or the exact nature of the threat. WDSU’s and WWLTV’s coverage reiterate the hijack-alert sequence and safe landing at MSY, while indicating that other related security incidents from Ontario (the Frontier Airlines case) are not tied to the United incident in their materials.

Newspaper and broadcast summaries from New York Post, WDSU, WWLTV, and related outlets highlight the core sequence: an in-flight hijack alert after a bomb-claim, followed by a secure landing at the destination, with no injuries reported in connection to the United incident based on the cited material. The coverage notes that while Ontario’s security episode is described by some outlets, the material does not establish a direct connection between the Ontario incident and the United MSY flight. The aggregation emphasizes that, as described, no injuries or terminal evacuations are reported in connection with the United hijack-alert event.

Taken together, the material presents two main threads: a federal probe into whether major U.S. airlines use personal data to personalize fares and a separate aviation incident cluster around LAX and related security and connectivity discussions. The FTC inquiry is described as a formal request for details on pricing processes and data usage, while the LAX near-miss is being investigated by the FAA with limited specifics available in the provided material. A hijack-alert incident involving a United flight from Newark to New Orleans is documented with a safe landing in MSY and no injuries reported, as reported by multiple outlets in the coverage bundle.