Tag

Runway Collision

All articles tagged with #runway collision

Near-Collision at Reagan National Airport Spurs FAA Probe
aviation-safety1 year ago

Near-Collision at Reagan National Airport Spurs FAA Probe

An American Airlines flight bound for Boston had to abruptly stop during takeoff at Reagan National Airport to avoid a collision with a private plane that had landed on an intersecting runway. The FAA is investigating the incident, which is the second close call at the airport in six weeks. The flight eventually departed four hours late and landed safely in Boston.

"Close Call: JetBlue and Southwest Planes Narrowly Avoid Collision on D.C. Airport Runway"
aviation-safety1 year ago

"Close Call: JetBlue and Southwest Planes Narrowly Avoid Collision on D.C. Airport Runway"

A JetBlue flight nearly collided with a Southwest Airlines plane at Reagan National Airport, prompting the FAA to investigate the incident. The planes came within 1,000 feet of each other, leading to the JetBlue flight aborting takeoff. This close call raises concerns about operational errors and air traffic control management, following a series of recent near-collisions at American airports. The FAA has committed to a goal of zero serious close calls and is taking steps to address controller fatigue and increase the number of air traffic controllers.

JetBlue pilot's last-second maneuver prevents collision on Colorado runway
aviation2 years ago

JetBlue pilot's last-second maneuver prevents collision on Colorado runway

A new report from the National Transportation Safety Board (NTSB) revealed that a pilot's last-second maneuver prevented a collision between two planes on the same runway at Yampa Valley Airport in Colorado. The incident occurred due to unclear communication between the two aircraft and the traffic control center. The report stated that the planes were approximately 2.2 miles apart when the incident took place. The JetBlue Airbus A320 incurred a tail strike during takeoff, resulting in substantial damage to the airplane. No injuries were reported, and the NTSB attributed the incident to poor communication.