Globaliser

Indeed, we should wait to find out whether this allegation is even true. In another PPlace, it's been unequivocally said that the tech crew did report this to ATC.

TWA Fan 1

Just look at the quality of the inofrmation that was made available in the first minutes after this incident occured. One story referred to the "LH 767" and then later in the story the same a/c was referred to as the "LH 747"

I would be floored if the flight deck crew didn't report the incident. That would be unheard of unless they were planning to never work as pilots again.

It may turn out, instead, that a wind incident forced them off course at the last moment and that the fact that they landed on the taxiway without incident (which requires great skill) averted a horrific tragedy.

HobokenFlyer

I am scheduled on CO 1883 from MCO-EWR next Monday (11/6) AAAAIIIGGGHHHH!!!!!! (just kidding)

- HF

USA_flyer

I hate getting these things wrong (it has been known ) but I think this unlikely. In the event of a crosswind that managed to blow a 757 off course a go-around would have been the expected proccedure. Also, if there were heavy crosswinds, why weren't they using the main parallels?

I can't wait to see how the number the ORD runways once they're all parallel.

TWA Fan 1

My understanding is that the cross winds were primarily affecting the main parallels (I could be wrong). But, as you know, wind can shift. So it's not inconcievable that there was a last-second "wind shear" type incident that forced the plane off course. I agree that a go around would seem to be logical, but we, of course, don't have all the facts.

What is clear, is that it was very, very windy, with gusts well over 50 mph, making a pure visual landing pretty challenging at dusk.

Xyzzy

You are correct. If they were not, 29 wouldn't have been used for that flight.

cruisr

Why not use the car/truck lanes of the NJTurnpike....or Rte 1/9

AustinWeatherGuy

Wed / 01 Nov 315pm CT

All:

This just arrived from the NTSB just a minute ago.
Thought you'd like to read:

National Transportation Safety Board
Washington, DC 20594

November 1, 2006

************************************************** **********

NTSB INVESTIGATING THREE RECENT AIRLINER INCIDENTS

************************************************** **********

National Transportation Safety Board Chairman Mark V.
Rosenker has assigned investigators to look into three
recent incidents involving airliners, two at Newark Liberty
International Airport and another in Seattle.

Newark Liberty International Airport, October 28

On Saturday evening, October 28, Continental Airlines
flight 1883, a Boeing 757 arriving from Orlando, Florida,
landed on taxiway Zulu rather than runway 29, which
parallel's the taxiway, following a circle-to-land
instrument approach. There were no injuries to the 152
persons aboard nor damage to the aircraft. Jill Andrews
from the Board's Parsippany, New Jersey regional office is
the Investigator-in-Charge of this incident. The NTSB
identification number for this incident is NYC07IA015.

Seattle-Tacoma International Airport, October 30

On Monday morning, October 30, Alaska Airlines flight
61, a Boeing 737, took off from runway 34 right, instead of
the assigned runway 34 center, at the Seattle-Tacoma
International Airport. There were no injuries or damage,
and the flight continued uneventfully to Juneau, Alaska.
Joseph Sedor from the NTSB's Major Investigations Division
has been assigned as Investigator-in-Charge. The NTSB
identification number for this incident is DCA07IA008.

Newark Liberty International Airport, October 31

On Tuesday evening, October 31, the left wingtip of
Lufthansa flight 403, a Boeing 747 that was taxiing for
takeoff, struck the right wingtip of a Continental Airlines
757 that was being towed. There were 313 persons aboard the
Lufthansa aircraft; there were no passengers aboard the 757.
No injuries were reported and minor damage was noted on the
747's wingtip. Paul Cox from the NTSB's Ashburn, Virginia
regional office has been assigned as Investigator-in-Charge.
The NTSB identification number for this incident
investigation is NYC07IA017.

Preliminary reports for all of these incidents will be
available shortly on the Board's website at www.ntsb.gov.
Investigators will interview crewmembers, obtain air traffic
control data, and analyze information from flight recorders
from all of these incidents.

- 30 -

Bernoulli 777

Facts are always better than conjecture, though sometimes less spectacular and entertaining!

B7

VideoPaul

WOW. Is he now known as "Forrest GUMPS"??

--PP

theblakefish

Hmmmm...with all of the congestion and delays at EWR, and now this incident, I think that the PANYNJ would be smart to consider upgrading the equipment on RWY 11/29.

C'mon PA, why did it take an event such as this for you guys to realize the obvoious????

I'mOffOne

Not so easy. Aircraft do the circle to 29 instead of a straight-in because there isn't enough room. The extended final of 29 would get very close to Lower Manhattan, so there isn't enough room out there for an instrument approach. EWR is in too confined of an area to permit much (or any) expansion of the airport or approaches.

TWA Fan 1

Exactly. There are a couple of other issues with Rwy 11/29. At 6,800 ft it's really just a little too short to be used for transcon, TATL or any long-haul heavies.

Also, since Rwy 29 abuts the NJ Turnpike, a rail line and a dockyard, there is no place for any ALS which is really a necessary part of any complete ILS/DME system.

You've mentioned the airspace issues, but Rwy 29 could be used more commonly even with the circle approach. However, without any ILS, this runway will never be heavily used in a context like EWR where the heavy traffic volume requires ILS landings because of the close spacing between a/c.

IIRC, there had been talk a few years ago of building a third runway 4/22, but this also ran into real estate issues.

One thing to keep in mind, though, is that both runways 4/22 are excellent, very long, and have all the latest state-of-the-art instrumentation available.

ewrfox

Not sure if this has been posted before, but according to local reports the NTSB has decided to get into the investigation, because the Cockpit voice recorder was intentionally erased�

TWA Fan 1

First, the NTSB is involved because of the incident itself, irrespective of the CVR issue.

Second, that's very interesting information about the CVR being intentionally erased. I'm wondering where that information came from.