![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#6
|
|||
|
|||
![]()
On Tue, 26 Oct 2004 at 18:12:20 in message
TBCfd.18911$SW3.16862@fed1read01, Jay Beckman wrote: Is that due to the crash at the Paris Airshow several years back? Many people say Paris - it wasn't Paris it was Mulhouse, in the upper Rhine Valley near the junction of the Swiss and German borders. It was only a local air show and the aircraft was an almost new A320 (it had been in service for 2 days). The Airport (if you could call it that) has one main paved runway only 1000m long plus some grass strips for gliders. Air France were invited to display an A320. It could not land there. Not only that but it was a charter flight with 130 passengers aboard - how often does that happen at the Paris Air Show I wonder? The crew were probably given an inadequate briefing on the airport. The idea was to do a low slow pass in landing configuration at about 100ft. (Often done in France although the air show regulations said 170 ft.) They intended to reach the maximum allowable angle of attack in the low pass. They meant they would inhibit the 'alpha floor' limit which would automatically increase power at that point. The co-pilot was supposed to control the power. When they identified the airport they were close but they saw that the crowd seemed to be along a grass strip and not along the chosen paved runway 02. They realigned and at 100 ft deactivated the alpha floor function. They sank to only 30 ft above the strip. They then suddenly realised there were trees ahead at the same height or higher than the aircraft. They then called for TO power but it was too late. Speed had reduced to 122k and the engines now at flight idle responded as they should. There was then nothing anyone or the aircraft could do. 4.5 seconds after power started increasing it began hitting the trees. That is a very much abbreviated version but I believe substantially correct. IIRC, the pilot commanded a flight attitude in the landing config that the software wouldn't allow and that led to the aircraft settling into the trees. Sorry that is wrong. And it did not settle into the trees; it flew horizontally into them at an altitude of 24 ft and then sank! This accident is very often badly reported. Although the system would not permit main flight restrictions to be exceeded the performance at those low limits was as limited as any conventional aircraft would have been. It could not climb at flight idle at 122 knots and 15 degrees nose up. That is not a surprise. This case is a bad example but often used. Ref: Air Disaster Volume 3 by Macarthur Job. Roughly 13 pages -- David CL Francis |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
AOPA Stall/Spin Study -- Stowell's Review (8,000 words) | Rich Stowell | Aerobatics | 28 | January 2nd 09 02:26 PM |
Military: Pilot confusion led to F-16 crash that killed one pilot | Otis Willie | Military Aviation | 0 | September 1st 04 12:30 AM |
P-51C crash kills pilot | Paul Hirose | Military Aviation | 0 | June 30th 04 05:37 AM |
Fatal plane crash kills pilot in Ukiah CA | Randy Wentzel | Piloting | 1 | April 5th 04 05:23 PM |
AmeriFlight Crash | C J Campbell | Piloting | 5 | December 1st 03 02:13 PM |