JetBlue Airways Flight 292
As N536JB's front wheels touched down, their tires were torn off, leaving sparks shooting from the wheels' metal rims as they scraped along the asphalt. |
|
| Incident summary | |
|---|---|
| Date | September 21, 2005 |
| Summary | Undercarriage malfunction |
| Site | Los Angeles, California |
| Passengers | 140 |
| Crew | 6 |
| Survivors | 146 (all) |
| Aircraft type | Airbus A320-232 |
| Aircraft name | Canyon Blue |
| Operator | JetBlue Airways |
| Registration | N536JB |
| Flight origin | Bob Hope Airport, Burbank, California |
| Destination | John F. Kennedy Int'l Airport, New York City |
JetBlue Airways Flight 292 was a scheduled flight from Bob Hope Airport (BUR) in Burbank, California to John F. Kennedy International Airport (JFK) in New York City. On September 21, 2005, flight 292 executed an emergency landing at Los Angeles International Airport (LAX) after the nose wheels jammed in an abnormal position. No one was injured.
Contents |
September 21, 2005 flight [edit]
Carrying 140 passengers and six crew, the Airbus A320-232 aircraft departed from Burbank at 3:17 pm PDT (UTC-7). The aircraft, which was built in 2002,[1] bore the tail number N536JB and the name "Canyon Blue". It was scheduled to fly 2,465 miles (3,967 km) to JFK airport.
After takeoff from Burbank, the pilots realized that they could not retract the landing gear. They then flew low over Long Beach Municipal Airport (LGB) in Long Beach (the location of a JetBlue hub) to allow officials in the airport's control tower to take stock of the damage to its landing gear before attempting a landing. It was found that the nosewheel was rotated ninety degrees to the left, perpendicular to the direction of the fuselage.
Rather than land at Long Beach Airport, the pilot-in-command made the decision that the aircraft would land at Los Angeles International Airport (LAX), in order to take advantage of its long, wide runways and modern safety equipment.
The pilots flew the aircraft, which can carry up to 46,860 pounds (21,255 kg) of aviation fuel, in a figure eight pattern between Bob Hope Airport in Burbank and LAX for more than two hours in order to burn fuel and lower the risk of fire upon landing. This also served to lighten the plane, reducing potential stress on the landing gear and dramatically lowering landing speed as well.[2][3] The Airbus A320 does not have the mechanical facility to dump fuel,[4] despite various news agencies reporting that the aircraft was doing so over the ocean.
Because JetBlue planes are equipped with DirecTV satellite television, passengers on Flight 292 were able to watch live news coverage of their flight while the plane circled over the Pacific for hours. The in-flight video system was turned off "well before landing".[5]
Emergency services and fire engines were standing by on the LAX tarmac ahead of the landing. Although foam trucks were available, they were not used. The U.S. FAA no longer recommends pre-foaming runways, chiefly due to concerns that it would deplete firefighting foam supplies which might later be needed to respond to a fire; it is also difficult to determine exactly where a runway should be foamed, and pre-foaming might also reduce the effectiveness of the aircraft's brakes, potentially causing it to slide off the runway.[6]
Los Angeles Fire Dept. Battalion Chief Lou Roupoli said, "The pilot did an outstanding job. He kept the plane on its rear tires as long as he could before he brought [the nose gear down]."[7] When the nose gear did touch down, there were sparks and flames from it, but no apparent damage to the rest of the plane. At 6:20pm PDT (UTC-7), the aircraft came to a stop very close to the end of the 11,096-foot (3382-meter) runway 25L. In an attempt to keep the nose gear off the ground as long as possible, reverse thrust was not used to slow the aircraft. The pilots therefore used a much larger portion of the available runway than in a typical landing, stopping 1,000 feet / 305 m before the end of the runway, validating the decision to divert from Long Beach, where the longest runway is 10,000 feet (3048 m).[citation needed]
Aftermath and evaluation [edit]
Passengers began to disembark less than seven minutes later. The landing was smooth and no physical injuries were reported. The aircraft was evacuated via airstairs, as opposed to Evacuation Slides typically used in an emergency situation.
As JetBlue did not operate from LAX at the time, the aircraft was towed to a Continental Airlines hangar at LAX for evaluation.[8]
Expert opinion expressed was that, despite the drama and live worldwide coverage, there was little real danger to the passengers or crew of Flight 292.[9] The A320, like all modern airliners, is engineered to tolerate certain failures, and if necessary can be landed without the nose gear at all.[9]
A similar incident with an A320 occurred on an America West Airlines flight in February 1999 in Columbus, Ohio (Flight 2811).[10] The NTSB found the cause was a failure of the external o-rings in the nose landing gear steering module."[3] That plane also landed safely.
The media reported that this was at least the seventh occurrence of an Airbus A320 series aircraft touching down with the landing gear locked ninety degrees out of position, and one of at least sixty-seven "nose wheel failures" on A319, A320 and A321 aircraft worldwide since 1989. Earlier incidents included another JetBlue flight bound for New York City, a United Airlines flight into Chicago, and the America West flight into Columbus, Ohio. While some incidents were traced to faulty maintenance and denied as a design flaw by Airbus Industrie, the manufacturer had issued maintenance advisories to A320 owners which were later mandated as Airworthiness Directives by American and French aviation authorities.[11] Messier-Dowty, which manufactures nose gear assemblies for the A320, stated in a National Transportation Safety Board (NTSB) report in 2004 that part of the gear had been redesigned to prevent future problems, but at the time the redesign was awaiting approval.[12] Mechanics familiar with this common fault usually replace or re-program the Brake Steering Control Unit (BSCU) computer.
The NTSB report says that worn-out seals were to blame for the malfunction. Also the brake steering control unit system contributed to the problem. Airbus claims to have fixed the problem in an upgrade.[13]
Following the incident, the aircraft was repaired and returned to service still bearing the name "Canyon Blue." JetBlue no longer uses Flight 292 on its Burbank-JFK route; the flight route designation for JetBlue's flights between Burbank and New York are now Flights 350 and 358.
References [edit]
- ^ 7 Airbus Jets Had Landing Gear Trouble
- ^ "JetBlue Flight Lands Safely". Fox News. September 22, 2005.
- ^ a b Emergency landing televised on flight - Life - MSNBC.com
- ^ Morin, Monte; Stuart Pfeifer, Megan Garvey (September 22, 2003). "Disabled Airliner Creates a 3-Hour Drama in Skies". Los Angeles Times. Retrieved 2008-08-05.
- ^ AFA-CWA | UAL Council 12 | Los Angeles | AFALAX.ORG
- ^ "CertAlert No. 02-04" (RTF). FAA. 2002. Retrieved 2007-04-02.
- ^ "Even passengers watch plane's drama on TV". The Seattle Times. September 22, 2005. Retrieved 16 December 2012.
- ^ Oldham, Jennifer; Garvey, Megan (September 23, 2005). "7 Airbus Jets Had Landing Gear Trouble". Los Angeles Times. Retrieved 12 December 2012.
- ^ a b Great Video, But Little Danger in Emergency Jet Landing
- ^ NYC99IA062
- ^ NYC99IA062
- ^ Broder, John M.; Wald, Matthew L. (September 23, 2005). "Earlier Landing Gear Problems in Airbus Jets". The New York Times. Retrieved May 6, 2010.
- ^ Worn-out seals blamed in 2005 JetBlue landing
External links [edit]
- NTSB Report
- JetBlue Flight 292 Video of the landing
- [1] Captured audio of Pilot discussing problem with Air Traffic Control, from the Fly With Me podcast.
|
||||||||||||
Coordinates: 33°56′09″N 118°23′50″W / 33.93583°N 118.39722°W