2005 Logan Airport runway incursion

Coordinates: 42°21′31″N 70°59′49″W / 42.35861°N 70.99694°W / 42.35861; -70.99694
Source: Wikipedia, the free encyclopedia.

2005 Logan Airport near runway incursion
Incident
DateJune 9, 2005 (2005-06-09)
Summary
Boeing 737-300 involved in the incident, USAir livery with a previous registration.
TypeBoeing 737-3B7
OperatorUS Airways
IATA flight No.US1170
ICAO flight No.USA1170
Call signUSAIR1170
RegistrationN394US
Flight originLogan International Airport
Boston, Massachusetts
DestinationPhiladelphia Int'l Airport
Philadelphia, Pennsylvania
Occupants109
Passengers103
Crew6
Fatalities0
Injuries0
Survivors109

The 2005 Logan Airport

EDT on June 9, 2005 between US Airways Flight 1170 (US1170) and Aer Lingus Flight 132 (EI132). EI132 was an Airbus A330-300 aircraft, owned and operated by the Irish airline Aer Lingus, destined for Shannon, Ireland, and carrying 12 crew members and 260 passengers. US1170 was a Boeing 737-300 US Airways flight destined for Philadelphia and carrying six crew members and 103 passengers. The near-collision took place on the runway at Logan International Airport (BOS) in Boston, Massachusetts
.

Incident

Runway layout at Logan Airport at the time of the incident. Runway 15R runs from top left to bottom right, while runway 9 runs from lower center to mid-right

To reduce radio congestion and consequences resulting from pilot or controller error, airports with a large number of operations will typically split the

tower (local) controller into two or more positions. This was the case on the evening of June 9, 2005, when the two incident flights were handled by different controllers. The local control west controller was responsible for Aer Lingus Flight 132 and the local control east controller was responsible for US Airways Flight 1170.[1]

At 19:39:10, Aer Lingus Flight 132 was cleared for takeoff from Runway 15R by local control west. Five seconds later, local control east cleared US Airways Flight 1170 for takeoff from Runway 9, which intersects with Runway 15R; the aircraft had essentially been sent on a collision course. With the airport terminals between the two aircraft as the takeoffs began, the flight crews could not initially see each other.[1]

During the takeoff roll, the US Airways

V1 speed and could no longer safely abort takeoff. Therefore, the flight crew continued down the runway and lifted off after passing through the intersection.[1][2]

Superior Airmanship Award

Air Line Pilots Association (ALPA) for their quick reactions and expert adjustment of their takeoff maneuver.[2]

Probable cause

The

NTSB completed its investigation and found that the east tower controller had given the west tower controller permission for the Aer Lingus to depart on 15R. While coordinating other traffic, he forgot about releasing that aircraft and cleared the US Airways flight for takeoff. Local procedures required the east controller to wait until the departure on 15R had passed through the intersection before clearing the aircraft on Runway 9 for takeoff. The NTSB reported that the probable cause of the incident was that the east local controller failed to follow FAA Order 7110.65 and local procedures, which resulted in a runway incursion.[1]

After the incident, the Boston tower changed its procedures so that only the west local controller may initiate a departure on the crossing Runway 15R, and that once the east controller accepts the release, the aircraft must be cleared for takeoff within five seconds. Further, to reduce the chance of this type of incident happening again, aircraft must not be held on Runway 9 waiting for their takeoff clearance while there is a departure on 15R. Once the departure has cleared the intersection, local west must inform the east controller that the intersection has been cleared.[1]

See also

References

  1. ^ a b c d e "Aviation Incident Final Report". National Transportation Safety Board. May 29, 2007. NYC05IA095A. Archived from the original on September 21, 2018. Retrieved August 12, 2020.
  2. ^ a b "Alpa release". Archived from the original on September 28, 2007.

External links