Delta B767-300 lands on taxiway in Atlanta . . .

No problem. I just can’t help but recall the disaster at Tenerife, which was the conclusion of a chain of small errors which culminated in the large error of the KLM Capt. taking off without clearance.

All it takes is one aircraft not following directions and winding up where no one expects it.

Really.

In events such as this I always think of a 1987 Delta flight from Louisville (SDF) to Lexington, KY (LEX) that landed "seventeen NM from their destination when the crew touched down in a 737 at Frankfort, KY (FFT). I never heard what became of that crew.

October 21, 2009


NTSB INVESTIGATING LANDING OF COMMERCIAL JETLINER ON TAXIWAY

IN ATLANTA


The National Transportation Safety Board is investigating

the landing of a Delta B-767 on an active taxiway at Atlanta

Hartsfield International Airport (ATL).

According to preliminary information received from several

sources, on Monday, October 19, 2009, at 6:05 a.m. EDT, a

Boeing B767-332ER (N185DN) operating as Delta Air Lines

flight 60 from Rio de Janeiro to Atlanta landed on taxiway M

at ATL after being cleared to land on runway 27R. No

injuries to any of the 182 passengers or 11 crewmembers were

reported.

A check airman was on the flight deck along with the captain

and first officer. During cruise flight, the check airman

became ill and was relocated to the cabin for the remainder

of the flight. A medical emergency was declared and the

company was notified by the crew. A determination was made

to land at the scheduled destination of ATL.

The flight was cleared to land on runway 27R but instead

landed on taxiway M, which is situated immediately to the

north and parallel to runway 27R. The runway lights for 27R

were illuminated; the localizer and approach lights for 27R

were not turned on. Taxiway M was active but was clear of

aircraft and ground vehicles at the time the aircraft

landed. The wind was calm with 10 miles visibility.

Night/dark conditions prevailed; twilight conditions began

at about 7:20 a.m. EDT and the official sunrise was at 7:46

a.m. EDT.

A team of four from the NTSB, led by David Helson, is

investigating the incident.

Thanks for the info. :smiley: Can somebody tell me exactly what the localizer does?

The LOC was not turned on, that says a ton

Will- here I’ll do the work for ya again
http://en.wikipedia.org/wiki/Localizer

Seems like a wonder that the World’s Busiest airport wouldn’t have any ground movement on that taxiway, especially at that hour of the morning.

en.wikipedia.org/wiki/Localizer

In short, it lines you up with the runway.

Thanks ya’ll. I try looking up stuff like that and I never find it. :unamused:

This is all I’m gonna say then I will shut-up. People, that is how God works!

Bookmark this:

www.google.com

Boy, maybe the FAA should think about making runways appear different than taxiways, like painting great big numbers on them, or perhaps puttting great big white stripes on either side of the centerline that serve as touchdown aiming points. Makes you wonder if this was the Captain’s first OE flight in the airplane after sim training?

I do use google.

Yeah, that sounds like a good idea. But they should do something to make them stand out at night, too. Maybe they could use dim, blue lights for taxiways, and bright white lights that are visible for miles for the runway.

I don’t remember where I heard this, but some guy came up with a fantastic business model. It’d be just like a video rental store, only for books…

In seriousness, this incident reminds me of a NWA plane that landed at the AFB in fargo instead of at the fargo airport. Passengers were instructed to close their window shades so they wouldn’t see anything classified until they could bus over a new crew to fly them to the airport.

Yes, By the GRACE of God, disaster was adverted. 5 Minutes ealier or later, the outcome may have been different. Between 5 am and 7 am, KATL operations are mainly arrivals. The Internationals between 5 and 630am. There are a lot of them. It’s not uncommon to have 4 B777, 6 B767, and a B747 moving about the airport around 6 am. I hope that the Pilot is able to keep his job, although it was a horrible mistake with the best possible outcome. I am sure he realized his error just prior to touchdown. The taxiway was clear and medical emergency was onboard. Someone made a comment about the localizer. The loc for 27R was off, and so was the approach lights. The advertised arrival runways were 27L and 26R. The pilot was lined up for 27L and was offered 27R. AT 4 miles he side-stepped over to Taxiway Mike. I really want to know what happened and maybe pilots and controllers can learn from it. :slight_smile:

Undercover01 Thanks for that-

the approach light were off also?
I can see how this can happen now.
There were a cascade of events that lead to this (like there always is) Medical, LOC turned off, the side step 4 miles out, no approach lights. This crew might live to fight another day.

Has anyone found the live ATC feed from this?

The more I learn about this, the less outrageous it seems.

From an airport operations point of view, what do you have to do to switch on LOC and approach lights for a runway? Is it just punching a button or flipping a switch in the tower, or is it more complicated than that? How long would it have taken ATC to switch on the lights after giving him clearance to land 27R?

Very close, in both aspects.

The NWA flight in question landed at KCRA instead of its destination, KRAP. a friend of mine was on that flight, and had some stories to tell after he got off the plane.

BL.

LiveATC.net doesn’t have an ATL feed. Anybody know of any others?

Still looking. Been en route to MMU so I’ve been offline.

Yeah, that sounds right. But you mean KRCA, Ellsworth AFB, not KCRA.