<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The Politically Correct Airplane Crash</title>
	<atom:link href="http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/</link>
	<description></description>
	<pubDate>Thu, 29 Jul 2010 13:07:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: ADAT ENGINEER</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-236895</link>
		<dc:creator>ADAT ENGINEER</dc:creator>
		<pubDate>Fri, 12 Feb 2010 17:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-236895</guid>
		<description>Accident on November 15, 2007at Toulouse Blagnac Airportto Airbus A340-600 serial number 856
CAUTION
This report presents the technical conclusions reached by the BEA on the circumstances and causes of this accident.In judicial terms, this occurrence does not constitute an aviation accident or incident, since none of the people on board intended to perform a flight. Nevertheless, the term ‘accident’ will be used in this report, as commonly understood and accepted.In accordance with Annex 13 of the Convention on International Civil Aviation, with EC directive 94/56/CE and with Law N°99-243 of 29 March 1999, the investigation of the accident is intended neither to apportion blame, nor to assess individual or collective responsibility. The sole objective is to draw lessons from this occurrence which may help to prevent future accidents or incidents.Consequently, the use of this report for any purpose other than for the prevention of future accidents could lead to erroneous interpretations.
Table of Contents
Caution
Glossary
Synopsis
Organization of the investigation
1 – FACTUAL INFORMATION1.1 Summary of the event1.2 Injuries and fatalities1.3 Aircraft damage1.4 Other damage1.5 Personnel information1.5.1 Persons on the flight deck1.6 Aircraft information1.7 Meteorological conditions1.8 Communications1.9 Airfield information1.10 Flight recorders1.10.1 CVR1.10.2 FDR1.10.3 Readout of the flight recorders1.11 Information on the site and the wreckage1.12 Medical and pathological Information1.13 Tests and research1.14 Information on the organizations and management1.15 Additional information1.15.1 Testimonies
2 – ANALYSIS2.1 Test procedure2.2 Reactions in the cockpit2.3 Oversight of these activities
3 - CONCLUSIONS3.1 Findings of the investigation3.2 Causes of the accident3.3 Measures taken following the accident
4 – SAFETY RECOMMENDATIONS
GLOSSARY
AESA Agence Européenne de la Sécurité AérienneAMM Aircraft Maintenance ManualBEA Bureau d’Enquêtes et d’Analyses(BEAD-Air) Bureau Enquête Accidents Défense AirCAM Customer Acceptance ManualCEV Centre d’Essais en VolCVR Cockpit Voice RecorderEPR Engine Pressure RatioFDR Flight Data RecorderGSAC Groupement pour la Sécurité de l’Aviation CivileJAR Joint Aviation RulesUTC Coordinated Universal Time
SYNOPSIS
Date of accidentThursday November 15, 2007 at 1610 hrs (1)
AircraftAirbus A-340-600Registered as F-WWCJ
Location of accidentToulouse Blagnac Airport
OwnerAirbus
Purpose of flightEngine ground run test
Persons on board9
Note (1): Unless stated otherwise, the times quoted in this report refer to Coordinated Universal Time (UTC). One hour should be added to obtain the local time in France at the time of the event.
1- FACTUAL INFORMATION
1.1 Summary of the event
On 15 November 2007, the Airbus A-340-600 F-WWCJ was undergoing static engine ground runs on the Toulouse-Blagnac airfield. The purpose was to test various systems with technicians of the airline that had ordered the aircraft. No wheel chocks were used. On completion of these tests, after having stopped and inspected the engines, the technicians started the engines again for another engine run at high power to find the origin of oil leaks.
Approximately three minutes after power up, the aircraft began to move forward. The technician in the left seat perceived the motion and informed the Airbus technician in the right seat. The latter acted on the brake pedals and then released the parking brake. The DFDR (digital flight data recorder) then indicates a partial release of the brake pedal command. Since the aircraft continued to move forward, he tried to modify its trajectory by using the nose wheel steering. The nose wheel gear quickly skidded sideways as the aircraft accelerated.The aircraft struck the slope of the anti-blast wall. The forward fuselage broke and fell down on the other side of the wall.
There were thirteen seconds between the start of aircraft movement and the collision with the wall.
1.2 Injuries and fatalities
Fatal - 0Serious - 4Slight/None – 5
1.3 Aircraft damage
The aircraft was destroyed.
1.4 Other damage
The anti-blast wall was damaged.
1.5 Personnel information
The ground tests during the customer delivery phase are performed under the responsibility of only one ground test technician, an Airbus employee. He was usually accompanied by one or more persons representing the customer, and sometimes by other Airbus employees. Airbus had no special qualification requirement toward the customer representatives attending testing. The representatives of the customer sitting in the cockpit normally had observer roles, but it could happen that the ground test technician allowed the representative of the customer to participate, for example by allowing him to taxi.
During this test, the technician in charge of ground testing was in the right seat, an aeronautical technician representing the customer was in the left seat and a flight test engineer was on the jump seat. The customer representative and the flight test engineer had no specific function in the aircraft handling. The role of the customer representative was to observe the parameters during testing to ensure compliance with the requirements of the customer.
1.5.1 Persons on the flight deck
1.5.1.1 Ground test technician in the right seat:
Male, 41 years old, Airbus employee, responsible for the test• Line maintenance technician since 1992• Ground test technician since 1998• Course for engine tests and ground runs on A330 - A340 in 1998.• RR Trent 500 familiarization course in May 2000• Attached to the Flight Test / Aircraft Delivery Department since 2004• Flight test engineer since 2004• Recurrent training for A-330/340 engine test in October 2006
1.5.1.2 Aeronautical technician in the left seat:
Male, 36 years old, employee of a maintenance company (GAMCO), which maintains the Etihad Airlines aircraft and carries out their acceptance tests.• Technician for the GAMCO company since 1997• Courses at Lufthansa Technik and Airbus in 2002• A-340-600 engine ground run training in 2006
1.5.1.3 Flight test engineer on the jump seat:
Male, 42 years old, Airbus employee• Flight test engineer in 2000• Attached to the Flight Test / Delivery Department since 2000• Authorized to perform engine tests on Airbus family aircraft• Commercial airplane pilot since 1998• A-320 type rating in 2004• ATR-42 type rating in 20061.6 Aircraft InformationAirframe:• Manufacturer: Airbus• Type: A340-600• Serial Number: 856• Provisional Registration: F-WWCJEngines:Engine #1 Engine #2 Engine # 3 Engine #4Manufacturer Rolls-Royce Rolls-Royce Rolls-Royce Rolls-Royce
Type Trent Trent Trent Trent556A2-61 556A2-61 556A2-61 556A2-61
Serial Number 71492 71490 71491 71493Total Time 24 h 26 h 24 h 23 h
Engine control parameter
The thrust of the A-340-600 engines is expressed in terms of the EPR (Engine Pressure Ratio) which represents the ratio of total pressure between the turbine outlet and compressor inlet. This ratio varies approximately between 1 (ground idle) and 1.41 (full thrust, or around 28000 daN).
Weight and balance
The aircraft weight was 223 tons including 40 tons of fuel, and the CG was at 25.8%. Ground tests are usually performed with 80 tons of fuel. The maximum certified take-off weight is 380 tons.
Braking system
Description of the system
The A-340-600 has two Main LG, one on the right side and one on the left, one Central LG and one Nose LG. Each MLG and the CLG have 4 wheels each. The CLG is slightly aft of both MLG. Each MLG wheel and CLG wheel is equipped with a braking system, and each brake is powered by two independent hydraulic systems. The NORMAL braking pressure is controlled through the green system. The blue system powers the ALTERNATE braking.
When the parking brake is set, the blue system applies 2500 psi to both MLG. The CLG brakes are not operated by the parking brake.
When the brake pedals are pressed, the green system operates both MLG and the CLG, with the amount of pressure applied depending of the position of the brake pedals. The green system pressure is inhibited as long as the parking brake is activated.
If the parking brake is released while simultaneously pressing on the brake pedals, the system allows both circuits to be pressurized together, while the ALTERNATE circuit depressurizes. This applies only to both MLG and the total amount of pressure from both circuits is limited to 2770 psi.
In addition, the braking of the CLG wheels is automatically reduced when the nose wheels are steered. When the nosewheel steering command is greater than 20 degrees, the CLG braking is completely inhibited.
Certification standard
The JAR25.735d regulation for certification indicates that the parking brake must be designed to prevent the aircraft from moving on a dry paved runway with one engine at maximum thrust, the others being at ground idle. In these circumstances, the A-340-600 parking brake must develop a minimal braking force of 28000 daN or 3500 daN per braked wheel. The system was designed to develop a braking force of 8500 daN per braked wheel with a brake pressure of 2500 psi.
1.7 Meteorological conditions
At 1600 hrs, the meteorological conditions measured at the Toulouse Blagnac airfield were:
-Wind 330°/16 knots, visibility greater than 10 km, cloud cover few at 4100 feet, temperature 5°C, dewpoint -5°C, QNH 1019 hPa.
1.8 Communications
The ground test technician, who taxied the aircraft, was in contact with the ground controller of the St-Martin watchtower. This frequency, specific to Airbus, makes it possible to control the traffic during the taxiing of aircraft on the Airbus site of the Toulouse Blagnac airfield.
1.9 Airfield information
The accident occurred on the BIKINI ramp. This area is dedicated to testing and is part of the manufacturer’s facilities.
No grip data for the surface of the test area were available before the accident. To enable a quantitative analysis of the braking performance, it was necessary to undertake measurements of slipperiness. These measurements were carried out in conditions close to those on the day of the accident. The measured friction coefficients were between 0.65 and 0.68. These values correspond to the coefficient of a dry runway in good condition.
1.10 Flight recorders
In accordance with the applicable regulations, the aircraft was equipped with a cockpit voice recorder (CVR) and a flight data recorder (FDR).
1.10.1 CVR
The CVR is a recorder with static storage capable of storing the last two hours of recording.
• Manufacturer: L-3 Communications• Model: FA 2100• Type Number: 2100-1020-02• Serial Number: 455462
The following tracks are recorded:
1. VHF and mouth microphone from the third seat (rear location)2. VHF and mouth microphone from the captain’s seat (left side)3. VHF and mouth microphone from the first officer’s seat (right side) and FSK signal4. Area microphone
The recording quality was good and lasts a little more than two hours. The event has been recorded in its entirety.
1.10.2 FDR
The FDR is a recorder with static storage capable of reproducing at least the last twenty five hours of recording.
• Manufacturer: L-3 Communications• Model: FA 2100• Type Number: 2100-4043-02• Serial Number: 440952
The data are of good quality and the event could be identified at the end of the recording. The graphs of the recorded significant parameters appear in the annex.
1.10.3 Readout of the flight recorders
The CVR and FDR have been synchronized using the UTC time recorded in the FDR and the “Master Caution” “Single Chime” identified on the CVR.
The aircraft arrives at the BIKINI area approximately 14:19It is at a magnetic heading of 312 degrees. The parking brake is set and active.
During the tests between 14:19 and 14:58 the maximum EPR values are between 1.04 and 1.22
The last engine ground run is started at 15:58. The aircraft is still not moving.
Between 15:58:10 and 15:59:03 the thrust is increased gradually from idle to a steady value of 1.25 EPR. This engine thrust setting corresponds to a position of the thrust levers between MCT (Max Continuous Thrust) and MTO (Max Take Off Thrust).
The ALTERNATE pressure values are close to 2600 psi for the wheels 1,2,5,6 (left gear) and 3,4,7,8 (right gear). They are at 64 psi for the wheels 9,10,11,12 (central gear) (2).
Note (2): Brake pressure values are recorded in increments of 64 psi
At 16:02:06 the person in the right seat starts talking but is interrupted at 16:02:08 by the person in the left seat who announces :“Euh … cabin is … aircraft is moving forward”
The first significant LONGITUDINAL ACCELERATION parameter values showing a forward acceleration of the aircraft are observed around 16:02:07. The recorded ground speed starts to increase at 16:02:09 (3)
Note (3): Ground Speed values are recorded in increments of 1 kt.
Between 16:02:08 and 16:02:13 the ground speed increases from 0 to 4 kt.
At 16:02:11 the person on the left seat again says :“Aircraft is moving forward”
An action on the brake pedals is recorded from around 16:02:11
The parking brake is deactivated around 16:02:13The person on the right seat announces :“Parking brake off”
From the moment the park brake is released:• the brake pedals are briefly released on two occasions• the ALTERNATE circuit braking pressures drop below 192 psi• the NORMAL circuit braking pressures on the MLG are consistent with the brake pedals position on both right and left sides, and increase from 300 to 2500 psi in one second• the NORMAL circuit braking pressures for the CLG reach a maximum of 192 psi at 16:02:14 and then decrease to 64 psi and stabilize at that value• the wheel speed values which were still recorded as zero (the sensors do not work until a wheel speed of 3 to 5 kt) become positive and are consistent with recorded ground speed and aircraft movement• the recorded ground speed increases rapidly from 4 to 31 kt in seven secondsBetween 16:02:13 and 16:02:15 the command given from the right-hand side to the NWS (Nose Wheel Steering) goes from 0 to -75 degrees (full right command against the stops). The evolution of the nose wheel angle until impact is consistent with that command. From 16:02:15 the magnetic heading of the aircraft begins to increase; it goes from 312 to 349 degrees in seven seconds.
The angle of the nose gear reaches 77 degrees right at 16:02:19 and remains at that value until the end of the recording. From 16:02:18 we can hear on the CVR severe vibration noises followed by impact noises.
The thrust levers did not move until 16:02:20 when they are retarded to the IDLE detent. The EPR values of the 4 engines start to decrease immediately afterward.
The longitudinal acceleration becomes significantly positive, indicating an aircraft deceleration, around 16:02:20.5
FDR recording ends between 16:02:21 and 16:02:22CVR recording ends at 16:02:23
1.11 Information on the site and the wreckage
The aircraft was involved in a collision with the anti-blast wall located at the north side of the BIKINI ramp. It came to rest leaning on the wall, pointing to the north. The tail cone and the tip of the right wing were in contact with the ground. Only the right MLG was touching the ground.
The aircraft had struck the anti-blast wall at an angle of about 30 degrees. The underside of the forward cabin was torn over about fifteen meters and folded to the ground when passing the anti-blast wall.
The cockpit crashed to the ground north of the wall. The avionics bay containing most of the flight control computers, located under the cockpit, was completely destroyed.
Engine #1 and #2 hit the wall and were severely damaged. The #2 pylon was twisted. Engine #3 and #4 kept running after impact and did not stop immediately. It was not possible to shut them down, neither by activating the fire extinguisher handles nor by positioning the thrust levers on OFF. Water and foam spray on engine #4 managed to extinguish it at 18:48.
Due to the proximity of the wall this was not was not possible with engine #3 in a similar manner to engine #4. It shut down by itself only on November 16 at 01:25 after it had consumed all the fuel from its collector tank.
The NWG was broken and separated from the fuselage. The wheels were oriented to the right and had a steering angle close to the maximum value. The nosewheel tires had cuts in them, and showed marks of rubbing at right angles to the tread.
Ground tire traces
For the following descriptions, the distance reference is taken from the point of impact on the wall, and back along the aircraft trajectory.
A first tire trace, corresponding to one of the internal wheels of the right MLG, is visible starting at 120 meters over a length of approximately 10 meters. The trace of the external tires is present but less marked. Those traces are oriented along an axis with a magnetic heading of 330 degrees. No trace of the left MLG tires was observed.
At 83 meters, we can see the first NWG marks. They curve toward a northerly heading. They are initially parallel, then at 50 meters converge to leave only one single trace. By then, the NLG is no longer directional.
Symmetrical braking traces from both MLG are present from around 60 meters until the wall.
1.12 Medical and pathological information
The investigation did not highlight any medical anomalies likely to have deteriorated the capacities of the occupants.
1.13 Tests and research
Video camera
The recording of a video camera permanently filming the BIKINI area was reviewed. It shows the aircraft during the last test. At first the aircraft moves slowly then suddenly accelerates. While the path begins to slowly turn to the right, the NLG starts skidding sideways. The plane continues on its path until it hits the wall. The forward section rises, falls back on the wall and the fuselage breaks. There are flames at engines #1 and #2 as well as on the aft section of the aircraft.
By looking at the recordings from several days before the accident, it can be seen that some tests are carried out with wheel chocks and some others without.
Analysis of braking force and surface grip
The braking system of the aircraft has been modelized, in order to better understand the cause of the aircraft having started to move. The modelling uses the theoretical system functioning as described in paragraph 1.6 and is based on the values of the brake pressure parameters recorded by the FDR. The values of the EPR parameters of the four engines have also been used to determine the total thrust.
Braking force
For each of the braked wheels, the maximum braking force created by the brake pressure is determined based on the specification of the brakes, as a function of the recorded pressure. The overall braking force is obtained by summing the braking forces from the 12 wheels. When the parking brake alone is used, the brake pressure on the CLG wheels is zero and only the MLG wheels contribute to braking.
Slip resistance force
For each of the wheels, the value of the slip resistance is equal to the weight supported by the wheel multiplied by the friction coefficient μ between tire and tarmac. The simulation allows computation of the limit friction coefficient value below which the wheels would slip, under certain mass distribution assumptions. In the same way, the forces of slip resistance for each of the wheels are summed to obtain the overall slip resistance force.
Engine thrust
The thrust of the engines was calculated from the recorded EPR parameters and from manufacturer data, based on the day conditions (320 ft, nil speed, ISA -9C, no bleed air from engines). It stabilized at approximately 83500 daN.
Results
The model allows calculation of the theoretical changes in thrust and the maximum braking force developed by the braking system, and compare these to the slip limit force above which the wheels start to slip. For the aircraft to remain motionless, it is necessary that the thrust is less than both the maximum braking force developed by the system and the slip limit force.
Throughout the last test, the thrust of the engines and the maximum braking force on the parking brake are very close. To obtain under the same conditions a slip limit force equivalent to the thrust force, a friction coefficient μ of 0.687 is necessary. Given the measured friction coefficient values, it is reasonable to believe that the aircraft was quickly on the edge of slipping.
The fact that a balance, even fragile, has existed for about three minutes confirms that the brakes were functioning in accordance with their specifications.
Therefore, modeling has allowed to establish, with a reasonable confidence level, that during the last test the thrust and braking forces compensated each other, but that the balance of those forces was particularly precarious.
Thus, the aircraft remained motionless with 8 wheels braked through the parking brake, then started moving. Several factors may have contributed to the aircraft starting to move, notably :• the vibrations created by the engines• the reduction of weight due to fuel consumption (about 1270 kg)• a slight local brake pressure reduction on one of the wheels
When the parking brake was released, the application of the brake pedals never allowed to attain the same level of braking action despite the fact that brakes were applied to 12 wheels. This is due to two factors: first, the actions on the brake pedals were not sustained at the maximum level, and, secondly, the action on the NWS very quickly led to inhibiting the CLG braking. The resulting braking during the motion varied between 65 and 95% of the braking level obtained before the aircraft movement&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('236895','ADAT ENGINEER'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('236895','ADAT ENGINEER','Accident on November 15, 2007at Toulouse Blagnac Airportto Airbus A340-600 serial number 856\r\nCAUTION\r\nThis report presents the technical conclusions reached by the BEA on the circumstances and causes of this accident.In judicial terms, this occurrence does not constitute an aviation accident or incident, since none of the people on board intended to perform a flight. Nevertheless, the term &#226;accident&#226; will be used in this report, as commonly understood and accepted.In accordance with Annex 13 of the Convention on International Civil Aviation, with EC directive 94\/56\/CE and with Law N&#194;&#176;99-243 of 29 March 1999, the investigation of the accident is intended neither to apportion blame, nor to assess individual or collective responsibility. The sole objective is to draw lessons from this occurrence which may help to prevent future accidents or incidents.Consequently, the use of this report for any purpose other than for the prevention of future accidents could lead to erroneous interpretations.\r\nTable of Contents\r\nCaution\r\nGlossary\r\nSynopsis\r\nOrganization of the investigation\r\n1 &#226; FACTUAL INFORMATION1.1 Summary of the event1.2 Injuries and fatalities1.3 Aircraft damage1.4 Other damage1.5 Personnel information1.5.1 Persons on the flight deck1.6 Aircraft information1.7 Meteorological conditions1.8 Communications1.9 Airfield information1.10 Flight recorders1.10.1 CVR1.10.2 FDR1.10.3 Readout of the flight recorders1.11 Information on the site and the wreckage1.12 Medical and pathological Information1.13 Tests and research1.14 Information on the organizations and management1.15 Additional information1.15.1 Testimonies\r\n2 &#226; ANALYSIS2.1 Test procedure2.2 Reactions in the cockpit2.3 Oversight of these activities\r\n3 - CONCLUSIONS3.1 Findings of the investigation3.2 Causes of the accident3.3 Measures taken following the accident\r\n4 &#226; SAFETY RECOMMENDATIONS\r\nGLOSSARY\r\nAESA Agence Europ&#195;&#169;enne de la S&#195;&#169;curit&#195;&#169; A&#195;&#169;rienneAMM Aircraft Maintenance ManualBEA Bureau d&#226;Enqu&#195;&#170;tes et d&#226;Analyses(BEAD-Air) Bureau Enqu&#195;&#170;te Accidents D&#195;&#169;fense AirCAM Customer Acceptance ManualCEV Centre d&#226;Essais en VolCVR Cockpit Voice RecorderEPR Engine Pressure RatioFDR Flight Data RecorderGSAC Groupement pour la S&#195;&#169;curit&#195;&#169; de l&#226;Aviation CivileJAR Joint Aviation RulesUTC Coordinated Universal Time\r\nSYNOPSIS\r\nDate of accidentThursday November 15, 2007 at 1610 hrs (1)\r\nAircraftAirbus A-340-600Registered as F-WWCJ\r\nLocation of accidentToulouse Blagnac Airport\r\nOwnerAirbus\r\nPurpose of flightEngine ground run test\r\nPersons on board9\r\nNote (1): Unless stated otherwise, the times quoted in this report refer to Coordinated Universal Time (UTC). One hour should be added to obtain the local time in France at the time of the event.\r\n1- FACTUAL INFORMATION\r\n1.1 Summary of the event\r\nOn 15 November 2007, the Airbus A-340-600 F-WWCJ was undergoing static engine ground runs on the Toulouse-Blagnac airfield. The purpose was to test various systems with technicians of the airline that had ordered the aircraft. No wheel chocks were used. On completion of these tests, after having stopped and inspected the engines, the technicians started the engines again for another engine run at high power to find the origin of oil leaks.\r\nApproximately three minutes after power up, the aircraft began to move forward. The technician in the left seat perceived the motion and informed the Airbus technician in the right seat. The latter acted on the brake pedals and then released the parking brake. The DFDR (digital flight data recorder) then indicates a partial release of the brake pedal command. Since the aircraft continued to move forward, he tried to modify its trajectory by using the nose wheel steering. The nose wheel gear quickly skidded sideways as the aircraft accelerated.The aircraft struck the slope of the anti-blast wall. The forward fuselage broke and fell down on the other side of the wall.\r\nThere were thirteen seconds between the start of aircraft movement and the collision with the wall.\r\n1.2 Injuries and fatalities\r\nFatal - 0Serious - 4Slight\/None &#226; 5\r\n1.3 Aircraft damage\r\nThe aircraft was destroyed.\r\n1.4 Other damage\r\nThe anti-blast wall was damaged.\r\n1.5 Personnel information\r\nThe ground tests during the customer delivery phase are performed under the responsibility of only one ground test technician, an Airbus employee. He was usually accompanied by one or more persons representing the customer, and sometimes by other Airbus employees. Airbus had no special qualification requirement toward the customer representatives attending testing. The representatives of the customer sitting in the cockpit normally had observer roles, but it could happen that the ground test technician allowed the representative of the customer to participate, for example by allowing him to taxi.\r\nDuring this test, the technician in charge of ground testing was in the right seat, an aeronautical technician representing the customer was in the left seat and a flight test engineer was on the jump seat. The customer representative and the flight test engineer had no specific function in the aircraft handling. The role of the customer representative was to observe the parameters during testing to ensure compliance with the requirements of the customer.\r\n1.5.1 Persons on the flight deck\r\n1.5.1.1 Ground test technician in the right seat:\r\nMale, 41 years old, Airbus employee, responsible for the test&#226;&#162; Line maintenance technician since 1992&#226;&#162; Ground test technician since 1998&#226;&#162; Course for engine tests and ground runs on A330 - A340 in 1998.&#226;&#162; RR Trent 500 familiarization course in May 2000&#226;&#162; Attached to the Flight Test \/ Aircraft Delivery Department since 2004&#226;&#162; Flight test engineer since 2004&#226;&#162; Recurrent training for A-330\/340 engine test in October 2006\r\n1.5.1.2 Aeronautical technician in the left seat:\r\nMale, 36 years old, employee of a maintenance company (GAMCO), which maintains the Etihad Airlines aircraft and carries out their acceptance tests.&#226;&#162; Technician for the GAMCO company since 1997&#226;&#162; Courses at Lufthansa Technik and Airbus in 2002&#226;&#162; A-340-600 engine ground run training in 2006\r\n1.5.1.3 Flight test engineer on the jump seat:\r\nMale, 42 years old, Airbus employee&#226;&#162; Flight test engineer in 2000&#226;&#162; Attached to the Flight Test \/ Delivery Department since 2000&#226;&#162; Authorized to perform engine tests on Airbus family aircraft&#226;&#162; Commercial airplane pilot since 1998&#226;&#162; A-320 type rating in 2004&#226;&#162; ATR-42 type rating in 20061.6 Aircraft InformationAirframe:&#226;&#162; Manufacturer: Airbus&#226;&#162; Type: A340-600&#226;&#162; Serial Number: 856&#226;&#162; Provisional Registration: F-WWCJEngines:Engine #1 Engine #2 Engine # 3 Engine #4Manufacturer Rolls-Royce Rolls-Royce Rolls-Royce Rolls-Royce\r\nType Trent Trent Trent Trent556A2-61 556A2-61 556A2-61 556A2-61\r\nSerial Number 71492 71490 71491 71493Total Time 24 h 26 h 24 h 23 h\r\nEngine control parameter\r\nThe thrust of the A-340-600 engines is expressed in terms of the EPR (Engine Pressure Ratio) which represents the ratio of total pressure between the turbine outlet and compressor inlet. This ratio varies approximately between 1 (ground idle) and 1.41 (full thrust, or around 28000 daN).\r\nWeight and balance\r\nThe aircraft weight was 223 tons including 40 tons of fuel, and the CG was at 25.8%. Ground tests are usually performed with 80 tons of fuel. The maximum certified take-off weight is 380 tons.\r\nBraking system\r\nDescription of the system\r\nThe A-340-600 has two Main LG, one on the right side and one on the left, one Central LG and one Nose LG. Each MLG and the CLG have 4 wheels each. The CLG is slightly aft of both MLG. Each MLG wheel and CLG wheel is equipped with a braking system, and each brake is powered by two independent hydraulic systems. The NORMAL braking pressure is controlled through the green system. The blue system powers the ALTERNATE braking.\r\nWhen the parking brake is set, the blue system applies 2500 psi to both MLG. The CLG brakes are not operated by the parking brake.\r\nWhen the brake pedals are pressed, the green system operates both MLG and the CLG, with the amount of pressure applied depending of the position of the brake pedals. The green system pressure is inhibited as long as the parking brake is activated.\r\nIf the parking brake is released while simultaneously pressing on the brake pedals, the system allows both circuits to be pressurized together, while the ALTERNATE circuit depressurizes. This applies only to both MLG and the total amount of pressure from both circuits is limited to 2770 psi.\r\nIn addition, the braking of the CLG wheels is automatically reduced when the nose wheels are steered. When the nosewheel steering command is greater than 20 degrees, the CLG braking is completely inhibited.\r\nCertification standard\r\nThe JAR25.735d regulation for certification indicates that the parking brake must be designed to prevent the aircraft from moving on a dry paved runway with one engine at maximum thrust, the others being at ground idle. In these circumstances, the A-340-600 parking brake must develop a minimal braking force of 28000 daN or 3500 daN per braked wheel. The system was designed to develop a braking force of 8500 daN per braked wheel with a brake pressure of 2500 psi.\r\n1.7 Meteorological conditions\r\nAt 1600 hrs, the meteorological conditions measured at the Toulouse Blagnac airfield were:\r\n-Wind 330&#194;&#176;\/16 knots, visibility greater than 10 km, cloud cover few at 4100 feet, temperature 5&#194;&#176;C, dewpoint -5&#194;&#176;C, QNH 1019 hPa.\r\n1.8 Communications\r\nThe ground test technician, who taxied the aircraft, was in contact with the ground controller of the St-Martin watchtower. This frequency, specific to Airbus, makes it possible to control the traffic during the taxiing of aircraft on the Airbus site of the Toulouse Blagnac airfield.\r\n1.9 Airfield information\r\nThe accident occurred on the BIKINI ramp. This area is dedicated to testing and is part of the manufacturer&#226;s facilities.\r\nNo grip data for the surface of the test area were available before the accident. To enable a quantitative analysis of the braking performance, it was necessary to undertake measurements of slipperiness. These measurements were carried out in conditions close to those on the day of the accident. The measured friction coefficients were between 0.65 and 0.68. These values correspond to the coefficient of a dry runway in good condition.\r\n1.10 Flight recorders\r\nIn accordance with the applicable regulations, the aircraft was equipped with a cockpit voice recorder (CVR) and a flight data recorder (FDR).\r\n1.10.1 CVR\r\nThe CVR is a recorder with static storage capable of storing the last two hours of recording.\r\n&#226;&#162; Manufacturer: L-3 Communications&#226;&#162; Model: FA 2100&#226;&#162; Type Number: 2100-1020-02&#226;&#162; Serial Number: 455462\r\nThe following tracks are recorded:\r\n1. VHF and mouth microphone from the third seat (rear location)2. VHF and mouth microphone from the captain&#226;s seat (left side)3. VHF and mouth microphone from the first officer&#226;s seat (right side) and FSK signal4. Area microphone\r\nThe recording quality was good and lasts a little more than two hours. The event has been recorded in its entirety.\r\n1.10.2 FDR\r\nThe FDR is a recorder with static storage capable of reproducing at least the last twenty five hours of recording.\r\n&#226;&#162; Manufacturer: L-3 Communications&#226;&#162; Model: FA 2100&#226;&#162; Type Number: 2100-4043-02&#226;&#162; Serial Number: 440952\r\nThe data are of good quality and the event could be identified at the end of the recording. The graphs of the recorded significant parameters appear in the annex.\r\n1.10.3 Readout of the flight recorders\r\nThe CVR and FDR have been synchronized using the UTC time recorded in the FDR and the &#226;Master Caution&#226; &#226;Single Chime&#226; identified on the CVR.\r\nThe aircraft arrives at the BIKINI area approximately 14:19It is at a magnetic heading of 312 degrees. The parking brake is set and active.\r\nDuring the tests between 14:19 and 14:58 the maximum EPR values are between 1.04 and 1.22\r\nThe last engine ground run is started at 15:58. The aircraft is still not moving.\r\nBetween 15:58:10 and 15:59:03 the thrust is increased gradually from idle to a steady value of 1.25 EPR. This engine thrust setting corresponds to a position of the thrust levers between MCT (Max Continuous Thrust) and MTO (Max Take Off Thrust).\r\nThe ALTERNATE pressure values are close to 2600 psi for the wheels 1,2,5,6 (left gear) and 3,4,7,8 (right gear). They are at 64 psi for the wheels 9,10,11,12 (central gear) (2).\r\nNote (2): Brake pressure values are recorded in increments of 64 psi\r\nAt 16:02:06 the person in the right seat starts talking but is interrupted at 16:02:08 by the person in the left seat who announces :&#226;Euh &#226;&#166; cabin is &#226;&#166; aircraft is moving forward&#226;\r\nThe first significant LONGITUDINAL ACCELERATION parameter values showing a forward acceleration of the aircraft are observed around 16:02:07. The recorded ground speed starts to increase at 16:02:09 (3)\r\nNote (3): Ground Speed values are recorded in increments of 1 kt.\r\nBetween 16:02:08 and 16:02:13 the ground speed increases from 0 to 4 kt.\r\nAt 16:02:11 the person on the left seat again says :&#226;Aircraft is moving forward&#226;\r\nAn action on the brake pedals is recorded from around 16:02:11\r\nThe parking brake is deactivated around 16:02:13The person on the right seat announces :&#226;Parking brake off&#226;\r\nFrom the moment the park brake is released:&#226;&#162; the brake pedals are briefly released on two occasions&#226;&#162; the ALTERNATE circuit braking pressures drop below 192 psi&#226;&#162; the NORMAL circuit braking pressures on the MLG are consistent with the brake pedals position on both right and left sides, and increase from 300 to 2500 psi in one second&#226;&#162; the NORMAL circuit braking pressures for the CLG reach a maximum of 192 psi at 16:02:14 and then decrease to 64 psi and stabilize at that value&#226;&#162; the wheel speed values which were still recorded as zero (the sensors do not work until a wheel speed of 3 to 5 kt) become positive and are consistent with recorded ground speed and aircraft movement&#226;&#162; the recorded ground speed increases rapidly from 4 to 31 kt in seven secondsBetween 16:02:13 and 16:02:15 the command given from the right-hand side to the NWS (Nose Wheel Steering) goes from 0 to -75 degrees (full right command against the stops). The evolution of the nose wheel angle until impact is consistent with that command. From 16:02:15 the magnetic heading of the aircraft begins to increase; it goes from 312 to 349 degrees in seven seconds.\r\nThe angle of the nose gear reaches 77 degrees right at 16:02:19 and remains at that value until the end of the recording. From 16:02:18 we can hear on the CVR severe vibration noises followed by impact noises.\r\nThe thrust levers did not move until 16:02:20 when they are retarded to the IDLE detent. The EPR values of the 4 engines start to decrease immediately afterward.\r\nThe longitudinal acceleration becomes significantly positive, indicating an aircraft deceleration, around 16:02:20.5\r\nFDR recording ends between 16:02:21 and 16:02:22CVR recording ends at 16:02:23\r\n1.11 Information on the site and the wreckage\r\nThe aircraft was involved in a collision with the anti-blast wall located at the north side of the BIKINI ramp. It came to rest leaning on the wall, pointing to the north. The tail cone and the tip of the right wing were in contact with the ground. Only the right MLG was touching the ground.\r\nThe aircraft had struck the anti-blast wall at an angle of about 30 degrees. The underside of the forward cabin was torn over about fifteen meters and folded to the ground when passing the anti-blast wall.\r\nThe cockpit crashed to the ground north of the wall. The avionics bay containing most of the flight control computers, located under the cockpit, was completely destroyed.\r\nEngine #1 and #2 hit the wall and were severely damaged. The #2 pylon was twisted. Engine #3 and #4 kept running after impact and did not stop immediately. It was not possible to shut them down, neither by activating the fire extinguisher handles nor by positioning the thrust levers on OFF. Water and foam spray on engine #4 managed to extinguish it at 18:48.\r\nDue to the proximity of the wall this was not was not possible with engine #3 in a similar manner to engine #4. It shut down by itself only on November 16 at 01:25 after it had consumed all the fuel from its collector tank.\r\nThe NWG was broken and separated from the fuselage. The wheels were oriented to the right and had a steering angle close to the maximum value. The nosewheel tires had cuts in them, and showed marks of rubbing at right angles to the tread.\r\nGround tire traces\r\nFor the following descriptions, the distance reference is taken from the point of impact on the wall, and back along the aircraft trajectory.\r\nA first tire trace, corresponding to one of the internal wheels of the right MLG, is visible starting at 120 meters over a length of approximately 10 meters. The trace of the external tires is present but less marked. Those traces are oriented along an axis with a magnetic heading of 330 degrees. No trace of the left MLG tires was observed.\r\nAt 83 meters, we can see the first NWG marks. They curve toward a northerly heading. They are initially parallel, then at 50 meters converge to leave only one single trace. By then, the NLG is no longer directional.\r\nSymmetrical braking traces from both MLG are present from around 60 meters until the wall.\r\n1.12 Medical and pathological information\r\nThe investigation did not highlight any medical anomalies likely to have deteriorated the capacities of the occupants.\r\n1.13 Tests and research\r\nVideo camera\r\nThe recording of a video camera permanently filming the BIKINI area was reviewed. It shows the aircraft during the last test. At first the aircraft moves slowly then suddenly accelerates. While the path begins to slowly turn to the right, the NLG starts skidding sideways. The plane continues on its path until it hits the wall. The forward section rises, falls back on the wall and the fuselage breaks. There are flames at engines #1 and #2 as well as on the aft section of the aircraft.\r\nBy looking at the recordings from several days before the accident, it can be seen that some tests are carried out with wheel chocks and some others without.\r\nAnalysis of braking force and surface grip\r\nThe braking system of the aircraft has been modelized, in order to better understand the cause of the aircraft having started to move. The modelling uses the theoretical system functioning as described in paragraph 1.6 and is based on the values of the brake pressure parameters recorded by the FDR. The values of the EPR parameters of the four engines have also been used to determine the total thrust.\r\nBraking force\r\nFor each of the braked wheels, the maximum braking force created by the brake pressure is determined based on the specification of the brakes, as a function of the recorded pressure. The overall braking force is obtained by summing the braking forces from the 12 wheels. When the parking brake alone is used, the brake pressure on the CLG wheels is zero and only the MLG wheels contribute to braking.\r\nSlip resistance force\r\nFor each of the wheels, the value of the slip resistance is equal to the weight supported by the wheel multiplied by the friction coefficient &#206;&#188; between tire and tarmac. The simulation allows computation of the limit friction coefficient value below which the wheels would slip, under certain mass distribution assumptions. In the same way, the forces of slip resistance for each of the wheels are summed to obtain the overall slip resistance force.\r\nEngine thrust\r\nThe thrust of the engines was calculated from the recorded EPR parameters and from manufacturer data, based on the day conditions (320 ft, nil speed, ISA -9C, no bleed air from engines). It stabilized at approximately 83500 daN.\r\nResults\r\nThe model allows calculation of the theoretical changes in thrust and the maximum braking force developed by the braking system, and compare these to the slip limit force above which the wheels start to slip. For the aircraft to remain motionless, it is necessary that the thrust is less than both the maximum braking force developed by the system and the slip limit force.\r\nThroughout the last test, the thrust of the engines and the maximum braking force on the parking brake are very close. To obtain under the same conditions a slip limit force equivalent to the thrust force, a friction coefficient &#206;&#188; of 0.687 is necessary. Given the measured friction coefficient values, it is reasonable to believe that the aircraft was quickly on the edge of slipping.\r\nThe fact that a balance, even fragile, has existed for about three minutes confirms that the brakes were functioning in accordance with their specifications.\r\nTherefore, modeling has allowed to establish, with a reasonable confidence level, that during the last test the thrust and braking forces compensated each other, but that the balance of those forces was particularly precarious.\r\nThus, the aircraft remained motionless with 8 wheels braked through the parking brake, then started moving. Several factors may have contributed to the aircraft starting to move, notably :&#226;&#162; the vibrations created by the engines&#226;&#162; the reduction of weight due to fuel consumption (about 1270 kg)&#226;&#162; a slight local brake pressure reduction on one of the wheels\r\nWhen the parking brake was released, the application of the brake pedals never allowed to attain the same level of braking action despite the fact that brakes were applied to 12 wheels. This is due to two factors: first, the actions on the brake pedals were not sustained at the maximum level, and, secondly, the action on the NWS very quickly led to inhibiting the CLG braking. The resulting braking during the motion varied between 65 and 95% of the braking level obtained before the aircraft movement'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-182171</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Tue, 17 Nov 2009 14:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-182171</guid>
		<description>
The accident report, in French. Some translating for those who don’t read Francais below.
&lt;a href="http://go2.wordpress.com/?id=725X1342&#38;site=airlineworld.wordpress.com&#38;url=http%3A%2F%2Fwww.bea.aero%2Fdocspa%2F2007%2Ff-cj071115%2Fpdf%2Ff-cj071115.pdf" rel="nofollow"&gt;http://www.bea.aero/docspa/2007/f-cj071115/pdf/f-cj071115.pdf&lt;/a&gt;
This is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:
A. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline’s behalf.
3 people in the cockpit for the test: 2 from Airbus, one from the contractor.
Running the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.
In the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.
In the “service” seat (like the navigator’s seat, only the A340 ain’t got no navigator, I don’t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.
B. There were two main causes: 1) no chocks were used to hold the aircraft’s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines – the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.
Short answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.
Contributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area’s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.
C. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning – 9 hrs later – when it ran out of gas: it was too jammed into the wall to get any water/foam into it.
&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('182171','Pete'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('182171','Pete','\r\nThe accident report, in French. Some translating for those who don&#226;t read Francais below.\r\n&#60;a href=\&#34;http:\/\/go2.wordpress.com\/?id=725X1342&#38;amp;site=airlineworld.wordpress.com&#38;amp;url=http%3A%2F%2Fwww.bea.aero%2Fdocspa%2F2007%2Ff-cj071115%2Fpdf%2Ff-cj071115.pdf\&#34; rel=\&#34;nofollow\&#34;&#62;http:\/\/www.bea.aero\/docspa\/2007\/f-cj071115\/pdf\/f-cj071115.pdf&#60;\/a&#62;\r\nThis is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:\r\nA. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline&#226;s behalf.\r\n3 people in the cockpit for the test: 2 from Airbus, one from the contractor.\r\nRunning the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.\r\nIn the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.\r\nIn the &#226;service&#226; seat (like the navigator&#226;s seat, only the A340 ain&#226;t got no navigator, I don&#226;t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.\r\nB. There were two main causes: 1) no chocks were used to hold the aircraft&#226;s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines &#226; the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.\r\nShort answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.\r\nContributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area&#226;s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.\r\nC. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning &#226; 9 hrs later &#226; when it ran out of gas: it was too jammed into the wall to get any water\/foam into it.\r\n'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>The accident report, in French. Some translating for those who don’t read Francais below.<br />
<a href="http://go2.wordpress.com/?id=725X1342&amp;site=airlineworld.wordpress.com&amp;url=http%3A%2F%2Fwww.bea.aero%2Fdocspa%2F2007%2Ff-cj071115%2Fpdf%2Ff-cj071115.pdf" rel="nofollow">http://www.bea.aero/docspa/2007/f-cj071115/pdf/f-cj071115.pdf</a><br />
This is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:<br />
A. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline’s behalf.<br />
3 people in the cockpit for the test: 2 from Airbus, one from the contractor.<br />
Running the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.<br />
In the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.<br />
In the “service” seat (like the navigator’s seat, only the A340 ain’t got no navigator, I don’t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.<br />
B. There were two main causes: 1) no chocks were used to hold the aircraft’s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines – the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.<br />
Short answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.<br />
Contributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area’s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.<br />
C. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning – 9 hrs later – when it ran out of gas: it was too jammed into the wall to get any water/foam into it.</p>
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('182171','Pete'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('182171','Pete','\r\nThe accident report, in French. Some translating for those who don&acirc;t read Francais below.\r\n&lt;a href=\&quot;http:\/\/go2.wordpress.com\/?id=725X1342&amp;amp;site=airlineworld.wordpress.com&amp;amp;url=http%3A%2F%2Fwww.bea.aero%2Fdocspa%2F2007%2Ff-cj071115%2Fpdf%2Ff-cj071115.pdf\&quot; rel=\&quot;nofollow\&quot;&gt;http:\/\/www.bea.aero\/docspa\/2007\/f-cj071115\/pdf\/f-cj071115.pdf&lt;\/a&gt;\r\nThis is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:\r\nA. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline&acirc;s behalf.\r\n3 people in the cockpit for the test: 2 from Airbus, one from the contractor.\r\nRunning the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.\r\nIn the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.\r\nIn the &acirc;service&acirc; seat (like the navigator&acirc;s seat, only the A340 ain&acirc;t got no navigator, I don&acirc;t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.\r\nB. There were two main causes: 1) no chocks were used to hold the aircraft&acirc;s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines &acirc; the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.\r\nShort answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.\r\nContributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area&acirc;s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.\r\nC. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning &acirc; 9 hrs later &acirc; when it ran out of gas: it was too jammed into the wall to get any water\/foam into it.\r\n'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-27378</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Tue, 30 Jun 2009 13:25:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-27378</guid>
		<description>I read up on plane crashes on the net every so often. I often find accidents all over the world which didn't involve loss of life or did not have passengers involved which I'd never heard about in the news. Check in airdisaster.com for eg, there are incidents all the time which I'll bet you didn't hear about (recent ones as well).&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('27378','Fred'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('27378','Fred','I read up on plane crashes on the net every so often. I often find accidents all over the world which didn\'t involve loss of life or did not have passengers involved which I\'d never heard about in the news. Check in airdisaster.com for eg, there are incidents all the time which I\'ll bet you didn\'t hear about (recent ones as well).'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>I read up on plane crashes on the net every so often. I often find accidents all over the world which didn&#8217;t involve loss of life or did not have passengers involved which I&#8217;d never heard about in the news. Check in airdisaster.com for eg, there are incidents all the time which I&#8217;ll bet you didn&#8217;t hear about (recent ones as well).
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('27378','Fred'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('27378','Fred','I read up on plane crashes on the net every so often. I often find accidents all over the world which didn\'t involve loss of life or did not have passengers involved which I\'d never heard about in the news. Check in airdisaster.com for eg, there are incidents all the time which I\'ll bet you didn\'t hear about (recent ones as well).'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laer</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-2950</link>
		<dc:creator>Laer</dc:creator>
		<pubDate>Sat, 09 May 2009 16:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-2950</guid>
		<description>&lt;p&gt;Mal - You miss my point.  I wrote specifically about the media's inattentetion to the incident, not what's online or not online.&lt;/p&gt;&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('2950','Laer'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('2950','Laer','&#60;p&#62;Mal - You miss my point.&#194;&#160; I wrote specifically about the media\'s inattentetion to the incident, not what\'s online or not online.&#60;\/p&#62;'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>Mal - You miss my point.  I wrote specifically about the media&#8217;s inattentetion to the incident, not what&#8217;s online or not online.</p>
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('2950','Laer'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('2950','Laer','&lt;p&gt;Mal - You miss my point.&Acirc;&nbsp; I wrote specifically about the media\'s inattentetion to the incident, not what\'s online or not online.&lt;\/p&gt;'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mal</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-2948</link>
		<dc:creator>Mal</dc:creator>
		<pubDate>Sat, 09 May 2009 04:35:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-2948</guid>
		<description>You need to research a bit better. There are copies of the incident report on the net. Just google A340 crash. That story is a furphy.&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('2948','Mal'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('2948','Mal','You need to research a bit better. There are copies of the incident report on the net. Just google A340 crash. That story is a furphy.'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>You need to research a bit better. There are copies of the incident report on the net. Just google A340 crash. That story is a furphy.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('2948','Mal'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('2948','Mal','You need to research a bit better. There are copies of the incident report on the net. Just google A340 crash. That story is a furphy.'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-2796</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 27 Apr 2009 09:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-2796</guid>
		<description>
I found this on another website.
jaouad, the accident report, in French.  I’ve done a little translating for those who don’t read Francais.
&lt;a href="http://www.bea.aero/docspa/2007/f-cj071115/pdf/f-cj071115.pdf" rel="nofollow"&gt;http://www.bea.aero/docspa/2007/f-cj071115/pdf/f-cj071115.pdf&lt;/a&gt;

&lt;a href="http://blog.flightstory.net/418/airbus-a340-600-ground-test-accident/#comment-73693" title="Permanent Link to this Comment" rel="nofollow"&gt;32&lt;/a&gt; stevie  &lt;a href="http://blog.flightstory.net/418/airbus-a340-600-ground-test-accident/#comment-73693" title="Permanent Link to this Comment" rel="nofollow"&gt;Mar 24th, 2009 at 10:20 pm&lt;/a&gt; 
This is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:
A. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline’s behalf.
3 people in the cockpit for the test: 2 from Airbus, one from the contractor.
Running the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.
In the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.
In the “service” seat (like the navigator’s seat, only the A340 ain’t got no navigator, I don’t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.
B. There were two main causes: 1) no chocks were used to hold the aircraft’s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines - the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.
Short answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.
Contributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area’s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.
C. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning - 9 hrs later - when it ran out of gas: it was too jammed into the wall to get any water/foam into it. Now THAT’S hi-larious. And not a bad advertisement for Rolls-Royce engines, it seems to me.&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('2796','David'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('2796','David','\r\nI found this on another website.\r\njaouad, the accident report, in French.  I&#226;ve done a little translating for those who don&#226;t read Francais.\r\n&#60;a href=\&#34;http:\/\/www.bea.aero\/docspa\/2007\/f-cj071115\/pdf\/f-cj071115.pdf\&#34; rel=\&#34;nofollow\&#34;&#62;http:\/\/www.bea.aero\/docspa\/2007\/f-cj071115\/pdf\/f-cj071115.pdf&#60;\/a&#62;\r\n\r\n&#60;a href=\&#34;http:\/\/blog.flightstory.net\/418\/airbus-a340-600-ground-test-accident\/#comment-73693\&#34; title=\&#34;Permanent Link to this Comment\&#34; rel=\&#34;nofollow\&#34;&#62;32&#60;\/a&#62; stevie  &#60;a href=\&#34;http:\/\/blog.flightstory.net\/418\/airbus-a340-600-ground-test-accident\/#comment-73693\&#34; title=\&#34;Permanent Link to this Comment\&#34; rel=\&#34;nofollow\&#34;&#62;Mar 24th, 2009 at 10:20 pm&#60;\/a&#62; \r\nThis is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:\r\nA. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline&#226;s behalf.\r\n3 people in the cockpit for the test: 2 from Airbus, one from the contractor.\r\nRunning the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.\r\nIn the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.\r\nIn the &#226;service&#226; seat (like the navigator&#226;s seat, only the A340 ain&#226;t got no navigator, I don&#226;t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.\r\nB. There were two main causes: 1) no chocks were used to hold the aircraft&#226;s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines - the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.\r\nShort answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.\r\nContributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area&#226;s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.\r\nC. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning - 9 hrs later - when it ran out of gas: it was too jammed into the wall to get any water\/foam into it. Now THAT&#226;S hi-larious. And not a bad advertisement for Rolls-Royce engines, it seems to me.'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>I found this on another website.<br />
jaouad, the accident report, in French.  I’ve done a little translating for those who don’t read Francais.<br />
<a href="http://www.bea.aero/docspa/2007/f-cj071115/pdf/f-cj071115.pdf" rel="nofollow">http://www.bea.aero/docspa/2007/f-cj071115/pdf/f-cj071115.pdf</a></p>
<p><a href="http://blog.flightstory.net/418/airbus-a340-600-ground-test-accident/#comment-73693" title="Permanent Link to this Comment" rel="nofollow">32</a> stevie  <a href="http://blog.flightstory.net/418/airbus-a340-600-ground-test-accident/#comment-73693" title="Permanent Link to this Comment" rel="nofollow">Mar 24th, 2009 at 10:20 pm</a><br />
This is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:<br />
A. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline’s behalf.<br />
3 people in the cockpit for the test: 2 from Airbus, one from the contractor.<br />
Running the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.<br />
In the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.<br />
In the “service” seat (like the navigator’s seat, only the A340 ain’t got no navigator, I don’t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.<br />
B. There were two main causes: 1) no chocks were used to hold the aircraft’s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines - the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.<br />
Short answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.<br />
Contributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area’s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.<br />
C. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning - 9 hrs later - when it ran out of gas: it was too jammed into the wall to get any water/foam into it. Now THAT’S hi-larious. And not a bad advertisement for Rolls-Royce engines, it seems to me.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('2796','David'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('2796','David','\r\nI found this on another website.\r\njaouad, the accident report, in French.  I&acirc;ve done a little translating for those who don&acirc;t read Francais.\r\n&lt;a href=\&quot;http:\/\/www.bea.aero\/docspa\/2007\/f-cj071115\/pdf\/f-cj071115.pdf\&quot; rel=\&quot;nofollow\&quot;&gt;http:\/\/www.bea.aero\/docspa\/2007\/f-cj071115\/pdf\/f-cj071115.pdf&lt;\/a&gt;\r\n\r\n&lt;a href=\&quot;http:\/\/blog.flightstory.net\/418\/airbus-a340-600-ground-test-accident\/#comment-73693\&quot; title=\&quot;Permanent Link to this Comment\&quot; rel=\&quot;nofollow\&quot;&gt;32&lt;\/a&gt; stevie  &lt;a href=\&quot;http:\/\/blog.flightstory.net\/418\/airbus-a340-600-ground-test-accident\/#comment-73693\&quot; title=\&quot;Permanent Link to this Comment\&quot; rel=\&quot;nofollow\&quot;&gt;Mar 24th, 2009 at 10:20 pm&lt;\/a&gt; \r\nThis is info from the accident investigation report, from the French version of the NTSB (I believe), the BEA:\r\nA. Mixed ground test crew of 9 on board: some from Airbus proper, based there in Toulouse, some from the Abu Dhabi-based contractor working on the airline&acirc;s behalf.\r\n3 people in the cockpit for the test: 2 from Airbus, one from the contractor.\r\nRunning the test, in the right seat of the cockpit, in charge of the all controls: Airbus technician, 15 yr employee, 9 yrs experience testing these engines. When he was alerted that the aircraft was moving, his only actions were to kill the parking brake while simultaneously stomping on the main brakes.\r\nIn the left seat, observing the test: contractor employee, alerted the test tech that the aircraft was moving. Has no specified role in the test other than to observe.\r\nIn the &acirc;service&acirc; seat (like the navigator&acirc;s seat, only the A340 ain&acirc;t got no navigator, I don&acirc;t believe): Airbus-employed test pilot, 9 yrs experience as a professional pilot, 7 as a test pilot, not type rated (i.e., not an A340 pilot), perhaps a manager qualified to supervise such tests. Once again, no specific role other than to observe, but in the end it was him who pulled the throttles back.\r\nB. There were two main causes: 1) no chocks were used to hold the aircraft&acirc;s wheels in place during the test. 2) All four engines were brought to full power to test one leaky engine. Procedures required the use of chocks and running up two engines - the one leaking and one on the other wing (to prevent torquing and yawing of the fuselage). These two procedures had been frequently ignored by all Airbus technicians at the test center for some time.\r\nShort answer: the test was done improperly, not in accordance with written procedures and standards. The fault of the Airbus technician.\r\nContributing causes: 1) the full power of four engines is almost exactly equal to the braking power of the A340s parking brake and the frictional coefficient of the test area&acirc;s tarmac, hence the aircraft only moved when shaking of the aircraft and the burning off of fuel lessened the overall braking coefficient. 2) The technician tried to use the brakes alone to stop the aircraft rather than retarding the throttles as well.\r\nC. Fun fact: the numbers 3 and 4 engines could not be shut down after impact because the throttle control connection to them had been severed. No. 4 was finally killed over two-and-a-half hours later when enough water and fire-fighting foam had been pumped into it to snuff it out. The No. 3 engine died at 1:25 am the next morning - 9 hrs later - when it ran out of gas: it was too jammed into the wall to get any water\/foam into it. Now THAT&acirc;S hi-larious. And not a bad advertisement for Rolls-Royce engines, it seems to me.'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meat</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-2681</link>
		<dc:creator>Meat</dc:creator>
		<pubDate>Thu, 09 Apr 2009 05:01:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-2681</guid>
		<description>Bet Captain Sully Sullenberger wouldn't have done that.
 
Your pal,
Meat.&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('2681','Meat'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('2681','Meat','Bet Captain Sully Sullenberger wouldn\'t have done that.\r\n&#194;&#160;\r\nYour pal,\r\nMeat.'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>Bet Captain Sully Sullenberger wouldn&#8217;t have done that.<br />
 <br />
Your pal,<br />
Meat.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('2681','Meat'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('2681','Meat','Bet Captain Sully Sullenberger wouldn\'t have done that.\r\n&Acirc;&nbsp;\r\nYour pal,\r\nMeat.'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mtnbiker</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-2674</link>
		<dc:creator>Mtnbiker</dc:creator>
		<pubDate>Mon, 06 Apr 2009 23:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-2674</guid>
		<description>What -- No Towers In France?&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('2674','Mtnbiker'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('2674','Mtnbiker','What -- No Towers In France?'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>What &#8212; No Towers In France?
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('2674','Mtnbiker'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('2674','Mtnbiker','What -- No Towers In France?'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laer</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-2658</link>
		<dc:creator>Laer</dc:creator>
		<pubDate>Thu, 02 Apr 2009 14:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-2658</guid>
		<description>&lt;p&gt;Thanks, Capt'n.&lt;/p&gt;&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('2658','Laer'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('2658','Laer','&#60;p&#62;Thanks, Capt\'n.&#60;\/p&#62;'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>Thanks, Capt&#8217;n.</p>
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('2658','Laer'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('2658','Laer','&lt;p&gt;Thanks, Capt\'n.&lt;\/p&gt;'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Captain Bob</title>
		<link>http://www.cheatseekingmissiles.com/2009/03/28/the-politically-correct-airplane-crash/#comment-2657</link>
		<dc:creator>Captain Bob</dc:creator>
		<pubDate>Wed, 01 Apr 2009 22:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheatseekingmissiles.com/?p=6614#comment-2657</guid>
		<description>The Airbus A340-600 is not the largest jet Airbus makes, it's the second largest. The double decker Airbus A380 is the largest jet they make.&lt;div class="comment-remix-meta"&gt;&lt;a href="#" class="replyto" onclick="replyto('2657','Captain Bob'); return false;"&gt;Reply&lt;/a&gt;  - &lt;a href="#" class="quote" onclick="quote('2657','Captain Bob','The Airbus A340-600 is not the largest jet Airbus makes, it\'s the second largest. The double decker Airbus A380 is the largest jet they make.'); return false;"&gt;Quote&lt;/a&gt;&lt;/div&gt;</description>
		<content:encoded><![CDATA[<p>The Airbus A340-600 is not the largest jet Airbus makes, it&#8217;s the second largest. The double decker Airbus A380 is the largest jet they make.
<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('2657','Captain Bob'); return false;">Reply</a>  - <a href="#" class="quote" onclick="quote('2657','Captain Bob','The Airbus A340-600 is not the largest jet Airbus makes, it\'s the second largest. The double decker Airbus A380 is the largest jet they make.'); return false;">Quote</a></div>
]]></content:encoded>
	</item>
</channel>
</rss>
