Jump to content

Continental Airlines Flight 1883

From Wikipedia, the free encyclopedia

Continental Airlines Flight 1883
N17105, the aircraft involved in the incident
Incident
DateOctober 28, 2006 (2006-10-28)
SummaryTaxiway landing due to runway identification error[1]
SiteNewark Liberty International Airport, Newark, New Jersey, United States
Aircraft
Aircraft typeBoeing 757-224
OperatorContinental Airlines
RegistrationN17105
Flight originOrlando International Airport
DestinationNewark Liberty International Airport
Occupants154
Passengers148
Crew6
Fatalities0
Injuries0
Survivors154

Continental Airlines Flight 1883 was a Boeing 757 that mistakenly landed on a taxiway at Newark Liberty International Airport on the evening of October 28, 2006. There were no reported injuries or damage, but the narrowly averted disaster was investigated by the National Transportation Safety Board, and caused the Federal Aviation Administration to reevaluate and modify air and ground safety procedures at and around Newark Airport.[1][2][3]

Aircraft and flight information

[edit]

Continental Airlines Flight 1883 was a regularly scheduled domestic passenger flight to Newark from Orlando International Airport in Orlando, Florida. On October 28, 2006, the flight was operated using a Boeing 757-224, a narrow-body twin-engine jet airliner (registration number N17105). Flight 1883 had 148 passengers and 6 crew on board.[4]

The first officer was flying the aircraft for the approach to Newark; it was his first time landing at Newark on runway 29.[5]

Incident

[edit]

Flight 1883 approached Newark from the north, initially planning to land on runway 22L using an ILS instrument approach. As the flight descended to an altitude of about 8,000–9,000 feet (2,400–2,700 m), air traffic controllers instructed Flight 1883 to circle to land on runway 29. This required descending toward runway 22L, followed by a low altitude circling maneuver that required a right turn at only 900 feet (270 m) to line up for runway 29.[5]

As the flight crew descended and turned toward the airport, they observed four white path indicator lights, which they believed were located to the left of the runway. This was incorrect; the instrument procedures for Newark described these indicator lights as being to the right of the runway.[5] Keeping the indicator lights to their left, the pilots landed on 75 feet (23 m) wide taxiway Z at 18:31 EDT. The Boeing 757 jetliner, with a wingspan of 124 feet (38 m), touched down at 130 knots (150 mph; 240 km/h) near the intersection of taxiways Z and R, rolled out and came to a stop without incident. The aircraft then taxied to the gate where all passengers were deplaned.[4] According to the FAA, all lighting systems associated with runway 29 and taxiway Z were operating normally at the time. Runway 29, the intended landing runway, is 150 feet (46 m) wide and 6,800 feet (2,100 m) long.[2][6]

Investigation

[edit]
Section of KEWR taxiway diagram with red dot depicting approx. location of touchdown - landing roll was westbound on Z, leftward from red dot

The incident was investigated by the National Transportation Safety Board (NTSB).[1]

As part of its investigation, the NTSB conducted a flight around the airport, to evaluate the lighting and visibility of the runways and taxiways. With the lighting of runway 29 and the taxiway set to the same brightness levels used during the incident, the NTSB noted that the lights for taxiway Z appeared slightly brighter than the lights for runway 29. During testing, however, the difference in lighting color (green centerline lights used on Z to indicate a taxiway, white centerline lights used on 29 to indicate a runway) was clearly visible to planes on approach.[4]

In its final report, the NTSB described the probable cause of the incident as:[5]

The flight crew's misidentification of the parallel taxiway as the active runway, resulting in the flight crew executing a landing on the taxiway. Contributing was the night lighting conditions.

Aftermath

[edit]
N17105 in service with United Airlines (2014)

This rare event caused a reassessment of differential runway and taxiway lighting, as well as arrival procedures at Newark airport.[2][7] The NTSB noted in its report that as a result of the incident, the FAA instituted two types of changes in its procedures, in the air and on the ground, to reduce the chance of a recurrence.[1][4] In the air, the FAA added two new arrival procedures, GIMEE 19-7-1 and GRITY 19-7-1A, which it expects will provide improved navigational guidance to the runway under similar conditions. On the ground, the FAA and airport officials increased the difference between the lighting intensities of taxiways and runways, to enable pilots to better differentiate between them under low light conditions.[5][6]

Both pilots were grounded by the airline after the incident but were returned to duty after retraining.[2][6]

See also

[edit]

References

[edit]
  1. ^ a b c d "NTSB Identification: NYC07IA015". National Transportation Safety Board. NYC07IA015. Archived from the original on October 17, 2016. Retrieved September 11, 2016.
  2. ^ a b c d Porter, David (November 2, 2006). "Plane landing on Newark airport's taxiway a rare occurrence". Associated Press.
  3. ^ "Airline Pilot in Blunderland". New York Post. October 31, 2006.[permanent dead link]
  4. ^ a b c d "NYC07IA015: Full Narrative". National Transportation Safety Board. Retrieved September 11, 2016.
  5. ^ a b c d e Kaminski-Morrow, David (April 4, 2008). "Continental 757 crew misidentified lights before taxiway landing". FlightGlobal. Retrieved September 11, 2016.
  6. ^ a b c "Lighting a factor in Newark taxiway landing". Associated Press. April 1, 2008. Retrieved September 11, 2016.
  7. ^ Porter, David (November 4, 2006). "Runway errors spur call for tech upgrades". Associated Press.
[edit]
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy