Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Pilot Mistakenly Lands At Ellsworth

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

sqwkvfr

Baseball junkie
Joined
Dec 20, 2003
Posts
1,673
06/20/2004
Pilot Mistakenly Lands At Ellsworth
A Northwest Airlines plane landed at Ellsworth Air Force Base yesterday after the pilot apparently confused it for Rapid City Regional Airport.

Since the base controls the airspace, Ellsworth officials knew the plane was in the area and prepared for a landing.

Once the plane was on the ground, the 117 passengers and five crew members waited for three hours before they could take off and land on the correct airstrip.
© 2004 Associated Press.


From the St. Paul Pioneer Press:

NORTHWEST FLIGHT ENDS UP AT AIR BASE

Passengers told not to peek as route originating in Twin Cities misses it's mark.

Robert Morrell's Northwest Airlines flight was only two minutes late Saturday departing the Twin Cities for Rapid City, S.D.

The Airbus 319 with Morrell and 116 other passengers on board didn't make up the time, but they did land within five minutes of its scheduled arrival.

But one glance out the window and Morrell wondered whether something was wrong. He saw barracks-like structures and military officials.

When none of the crew got on the intercom to welcome everyone to Rapid City, he figured something was up. When he and the other passengers were asked to pull down their window shades, he knew all was not right.

Northwest Airlines flight 1152 was sitting on the runway of Ellsworth Air Force Base, five miles and "just over the hill" from its intended destination of Rapid City Regional Airport.

After about five minutes, a voice from the cockpit broke the news to the passengers.

"He (the pilot) hemmed and he hawed and he said, 'We have landed at an Air Force base a few miles from the Rapid City airport and now we are going to figure out how we're going to get from here to there,' " Morrell said.

The figuring-out part stretched past three hours as passengers waited in the nearly full plane. During that time, military officials questioned the crew. Eventually, the captain and first officer were replaced by a different Northwest crew, which flew the passengers over the hill to the regional airport.

Northwest released little information about the incident, confirming only that the crew made an "unscheduled landing" at the military base at 12:15 p.m., Mountain Time.

"The situation is under review and we have nothing further to add," said Northwest spokesman Kurt Ebenhoch. "We're not acknowledging it was pilot error."

Morrell, a physician from Raleigh, N.C., interviewed on his cell phone during the delay, offered the consensus opinion of the passengers:

"Everyone is surmising it was pilot error. The presumption is that the pilot just landed at the wrong **CENSORED****CENSORED****CENSORED****CENSORED** airport."

Passengers were allowed to use cell phones and the lavatories but were told to draw their window shades for security purposes, Morrell explained. After the new crew came aboard, the airliner made the short flight to Rapid City, landing at 3:45 p.m., Mountain Time, three hours and 42 minutes late.

Ellsworth controls all airplanes in airspace 40 miles around the base and clears flights to land at the Rapid City airport and the base. Ellsworth confirmed with Rapid City airport officials that the Northwest plane was authorized in the airspace. The pilot was using what is called an instrument landing, according to a spokeswoman for Ellsworth. The pilot was using visual guides as well, she said.

"He was looking toward an airfield, saw one and thought it was the other," said Lt. Christine Millette. "As far as we knew, they were on track, and then they weren't."

Asked where the regional airport runway was in relation to the air base runway, Millette said, "Just over the hill."

Details about how the pilot veered off course were sketchy. It also was unclear why the crew relied on visual guides during an instrument landing. Instrument-guided approaches align a plane horizontally and vertically to the airstrip's runway and give precise guidance to an airport, said Hal Myers, a Northwest pilot and spokesman for the airline pilots union.

"If it was an instrument approach, it seems like a small likelihood you would end up at the wrong airport," Myers said.

A plane flying low as it approaches landing drops off radar. The Northwest jet was flying off radar, making its approach when the crew briefly spotted what they thought was Rapid City's airstrip. Then the plane went into the clouds, Millette said.

"So as they were coming out of the clouds, they were just about to land and they realized they were at the wrong airstrip," she said. "They said (to air controllers), 'Hey, we are landing' and within seconds they were on our airstrip."

Northwest would not discuss those details.

"We cannot confirm what they are saying and they don't speak for Northwest Airlines," Ebenhoch said.

He also declined to:

• Identify the pilots.

• Specify how long they'd been flying on Saturday.

• Specify their experience level or whether they'd ever landed at Rapid City.

• Say whether the pilots were suspended.

"We apologize to the customers for any inconvenience," he said, explaining that the passengers will receive roundtrip tickets to the destination of their choice within the lower 48 states.

The Federal Aviation Administration was contacted and is investigating, Millette said. Civilian airplanes occasionally make emergency landings at Ellsworth, she said. The last time was in March when an American Airlines jet landed at the base with mechanical difficulties.
 
Last edited:
Flame away if you wish (and will), but with all of the electronics we have at our disposal these days; ie FMS, GPS, ILS, VOR, LORAN....you name it; there just is not a good excuse. Wrong approach plate? Sure, the runways are the same direction (even if RCA is missing one with facilities on the opposite side of the field) buts it's a 319.....last I looked they had all the goodies including 2 FMSs.

We'll all make mistakes but the dumb ones like this just keep adding fuel to the media fire....
 
Sucks to be that crew, but it's understandable to a degree. Bigger runway, closer to town, on the east side of the city - the direction from which they were approaching. The Ellsworth Approach controllers are military, and are less than no help. Some of the poorest service I've ever received has been flying into RAP. I offer this broken english, 3rd grade reading level quote as evidence:

"He was looking toward an airfield, saw one and thought it was the other," said Lt. Christine Millette. "As far as we knew, they were on track, and then they weren't." "So as they were coming out of the clouds, they were just about to land and they realized they were at the wrong airstrip," she said. "They said (to air controllers), 'Hey, we are landing' and within seconds they were on our airstrip."


KRAP 191752Z 17009KT 10SM OVC021 11/06 A3030 RMK AO2 SLP268
 
Cardinal said:
Sucks to be that crew, but it's understandable to a degree. Bigger runway, closer to town, on the east side of the city - the direction from which they were approaching. The Ellsworth Approach controllers are military, and are less than no help. Some of the poorest service I've ever received has been flying into RAP. I offer this broken english, 3rd grade reading level quote as evidence:



KRAP 191752Z 17009KT 10SM OVC021 11/06 A3030 RMK AO2 SLP268

It looks pretty clear what happened, they broke out of the 2000 overcast right as they leveled at the min altitude for starting the approach, they saw a 2 mile long runway lined up with they final approach course and made the mistake of not checking the DME.
 
The report says nothing with the two airports being 'in line' with one another. Why, breaking out on the final approach course, would they choose the wrong airport? Were they actually aligned on final, and what if the clouds were lower than 2 grand? Were they even on altitude if they were possibly not on course?


I would have been pissed if I was a pax on that plane. Lack of professionalism in the cockpit. That is my guess.
 
I posted the link to the approach chart above, click on SD and RAP than click the VOR 14 and you'll see that there is a 14,000' runway lined up with their final approach course 5 miles from their destination airport.

You can also click on the ILS 13 into Ellsworth and check it out.

I would've been upset too, a crewed airplane shouldn't make that mistake, but I cannot say that I have not made mistakes before, including one where I almost landed at the wrong field.

What I've learned from this is to brief the approach better, learn the difference between an 8700' runway and a 13,500' runway, what type of approach lights should I have when I break out, I don't know Ellsworth had the lights on for runway 13, but if they did they were ALSF-1, Rapid City 14 doesn't have approach lights.
 
Last edited:
The two airports are aligned on final, but Ellsworth is clearly depicted on the plan view, doesn't have a cross runway and both are depicted on the airways chart. Landing at the wrong airport here is easy if you haven't done a proper approach brief and looked at the plan view, the field diagram or airways chart. I had an experience at Myrtle Beach one time, where I identified the possiblity of confusing airports while we were flight planning. We were careful as hell to make sure we were landing at the right airport. Too bad approach control handed us off to the wrong tower while we were on final to the correct airport. That one got interesting as we couldn't find the tow plane the tower kept calling out as on the runway midfield. Didn't land and finally got on the right freq and it worked out okay, but even the best laid plans...
 
same deal at Key West

one time I almost landed at Key West NAS instead of Key West civilian airport. Any lower and the follow-me truck would have been waiting for me.

fortunately, Approach control was cool and things worked out, but a close call
 
I was waiting for my new 10 day instrument student on a nice sunny sunday, while I chatted with the CFI and line guy of the FBO. It was going to be an easy day. Help get her plane fueled and tied down, introduce myself, hand her her books, get her hooked up with her rental car, and get her headed with directions to the hotel...oh, and collect the "CHECK".

As we were waiting, I heard her call out for advisories, 10 miles, 5 miles, entering midfield down wind, base and then final. I continued to chat with the FBO staff at the front desk for what seemed only moments, but turned out to be better than 20 minutes...when all the sudden we realized we never saw my student taxi up in her warrior. As we were begining to wonder what happened, the phone rang. The FBO line guy hands me the phone and says it's Major So and So from the Beaufort Marine Corps Air Station...

They never even saw her till she was on short final and landing at the Marine base. It must have been a funny feeling, seeing the pointy end of a bunch of M-16's.
 
I wonder if the tower guys in KRAP would agree completely with this:




"Ellsworth controls all airplanes in airspace 40 miles around the base and clears flights to land at the Rapid City airport and the base. "


AF :cool:
 
I came awful close to making the same mistake my first trip up there (of course, no media would be interested in a cargo plane landing at Ellsworth by mistake)...and I was even warned about it beforehand. Remember folks, if you call the airport in sight and there are orange-tint buildings surrounding it, that's the AFB, not RAP!
 
Hyper, your avatar is great, tell me you were on the approach?
 
I know Lt Christine (Chris) Millette (the PAO at Ellsworth). I'll have to drop her an e-mail and give her a hard time. :D
 
A DC9 crew with steam-driven avionics, I could almost accept this - but an instrument rated crew, in an A319 with all the bells and whistles - how in the he11?

The same thing should happen to this NW crew that happened to the NW DC10 crew a few years back - landed at Brussels thinking it was Frankfurt. Funny thing was the passengers all knew they were landing at BRU due to the moving map displays in the passenger cabin. F/As thought they had a mechanical issue that required landing at BRU. Everyone but the three crew members up front (who were allegedly navigating) knew they were landing at the wrong airport.

BRU and FRAs runways are aligned the same, but at FRA, the runways are blacktop - BRU they are concrete.

The pilots were terminated; the F/E had to do recurrent (I think, my memory is a bit fuzzy - been a while back, 1995 I think)
 
RideTheWind said:
Looks like an easy mistake to make if you're new to that approach and didn't brief it well.
Perhaps they took to heart the advice offered on this forum not too many weeks ago about how to brief an approach - - my landing, questions?

OUCH :o
 
LR25, thanks. Yea, the ILS6 @ TEB. My last run as a freight dog for Airnet and I just thought I needed something to remind me of all the "good" times I had. ;)


If you look close, you can just see the approach lights coming into view.
 

Latest resources

Back
Top