2005 Logan Airport runway incursion

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2005 Logan Airport runway incursion
Incident summary
Date June 9, 2005 (2005-06-09)
Summary ATC error, near miss
Site Logan International Airport
Boston, Massachusetts, USA
Lua error in package.lua at line 80: module 'strict' not found.
Total injuries (non-fatal) 0
Total fatalities 0
Total survivors 381 (all)
First aircraft
180px
The Aer Lingus Airbus A330 involved in the incident.
Type Airbus A330-301
Name St Maeve
Operator Aer Lingus
Registration EI-ORD
Destination Shannon Airport
Shannon, Ireland
Passengers 260
Crew 12
Injuries (non-fatal) 0
Fatalities 0
Survivors 272 (all)
Second aircraft
180px
A US Airways Boeing 737-300 similar to the one involved.
Type Boeing 737-3B7
Operator US Airways
Registration N394US
Destination Philadelphia Int'l Airport
Philadelphia, Pennsylvania
Passengers 103
Crew 6
Injuries (non-fatal) 0
Fatalities 0
Survivors 109 (all)

The 2005 Logan Airport runway incursion was a near runway collision that occurred at approximately 7:40 p.m. Eastern Daylight Time on 9 June 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

File:BOS airfield map.png
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 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 70 feet (21 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 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

US Airways Captain Henry Jones and First Officer Jim Dannahower were later awarded a Superior Airmanship Award from the 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 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 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.[1]

See also

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 NTSB final report Final Report from NTSB
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=2005_Logan_Airport_runway_incursion&oldid=1469206"