A Delta Airlines B767 that had just begun its takeoff roll had to abort after a controller mistakenly cleared two other aircraft to taxi across the runway into the path of the departing aircraft. The Delta flight aborted the takeoff, turned onto a taxiway and rejoined the line-up for its departure to Los Angeles.
The incident happened at Atlanta's Hartsfield-Jackson International Airport. This was the second aborted takeoff due to controller error at that airport in three months.
Here is an account of what happened, as reported by the Atlanta Journal-Constitution:
The controller cleared Delta 509 at about 12:10 p.m. to take off on Runway 26 Left, which is about 10,000 feet long. Fourteen seconds later, the same controller cleared a Midwest Airlines Boeing 717 and an ASA CRJ to taxi across the runway downfield.Gary Brittain, a veteran controller at Hartsfield-Jackson, said mistakes are being made at the Atlanta tower because controllers are being short-staffed and overworked.
The Midwest jet had moved onto the runway and the ASA plane had crossed the "hold short" line that separates the taxiway from the runway when alarms in the control tower alerted air traffic controllers of the danger. The controller cancelled Delta Flight 509's takeoff while the plane was traveling about 40 miles an hour, then slowed and turned off the runway. It got back in line for takeoff and left uneventfully a few minutes later.
The Delta and Midwest planes were about 3,500 feet apart at their nearest point.
"This is the kind of thing that happens when you've got controllers working six-day weeks, week after week," he said. "They're beginning to crack a little."
The controller who reportedly caused the incident was decertified, subject to retraining.
[Photo Source]
4 comments:
I was on flight 509 headed to Los Angeles at 12:10 PM on Friday, March 2. Actually we were traveling much faster and our front wheels had lifted off the ground in lieu of our approaching take off. We felt a violent slam into the runway and then taxied to the nearest gate. We did not take off a few minutes later...it was actually over an hour and 30 minutes because the brakes had to cool after our violent slam to the runway. I am glad the controller is receiving more training and you all should create a more efficient schedule and appreciation for your workers so that they are not stressed and more likely to create dangerous situations. Please do not let this happen again! Thank you!
I've got to raise the flag on your comment. If in fact the front wheel was off the ground, chances are the flight crew was committed to the takeoff and would not abort for any reason. Second, you can thank our government for the understaffing overworking conditions at any government regulated agency. Unless, of course, you're a senator, congressman, president, VP, etc.
I have to second that flag. Standard procedure for a B767 says that the aircraft is committed to takeoff after reaching takeoff speed (which occurs at or before nose-wheel lifts off). At this point, it would have been more dangerous to abort and the pilot never would have done so.
I have to third a flag on that comment.. V1 speed- Look it up. Although, your version is much more interesting than the truth. Its just human nature to exaggerate beyond belief for effect.
Post a Comment