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

Turbulence over the Atlantic


Click to view full size photo at Airliners.net
Contact photographer Thomas Brackx

What: British Airways Boeing 777-200 en route from Antigua to London
Where: over the Atlantic
When: Oct 19th 2009
Why: While over the Atlantic, the flight encountered severe turbulence and descended to fly at a lower altitude. The flight arrived in London about a quarter of an hour ahead of schedule.

There is no indication at this point whether or not anyone was injured during the turbulence.


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

Lufthansa Flats at JFK


Click to view full size photo at Airliners.net
Contact photographer Christoph Flink

What: Lufthansa Boeing 747-400 en route from New York to Frankfurt/Main
Where: JFK,NY
When: Oct 11th 2009
Why: Prior to take-off, the plane was believed to run over runway lights, which blew out the plane’s main gear tires. The flight was delayed while the flat/damaged tires were removed and new tires were installed.


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

LAX: United Airlines Hydraulics Leak


Click to view full size photo at Airliners.net
Contact photographer Gerry Stegmeier

What: United Airlines Boeing 777-200 en route from Los Angeles ,CA to Narita
Where: Los Angeles
When: Oct 5th, 2009
Why: About twenty minutes after takeoff, the plane experienced a hydraulics leak. The flight crew decided to return to LAX, where it landed safely at 2:21 p.m.

Maintenance crews are inspecting the plane.


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

JAC Commuter Hydraulics Malfunction


PICTURED: A JAC De Havilland jet landing at Osaka
Click to view full size photo at Airliners.net
Contact Photographer Javier Guerrero

What: Japan Air Commuter Bombardier DHC-8-402 en route from Osaka to Miyazaki
(Also reported as a Havilland Dash 8-400)
Where: Osaka International Airport
When: Thursday Aug 20
Who: 22 passengers and four flight crew members
Why: Breitbart reports that while en route, the Bombardier’s hydraulic system indicator light reported a hydraulics malfunction. The plane landed safely with no reported injuries and was towed off the runway. It is not clear if the hydraulics or the indicator was at the source of the problem, but JAC is investigating.


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

Singapore Airlines Airbus Indicator Delays Flight


Click to view full size photo at Airliners.net
Contact Photographer Marco Toso

What: Singapore Airlines Airbus A380-800 en route from London Heathrow to Singapore
Where: London
When: Aug 8th 2009
Who: 363 passengers
Why: After takeoff, control panel indicated a problem on the plane that led to returning to the airport of origin. After landing, Singapore Airline maintenance determined that the flaw was in the signal. The plane was cleared for take-off and completed 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

Paris: Airbus Catches Fire on Runway


Click to view full size photo at Airliners.net
Contact Photographer Javier Gonzalez

What: Vueling Airbus A320-200 en route from Paris Orly Airport to Alicante Spain
Where: Paris
When: Aug 5th 2009 10h36
Who: 169 passengers
Why: After boarding but prior to takeoff, the Airbus’s right engine caught on fire. The official statement said that “the fire began when the aircraft was in “pushback” phase, the taxi procedure for towing the aircraft from loading up by a bar connected to a tractor trailer.”

Passengers debarked via slides. There were eight injuries reported; it was not released if the injuries were caused by the fire emergency or the slides, nor if those injured were passengers or crew.

Four and a half hours later, passengers were provided an alternative Airbus to take them to their destination.


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

DC: Turbulence on US Airways Landing


Click to view full size photo at Airliners.net
Contact Photographer

What: US Airways/ Republic Airlines Embraer ERJ-175 en route from West Palm Beach,FL to Washington DC
Where: Washington’s National Ronald Reagan Airport
When: Jul 25th 2009
Why: On the final approach, the plane was struck by turbulence and several passengers were injured. The flight landed safely. No more information has been reported–no details on the injuries or if anyone was actually hospitalized due to the turbulence injuries. One can conjecture it may have been members of the flight crew because everyone else should have been seated with belts on.


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

Vancouver BC: Philippine Airlines Airbus Emergency Landing


Click to view full size photo at Airliners.net
Contact Photographer

What: Philippine Airlines A343 en route from Manila to Vancouver, BC
Where: Vancouver BC
When: Jul 9th 2009
Why: While over the Pacific, the pilot shut down one of the engines for an unspecified reason. They landed under emergency circumstances without assistance in Vancouver. No injuries were reported.


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 Engine Fails during PreFlight


Pictured: Airbus similar to the one in the incident
Click to view full size photo at Airliners.net
Contact Photographer Ruud Brinks

What: Air France Airbus A320-200 en route from Paris Orly to Toulouse
Where: Paris
When: Jul 3rd 2009
Who: not available
Why: Prior to takeoff, during engine acceleration, the left engine failed. The flight was cancelled, and a replacement aircraft was required.
No more details were available.

George’s Point of View

At least THIS one wasn’t the Pitot tubes.


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

BMI Airbus Grounded by Mystery Smoke


Click to view full size photo at Airliners.net
Contact Photographer Rui Miguel

What: BMI British Midland Airbus A319-100 en route from London Heathrow to Edinburgh
Where: London
When: Jun 21st 2009
Who: 126 passengers,
Why: After the scent of smoke was detected in the cabin, the plane returned to London. The plane was replaced, but no source of smoke or fire was ever found.

George’s Point of View

When I read of accounts like this one, sometimes I wonder if someone snuck a smoke in the bathroom. Not that I would defend such a thing, but if that were the case, it would be better than there being an on-going problem with the electrics.


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

McDonnell Douglas Litters Chicago Midway


Click to view full size photo at Airliners.net
Contact photographer Shaun Edelstein

What: Delta Airlines McDonnell Douglas MD-90-30 en route from Atlanta, GA to Chicago Midway
Where: diverted to Cincinnati,KY and concluded in Chicago
When: May 26th 2009
Who: Not Listed.
Why: “DELTA AIRLINES FLIGHT 2090 MCDONNELL DOUGLAS 90-30 AIRCRAFT AFTER LANDING, INSPECTION REVEALED A PIECE OF THE AIRCRAFT FELL ONTO THE RUNWA. NO INJURIES REPORTED, CHICAGO, IL”

George’s Point of View

As you see, the FAA report indicates that the plane lost a piece of itself on landing. I don’t know what’s more curious–what exactly fell off the MD-90 when it landed (generally I don’t think of external plane parts as optional); or if the dropped item was related to the plane’s delay in Cincinnati.


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 Engine Shuts Down on Singapore-London flight

What: Singapore Airlines Airbus A380-800 en route from Singapore to London Heathrow
Where: Heathrow Airport
When: May 25th 2009
Why: One of the plane’s four engines shut down causing an hour’s delay. The plane was taken out of service, and the return flight was delayed until the Airbus was back in service.

George’s Point of View

Airbus is just starting out with this monster and already having engine issues. Engine shut down is serious stuff, even though the monster can fly on less than 4 engines, it’s serious.


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 Hydraulics Failure over Pittsburgh

What: United Flight 615 en route from Washington DC to Chicago O’Hare
Where: Pittsburgh
When: landed at 12:51 May 22, 2009
Who: 119 on board including Sen. Roland Burris (D-Ill.), Rep. Jan Schakowsky (D-Ill.) and White House Social Secretary Desiree Rogers
Why: After a hydraulic system failure was announced, the crew announced there would be an emergency landing. There had been “loud bang” at take-off, then the noise and vibration increased.

The landing was safe; and United was providing another plane for passengers to complete the flight to Chicago.


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 Canada Turbulence at LAX

What: Air Canada Embraer ERJ-190 en route from Calgary to Los Angeles,CA
Where: Los Angeles
When: May 18th 2009
Who: 58 passengers and 5 crew, 4 minor injuries
Why: The flight experienced a few minutes of moderate in-flight turbulence but landed as scheduled. Several passengers were treated at the 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

Airbus: Emergency Landing LAX

What: Airbus 320 en route from LAX to Dulles
Where: LAX
When: Friday, May 15, 2009 2:42 p.m.
Why: The plane developed a hydraulic leak and returned to LAX for an emergency landing. No Injuries were reported.


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 Nose Gear Issue in SF

What: Lufthansa Airbus A340-600 en route from Munich Germany to San Francisco,CA
Where: on far approach to San Francisco
When: May 5th 2009
Why: After reporting nose gear issues, the airbus was towed off the runway after landing, and it’s return flight was cancelled.


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

Two Delta Boeings with Technical Difficulties


Contact photographer John Farmington
What: Delta Airlines Boeing 767-300 en route from New York JFK,NY (USA) to Kiev (Ukraine)
Where: returned to New York
When: May 3rd 2009
Who: 212 on board
Why: The crew listed “operational reasons” but listed no details. They turned back over Moncton,NB and returned flying at lower altitude.


Contact photographer Wim Callaert
What: Delta Airlines Boeing 767-300 En route from New York JFK,NY (USA) to Rome Fiumicino
Where: Bangor,ME
When: May 4th 2009
Why: En route, the plane lost all air data computers and had lost most of the flight instruments, and requested to return to the airport of origin. Instead, they diverted to Bangor Maine. A replacement plane completed the flight. Fortunately, all that was suffered was a delay of nine hours.

George’s Point of View

This caught my eye mostly because two Boeings flying out of NY’s JFK were both listed as having “technical difficulties.” I wanted to doublecheck and see if they were the same plane.

Not the same plane.

The first incident with the undisclosed technical difficulty involved plane registration registration N182DN.
The second incident, the one with the data computer problem, involved plane registration N196DN.

I find myself curious to discover what is coincidence and what is not. It may not be the same plane; but it is the same airline, the same model plane. Is it the same flight crew? Same procedures? What about the equipment? Is there something here to discover?


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

A Lesson about Icing

What: American Eagle Saab 340
Where: Santa Maria, CA
When: Jan 2nd 2006
Who: 2 flight crew members, 1 flight attendant, and 25 passengers
Why: aircraft lost 5000 feet during climbout due to icing

George’s Point of View

Hopefully this incident is another lesson to icing and taking chances.

NTAB Report Follows:
LAX06IA076
HISTORY OF FLIGHT

On January 2, 2006, at 1439 Pacific standard time, a Saab-Scania AB SF340B+, N390AE, operated by American Eagle Airlines, Inc., as flight 3008, encountered icing conditions during the en route climb over Santa Maria, California. The airplane was at 11,700 feet mean sea level (msl) when it departed controlled flight, and descended to an altitude of about 6,500 feet msl. The pilots recovered control of the airplane, and continued to their scheduled destination of Los Angeles International Airport (LAX), Los Angeles California, where they landed at 1540 without further incident. The 2 flight crew members, 1 flight attendant, and 25 passengers were uninjured, and the airplane did not sustain substantial damage. Instrument meteorological conditions prevailed for the 14 Code of Federal Regulations (CFR) Part 121 scheduled domestic passenger flight that was operating on an instrument flight rules (IFR) flight plan. The flight originated from San Luis County Regional Airport (SBP), San Luis Obispo, California, at 1414.

A review of the American Eagle Airlines, Inc., flight log disclosed that the accident flight was scheduled to be the flight crew’s fifth trip of the day, and their second trip in the accident airplane. The 1 hour 26 minute accident flight was scheduled to depart from Santa Barbara at 1408, and terminate in Los Angeles at 1513.

The flight crew members stated in post incident interviews that before the incident flight, they had encountered light rime icing and moderate turbulence on the inbound leg to San Luis Obispo as they were descending from 9,000 to 5,000 feet. The pilots stated that, while preparing for the return flight to Los Angeles, they reviewed the weather conditions for the intended route of flight. The operator’s dispatch package noted two AIRMET (airmen’s meteorological information) reports for icing in clouds and two PIREPs (pilot weather reports) for turbulence. The pilots discussed the conditions that they had encountered on the way in, as well as the conditions for the intended route of flight outbound. Because of the gusty wind conditions and the short runway at San Luis Obispo, the captain decided to perform the departure. He was going to turn control of the airplane over to the first officer after completing the climb checklist at the acceleration altitude.

In accordance with American Eagle’s minimum equipment list (MEL), the incident airplane was dispatched with the continuous mode of the boot deice system inoperable for the inbound flight and the return incident flight. The flight crew reported that they performed the manual test of the deicer boots as called for in the MEL, and observed the operation of the inboard and outboard wing boot segments. However, they could not see the stabilizer segments, and did not have qualified ground personnel available to observe the test as required by the MEL. The pilots reported that they did confirm illumination of the green boot inflation lights on the overhead panel when they pressed the manual buttons.

In accordance with company procedures that require flight crews to activate the deice system at the first sign of ice accretion and operate the deice boots continually, the crew stated that they were prepared to operate the deice boots in manual mode as needed during the flight. They departed in level 2 weather conditions (defined as 10 degree Celsius or colder with visible moisture) and with the engine anti-ice on.

The pilots stated that the weather radar was on, and they did not observe any activity on it. The captain had the autopilot engaged in the medium (M) climb mode. Shortly after taking the controls about 2,500 feet, the first officer changed the autopilot to vertical speed (VS) mode, which gave pitch attitude commands to maintain the vertical speed existing at the time of mode engagement.

As the airplane climbed through 11,000 feet, the captain noted light rime ice accumulating on the windshield wiper blades and about a 1/2-inch-wide area of ice on the left wing.

The captain reported that, as he began to reach up to activate the manual deice boot system, he felt a heavy vibration in the airframe. He said that the windscreen immediately turned white. Immediately thereafter, the airplane’s nose dropped, the left wing dropped, and the autopilot disconnected. He grabbed the yoke to take control of the airplane. He said that the clacker sounded (indicating an imminent stall), the stick shaker activated, and the ground proximity warning system emitted a “bank angle” aural warning.

The flight crew reported that the airplane vibrated again, but less violently than the first episode. The captain leveled the wings, and began pulling up on the control yoke. At this point, he instructed the first officer to manually operate the deice boots. The captain stated that he pushed the condition levers to the maximum position, and brought the power levers to idle. The airplane stabilized in roll, and he could hear chunks of ice shedding off and hitting the fuselage. He kept the airplane in a nose-down attitude, maintaining a 500 feet per minute rate of descent until the airplane was below the freezing level.

PERSONNEL INFORMATION

Captain

The operator reported that the 34-year-old captain held an airline transport pilot (ATP) certificate with a rating for airplane multi-engine land. He held a commercial pilot certificate with ratings for airplane single-engine land and instrument airplane. He had a type rating in the SF340.

The captain held a first-class medical certificate issued on September 21, 2005. It had no limitations or waivers.

The captain had a total flight time of 6,764.08 hours, with 3,981.87 hours accumulated in Saab 340 airplanes, of which 2,519.46 hours was as the pilot-in-command (PIC). He had a total of 970 hours of instrument experience and between 1,700 and 1,900 hours of night flight. During the preceding 90 days, 30 days, and 24 hours, he reported that he had flown in both the capacity of PIC and second-in-command (SIC) approximately 172, 47, and 7 hours, respectively. He added that he had acquired numerous hours of aerobatic flight time in a Cessna 150 Aerobat airplane.

First Officer (FO)

The operator reported that the 32-year-old FO held a commercial pilot certificate with airplane instrument and multi-engine land ratings. He additionally held an SF340 Type Rating, with the limitations of SF340 SIC privileges only and circling approaches to be completed only in visual meteorological conditions (VMC). The FO was also a certified flight instructor (CFI) for instrument and multi-engine land airplane.

The FO’s second-class medical certificate was issued on May 25, 2005, with the limitation that he must wear corrective lenses.

The FO had a total flight time of 1,367.48 hours, with 132.48 hours accumulated in Saab 340 airplanes. He had a total of 94 hours of instrument experience and 185 hours of night flight. During the preceding 90 days, 30 days, and 24 hours, he reported that he had flown approximately 120, 71, and 5 hours, respectively.

AIRCRAFT INFORMATION

The airplane was a Saab SF340B+, serial number 340B-390. The airplane had a total airframe time of 17,291 hours at the examination following the incident.

Systems

National Transportation Safety Board investigators reviewed the airplane’s maintenance records and logbooks. The day prior to the incident, a flight crew reported that during an en route deice boot check, the timer light illuminated. The deicer timer failure light was later deferred in accordance with the operator’s MEL. The deferral procedures required a placard to be placed adjacent to the deicer timer switch and the auto cycling switch to remain in the “off” position. Investigators did observe an MEL placard (sticker) next to the deice system controls in the cockpit.

Initial examinations revealed that the airplane’s deice systems were operational; the deicer timer failure light illuminated.

Aileron Interconnect

The airplane was equipped with an Aileron Spring Unit. This would allow the flight crew to initially maintain authority in the roll axis if one aileron seized, until the aileron disconnect handle in the cockpit was pulled by a pilot. In the event an aileron seized, the pilot would have to overpower a preloaded spring unit to manipulate an aileron. When the pilot reduced control input pressure, the unit would close allowing the ailerons to be normally coupled. The FO stated that he believed that he did not have his hands on the controls after the captain assumed authority. The roll disconnect handle was not pulled during this incident.

WEATHER

A Safety Board meteorologist prepared a factual report, which is part of the public docket. AIRMET Zulu Update 4 for icing (SFOZ WA 022045) was issued on January 2, 2006, at 1345, and valid until 2000. It noted occasional moderate rime/mixed icing in clouds and in precipitation between the freezing level and FL220. The freezing level in central California was 6,000 to 8,000 feet; the freezing level in southern California was 7,000 to 11,000 feet.

The specialist reviewed San Joaquin Valley, California (HNX) Level II Doppler weather radar Base Reflectivity Images. At 1437:38 at the location of the icing encounter, the HNX beam center was about 16,500 feet with a beam width of about 8,000 feet. The top of the beam was about 20,500 feet, and the bottom of the beam was about 12,500 feet.

At 1442:36 at the location of the icing encounter, the HNX beam center was about 7,500 feet with a beam width of about 8,000 feet. The top of the beam was about 11,500 feet, and the bottom of the beam was about 3,500 feet.

A GOES-10 infrared image at 1441 PST at the location of the icing incident recorded a radiative temperature of 244 degrees K (-29 degrees C). Using NAM12 upper air data, this temperature corresponded to a cloud top of about 21,000 feet.

The report contained experimental Current Icing Potential (CIP) plots that a scientist at the National Center for Atmospheric Research in Boulder, Colorado, provided. It noted that the CIP product (Supercooled Liquid Droplets (SLD) and Ice) combines sensor and numerical model data to provide a three-dimensional diagnosis of the icing environment. The current CIP output consists of a likelihood field ranging from 0 (no icing) to 100 (certain icing). While this is not yet calibrated as a true probability value, CIP has value in pointing out real differences in the likelihood of encountering icing at a given location.

The plots were: icing severity category composite, maximum SLD potential in the column, maximum potential in column for experiencing icing field, icing severity at 12,000 feet, potential for SLD ice at 12,000 feet, potential for experiencing ice at 12,000 feet, icing severity at 9,000 feet, potential for experiencing ice at 9,000 feet, potential for SLD ice at 9,000 feet, and current icing potential.

DIGITAL FLIGHT DATA RECORDER (DFDR)

A Safety Board specialist examined the DFDR data, and the factual report is part of the public docket.

About 6 minutes after takeoff, the airplane was passing through 9,200 feet. The airspeed began to decline from 180 knots, and the pitch angle began to increase. Around 2 minutes later, at 1439:36, the pitch of the airplane was 14 degrees up and the roll was neutral. One second later, the altitude reached a maximum recorded value of 11,712 feet, and the airplane was in a 16-degree left roll. During the next second, the autopilot disconnected, and the airspeed registered 118 knots.

The rate of airspeed decay accelerated in the final 10 seconds before the autopilot disconnected. The airplane departed controlled flight at an airspeed of 130 knots indicated airspeed (KIAS), and before the stall warning activated. The DFDR data also revealed that about 26 seconds before the stall roll departure, while the airplane was at a speed of 144 KIAS, the airplane began to experience a slight rolling anomaly that was counter to the direction of the aileron input. Aileron input from the autopilot arrested this slight rolling motion.

The airplane rolled to 86 degrees left wing down, and then went through a series of roll and pitch movements. It reached 140 degrees of right roll, and a maximum pitch down angle of 48 degrees. It rolled to 75 degrees left wing down, and a pitch of 31 degrees nose down. It then rolled to 94 degrees right wing down, followed by a pitch angle to 40 degrees nose down. Starting at 1440, the altitude and outside air temperature parameters stopped recording valid data for a period of 15 seconds. At 1440:06, the airplane’s pitch angle began to increase. It passed through 0 degrees about 6 seconds later at an airspeed of 219 knots, and a recorded maximum vertical acceleration of 2.5 g’s. The pitch reached 23 degrees nose up at 1440:24; the minimum recorded airspeed value of 105 knots occurred 11 seconds later while the airplane was at an altitude of 7,840 feet. The parameters began to stabilize after this time.

The DFDR data disclosed that 14 seconds after the initial stall, both ailerons simultaneously traveled to the full up position for approximately 14 seconds.

DFDR Study

The DFDR specialist participated in a ground test to validate the control wheel and aileron position data recorded on the event flight and gather additional data related to a breakout scenario. The test did demonstrate that, under a normal scenario, the control wheel being manipulated would lead the control wheel not being manipulated. Also, it showed that moving the control wheel would drive the ailerons to their maximum range values, but moving the ailerons would not drive the control wheels to full range. Additionally, in manually manipulating the ailerons, the left one did not reach its full upwards range.

TESTS AND RESEARCH

Performance Study

A Safety Board specialist conducted a vehicle performance study, which is a part of the public docket. It showed that the airplane’s aerodynamics degraded with time until the airplane stalled. This stall occurred at a lower angle of attack than would be expected for an uncontaminated airframe. The study concluded that the aerodynamic degradation and early stall was consistent with airframe icing.

ADDITIONAL INFORMATION

Training

American Eagle had a recurrent and requalification simulator training syllabus for captains and first officers. It included approach to stalls in the takeoff, clean, and landing configurations. It also included unusual attitudes recoveries from nose low and nose high positions. One section dealt with normal and abnormal emergency situations operations including anti-icing and deicing systems, stall warning, and stick pusher.

American Eagle’s advanced aircraft maneuvering program (AAMP) includes a review of phenomena that cause upset events and unusual attitude recovery procedures.

The Operations Group chairperson interviewed several American Eagle pilots. All the pilots interviewed, including the incident captain and first officer, stated that they never practiced encountering a stall in icing conditions as part of their simulator training. Additionally, the pilots could not recall ever having the opportunity to practice a complete stall in the simulator, as they were always instructed to recover at the first indication of an impending stall.

Minimum Airspeeds for Flight in Icing Conditions

American Eagle’s 340B+ Airplane Operating manual (AOM) calls for flight crews to compute a final clean airplane climb speed, or Vcln, and to add 15 knots to that value to determine the minimum speed (Vcln+15) in icing conditions. For the incident flight, Vcln was computed to be 126 knots indicated airspeed (KIAS), and the minimum speed in icing conditions was 141 KIAS.

Use of Autopilot in Icing Conditions

The limitations section of the American Eagle 340B+ AOM stipulates that the indicated airspeed (IAS) mode is the only authorized flight director/autopilot mode if an airplane is climbing when ice accretion is occurring, or with residual ice on the airframe. In IAS mode, the flight control computer gives pitch attitude commands to maintain the indicated airspeed existing at the time of mode engagement. In the vertical speed (VS) mode of the incident flight, the autopilot would sacrifice airspeed to maintain climb rate.

Recommendations

The Safety Board issued several recommendations as a result of the investigation.

Urgent recommendation A-06-48 asked the FAA to require all operators of Saab SF340 series airplanes to instruct pilots to maintain a minimum operating airspeed of 1.45xVs during icing encounters and before entering known or forecast icing conditions and to exit icing conditions as soon as performance degradations prevent the airplane from maintaining 1.45xVs.

Recommendation A-06-49 asked the FAA to require the installation of modified stall protection logic in Saab SF340 series airplanes certified for flight into known icing conditions.

Recommendation A-06-50 asked the FAA to require the installation of an icing detection system on Saab SF340 series airplanes.

Recommendation A-06-51 asked the FAA to require all operators of turbo propeller-driven airplanes to instruct pilots, except during intermittent periods of high workload, to disengage the autopilot and fly the airplane manually when operating in icing conditions.

The Safety Board also reiterated the following recommendations to the FAA.

Recommendation A-03-53 asked the FAA to convene a panel of airplane design, aviation operations, and aviation human factors specialists, including representatives from the National Aeronautics and Space Administration, to determine whether a requirement for the installation of low-airspeed alert systems in airplanes engaged in commercial operations under 14 Code of Federal Regulations Parts 121 and 135 would be feasible, and submit a report of the panel’s findings.

Recommendation A-03-54 asked that if the panel requested in Safety Recommendation A-03-53 determines that a requirement for the installation of low-airspeed alert systems in airplanes engaged in commercial operations under 14 Code of Federal Regulations Part 121 and 135 is feasible, establish requirements for low-airspeed alert systems, based on the findings of the panel.


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

Phoenix: Mesa Runway Incident


Contact photographer David Marshall
What: Dehavilland DHC-8-202 en route from Guaymas, Mexico to Phoenix
Where: Phoenix Sky Harbor International Airport
When: April 20, 2009
Who: The captain, first officer, flight attendant, and 14 passengers
Why: The plane struck a ground power unit with the right propeller while taxiing to parking. NO injuries were reported.


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

Royal Air Maroc Boeing 767-300


Contact photographer Agustin Anaya
What: Royal Air Maroc Boeing 767-30 en route from Casablanca (Morocco) to New York John F. Kennedy Airport
Where: JFK
When: Apr 20th 2009
Why: Wake turbulence was such that the landing was hard. Complaints about the hard landing prompted plane inspection which turned up wrinkles found in the fuselage. The plane was grounded for repairs and further inspection.


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

Depressurized Airbus Lands in London


Contact photographer Bruce Leibowitz
What: Turkish Airlines Airbus A340-300, en route from New York JFK,NY to Istanbul Ataturk
Where: divert to London Heathrow
When: Apr 16th 2009 6:30 local
Who: 185 passengers and 15 crew
Why: The cabin depressurized en route, and the flight was diverted to Heathrow for a safe landing. Although passengers experienced shortness of breath and ear pain, oxygen masks never did deploy.


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

Ill Alitalia Pilot Down in Shannon


Pictured: an Alitalia Boeing-767-3S1
Click to view full size photo at Airliners.net
Contact photographer Josh May
What: Alitalia Boeing 767, travelling from Milan in Italy to New York’s JFK
Where: Shannon Airport
When: Wednesday April 15 2009 5 PM
Who: 168 passengers and eleven crew
Why: When the pilot became ill, the flight landed at Shannon Airport. The pilot was hospitalized in Limerick and the passengers were treated to an overnight hotel stay and will continue to JFK on Thursday. Rumor on the pilot network is that the pilot had a heart attack.

iLVolo.it says it in Italian


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

Alaska Airlines Quick Fix


Click to view full size photo at Airliners.net
Contact photographer Michael Carter
What: Alaska Airline Boeing 737 Phoenix to Seattle
Where: Phoenix Sky Harbor International Airport
When: emergency landing around 6:40 a.m
Who: 113 passengers
Why: After an emergency with an overheating hydraulic pump, the flight landed back at the Phoenix airport after 15 minutes; and (after 45 minutes of maintenance) was back in the air 1.5 hours behind schedule, but successfully en route to Seattle

George’s Point of View

Maintenance Maintenance Maintenance…


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

Fed Ex Crash in High Wind in Tokyo


Click to view full size photo at Airliners.net
Contact photographer Michael Carter
What: FedEx McDonnell Douglas MD-11F en route from Guangzhou Baiyun International Airport, China to Tokyo-Narita Airport, Japan
Where: Crash occurred on the runway Tokyo-Narita Airport, Japan
When: 23 MAR 2009 06:48
Who: 2 crew members aboard, both fatalities
Why: The plane landed in high winds, bounced on to the nosewheel, banked left and when the left wing, hit the runway, a fire ensued.

News Footage includes audio of Bob Francis, former NTSB VC


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 Hydraulics Failure


Click to view full size photo at Airliners.net
Contact photographer Mark Kopczak
What: United Airlines Airbus A319-100 registration N836UA en route from Chicago O’Hare,IL to Vancouver,BC
Where: runway 08R Vancouver
When: Mar 14th 2009
Why: After the failure of the hydraulics system on approach to Vancouver, the airbus managed a safe landing.

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

Site Credits