Last Updated on July 25, 2026 by Daniel Globe
The airline outage discussed here was the global CrowdStrike technology incident of July 19, 2024. A faulty security-content update caused some Windows computers running CrowdStrike Falcon software to crash, disrupting airline check-in, dispatch, crew-management, call-center, and other operational systems. The impact varied widely because airlines did not all use the same software, vendors, or recovery processes.
Quick Answer
During the July 19, 2024 CrowdStrike outage, Southwest said the event did not directly affect its operations, while JetBlue and Alaska Airlines reported little or no systemwide disruption. American and Delta were affected, so claims that they were unaffected are incorrect. Historical status does not confirm whether a flight is operating today.
Key Takeaways
- Southwest reported that the CrowdStrike outage did not directly affect its operations.
- JetBlue reported normal systemwide operations, while Alaska officials reported no outage-related delays for Alaska Airlines at Anchorage and Fairbanks at the time of their update.
- American Airlines and Delta Air Lines were affected and were subject to FAA-recorded ground stops.
- An airline with no direct computer failure could still face airport congestion, late inbound aircraft, vendor problems, or connecting-flight disruptions.
- For a current trip, check the airline and airport directly rather than relying on a historical list of unaffected airlines.
Warning: This is a historical review of the July 19, 2024 outage, not a live airline-status page. An airline that operated normally during that incident can still have delays or cancellations today because of weather, maintenance, air-traffic restrictions, staffing, or a different technology failure.
Overview of the Outage Impact
On July 19, 2024, CrowdStrike released a faulty content configuration update for its Falcon security software on Windows systems. CrowdStrike said the incident was not a cyberattack. The update caused affected Windows computers to crash or repeatedly restart, and restoring some machines required direct recovery work.
Microsoft estimated that approximately 8.5 million Windows devices were affected. That was less than 1% of all Windows machines, but many affected devices supported critical services in aviation, healthcare, banking, government, and other industries.
The outage showed how a problem affecting a relatively small share of computers can cause widespread disruption when those computers support essential operational systems.
Note: The incident is often called a “Microsoft outage,” but the widespread Windows crashes were caused by a defective CrowdStrike Falcon content update. Microsoft also experienced separate service issues around the same period, which added to public confusion.
Airlines Reporting Little or No Direct Impact
- Southwest Airlines: The airline said the outage did not directly affect its operations. Passengers could still encounter delays caused by congested airports or other affected organizations.
- JetBlue: The airline reported normal operations without systemwide cancellations or delays related to the outage, while advising customers to allow extra time at affected airports.
- Alaska Airlines: An official Alaska transportation update said Alaska Airlines flights at Anchorage and Fairbanks were on time, with no reported delays attributed to the outage at the time of the announcement.
These airlines are better described as minimally affected or not directly affected rather than universally unaffected. Conditions differed by airport, route, vendor, and time of day.
Airlines Confirmed as Affected
American Airlines and Delta Air Lines were among the carriers affected. FAA records show that both airlines requested broad ground stops on July 19, 2024. United Airlines and several other carriers also reported system or operational disruption.
American restored much of its operation relatively quickly, while Delta experienced a longer recovery. Once flights, crews, and aircraft fall out of position, cancellations can continue even after the original computer problem has been corrected.
Analysis of Unaffected Airlines’ Resilience
Lower disruption does not automatically mean that one airline has better technology than every affected competitor. In a vendor-specific incident, an organization may avoid the direct failure simply because it does not run the affected software on essential computers.
Southwest later attributed its limited direct impact to using a different primary endpoint-security provider and having redundancy for some vendors. That explanation is more credible than the viral claim that Southwest survived because it operated its airline on Windows 3.1. There is no reliable evidence that an obsolete consumer operating system was the reason for its continuity.
Several factors can reduce the effect of a technology incident:
- Different technology dependencies: Systems that do not use the faulty product are not exposed to the same failure.
- Dependency mapping: Airlines need to know which operational functions rely on each vendor, application, network, and device.
- Redundant systems: Critical services may have alternate platforms, backup environments, or separate communication channels.
- Staged software deployment: Updates can be tested on a smaller group of systems before being released more widely where technically possible.
- Manual fallback procedures: Trained teams may temporarily complete certain tasks manually when automated systems are unavailable.
- Tested recovery plans: Written procedures are most useful when employees regularly practice them.
Cloud hosting alone does not guarantee resilience. A cloud service, security vendor, identity system, network provider, or shared database can become a common point of failure. Effective continuity planning combines technology diversity, recovery procedures, trained staff, and realistic exercises.
Customer Experience and Satisfaction
During a disruption, passengers usually judge an airline by the clarity and speed of its response. Even an airline with functioning internal systems can create frustration if it gives conflicting updates or makes rebooking difficult.
| Passenger Situation | Possible Experience | Best Action |
|---|---|---|
| Airline systems are operating normally | Normal check-in and boarding, although the airport may still be crowded | Check the flight in the airline app before leaving |
| Airline is unaffected but the airport is disrupted | Longer security, baggage, gate, or service-desk lines | Allow extra time and monitor the departure gate |
| Inbound aircraft or crew is delayed | A flight may be late even though the airline’s main systems are working | Track the incoming aircraft and connection time |
| Flight is canceled | Automatic rebooking may be offered, but alternatives may be limited | Compare rebooking with the refund option before accepting |
Useful communication should include the reason for the disruption, the next update time, rebooking options, baggage instructions, and any available meal or hotel assistance. Vague promises such as “operations will resume soon” provide little help when passengers are deciding whether to remain at the airport.
Pro Tip: Check three sources before traveling during a major outage: the airline app, the departure airport’s website, and the status of the aircraft operating your flight. An “on time” label can change when the incoming aircraft or crew is delayed elsewhere.
How to Check Whether an Airline Is Affected Now
- Open the airline’s official app or flight-status page.
- Enter the flight number rather than checking only the route.
- Review the departure airport’s official website for gate or terminal disruption.
- Check for a travel waiver that permits free changes.
- Confirm the status again before leaving for the airport.
- Keep screenshots of cancellation notices, rebooking offers, and receipts.
Do not assume that every flight operated by an affected airline will be canceled. Likewise, do not assume that every flight operated by a minimally affected airline will depart on time.
Operational and Financial Implications
An airline that maintains most of its schedule during an industry disruption can protect revenue, avoid some recovery expenses, and preserve customer confidence. It may also receive bookings from travelers whose original flights were canceled by another carrier.
However, the long-term financial benefit should not be exaggerated. An unaffected airline may face higher airport costs, disrupted partner flights, displaced passengers, baggage problems, and congestion throughout the aviation network. A single day of stronger bookings does not prove a lasting increase in market share or profitability.
Affected airlines face more than the immediate cost of canceled flights. Recovery can involve:
- repositioning aircraft and flight crews;
- paying overtime and operational recovery expenses;
- providing refunds or passenger assistance;
- handling baggage separated from passengers;
- restoring call-center and airport systems;
- investigating vendor and technology dependencies;
- and rebuilding customer trust.
The scale of recovery depends on how many systems fail and how tightly those systems are connected. A failure in crew scheduling can continue disrupting flights after check-in computers and airport displays are restored.
Comparison with Affected Airlines
The difference between a minimally affected airline and an affected airline cannot be reduced to “modern technology” versus “outdated technology.” During the CrowdStrike incident, direct exposure depended first on whether critical Windows systems were running the affected Falcon software.
| Airline | July 19, 2024 Status | Important Context |
|---|---|---|
| Southwest | No direct operational impact reported | Could still experience indirect airport or network delays |
| JetBlue | Normal systemwide operations reported | Passengers were advised to monitor airport conditions |
| Alaska Airlines | Little reported direct impact | Alaska officials reported flights on time at Anchorage and Fairbanks at the time of their update |
| American Airlines | Affected | FAA records show a broad ground stop, followed by a relatively fast restoration of operations |
| Delta Air Lines | Heavily affected | FAA records show a systemwide ground stop, and crew-management disruption contributed to a longer recovery |
American and Delta demonstrate why the initial computer failure is only part of the story. Two airlines can encounter the same vendor incident but recover at different speeds because of fleet size, crew scheduling, application dependencies, backup systems, and the number of flights already disrupted.
Passenger Rebooking, Refunds, and Assistance
For flights to, from, or within the United States, passengers should review the current U.S. Department of Transportation refund guidance. When an airline cancels or significantly changes a flight and the passenger does not accept the offered alternative, a refund may be due under applicable DOT rules.
Meals, hotels, ground transportation, and rebooking on another carrier are different from ticket refunds. These benefits often depend on whether the disruption is considered within the airline’s control and on the commitments made by that airline.
The DOT’s Airline Cancellation and Delay Dashboard compares the services major U.S. airlines have committed to provide for qualifying controllable delays and cancellations.
- Ask whether the airline will rebook you on its next available flight.
- Ask whether rebooking on a partner or another airline is available.
- Request written information about meal, hotel, and transportation assistance.
- Keep itemized receipts for reasonable expenses.
- Do not accept a voucher automatically if you would prefer a refund and are eligible for one.
Lessons Learned and Future Preparedness
The CrowdStrike outage showed that aviation resilience depends on more than keeping a backup server. Airlines rely on interconnected systems for reservations, dispatch, crew scheduling, weight-and-balance calculations, maintenance, communications, baggage, and customer service.
Strong preparedness should include:
1. Map Critical Dependencies
Airlines should identify the applications, vendors, devices, networks, and identity services required for each safety-critical and customer-facing function. This makes it easier to predict which operations will fail when a provider becomes unavailable.
2. Reduce Single Points of Failure
Critical functions should not rely unnecessarily on one device type, vendor, network path, authentication service, or administrative tool. Redundancy must be separated enough that one faulty update cannot disable the primary and backup environment at the same time.
3. Test Updates and Recovery Procedures
Organizations should use controlled deployment groups where possible and regularly test restoration procedures. CrowdStrike’s investigation led to changes in content validation, staged deployment, testing, and customer controls.
4. Maintain Safe Manual Procedures
Some functions can continue temporarily through approved manual procedures, but safety requirements must remain the priority. A manual workaround should never bypass aircraft-dispatch, maintenance, security, or weight-and-balance controls.
5. Prepare for Operational Recovery
Restoring a computer does not automatically restore an airline schedule. Recovery plans must account for aircraft locations, crew duty limits, maintenance timing, passenger connections, baggage, and airport capacity.
6. Communicate Through Independent Channels
If the main website or call center fails, airlines need alternate ways to publish reliable updates. Mobile notifications, airport displays, social channels, text messages, and recorded telephone information should use a consistent source of truth.
The difference was not solar-powered airport or airline technology. The evidence points to software exposure, vendor choices, system dependencies, redundancy, and recovery capability. Energy innovation may support sustainability, but it did not explain why certain airlines avoided the CrowdStrike software failure.
Conclusion and Recommendations
Southwest, JetBlue, and Alaska Airlines were among the U.S. carriers reporting little or no direct systemwide disruption during the July 19, 2024 CrowdStrike outage. American Airlines and Delta Air Lines were affected, making the original claim that all three of Delta, Southwest, and American were unaffected inaccurate.
The event does not prove that minimally affected airlines have perfect systems or that every affected airline was poorly prepared. It shows that vendor exposure, system architecture, operational complexity, and recovery planning can produce very different outcomes during the same incident.
Travelers should treat any list of unaffected airlines as a dated snapshot. For a current journey, verify the exact flight through the airline, check the departure airport, review available travel waivers, and understand the difference between rebooking assistance and a refund.
Frequently Asked Questions
What airlines were not affected by the July 2024 CrowdStrike outage?
Southwest said the outage did not directly affect its operations. JetBlue reported normal systemwide operations, and Alaska Airlines experienced little reported direct disruption. However, individual flights could still be delayed by airport congestion, vendors, crews, or connecting aircraft.
Were Delta and American Airlines affected?
Yes. FAA records show broad ground stops for both American Airlines and Delta Air Lines on July 19, 2024. American restored much of its operation relatively quickly, while Delta experienced a longer recovery and continued cancellations.
Was Southwest protected because it used Windows 3.1?
No reliable evidence supports that viral explanation. Southwest later said it primarily used a different endpoint-security provider and had redundancy for some affected vendors. Its continuity should not be attributed to Windows 3.1.
Can an unaffected airline still have delayed flights?
Yes. An airline may avoid the direct computer failure but still be affected by airport congestion, ground-service vendors, air-traffic restrictions, delayed inbound aircraft, displaced crews, baggage systems, or connecting passengers.
How can I check whether my airline is affected today?
Check the exact flight number in the airline’s official app, review the departure airport’s website, look for a travel waiver, and confirm the status again before leaving. A historical article cannot provide live operational status.
Am I entitled to a refund if my flight is canceled?
For eligible flights to, from, or within the United States, a refund may be due when the airline cancels or significantly changes the flight and you do not accept the alternative offered. Check current U.S. Department of Transportation guidance because the exact result depends on the itinerary and circumstances.
Sources
- CrowdStrike Preliminary Post Incident Review — explains the defective Falcon content update and Windows system crashes.
- Microsoft: Helping Customers Through the CrowdStrike Outage — provides the estimate of approximately 8.5 million affected Windows devices.
- FAA American Airlines Ground Stop Advisory — confirms that American Airlines was affected on July 19, 2024.
- FAA Delta Air Lines Ground Stop Advisory — confirms Delta’s systemwide ground stop.
- Alaska Department of Transportation Outage Update — reports Alaska Airlines flights on time at Anchorage and Fairbanks during the incident.
- U.S. DOT Airline Cancellation and Delay Dashboard — compares airline commitments for qualifying controllable delays and cancellations.