MAK, the Interstate Aviation Committee investigated the Mar 22nd crash of the Aviastar-TU Tupolev TU-204-100 ferry flight en route from Hurghada Egypt to Moscow, and banned it from operating as a passenger airline. On the day of the crash, after the flight control computer failed, the Tu-204 flew 700 feet left of the runway when it was landing. The pilot was found to have “poor training” on simulators that did not correspond with the plane. According to Flight Global, “the crew failed to execute a go-around.”
Similar Posts
NTSB TO HOLD SYMPOSIUM ON AIRLINE CODE-SHARING ARRANGEMENTS AND THEIR ROLE IN AVIATION SAFETY
National Transportation Safety Board
Washington, DC 20594
August 16, 2010The National Transportation Safety Board will hold a two-day symposium on the role that airline code-sharing arrangements play in aviation safety. The event, chaired by NTSB Chairman Deborah A.P. Hersman, will be held on October 26-27, 2010, in Washington, DC.
Code-sharing is a marketing arrangement in which one airline places its designator code on a flight operated by another airline, then sells and issues tickets for that flight.
Recent NTSB investigations of accident flights operated under code-sharing arrangements include the February 2009 accident near Buffalo, New York, in which a Colgan Air flight was operated as Continental Connection; a 2007 accident in Traverse City, Michigan, in which a Pinnacle Airlines flight was operated as Northwest Airlink; a 2007 accident in Cleveland, Ohio, in which a Shuttle America flight was operated as Delta Connection; and a 2006 accident in Lexington, Kentucky, in which a Comair flight was operated as Delta Connection.
Today, most airlines participate in some type of code- sharing arrangement, either with domestic or international partners. More than half of passenger enplanements in the U.S. this year are on regional airlines, almost all of which are involved in code-sharing arrangements.
“In the past twenty years, code-sharing arrangements have so proliferated within commercial aviation that today the vast majority of airlines are involved in what are often complex business and operational arrangements.” said NTSB Chairman Deborah A.P. Hersman. “We have investigated many accidents in which passengers bought tickets on a major carrier and flew all or part of their trip on a different carrier – one that may have been operating to different safety standards than the carrier that issued the ticket. While all carriers are required to meet minimum standards, a clearer picture and deeper understanding of the best safety practices for code-sharing arrangements are the goals of this symposium.”
The symposium will be organized to elicit information on the following three issue areas: (1) structures, practices, and oversight of domestic and international code-sharing arrangements; (2) best practices regarding the sharing of safety information between airlines and their code-sharing partners; and (3) the role that a major airline would have in the family disaster assistance response for an accident involving a code-sharing partner.
These areas will be explored through presentations from major and regional airlines, industry organizations, and representatives of the traveling public.
The symposium, “Airline Code-Sharing Arrangements and Their Role in Aviation Safety” will be held at the NTSB Board Room and Conference Center, located at 429 L’Enfant Plaza, S.W., Washington, DC. A detailed agenda will be released closer to the date of the event.
- Air Safety | Brazil | politics
Tam: Business as usual?
With July’s fatal crash and a year of turmoil in the Brazilian airline sector, it has been a tough year for Brazil’s TAM Linhas Aéreas. Following months of air traffic controller strikes, airport delays and flight cancellations, one of Tam’s Airbus A320s overran the runway at São Paulo Congonhas airport in a catastrophe that claimed 199 lives.
TAM president Marco Antonio Bologna has been feeling the brunt of Brazil’s favorite blame game: “who is responsible?” Bologna is reluctant to discuss the accident other than to describe the measures taken by TAM to assist the victims’ families.
What did cause the crash?
Brazil’s aviation industry continues on in a climate of fear and mistrust.
NTSB Press Release: Pilot’s Failure to Maintain Altitude caused Maryland State Police Helicopter Crash in Maryland
Washington, DC – The National Transportation Safety Board today determined that the probable cause of the crash of a Maryland State Police (MSP) helicopter emergency medical services flight was the pilot’s attempt to regain visual conditions by performing a rapid descent and his failure to arrest the descent at the minimum descent altitude during a nonprecision approach.
On September 27, 2008, an Aerospatiale (Eurocopter), call sign Trooper 2 (N92MD), registered to and operated by the MSP as a public medical evacuation (medevac) flight, impacted terrain in District Heights, Maryland while on approach to Andrews Air Force Base (ADW). The pilot, one flight paramedic, one field provider, and one of two automobile accident patients being transported were killed. The other patient being transported survived with serious injuries from the helicopter accident and was taken to a local hospital.
The Board found that the pilot failed to adhere to instrument approach procedures when he did not prevent the helicopter’s descent at the MDA. The flight was cleared for an instrument landing system (ILS) approach. After the initial call to the ADW tower, the pilot reported that he could not capture the glideslope and was on a localizer approach. The controller responded that her ILS equipment status display was indicating no anomalies with the equipment. Post accident tests confirmed no anomalies with the instrument approach equipment and testing of the helicopter’s navigation equipment did not find any deficiencies that would have precluded the pilot from capturing the glideslope.
Furthermore, the Board concluded that although the descent rate and altitude information were readily available through cockpit instruments which the pilot had access to, he likely became preoccupied with looking for the ground, which he could not identify before impact because of the lack of external visual cues. Since there were no recorders on board the accident helicopter, the Safety Board could not determine why the pilot did not use other options available to conduct a safe landing in instrument conditions.
Several contributing factors to the cause of the accident, the Board noted, were the pilot’s limited recent instrument flight experience, the lack of adherence to effective risk management procedures by the Maryland State Police, the pilot’s inadequate assessment of the weather, which led to his decision to accept the flight, the failure of the Potomac Consolidated Terminal Radar Approach Control (PCT) controller to provide the current Andrews Air Force Base weather observation to the pilot, and the increased workload on the pilot due to inadequate Federal Aviation Administration air traffic control handling by the Ronald Reagan National Airport Tower and PCT controllers.
As a result of this accident investigation, the Safety Board issued recommendations to the Federal Aviation Administration, the MSP, Prince George’s County, and all public Helicopter Emergency Medical Service operators regarding pilot performance and training, air traffic control deficiencies, patient transport decisions, emergency response and FAA oversight.
A summary of the findings of the Board’s report will be available on the NTSB’s website at: http://www.ntsb.gov/events/Boardmeeting.htm
-30-
Media Contact: Keith Holloway (202) 314-6100
hollowk@ntsb.gov- Airbus | airliners.net | Lufthansa | weather | wind | wing strike
Lufthansa Wing Strike

Click to view full size photo at Airliners.net
Contact photographer Gerry StegmeierWhat: Lufthansa A320-200 en route from Munich to Hamburg
Where: Hamburg
When: Mar 1 2008
Who: 132 passengers and 5 crew
Why: On approach to Hamburg in stormy windy (47 knot wind gusts) weather, the left wing struck the runway on an attempted landing, veered, and had to make another go-round before a final landing.
Ural Airlines Flight Makes Emergency Landing in Saint Petersburg
Ural Airlines flight U6-365 had to return and make an emergency landing in Saint Petersburg, Russia, on December 7th.The Airbus A320-200 plane took off for Yekaterinburg, Russia, but had to turn back after the crew noticed disagreeing airspeeds.
The plane landed back safely. All one hundred and twenty-three passengers and six crew members remained unharmed.
Tragedy in Honduras

Click to view full size photo at Airliners.net
Contact photographer Nelson MejiaWhat: Central American Airways – CAA Let L-410UVP-E20 en route from San Pedro Sula-Ramon Villeda Morales Airport to Tegucigalpa-Toncontin
Where: Santa Ana, Cerro de Hula Honduras
When: Feb 14 2011
Who: 2 crew, 12 passengers, 14 fatalities
Why: The Central American Airways flight from San Pedro Sula to Tegucigalpa departed from San Pedro Sula at 07:04 for the 40 minute flight to Tegucigalpa and crashed at 8:02 in a forested area.Crash victims include labor leader, Israel Salinas Castellanos and Pedro Sula businessman Carlos Chahine, who served as minister Economy. The plane’s captain was Eduardo Ernesto Pach Pineda, and co-pilot Andersón Mejía. Salinas Elvir and Rodolfo Rovelo were also killed in the crash.
CREW:
1. Captain Oscar Anderson
2. Captain Eduardo Pach
PASSENGER LIST
1. Plutarch Molina
(Business Building)
2. Peter Jhon
3. Howar Jeams
4. Chuk Tom Klein
5. Joaquin Fernandez
6. Leda Cabrera
7. July Alvarenga
8. Israel Salinas
9. Carlos Chaín
10. Alejandra Figueroa
11. Rodolfo Rovelo
12. Sara Villacorta
