Aviation News, Headlines & Alerts
 
Category: <span>Airport</span>

Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Boeing 737 Emergency Landing in Volgograd


Click to view full size photo at Airliners.net
Contact photographer Snorre – VAP
What: Orenburg Airlines Boeing 737-400, registration VP-BGQ en route from Volgograd (Russia) to Sharm el Sheikh (Egypt)
Where: emergency landing at Domodedovo Airport
When: Thursday, Feb 26th 2009
Who: with 142 passengers, 7 crew
Why: On takeoff, the plane hit a runway edge light with its inner left main gear tire which resulted in destruction of the inner tire and hydraulics. The flight spent two hours burning fuel and eventually landed at Volgograd.

Is this the same plane described here, as being
“Boeing-747 passenger liner en route from Dubai, the United Arab Emirates to Orenburg.” ?

OR is it the flight described as flying from Volgograd (Russia) to Sharm el Sheikh (Egypt) ?


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Turkish Boeing Crash at Amsterdam’s Schiphol Airport


Click to view full size photo at Airliners.net
Contact photographer Joop Stroes – Global Aviation Photography
What: Turkish Airlines Boeing 737-800 (TC-JGE) Flight 1951 en route from Istanbul to Amsterdam.
Where: Amsterdam’s Schiphol Airport
When: 10:40 a.m. Wednesday Feb 25
Who: 135 passengers on board; eight crew members. (numbers vary)
Why: The plane crashed as it approached the runway to land. Witnesses say the approach was too low and the pilot tried to go higher to avoid crashing into the A-19 (hwy.) The wreckage is in three pieces lying in a field next to the runway; emergency crews are tending injured passengers on site. The cockpit was intact, adn the fuselage broke at the wings.There was an immediate report of one fatality which was later denied. There were at least 20 injured and at least 50 survivors. Another report estimated the majority of the passengers are injured. (Sorry the numbers don’t mesh, but this is the news as it came in–) There was no fire. Fights to and from Schiphol were suspended temporarily after the crash.
Update:
The number of deceased has been increased to 9.

More than 80 suffered injury.

25 suffered “serious” injury.
6 are hospitalized in critical condition.

Numbers corrected (again): 127 passengers 7 crew.

According to various passenger accounts, prior to the crash, twelve minutes to the scheduled landing, the plane was flying low, and an announcement was made that the plane was landing. (No announcement was made that the plane was in an emergency.) Immediately on landing, those who were able left the plane, and when there was no fire, they went back in and pulled the others out, especially in the front of the plane, where there was screaming. Outside help arrived within 20-25 minutes.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

R-44 Crashes In Panama; 3 Killed


Pictured: R-44
Click to view full sized photo at Airliners.net
Contact Photographer Jose Ramon Valero

What: Robinson-44 (tail # HP-AM3 ) Raven II owned by the Atlantic Suntoys Corp. en route from from the region of Tucuti, in the Panamanian province of Darien, on the border with Colombia en route to Albrook on the banks of the Panama Canal.
Where: Panama City’s international airport, Tocumen terminal
Who: pilot Gary Muschette, and passengers Arturo Kam Tello and Ramon Ricardo Perez
Why: Requesting permission to land at Tocumen, pilot Gary Muschette reported a mechanical malfunction.

Witnesses said the helicopter was on fire before it fell from the sky.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Ryanair Emergency Landing at Shannon

What: Ryanair plane en route from the UK
Where: Shannon Airport
When: shortly before 4pm in the afternoon feb 15
Who: 177 passengers and crew
Why: the pilot notified Shannon Airport control tower that it had a tire problem, performed a flyby to verify the condition of the landing gear, and then landed without further problems.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

American Airlines 757 Emergency Landing at LAX

What: American Airlines Flight 1236 on its way to Chicago from John Wayne Airport in California’s Orange County
Where: LAX
When: one engine died just minutes after takeoff at 3:21 p.m. Sunday.
Who: 149 passengers and a crew of six
Why: The flight was diverted to Los Angeles International Airport, where it landed safely around 3:31pm. There were no injuries.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Air Pacific jetliner Emergency Landing at LAX


Click here for full size photo on Airliners.net
Contact Photographer Snorre – VAP

What: Air Pacific jetliner (Boeing 747 ) Flight 811 en route to Fiji
Where: Los Angeles International Airport
When: Friday feb 13
Who: 441 passengers and crew
Why: The crew reported a “fuel transfer problem.” and was forced to return to Los Angeles International Airport


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Piper Incident in San Francisco


navaho not pictured
What: PA31 Piper
Where: RUNWAY 28R, SAN FRANCISCO INTERNATIONAL AIRPORT, SAN FRANCISCO, CA
When: 01/28/2009
Who: pilot
Why: Piper struck runway edge lights


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Saab Loses Hydraulics and Lands Safely at Yeager Airport

What: Colgan Aviation for United Express’ 34-seat Saab 340 twin-engine turboprop en route to Washington’s Dulles International Airport
Where: Yeager
When: 8:30 a.m.
Who: 13 passengers
Why: The plane underwent a total hydraulic failure, and prior to landing, circled Yeager for about 45 minutes to burn off fuel. This was a level two alert. Yeager airport has three alert levels. For a Level Two alert, county 911 dispatchers automatically sent fire and police personnel from Charleston to the airport to assist Air National Guard personnel.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Emergency Landing Vancouver International Airport

What: Bombardier Inc BD-700-1A10 en route from San Jose Cabo-Los Cabos Airport Mexico to Vancouver International * (The plane was also identified as a Cessna Citation)
Where: Vancouver International Airport
When: Jan 4 2009
Who: 5
Why: The pilot reported problems with the landing gear. The plane was substantially damaged on landing; fortunately the passengers were not.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Continental Boeing Crashes and Burns on Takeoff


What: Continental Airlines Boeing 737 flight 1404 Denver to Houston Registration N18611
Where: Denver International Airport on runway 34 Right
When: 20 DEC 2008 18:18 local time
Who: 107 passengers 5 crew (at least 38 injured, nothing life-threatening) Ten passengers were taken to Denver Health. 15 passengers were taken to the Medical Center of Aurora. University Hospital in Aurora took in eight. Four passengers were taken to Swedish Hospital
Why: The plane suffered a runway excursion at runway 34R during takeoff, slid into a ditch and caught fire after the crash. The #1 engine separated from the wing and the undercarriage collapsed. There was a 31 knot (36 mph) crosswind.
Passengers debarked on emergency slides as the plane burned. 38 people were taken to 4 Denver hospitals with injuries ranging from broken bones to bumps and bruises. Fire burned the right side of the plane. Two patients at University of Colorado Hospital initially listed in fair condition were downgraded to critical condition with fractures.

By the time the passengers had evacuated, the fire had spread inside and started melting the luggage compartments.

Debris remained on the runway, with the plane about 200 yards away and its landing gear and left engine shorn off.

The plane’s first flight was 1994-05-31.It has 2 CFMI CFM56-3C1 engines.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

United successful Belly Landing at O’Hare

What: The United Express flight 7164, en route from O’Hare bound for South Bend
Where: O’Hare Airport
When: Monday night Dec 15
Who: 28 passengers and 4 crew members
Why: The plane was about to land in South Bend but instead, circled the airport and returned to Chicago because of a landing gear problem. When the plane hit the tarmac, the left wing shot sparks. The belly landing as the plane slid down the runway, half on its belly.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Delta Emergency Landing at Quad City International Airport

What: Delta Flight 5083 en route from Cedar Rapids to Cincinnati
Where: Quad City International Airport.
When: Tuesday Dec 16, 2008 around noon
Who: 38 people were on board
Why: The pilot reported flap problems. Limited visibility prevented a return to Cedar Rapids. The plane landed safely.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Philadelphia Incident Sunday

What: US Airways Express CRJ Jet operated by Air Wisconsin en route from Norfolk, Va to Philadelphia.
Where: Philadelphia International Airport
When: 5:30 pm Sunday
Who: 3 people aboard, the captain, first officer and a flight attendant. The plane can hold 50 passengers
Why: The pilot reported problems with the landing gear. The plane landed safely on runway 27 Left on foam though its left landing gear was not down. Sparks were seen on the runway at landing, but no injuries were reported. The plane carries 3000 lb of fuel.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Delta Handles Double Emergency Landing


What: Delta Air Lines MD88 flight DL1102 en route from Washington Dulles,DC to Atlanta,GA
Where: diverted to Greenville-Spartanburg International Aiport for an emergency landing on runway 22.
When: 5 p.m. Thursday.
Who: 146 passengers and crew members
Why: Initially the crew noticed smoke in the cockpit and was diverted to Greenville-Spartanburg. Additionally on landing, one of the right main gear tires blew. Passengers were evacuated onto the taxiway using slides.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Embraer Emergency Landing in Palm Springs

What: Sky West Flight 6552 Embraer en route from Palm Springs International Airport to Los Angeles International Airport
Where: Palm Springs International Airport
When: 5:46 p.m
Who: 14 people on board
Why: After the crew detected smoke in the cockpit right after takeoff, the Sky West flight was able to land safely.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Historical Airbus


Jet Blue Emergency Landing in LAX 2005.

Shortly after the landing gear handle was positioned to the up position in the initial climb, the flight crew noted an error message on the Electric Centralized Aircraft Monitoring (ECAM) system listing a fault (L/G SHOCK ABSORBER FAULT) message for the nose landing gear (NLG) shock absorber. The gear handle was then moved to the down position and the crew received an error message of a fault for the nose wheel steering (WHEEL N/W STRG FAULT). After determining that the nose landing gear was cocked 90 degrees, the crew landed at an alternate airport, and the NLG tires and both wheels were worn down into the axle. Post incident examination of the nose gear assembly found that two of the four anti-rotation lugs on the NLG upper support assembly fractured and separated due to induced fatigue from the stearing system’s programed pre-landing dynamic steering tests that repeatedly cycles pressure to the stearing cylinders. The failed lugs allowed the NLG to deviate from its 0-degree position in the landing gear bay upon gear retraction on takeoff. This resulted in the L/G SHOCK ABSORBER FAULT error message on the ECAM system. When the pilots extended the incident airplane’s landing gear, the nose gear achieved the down and locked position 1.5 seconds before the main gear and/or all of the landing gear doors closed. The nose wheel assembly was not centered at this time. The Brake Steering Control Unit (BSCU) detected this off center condition of the NLG and attempted to re-center the nose wheel; however, due to the sequencing of the nose and main landing gear and their respective doors, hydraulic pressure was shut off to the NLG steering valve. This lack of hydraulic power to the servo valve resulted in a lack of position feedback to the BSCU. After a 0.5-second monitoring time period, the BSCU detected this as a fault and deactivated the steering system so that the BSCU could not return the nose wheels to center. Failure of the nosewheels to center initiated a WHEEL N/W STRG FAULT caution message on the ECAM. There were no approved procedures that allowed the flight crew to attempt to reset the BSCU system, which would have re-enabled the hydraulic system and could have resulted in the system recentering the nose wheels.

The National Transportation Safety Board determines the probable cause(s) of this incident as follows:

The fatigue failure of two anti-rotation lugs due to repeated cyclic pre-landing tests, which allowed the nosewheels to deviate from the 0-degree position on landing gear retraction. A contributing factor was the design of the Brake Steering Control Unit (BSCU) system logic, which prevented the nosewheels from centering. Also contributing was the lack of a procedure to attempt to reset the BSCU system under these conditions.

LAX05IA312
1.1 HISTORY OF FLIGHT

On September 21, 2005, at 1818 Pacific daylight time, Jet Blue Airways flight 292, an Airbus A320, N536JB, landed at Los Angeles International Airport, Los Angeles, California, with the nose wheels cocked 90 degrees. Jet Blue Airways, Inc., was operating the airplane as a scheduled domestic passenger flight under the provisions of 14 Code of Federal Regulations (CFR) Part 121. The airline transport pilot licensed captain, first officer, 4 flight attendants, and 141 passengers were not injured. The flight departed Burbank, California, at 1531 as a non-stop to JFK Airport, New York, New York. Visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed.

The first officer (FO) was the pilot flying. He noted no problems during the initial departure, and observed a positive rate of climb. Information from the digital flight data recorder (DFDR) indicated that after liftoff the gear handle was positioned to the up position.

The flight crew noted an error message displayed on the Electric Centralized Aircraft Monitoring (ECAM) system. There was a fault (L/G SHOCK ABSORBER FAULT) message for a nose landing gear (NLG) shock absorber.

The DFDR data then indicated that the gear handle was positioned to the down position. The crew then received an error message of a fault for the nose wheel steering (WHEEL N/W STRG FAULT). There was no master warning so the FO continued flying the airplane while the captain troubleshot the ECAM system.

The FO flew the airplane over Palmdale, California, at 14,000 feet mean sea level (msl) while the captain consulted the flight crew operating manual (FCOM) and maintenance control. The FCOM noted that the nose gear “may be caught at 90 degrees.” The captain continued to evaluate the problem to ascertain the systems’ status. The flight crew continually updated the cabin crew and passengers.

The flight diverted to Long Beach, California. The captain decided to perform a flyby of the tower for verification on the gear status. The tower, Jet Blue ground personnel, and a local news helicopter advised him that the nose gear was canted 90 degrees to the left. The captain stated that after discussing the situation with company representatives, he decided to divert to LAX because it had optimum field conditions, runway length, and a better emergency/abnormal support services. The crew flew for several hours to burn fuel so that they could land at a lighter weight.

The captain took note of the fuel burn to ensure that the center of gravity stayed within limits. The captain also advised the cabin crew that in the event that the nose gear collapsed, evacuation from the aft doors was not available so everyone would deplane from the forward exits. The flight crew advised the cabin crew to take the emergency procedures up to the point of egress, at which time the captain would advise the method.

Prior to touchdown, the captain announced “brace” and the flight attendants also transmitted “brace” over the public address system.

The captain flew the airplane for the landing. He touched down at 120 knots, and applied normal braking at 90 knots. He held the nose gear off of the ground as long as possible. At 60 knots, the flight crew shut down the engines. They did not use ground spoilers, reverse thrust, or auto braking. During the landing, the forward cabin crew could smell burnt rubber. The cabin crew remained at their stations as previously defined by the captain. The air traffic control tower confirmed that there was no fire, and the captain announced this to the cabin crew. After this notification, the passengers deplaned normally using an air stair.

Upon touchdown, the NLG tires rapidly deflated and tore apart, and both wheels were worn into the axle. During landing, the airplane’s trajectory was not affected by the abnormal NLG configuration or subsequent tire destruction, and the airplane stayed on the runway centerline.

Maintenance personnel jacked the airplane up, and removed the damaged wheels. They installed a right nose wheel, and towed the airplane to a maintenance hangar.

1.2 INJURIES TO PERSONS

No one on board the airplane sustained an injury.

1.3 DAMAGE TO AIRCRAFT

Damage was limited to the NLG assembly.

1.4 OTHER DAMAGE

There was no damage to any objects other than the airplane.

1.5 PERSONNEL INFORMATION

1.5.1 Captain

The operator reported that the captain held an airline transport pilot certificate with ratings for airplane single-engine land, multiengine land, and instrument airplane.

The captain held a first-class medical certificate issued on August 12, 2005. It had the limitation that he must wear corrective lenses.

The operator reported that the captain had a total flight time of 10,829 hours. He logged 160 hours in the last 90 days, and 39 in the last 30 days. He had en estimated 2,552 hours in this make and model.

1.5.2 First Officer

The operator reported that the FO held an airline transport pilot certificate with ratings for airplane single-engine land, multiengine land, and instrument airplane.

The FO held a second-class medical certificate issued on April 19, 2005. It had no limitations or waivers.

The operator reported that the FO had a total flight time of 5,732 hours. He logged 254 hours in the last 90 days, and 94 in the last 30 days. He had en estimated 1,284 hours in this make and model.

1.6 AIRCRAFT INFORMATION

The airplane was an Airbus A320, serial number 1784. The operator reported that the airplane had a total airframe time of 14,227 flight hours and 5,098 landing cycles. It was on a continuous airworthiness inspection program. Maintenance records indicated that Jet Blue maintenance technicians replaced a proximity sensor on the nose wheel prior to the previous flight’s departure from New York earlier that day.

1.6.1 NORMAL OPERATION

The landing gear (L/G) normal extension and retraction system is electrically controlled and hydraulically operated.

The electrical system has a landing gear control lever, two Landing Gear and Control Interface Units (LGCIU), a gear electro-hydraulic selector valve, a door electro-hydraulic selector valve, 32 proximity sensors and their related targets, and a set of indicator lights. The electrical control system has two subsystems; each is governed by a separate LGCIU. At any given time, one LGCIU is in CONTROL and the other is in MONITORING mode (while using the data from the respective proximity sensors).

The hydro-mechanical components include three gear actuating cylinders, three door actuating cylinders, three gear uplocks, three door uplocks, three door by-pass valves (ground opening function for the door), a NLG downlock release actuator, and two MLG lockstay actuating cylinders. For this airplane, the green hydraulic system provides hydraulic power to operate the landing gear.

Upon movement of the L/G control lever, the LGCIU sends a signal to the electro-hydraulic valve assembly. The proximity sensors send signals to the LGCIU, which ensures that the L/G operate in the correct sequence.

The NLG retracts forward into a bay in the fuselage, and centers fore and aft.

When the nose landing gear is in the retracted/uplocked position there is clearance around the wheels. Therefore, if the mechanical centering of the nose wheels fails, the wheels can rotate a certain amount (approximately 20 degrees) until they contact the roof of the NLG bay. Airbus tests have shown that, even with this amount of rotation, the gear will still achieve a free fall, so the gear will not jam in the bay. Following retraction on takeoff, if the nose wheels deviate from their mechanically centered position while in the landing gear bay, a L/G SHOCK ABSORBER FAULT caution light will illuminate.

There are a pair of proximity sensors and targets on the NLG that detect if the gear is extended (airplane in air) or if the gear is compressed (airplane on ground). The proximity sensors also indicate that the wheels are aligned fore and aft. If the wheels are not aligned, retraction is prevented. When the gear is fully extended (flight condition), the sensors detect the targets as near. When the NLG gear is compressed, the targets move away from the sensors (target far), setting the ground/compressed condition. However, a failure condition can exist that results in the NLG system sensing “ground/compressed” when the gear is extended and a mechanical failure allows the NLG wheel to rotate to a position greater than 6 degrees.

1.6.1.1 Brake Steering Control Unit (BSCU)

The Airbus model A320 airplane has a NLG steering system that is electrically controlled by the BSCU and hydraulically actuated by the steering control module and two steering actuators. When commanded from the tillers and/or rudder pedals, the BSCU computes and electrically sends steering commands to a servo valve, contained within the steering control module, to hydraulically position the nose wheel assembly to the commanded position. The BSCU receives electrical NLG position feedback signals from sensors installed on the NLG and from a sensor that monitors the position of the steering control module servo valve. When both the nose and main landing gear are extended with their respective doors closed, the nose wheel steering control module is energized and applies hydraulic pressure to the steering servo valve. However, hydraulic pressure will not be available to the steering control module until all gear doors are commanded closed. The BSCU also controls the parking brake and applies braking to the main wheels during landing gear retraction. The A320 features two types of BSCU standards, the CONVENTIONAL and the Enhanced Manufacturing and Maintainability (EMM), which is also called the COMMON.

The airplane had EMM/COMMOM BSCU software standard L4.5 (P/N E21327003) installed, which, as does standard L4.1, features a pre-landing dynamic steering test, as does the CONVENTIONAL BSCU. However, the EMM/COMMON BSCU and the CONVENTIONAL BSCU pre-landing steering tests are significantly different. While both the COMMON and the CONVENTIONAL BSCU essentially work the same way, the COMMON BSCU results in significantly more physical movement of the gear while trying to rotate the gear (in the mechanically centered locked position) during the pre-land test.

Once the BSCU receives a signal indicating that the NLG is down and locked, it starts monitoring the angular position of the NLG. It begins a series of five steering tests. After a brake test has been completed and hydraulic system power is available to the steering servo valve (nose gear down and locked and all gear doors are commanded closed), the BSCU starts the steering test. After the first four test sequences are completed, the EMM/COMMON BSCU (Std L4-1 and L4-5 only) electrically commands the NLG wheel assembly to rotate 2.5 degrees left from center, back to center, 2.5 degrees right, then back to center. This cycle takes approximately 5.0 seconds to complete, and is continuously performed until touchdown of the main gear assembly. According to information provided by Airbus representatives, the NLG completes the left and right cycle an average of 57 times per flight. The CONVENTIONAL BSCU on the other hand applies a 10-degree rotation command for only 0.5 seconds, which achieves a pulse movement up to 1 degree.

After the landing gear is selected down, and 1 second after the NLG is down and locked, the BSCU determines the position of the NLG wheel assembly. If the BSCU detects that the NLG has deviated out of its mechanically centered 0-degree position, it will attempt to center the NLG. It electronically commands the servo valve to reposition the NLG wheel assembly to center. If the BSCU does not receive a position feedback response indicating that the servo valve moved as commanded, the BSCU will continue to monitor the servo valve position for 0.5 second. If there is still no response, the BSCU shuts off hydraulic pressure, and nosewheel steering is not available. The NLG cannot be moved without hydraulic pressure. Failure of the NLG to center initiates a WHEEL N/W STRG FAULT caution on the ECAM.

1.6.3 NLG ASSEMBLY

The nose landing gear assembly consists of a shock absorber in the barrel of the NLG leg structure, and its lower part consists of the wheel axle. It absorbs the landing shock and dampens oscillations when rolling. The upper part of the shock absorber is attached to the barrel of the landing gear leg. Wheel centering takes place at the end of the shock absorber extension phase by means of two centering cams on it.

On top of the NLG leg is an upper support assembly. A pair of anti-rotation lugs on top of a shock absorber inner cylinder mesh with slots on the upper support assembly. When engaged with the anti-rotation lugs, the upper support assembly lugs assist in connecting the NLG shock absorber to the NLG leg structure. They are intented to maintain the proper relationship between the shock absorber and the leg assembly in the longitudinal axis.

1.7 METEOROLOGICAL INFORMATION

Day visual meteorological conditions prevailed; the winds were from 250 at 8 knots.

1.8 AIDS TO NAVIGATION

The airplane flew an approach into Los Angeles International.

1.9 COMMUNICATIONS

The airplane was in contact with Los Angeles Air Route Traffic Control Center (ARTCC) Center, Southern California Terminal Radar Approach Control (SCT), the Long Beach airport air traffic control tower (ATCT), and the Los Angeles ATCT.

1.10 AIRPORT INFORMATION

The Airport/Facility Directory, Southwest U. S., indicated that Los Angeles International runway 25L was 11,096 feet long and 200 feet wide. The runway surface was concrete.

1.11 FLIGHT RECORDERS

1.11.1 A Safety Board specialist examined the DFDR, and prepared a factual report. Pertinent parts of the report follow.

The landing gear handle was positioned to the up position within a few seconds of the main gear leaving the ground. About 6 seconds later, which was 25 seconds after the nose gear squat switch first indicated AIR, the switch indicated GROUND for about 11 seconds. It returned to AIR for 2 seconds, and then indicated GROUND for the remainder of the flight.

1.12 WRECKAGE AND IMPACT INFORMATION

The airplane sustained minor damage when the tires deflated and tore apart. The nose wheels ground down into the axle.

1.13 MEDICAL AND PATHOLOGICAL INFORMATION

There were no injuries.

1.14 FIRE

Flames from runway contact flared each time the airplane’s cocked nose wheel passed over a paint stripe on the runway centerline. The wheel assembly was scorched.

1.15 SURVIVAL ASPECTS

The cabin crew detected something out of the ordinary immediately after takeoff. They began to reference their manuals as they waited for information from the flight crew.

The captain communicated with the cabin crew and passengers. The cabin crew emptied the first three rows of seats, and moved baggage as far aft as possible. They placed able-bodied persons in the exit rows, and removed all baggage and paperwork from the seating area. They showed the able-bodied persons how to operate the doors, and gave additional instructions.

The lead flight attendant placed the in flight entertainment (IFE) master switch in the standby mode, which muted the audio sound and disabled the visual picture. She disabled the system entirely the last 50 minutes of the flight. The cabin crew provided blankets, pillows, water, and non-alcoholic beverages to the passengers.

The flight attendants spoke to the passengers individually prior to the landing to ensure that each one knew the emergency procedures that would take place and how to properly brace. The flight attendants checked and double-checked each other’s work to ensure that everything was completed and would go according to plan.

JetBlue’s policy did not allow use of personal electronic devices below 10,000 feet. However, they briefly allowed the passengers to call family members on cell phones while the airplane was at 6,000 feet. They instructed passengers to stow them and other personal belongings for the landing.

The cabin crew remained at their stations as previously defined by the captain, until he sent word that there was no fire. After this notification, the passengers deplaned normally through the L1 door to air-stairs brought to the airplane.

1.16 TESTS AND RESEARCH

1.16.1 A post flight readout from the BSCU indicated 6.5 degrees for the NLG, which meant that the NLG was beyond 6.5 degrees from the centered position. It recorded two faults: at 1531, the L/G SHOCK ABSORBER FAULT, and at 1532, the WHEEL N/W STRG FAULT. Examination of the nose wheel assembly with a borescope revealed fractured and separated anti-rotation lugs.

1.16.2 NLG Upper Support Assembly Examination

A Safety Board metallurgist and a systems engineer supervised the examination of the NLG assembly at Messier Services, Sterling, Virginia. The examination of the NLG assembly revealed that two of the four anti-rotation lugs on the NLG upper support assembly had fractured and separated from the upper support assembly. The other two lugs contained cracks. A summary of the metallurgist’s findings follows.

1.16.2.1 Materials Laboratory Report on Upper Support Assembly

The metallurgist arbitrarily labeled the fractured upper support assembly lugs one through four.

Bench binocular microscope examination of lug number one revealed that its fracture face contained ratchet marks (radial lines), typical of a fatigue crack. The fracture originated within the radius between the slot side of the lug and the lower surface of the upper support, near the inner diameter of the upper support. The fatigue crack propagated through more than 95 percent of the fracture face.

The fracture face of lug number two contained ratchet features (radial lines) typical of a fatigue crack. The fatigue crack propagated through more than 95 percent of the fracture face. For the most part, the last 5 percent of the fracture length showed ductile dimple features typical of overstress separation.

The contour of the crack at the base of lug number three was similar to the contour of the fracture path on lugs one and two. The fracture face contained crack arrests features typical of a fatigue crack.

The crack at the base of lug number four measured approximately 0.1 inch; the metallurgist did not excise it for examination.

1.16.3 Tests

The systems group chairman supervised examination and testing of the LGCIU’s landing gear control lever, and the BSCU. The following paragraphs detail the results.

1.16.3.1 LGCIU (Landing Gear Control Interface Unit)

The internal BITE data from both LGCIUs was downloaded and analyzed; no faults were found. Functional and acceptance tests were conducted on each unit; the testing revealed no anomalies.

The landing gear control lever was also tested and found functional.

1.16.3.2 NLG Wheel Steering tests

The purpose of the test was to find the root cause of the steering anomaly detected by the airplane’s BSCU. Data retrieved from the unit indicated that a WHEEL N/W STRG FAULT was displayed on the ECAM and failure code 671 was triggered and recorded by the BSCU internal memory (BITE). This fault code is triggered when the BSCU detects that the steering servo valve spool does not move. Testing was conducted to help understand why the servo valve spool did not move, preventing the BSCU from returning the nose wheels to the centered position.

The steering tests were performed on an Airbus test rig using the BSCU and hydraulic control unit 6GC from airplane N536JB. The testing verified that when hydraulic pressure was available to the unit, the BSCU automatically moved the nose wheel assembly from a position greater than 6.5 degrees to its mechanically centered position without triggering any fault code.

The testing also indicated that when hydraulic pressure was not available to the unit, the BSCU would not automatically move the nose wheel assembly from a position greater than 6.5 degrees to its mechanically centered position and fault code 671 would be triggered.

Testing also verified that when the BSCU was reset and hydraulic pressure was available, it was able to automatically move the nose wheel assembly from a position greater than 6.5 degrees to its mechanically centered position, and steering was recovered. Fault code 671 remained stored within the BSCU’s bite to assist maintenance troubleshooting.

1.17 ADDITIONAL INFORMATION

CORRECTIVE ACTIONS

Airbus issued Operations Engineering Bulletin (OEB) 175-1 (post Flight Warning Computer standard E3) and OEB 176 (Flight Warning Computer standard E2) in October 2005. This provided a procedure for the flight crew to reset the BSCU in flight. It discussed steps to take if the L/G SHOCK ABSORBER FAULT ECAM message was triggered at any time in flight and the WHEEL N/W STRG FAULT ECAM caution light illuminated after landing gear extension. Under those conditions, it noted that the flight crew could reset the BSCU when all landing gear doors indicated closed on the ECAM WHEEL page. Successful NLG centering and nosewheel steering recovery would be indicated if the WHEEL N/W STRG FAULT ECAM light was no longer illuminated. FAA AD 2005-24-06 and EASA AD 2006-0174 were subsequently issued to perform a NLG shock absorber charge pressure check and a repetitive borescope inspection of NLG upper support/cylinder lugs to mitigate the fatigue cracks that were induced by the BSCU Standard L4.5 (or earlier EMM standards). Furthermore, FAA AD 2007-18-19 was issued to supersede FAA AD 2005-24-06 and defines the related investigative/corrective actions referencing Airbus SB A320-32-1310. The SB A320-32-1310 introduces a modified and more robust upper support. The FAA AD 2007-18-09 also provides optional terminating action for repetitive inspections.

RETROFIT

Airbus issued new software standards L4.8 (sb a320-32-1305) and L4.9B that cancelled OEBs 175 and 176. BSCU standard 4.8 reduced the number of pre-landing test cycles to eight per flight, which they felt reduced the likelihood of fatigue. Standard 4.9B has no effective pre-landing test cycles to induce fatigue. Airbus made a design change to the upper support assembly and provided specific inspection requirements at NLG overhaul. They consider those changes plus incorporation of Standard 4.9B to be terminating action for this issue.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Airbus Emergency Landing in Norway


What: SAS airlines Airbus 330 en route from Stockholm, Sweden, to Chicago
Where: Vaernes Airport in central Norway
When: Thursday November 27, 2008
Who: 180 passengers 13 crew members
Why: One of the planes engines was shut down forcing a “security landing”


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Flock of Starlings Downs Ryanair Boeing in Italy


What: Ryanair Boeing 737-800 flight FR4102 from Frankfurt
Where: approached Rome Ciampino Airport at 7.56am
When: Monday November 10 2008
Who: two crew members and eight of the 166 passengers received medical treatment
Why: After the both of the plane’s engine ingested a number of European starlings, smoke started pouring out of one of the engines and oxygen masks fell from the ceiling. As the plane was coming in to land, Passengers debarked via emergency exits and escape chutes. The landing gear sustained damage also. The pilots did not have the time or momentum to bypass a huge flock of birds encountered on landing.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Air India Emergency Landing at Indira Gandhi International Airport

What: Air India’s Delhi- Hyderabad-Tirupati flight (IC 942) en route from Indira Gandhi International airport to London
Where: Indira Gandhi International airport
When: Friday-10.15 takeoff; declared emergency around 11.15 am
Who: 66 passengers on board 6 crew members
Why: emergency landing an hour after take off. Passengers rerouted in another aircraft around 12.30 and took off around 1 pm. There was a technical emergency. No one was injured.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Queasy Stomachs Land at O’Hare

What: United Airlines Flight 167 en route to Los Angeles from Boston

Where: diverted to O’Hare International Airport

When: Wednesday 8:37 p.m

Who: 138 people were on board.

Why: When about a dozen passengers became sick during a flight, the flight was diverted to O’Hare and an EMS Plan 2 was called which sends at least 10 ambulances to the scene. Some passengers became sick from the smell of vomit on the plane. Those who fell ill were reportedly part of the same tour group of about 40. One among them reported feeling sick prior to takeoff. Four were hospitalized at Lutheran General Hospital. Fourteen declined to be hospitalized when examined by paramedics though the entire tour group was examined by paramedics. No food was served on the flight.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

UA Emergency Landing in Shannon

What: United Airlines flight 952 en route from Dulles International Airport in Washington D.C. to Frankfurt in Germany
Where: emergency landing at Shannon Airport. Shannon Airport is reducing from 280 staff to being manned by skeleton staff of fewer than five Aer Lingus ground personnel; but emergency services were deployed.
When: Friday October 17 2008 landing safely at landed safely at 6.13am
Who: 190 passengers and crew
Why: A technical problem in the cockpit area resulted in smoke entering the flight deck. A replacement plane was provided for the passengers.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Norway: Rygge Airport Emergency Landing

What: Norwegian Air Boeing 737-8Q8 en route from Rygge Airport to Barcelona
Where: Rygge Airport
When: 10/17/2007 Friday
Who: 163 passengers 7 crew
Why: 20 minutes into the flight, an alarm warned of fire in one of the wings. Smoke was reported in the cabin.The aircraft was breaking very hard, and used half the runway to stop. On return to the airport, passengers deplaned via emergency slides, but there was apparently no external wing fire. There was a minor injury on the slide disembarkment.

In Dutch


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Emergency Landing at Heathrow

What: British Airways Flight BA 341 Boeing 757, en route from France
Where: priority landing at Heathrow airport
When: British Summer Time (BST) 063 Sunday
Who: 137 passengers
Why: Fumes were detected in the passenger cabin, instigating an emergency landing. There were no injuries.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Malibu Beach Crash

What: Northfield Aviation single-engine Sky Arrow 600 taking off from Santa Monica Airport
Where: in the ocean off Malibu Beach
When: Oct 7 5:15 p.m
Who: Two men were on board: One was Griff Horner, 70, an experienced pilot and helicopter instructor. Critical injuries.
Why:The incident is under investigation.

Content not attributed to or linked to original, is the property of AirFlightDisaster.com; all rights reserved.

Site Credits