Published on : 19 Jan 2026

United Airlines Airbus A321neo registration N14502 hard landing Orlando International Airport January 18 2026 right nose wheel separated detached 54 mph wind gusts 200 passengers trapped runway 1 hour FAA investigation viral video Chicago flight UA2323

BREAKING: United Airlines Flight UA2323—Airbus A321neo registration N14502, delivered brand-new just 2 years ago in November 2023—suffered CATASTROPHIC nose wheel failure during hard landing at Orlando International Airport (MCO) Sunday January 18, 2026 at 12:35 PM EST after encountering 54 MPH wind gusts on final approach from Chicago O’Hare, causing aircraft to BOUNCE violently upon touchdown as right front nose wheel SEPARATED from landing gear and ROLLED AWAY across runway while 200 passengers + 6 crew remained TRAPPED onboard for 1 HOUR unable to evacuate as disabled aircraft blocked active runway, forcing FAA to issue GROUND STOP that halted ALL arrivals at Florida’s busiest airport during peak holiday weekend, creating CASCADE of flight delays affecting thousands—though ALL 206 souls eventually bussed safely to terminal with ZERO injuries, viral video capturing wheel separation moment reached 2 MILLION+ views sparking urgent questions about why United’s NEWEST widebodies are experiencing disturbing landing gear failures (April 2025 Frontier A321neo suffered identical nose wheel loss in Puerto Rico).

Published: January 19, 2026, 3:00 PM EST
Incident Date/Time: Sunday, January 18, 2026, 12:35 PM EST
Flight: United Airlines UA2323
Route: Chicago O’Hare (ORD) → Orlando International (MCO)
Aircraft: Airbus A321-271NX (A321neo)
Registration: N14502
Aircraft Age: 2.2 years (delivered November 2023)
Souls Onboard: 206 (200 passengers + 6 crew)
Injuries: ZERO
Damage: Right nose wheel separated, possible landing gear structural damage
Weather: 54 MPH wind gusts, cold front passage
Ground Stop: Issued 12:40 PM, lifted 2:15 PM (1 hour 35 minutes)
Passengers Trapped: ~1 hour on runway before bus evacuation
FAA Status: Active investigation
Aircraft Status: Grounded pending maintenance inspection

The Viral Video That Shows Everything

Sunday, January 18, 2026 – 12:35 PM EST:

Planespotter positioned at Orlando International Airport captures United Airlines Flight UA2323 on final approach.

Weather conditions:

Wind: Northwest 15-20 MPH sustained
Gusts: 54 MPH recorded at touchdown
Temperature: 58°F (14°C)
Visibility: 10 miles (excellent)
Ceiling: Scattered clouds at 4,500 feet

The Landing Sequence (Frame-by-Frame):

0:00 – Normal Approach:

Airbus A321neo on glide slope
Landing gear down (3 green)
Flaps extended
Airspeed appropriate (~140 knots)

0:03 – First Touchdown:

LEFT main gear touches runway first
Normal touchdown point (~1,000 feet from threshold)
Aircraft nose still elevated

0:04 – The BOUNCE:

Strong crosswind gust hits aircraft (54 MPH)
Aircraft BOUNCES violently
LEFT main gear LIFTS BACK INTO AIR
Aircraft tilts sharply RIGHT

0:05 – Second Touchdown:

RIGHT main gear slams down HARD
Nose gear descends toward runway
Aircraft still rolling right

0:06 – NOSE WHEEL SEPARATION:

Nose gear contacts runway
RIGHT NOSE WHEEL SEPARATES
Wheel ROLLS AWAY to the right
Left nose wheel remains attached

0:07-0:10 – Disabled Aircraft:

Plane continues rolling on runway
Nose tilts slightly to right (missing wheel)
Sparks visible from metal-on-concrete contact
Aircraft eventually stops on centerline

What Eyewitnesses Saw:

JonNYC (@xJonNYC – Aviation Twitter):

“MCO today, ‘can see what looks like a nose wheel roll off the gear and exit to the right.'”

His video: 2 MILLION+ views in 24 hours.

Turbine Traveller (@Turbinetraveler):

“WATCH: The moment a United A321neo (N14502) operating UA2323 from Chicago O’Hare makes a hard landing at Orlando around 12:30pm ET amid 54 mph gusts. The jet bounced on touchdown before the right nose wheel separated, leaving the aircraft unable to taxi. About 200 passengers and [crew]…”

Video views: 500,000+ in 12 hours.

Ground crew witness (Orlando airport employee, anonymous):

“I was on the ramp when I heard the squeal. Looked up and saw the plane bounce like a basketball. Then I saw something ROLL across the runway—took me a second to realize it was a WHEEL. The plane settled down but you could see it leaning to one side. Emergency vehicles surrounded it within 2 minutes.”

Inside the Cabin: Passenger Accounts

Reddit User Account (r/unitedairlines):

User claims to have been onboard Flight UA2323.

Posted 8 hours after incident:

“Was on this flight. Didn’t seem that rough of a landing all things considered, but we sat on the runway for about an hour while they figured out what to do. Pilot came on and said we had a ‘mechanical issue’ and would need to deplane via bus. Didn’t realize the wheel fell off until I saw the video on Twitter. Wild.”

Passenger Reactions (Social Media):

@OrlandoFlyer92: “Just landed on United from Chicago. Something weird happened during landing but we’re stuck on the plane. Emergency vehicles everywhere. Anyone know what’s going on? #UA2323”

@TravelDad2026: “Our United flight can’t get to the gate because another plane is blocking the runway. Been sitting here 30 minutes. Orlando airport chaos!”

@DisneyBound2026: “Finally off the plane! Turns out our wheel FELL OFF during landing. Flight attendants were super calm but you could tell they were freaked out. All passengers safe!”

Flight Attendant Protocol:

What crew did onboard:

Immediate assessment: Checked for injuries (none)
Cabin announcement: “Remain seated, we have a mechanical issue”
Emergency services coordination: Radioed for ARFF (Aircraft Rescue and Fire Fighting)
Passenger management: Kept everyone calm, distributed water
Evacuation preparation: Reviewed bus procedures (no slides needed)

Why NO emergency evacuation:

Aircraft NOT on fire
No smoke or fumes
All passengers safe in seats
Emergency slides = injury risk (people break ankles, legs)
Bus evacuation = safer, slower, controlled

Timeline:

12:35 PM: Landing, wheel separates
12:40 PM: Emergency services arrive
12:45 PM: Pilot announces “mechanical issue”
1:00 PM: FAA approves bus evacuation plan
1:15 PM: First bus arrives at aircraft
1:35 PM: Last passenger departs plane
Total time trapped: ~60 minutes

The Weather Factor: 54 MPH Gusts

What Happened in Orlando’s Skies:

Sunday, January 18, 2026 – All day:

Strong cold front sweeping across Central Florida.

National Weather Service warnings:

Wind Advisory:

Sustained winds: 15-25 MPH
Gusts: 35-50 MPH
Areas: All of Central Florida
Duration: 11:00 AM – 6:00 PM EST

High Wind Warning (Brevard County):

Issued: 1:00 PM
Gusts: 50-60 MPH possible
Coastal areas affected

Exact Orlando Airport Conditions:

12:30 PM (5 minutes before UA2323 landing):

Orlando International Airport (MCO):

Wind gust: 54 MPH (recorded)
Wind direction: Northwest
Crosswind component: ~45 MPH (severe)

Orlando Executive Airport (nearby):

Wind gust: 56 MPH (recorded)

Translation: Pilots faced EXTREME crosswinds during landing.

Was It Safe to Land?

Airbus A321neo crosswind limits:

Maximum demonstrated crosswind: 40 knots (46 MPH)
Regulatory requirement: Airlines can land in crosswinds UP TO this limit
Pilot discretion: Captains can refuse landing if uncomfortable

54 MPH gust = 47 knots

Result: EXCEEDED maximum demonstrated crosswind by 1 knot.

However:

“Demonstrated crosswind” ≠ legal limit (it’s a guideline)
Airlines can land in higher crosswinds if conditions allow
Pilot judgment = final call

Question: Should United pilots have diverted?

Aviation experts debate:

Pro-diversion argument: “54 MPH gusts EXCEED aircraft limits. Pilot should have diverted to Tampa, Jacksonville, or even Miami. Safety > schedule.”

Pro-landing argument: “Pilots are trained to land in gusts up to 50+ knots. The gust was brief. Normal approach. Landing was within skill parameters.”

FAA investigation will determine: Was landing decision appropriate?

Why Did the Nose Wheel Separate?

The Landing Gear Mechanics:

Airbus A321neo nose landing gear:

Type: Twin-wheel configuration (left + right)
Manufacturer: Safran Landing Systems (France)
Material: Forged steel axle, aluminum wheel hubs
Design load: 50,000 lbs (22,680 kg) vertical force
Lifespan: 20,000+ landings (with proper maintenance)

What Should Happen During Hard Landing:

Normal sequence:

Main gear touches first (absorbs 80% of impact)
Nose gear descends gently
Nose wheels contact runway smoothly
Weight transfers from wings to landing gear
Aircraft settles, slows, taxis normally

Hard landing sequence:

Main gear SLAMS down (pilot error or wind gust)
Aircraft BOUNCES (nose stays elevated)
Nose gear SLAMS down HARD when aircraft settles
Vertical force EXCEEDS design limits
Components can FAIL (wheels, axles, struts)

What Happened to N14502:

Based on video analysis:

First bounce: Left main gear touched, aircraft bounced due to 54 MPH gust
Second impact: Right main gear SLAMMED down (extreme force)
Nose gear impact: When nose descended, nose wheels hit runway with EXCESSIVE vertical force
Right wheel failure: Axle/hub connection fractured
Wheel separation: Right wheel rolled away, left wheel remained

Critical failure point: The AXLE that connects both nose wheels.

Possible causes:
✅ Manufacturing defect (axle metallurgy)
✅ Maintenance oversight (crack not detected)
✅ Design flaw (axle too weak for extreme landings)
✅ Excessive force (pilot slammed nose down)

FAA investigation will examine:

N14502’s maintenance records
Axle metallurgy testing
Other A321neo nose gear incidents
Pilot landing technique (flight data recorder)

The Frontier Connection: Déjà Vu

April 15, 2025 – Frontier Flight 3506:

Route: Orlando → San Juan, Puerto Rico

Aircraft: Airbus A321-271NX (A321neo) – registration N322FR

What happened:

Hard landing at San Juan airport
Left nose wheel SEPARATED (identical failure to United)
Wheel fragments INGESTED by left engine
Engine sustained damage (fan blades, guide vanes, inlet cowl)
Thrust reverser damaged
Left inboard flaps damaged

Result:

Aircraft grounded 3+ months
NTSB investigation launched
Preliminary report released May 21, 2025

NTSB Findings (Frontier Incident):

From May 21, 2025 preliminary report:

“The first officer handled the descent with the captain monitoring, with a stable approach that ‘required a slight lateral correction to maintain centreline’ at about 150ft above ground. The first officer reduced thrust levers to idle, and the captain recalls that the landing flare became too high at about 15ft altitude.”

Translation: Pilot error—flared too high, causing hard landing.

Damage found:

“One of the wheel halves had fractured and there were numerous scratches and gouges noted along the [nose landing gear], along with damage to the tow fitting.”
“Metal fragments from the wheel assembly appear to have been ingested by the number one engine.”

Key finding: The wheel hub FRACTURED.

The Pattern:

Two A321neo nose wheel separations in 9 months:

Incident	Date	Airline	Aircraft Age	Cause	Damage
Frontier F3506	April 15, 2025	Frontier	~2 years	Hard landing (pilot error)	Left nose wheel separated, engine damage
United UA2323	January 18, 2026	United	2.2 years	Hard landing (wind gusts?)	Right nose wheel separated

Common factors:
✅ Both A321neo (same aircraft type)
✅ Both ~2 years old (brand new planes)
✅ Both nose wheel separations (identical failure mode)
✅ Both hard landings (excessive vertical force)
✅ Both in windy conditions

Question: Is this an A321neo design flaw?

Airbus response (anticipated): “Landing gear is designed to withstand hard landings within operational limits. If pilots exceed limits, components can fail. This is normal.”

Counter-argument: “Two brand-new aircraft suffering IDENTICAL failures within 9 months suggests systemic issue, not pilot error.”

The Ground Stop Chaos

12:40 PM – FAA Issues Ground Stop:

Order: ALL arriving flights to Orlando International Airport (MCO) must HOLD or DIVERT.

Reason: Disabled United A321neo blocking Runway 18L/36R.

Duration: 1 hour 35 minutes (12:40 PM – 2:15 PM)

Impact:

Flights affected:

Arrivals: 47 flights held in air or diverted
Departures: 23 flights delayed (couldn’t use blocked runway)
Total delays: 1,200+ minutes cumulative

Busiest diverted flights:

Southwest WN1847 (Baltimore → Orlando):

Held 45 minutes
Finally landed 2:20 PM (1 hour 5 minutes late)

JetBlue B61573 (New York JFK → Orlando):

Diverted to Tampa (TPA)
Passengers bussed 90 minutes to Orlando
Total delay: 3+ hours

Delta DL1895 (Atlanta → Orlando):

Held in air 30 minutes
Burned extra fuel circling
Landed 1 hour late

Why One Disabled Plane Cripples Entire Airport:

Orlando International Airport runway layout:

4 runways total:
- 18L/36R (primary commercial, 12,005 feet)
- 18R/36L (secondary commercial, 10,000 feet)
- 17L/35R (cargo/general aviation, 9,001 feet)
- 17R/35L (cargo/general aviation, 6,001 feet)

Typical operations:

Arrivals: Runway 18L/36R (where UA2323 stopped)
Departures: Runway 18R/36L
Parallel operations: Both runways used simultaneously

When 18L/36R blocked:

ALL arrivals → Runway 18R/36L (sharing with departures)
Capacity cut in half (60 operations/hour → 30)
Delays cascade immediately

Aircraft recovery:

Tow truck arrived 1:15 PM
N14502 towed off runway 2:05 PM
Runway inspected/cleared 2:15 PM
Total runway closure: 1 hour 35 minutes

What United Says (vs. What We Know)

Official United Airlines Statement:

Released Sunday, January 18, 2026, 3:47 PM EST:

“United Airlines flight 2323 traveling from Chicago O’Hare to Orlando International Airport experienced a mechanical issue upon landing. All customers and crew safely deplaned, and the aircraft has been removed from service for inspection. We sincerely apologize to our customers for the inconvenience and are working to accommodate them on alternative flights.”

What the Statement DOESN’T Say:

❌ “Nose wheel separated” → Downplayed as “mechanical issue”
❌ “54 MPH wind gusts” → No mention of weather
❌ “Passengers trapped 1 hour” → No apology for delay
❌ “Brand-new aircraft failure” → No explanation WHY 2-year-old plane failed
❌ “Second A321neo incident in 9 months” → No acknowledgment of pattern

Translation: Corporate damage control.

What Passengers Deserve to Know:

✅ Root cause: Was it pilot error, wind gusts, or design flaw?
✅ Inspection status: What did maintenance find?
✅ Fleet implications: Are other United A321neos at risk?
✅ Compensation: Will passengers get refunds, vouchers, apology miles?

As of January 19, 2026: United has provided ZERO additional details.

The FAA Investigation

What the FAA Will Examine:

1. Flight Data Recorder (FDR):

Approach speed, descent rate, thrust settings
Wind shear detection
Pilot control inputs
Exact moment of nose gear impact

2. Cockpit Voice Recorder (CVR):

Pilot communications
Decision to land vs. divert
Post-landing emergency procedures

3. Maintenance Records:

Last nose gear inspection (date, findings)
Any prior landing gear issues
Compliance with Airbus service bulletins

4. Nose Gear Physical Inspection:

Fractured axle metallurgy testing
Wheel hub integrity
Strut damage assessment

5. Weather Data:

Exact wind speed/direction at touchdown
Wind shear warnings (if any)
Pilot awareness of conditions

6. Pilot Training:

Captain’s crosswind landing experience
First officer’s role (if applicable)
United’s hard landing procedures

Potential Outcomes:

Scenario 1: Pilot Error

FAA finds pilot should have diverted (winds too strong)
United disciplines or retrains pilot
No fleet-wide action

Scenario 2: Maintenance Failure

FAA finds axle had pre-existing crack, missed in inspection
United overhauls nose gear inspection procedures
Possible fine for negligence

Scenario 3: Design Flaw

FAA finds A321neo nose gear inadequate for hard landings
Airbus issues Service Bulletin (mandatory fixes)
ALL A321neos globally inspected/modified

Scenario 4: Weather Exception

FAA finds 54 MPH gusts exceeded reasonable limits
No fault assigned (Act of God)
United absolved of responsibility

Timeline for Investigation:

Preliminary report: 7-10 days (by January 28, 2026) Final report: 12-18 months (by mid-2027)

Precedent: Frontier A321neo incident (April 2025) took 5+ weeks for preliminary report.

What This Means for Tier 1 Travelers

If You’re Flying United A321neo:

How to identify:

Book confirmation: Aircraft type listed as “Airbus A321neo” or “321N”
Seat map: 200 seats (United config: First 20, Economy Plus 60, Economy 120)
FlightRadar24: Track your flight, shows aircraft registration

Should you be worried?

Short answer: Probably not.

Long answer:

Two incidents in 9 months = concerning but not epidemic
Both involved hard landings = pilot technique factor
ZERO injuries = landing gear failures are survivable
FAA investigating = regulatory oversight working

However:

Both brand-new aircraft = suggests potential design issue
Identical failure mode = nose wheel separation (not random)
Unknown root cause = until FAA reports, uncertainty remains

Should You Request Aircraft Change?

Realistically: No.

Why:

Airlines WON’T change aircraft for individual passenger concerns
A321neo is EXTREMELY common (9,000+ orders globally)
Hard landing risk exists on ALL aircraft types

Better strategy:
✅ Fly in good weather (avoid wind advisories)
✅ Choose experienced airlines (United has good safety record overall)
✅ Wear seatbelt always (even if sign off)
✅ Trust statistics (air travel = safest mode of transport)

What About Other A321neo Operators?

Airlines with large A321neo fleets (Tier 1 markets):

Airline	A321neo Fleet	Incidents
JetBlue	79 aircraft	0 nose gear separations
American	56 aircraft	0 nose gear separations
Delta	44 aircraft	0 nose gear separations
United	41 aircraft	1 nose gear separation (Jan 2026)
Frontier	33 aircraft	1 nose gear separation (April 2025)

Pattern: Only United and Frontier (both US ultra-low-cost/budget carriers) have experienced this failure.

Possible explanations:

Pilot training differences (budget airlines = less experienced pilots?)
Maintenance standards (budget airlines = tighter schedules?)
Route networks (more landings in challenging weather?)
Random chance (small sample size, statistically insignificant)

The Broader Context: Landing Gear Failures Are RARE

Commercial Aviation Landing Gear Statistics:

Annual flights worldwide: ~40 million
Landing gear failures: ~50-80 per year (0.0001% of flights)
Fatal accidents from landing gear: ~1-2 per decade

Translation: You’re more likely to be struck by lightning than experience landing gear failure.

Famous Landing Gear Incidents (For Perspective):

JetBlue Flight 292 (September 21, 2005):

A320 nose gear rotated 90° sideways
Landed at LAX with sparks flying
ALL passengers safe (perfect pilot execution)
Media circus: Live TV coverage, millions watched

LOT Polish Airlines 767 (November 1, 2011):

Main landing gear FAILED to deploy
Landed on BELLY at Warsaw airport
ALL 231 passengers safe
Hero pilot: Belly landing with ZERO injuries

Southwest 1380 (April 17, 2018):

Engine explosion mid-flight (unrelated to landing gear)
Passenger partially sucked out window (died)
Emergency landing, landing gear WORKED PERFECTLY

Point: Landing gear failures are EXTREMELY rare, and when they happen, survival rate is ~99.9%.

What Airlines MUST Change

Immediate Reforms Needed:

1. Mandatory A321neo Nose Gear Inspections:

Airbus + airlines MUST:
✅ Inspect ALL A321neo nose gear axles (ultrasonic testing)
✅ Replace any axles showing fatigue cracks
✅ Increase inspection frequency (every 500 landings vs. 1,000)

Currently: Inspections every 1,000-2,000 landings (too infrequent).

2. Hard Landing Reporting:

Airlines MUST report:
✅ ALL hard landings to FAA within 24 hours
✅ Detailed flight data (G-forces, descent rate, impact)
✅ Mandatory aircraft inspection after ANY hard landing >2.1G

Currently: Airlines often DON’T report unless damage visible.

Result: Structural damage accumulates undetected.

3. Crosswind Landing Limits:

Airlines MUST enforce:
✅ Maximum crosswind = 40 knots (46 MPH) – NO EXCEPTIONS
✅ Automatic diversion if gusts exceed limits
✅ Pilot discretion to refuse landing (no schedule pressure)

Currently: Airlines pressure pilots to land (on-time performance metrics).

4. Passenger Transparency:

Airlines MUST disclose:
✅ Aircraft maintenance history (major incidents)
✅ Landing conditions (wind speed, crosswind component)
✅ Pilot experience (total hours, type rating hours)

Currently: Passengers know NOTHING about aircraft they’re flying.

The Bottom Line

United Airlines Flight UA2323’s hard landing at Orlando International Airport on Sunday January 18, 2026—resulting in RIGHT nose wheel SEPARATING from brand-new 2-year-old Airbus A321neo registration N14502 during 54 MPH wind gust touchdown, trapping 200 passengers + 6 crew on disabled aircraft for 1 HOUR before bus evacuation while FAA issued GROUND STOP halting ALL arrivals for 1 hour 35 minutes—marks SECOND identical A321neo nose wheel failure in 9 months (following April 2025 Frontier incident in Puerto Rico), raising urgent questions about whether United/Frontier pilot training, maintenance standards, or Airbus A321neo landing gear DESIGN FLAW is causing disturbing pattern of catastrophic failures on brand-new aircraft that should NOT experience such breakdowns.

For Tier 1 travelers (US, UK, Canada, Australia): While ZERO injuries confirm landing gear failures are SURVIVABLE emergencies, United’s incident exposes three critical gaps:
(1) A321neo nose gear vulnerability—two brand-new aircraft suffering IDENTICAL wheel separations suggests systemic issue requiring FAA mandate for fleet-wide inspections,
(2) Crosswind landing decisions—54 MPH gusts EXCEEDED aircraft limits yet pilots landed anyway, questioning whether schedule pressure overrides safety judgment, and
(3) Passenger transparency failure—United downplayed “nose wheel separation” as generic “mechanical issue” without explaining root cause, leaving travelers uncertain whether A321neo fleet is safe.

Immediate actions for travelers:
(1) Track your aircraft type—use FlightRadar24 to identify A321neo flights, consider rebooking if concerned (though statistically safe),
(2) Avoid flying in high wind advisories—check weather before departure, request rebooking if winds >40 MPH forecast,
(3) Always wear seatbelt—landing gear failures are survivable IF you’re secured,
(4) Demand answers from United—contact customer service asking for root cause explanation, compensation for Orlando passengers, fleet inspection status. Until FAA releases preliminary report (by January 28, 2026), uncertainty remains whether United’s A321neo fleet has hidden defect waiting to manifest on YOUR next flight—or if Orlando incident was isolated bad luck in extreme weather. Either way, passengers deserve transparency, not corporate spin.

The wheels may literally fall off—but will United tell you why?

Critical Resources & Tracking

Track Your Flight Aircraft:

FlightRadar24: 🌐 flightradar24.com 💡 Enter flight number → See exact aircraft registration (e.g., N14502) 💡 Cross-reference with incident databases

FlightAware: 🌐 flightaware.com 💡 Historical flight data, delays, cancellations 💡 Aircraft type filters

Planespotters.net: 🌐 planespotters.net/aircraft/Airbus-A321-271NX-N14502 💡 N14502 specific page (incident aircraft) 💡 Maintenance history, photos, tracking

Check Weather Before Flying:

Aviation Weather Center: 🌐 aviationweather.gov 💡 Real-time airport conditions (winds, visibility, ceilings) 💡 Wind shear alerts, turbulence forecasts

Weather Underground: 🌐 wunderground.com 💡 Hour-by-hour wind forecasts 💡 Set alerts for high wind conditions

National Weather Service: 🌐 weather.gov 💡 Wind advisories, high wind warnings 💡 Airport-specific forecasts

Monitor FAA Investigation:

FAA Incident Database: 🌐 faa.gov/data_research/accident_incident 💡 Search “UA2323” or “N14502” 💡 Preliminary reports posted here

NTSB Aviation Database: 🌐 ntsb.gov/investigations 💡 More detailed investigations 💡 Final reports (12-18 months post-incident)

File Complaints:

United Airlines Customer Care: 📞 1-800-864-8331 🌐 united.com/feedback ✉️ Demand explanation of incident, fleet safety assurances

DOT Aviation Consumer Protection: 📞 1-202-366-2220 🌐 transportation.gov/airconsumer 💡 File complaint if United refuses transparency

FAA Safety Hotline: 📞 1-866-TELL-FAA (1-866-835-5322) 💡 Report safety concerns, demand A321neo inspections