1. Incident

2. Superior Airmanship Award

3. Probable cause

4. See also

5. References

6. External links

The 2005 Logan Airport runway incursion was a near runway collision that occurred at approximately 7:40 p.m. Eastern Daylight Time 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 aircraft owned by Wells Fargo Bank Northwest NA and operated by US Airways, destined for Philadelphia, Pennsylvania, and carrying 6 crew members and 103 passengers. The near collision took place on the runway at General Edward Lawrence Logan International Airport (BOS), in Boston, Massachusetts. In total 381 people were on board the two aircraft.

Incident

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 that evening when each of the incident flights were the responsibility of 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 take-off roll, the US Airways first officer noticed the other plane and realized that they could collide. He realized that at the runway intersection both aircraft would be slightly airborne. Telling the Captain to "keep it down", he pushed the control column forward. He was able to keep the aircraft from lifting off the runway, allowing it to reach the intersection and pass under the other aircraft as it took off. The two planes passed within an estimated {{convert|70|ft|m}} of each other, with the Aer Lingus aircraft flying over the US Airways aircraft. According to the NTSB report, the US Airways flight had already achieved its V₁ 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][1]

Superior Airmanship Award

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 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.^[2]

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 controllers 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.^[2]

See also

• List of accidents and incidents involving commercial aircraft

References

External links

• Photos of the US Airways jet
• Photos of the Aer Lingus jet
• [https://www.youtube.com/watch?v=SxRedCK_lWw CGI rendering of the incident as prepared by the NTSB]

• Kilkhor
• Kil, Kil
• Kilkilieh
• Kilkim zaibu
• Kilkim Zaibu
• Kilkim Žaibu
• Kilkim žaibu
• Kilkis
• Kilkis Archaeological Museum
• Kilkis (city), Greece
• Kilkishen
• Kilkis (prefecture)
• Kilkis Prefecture
• Kilkis Province
• Kilkivan
• Kilkivan Shire
• Kilkivan Shire Council
• Kilkov
• Kilksama
• Kill 2 This
• Killacycle
• Killadeas – Seskinore Fault
• Killadelphia (disambiguation)
• Kill a god
• Killah