A recent incident at Roanoke–Blacksburg Regional Airport saw a United Express Embraer 145 jet overrun a wet runway, prompting an NTSB investigation. Preliminary findings reveal the first officer attempted to initiate a go-around twice, but the captain continued the landing, raising serious questions about Crew Resource Management (CRM) and pilot decision-making under pressure, echoing critical aviation safety lessons from the past.
A routine landing turned into a concerning runway overrun at Roanoke–Blacksburg Regional Airport on September 24, when United Express Flight 4339, an Embraer 145 operated by regional carrier CommuteAir, skidded past the end of a wet runway. The incident, which saw the aircraft brought to a sudden halt by an EMAS (Engineered Material Arresting System) bed, miraculously resulted in no injuries to the 53 people on board. However, the preliminary report by the National Transportation Safety Board (NTSB) has cast a spotlight on critical pilot decision-making, revealing that the captain reportedly ignored multiple calls for a go-around from the first officer.
A Near Miss in Roanoke: The Incident Details
According to the NTSB’s preliminary report, Flight 4339 was approaching runway 34 in a rainstorm and was noted by the first officer (FO) to be too high. Despite this, the landing continued. “After crossing the runway markings, the FO called for a go-around, but the captain continued,” the NTSB stated. The situation escalated when, “About halfway down the runway, the FO called for a go-around a second time, but the captain continued.” This sequence of events, where a junior pilot’s safety calls were overridden, is now a central focus of the ongoing investigation, with the flight’s data and voice recorders currently being analyzed at the NTSB lab in Washington.
Understanding “Go-Arounds” and Pilot Protocol
A go-around, also known as a missed approach, is a fundamental aviation maneuver where pilots abort a landing attempt and climb away from the runway. This procedure is initiated when conditions are not safe for a successful landing, such as an unstable approach, runway obstructions, or adverse weather. A crucial aspect of modern aviation safety protocols, particularly Crew Resource Management (CRM), dictates that either pilot—captain or first officer—can call for a go-around, and the response to such a callout should be immediate. The Federal Aviation Administration (FAA), in 2010, emphasized this by calling for all airlines to implement policies that reinforce this shared responsibility in the cockpit. The Roanoke incident highlights a potential breakdown in this vital safety standard.
Historical Echoes: The Weight of Pilot Responsibility and Failed Go-Arounds
The Roanoke incident, though non-fatal, resonates with past aviation events that underscored the critical importance of pilot decision-making and adherence to established procedures.
Ferguson v. NTSB: The Reckless Conduct Precedent
Decades ago, the landmark aviation ruling of Ferguson v. NTSB, 678 F.2d 821 (9th Cir. 1982), established a significant precedent regarding pilot responsibility. On July 31, 1979, Captain Lowell G. Ferguson of Western Airlines Flight 44 mistakenly landed a Boeing 737-200 at Buffalo, Wyoming, believing it to be Sheridan, his intended destination. Despite Ferguson’s claim of an “honest mistake” and his clean record, his pilot certificate was suspended for 60 days. The NTSB and the court rejected his appeal, noting his failure to familiarize himself with available flight information and company policy requiring radio navigational instrument use for airport identification. The ruling coined the phrase, “inadvertent and not deliberate actions cannot encompass reckless conduct,” solidifying the expectation that professional pilots must take all available steps to avoid errors, regardless of intent. The full text of this ruling can be reviewed via OpenJurist.
Ferguson’s case highlights that even “honest mistakes” can lead to severe penalties if they stem from a failure to follow fundamental safety regulations and professional standards. The parallel with the Roanoke incident is stark: a professional pilot’s decision to proceed despite clear warnings raises similar questions of accountability and adherence to established protocols.
The Osh Overrun: Somatogravic Illusion and Passive Crew
Another striking example of a botched go-around occurred on November 22, 2015, involving an Avia Traffic Boeing 737-300 attempting to land in Osh, Kyrgyzstan, in poor visibility. Despite the decision to go around being “correct,” it was initiated belatedly. The captain, possibly experiencing somatogravic illusion due to fatigue, pushed forward on the yoke, causing the aircraft to descend instead of climb. Compounding the error, the first officer’s “passive” behavior meant the captain’s errors went uncorrected. The aircraft struck the runway with its gear retracting, sustained substantial damage, and eventually suffered an undercarriage collapse during an emergency landing. This incident, detailed by FlightGlobal, underscores the critical role of active Crew Resource Management and the dangers of uncorrected pilot errors, particularly when exacerbated by factors like fatigue or sensory illusions.
While the Roanoke incident’s first officer was not passive, having actively called for a go-around, the Osh overrun illustrates the dire consequences when a crew’s collective safety mechanisms fail to prevent an aircraft from continuing into danger. Both cases emphasize that effective communication and strict adherence to go-around procedures are non-negotiable for flight safety.
The Broader Implications for Aviation Safety
The Roanoke runway overrun serves as a potent reminder of several enduring challenges in aviation safety:
- Crew Resource Management (CRM): The incident highlights the paramount importance of robust CRM training, which empowers all crew members to speak up and challenge decisions that compromise safety, regardless of rank.
- Decision-Making Under Pressure: Pilots operate in high-stakes environments where split-second decisions are common. Understanding the psychological factors that can influence these decisions, such as stress, fatigue, or cognitive biases, is crucial for improving training and protocols.
- Adherence to Standard Operating Procedures (SOPs): Go-arounds are a safety net. When pilots deviate from established SOPs, even with good intentions, the risks escalate dramatically.
- Technological Safeguards: The EMAS system at Roanoke performed its function, preventing a potentially more severe outcome. This underscores the value of such infrastructure in mitigating the consequences of pilot error.
What the Community is Saying: Trust and Accountability
Across aviation enthusiast forums and expert discussions, the Roanoke incident has sparked conversations about the intricate dynamics within the cockpit. Community members often discuss the immense pressure on captains, the balance between a captain’s ultimate authority and the need for crew collaboration, and the psychological impact of errors on pilots. There’s a strong emphasis on maintaining unwavering trust in aviation professionals, yet also a demand for absolute accountability when established safety procedures are not followed. The public expects that pilots, as highly trained professionals, will prioritize safety above all else, making every effort to mitigate risks.
Moving Forward: Lessons from Roanoke and Beyond
As the NTSB’s investigation into United Express Flight 4339 continues, the aviation community awaits its final report. This incident, alongside historical precedents like Ferguson v. NTSB and the Osh overrun, will undoubtedly contribute to ongoing discussions about pilot training, CRM effectiveness, and the critical importance of a safety culture that prioritizes clear communication and adherence to procedures above all else. Every incident, even one without fatalities, offers invaluable lessons that propel the industry closer to its ultimate goal of perfect safety.
