By John Q. Hosedrinker 
A Southwest Airlines flight from Southern California experienced a sudden drop shortly after takeoff due to an alert about another aircraft nearby, resulting in passenger distress and injuries to two flight attendants. The plane descended approximately 300 feet in 36 seconds in response to the alert, which the FAA is now investigating. According to passenger accounts, the pilot mentioned a collision warning requiring an evasive maneuver, potentially involving a British fighter plane. Despite the incident, the flight continued to Las Vegas and landed safely, while Southwest Airlines is cooperating with the FAA to determine the specifics of the event.
Read the original article here
Southwest Airlines flight headed to Las Vegas takes dramatic plunge in response to nearby aircraft – it seems like there’s a bit of a buzz around this incident, doesn’t it? The initial reports used the word “plunge,” which is definitely going to grab attention, and when you combine that with an aircraft, it sets a certain tone. The incident involves a Southwest flight making a maneuver to avoid another aircraft. Flight tracking data indicates a descent of roughly 300 feet over a span of 36 seconds.
Now, let’s break down that 36-second descent. While the term “plunge” is used, the rate of descent described might not be as dramatic as the initial impression suggests. Some sources suggest the descent wouldn’t necessarily cause people to be thrown from their seats. The key here is the acceleration. What matters most is the initial rate of descent, specifically in those first few seconds, as this would generate the more significant G-force felt by the passengers.
The situation highlights the effectiveness of systems designed to prevent mid-air collisions, specifically the Traffic Collision Avoidance System, or TCAS. In this particular case, a Southwest 737 received a TCAS Resolution Advisory (RA). This is where the system identifies potential conflicts and provides instructions to the flight crew to avoid a collision. The crew’s swift response, a descent in this instance, is a normal procedure when following a TCAS RA. The other aircraft, identified as a Hawker Hunter, climbed. These systems are designed to issue instructions that help to quickly solve these potential problems.
The fact that the aircraft were separated by several miles horizontally and a few hundred feet vertically suggests that the system was working as intended, though the pilots will have to do some paperwork on the ground. The system is known to be sensitive, sometimes responding to circumstances that might seem minor, like turbulence causing small changes in altitude. This is also why it’s vital to keep seatbelts fastened while seated.
One of the initial comments mentions a possible shortage of air traffic controllers. Air traffic controllers are an essential part of flight safety. This shortage has the potential to increase the workload and, therefore, the potential for errors. It is certainly understandable why some might have concerns about these occurrences.
The fact that this incident involved a military aircraft, a Hawker Hunter, does raise some questions. A military aircraft operating in proximity to a commercial flight could potentially increase the risk of incidents. The reasons why this was happening aren’t entirely clear, but are potentially important.
The focus on the FAA, flight safety measures and staffing, and other such factors is worth pointing out. These are all crucial for ensuring a safe flying environment.
The incident reminds us of the importance of vigilance in air travel. Any time there’s a near miss, or an event that requires immediate action by pilots, it can be unsettling. This incident, despite its potentially sensationalized reporting, underscores the importance of the safety systems in place. The pilot and the crew did exactly what they were supposed to.