Aviation Crash Map

Airbus A300-600F N681FE

11 June 2002 · El Paso, Texas, United States · No injuries

Summary

On 11 June 2002 at about 03:30 local time, a Airbus A300-600F registered N681FE was involved in an accident near El Paso, Texas, United States. 2 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 03:30
Classification
Accident
Location
El Paso, Texas, United States
Nearest airport
El Paso International (KELP)
Coordinates
31.8067, -106.3778
Aircraft
Airbus A300-600F
Registration
N681FE
Category
Airplane
Engines
2
Operator
Not recorded
Operating rule
Part 121: Air Carrier
Phase of flight
Not recorded
Route
El Paso → Memphis
Aircraft damage
Substantial
Weather
VMC
Light
Night/Bright
NTSB number
FTW02LA198

People

Nobody was injured.

On board Died Serious Minor Uninjured
2 0 0 0 2

Probable cause

The flight crew's failure to obtain the Vr speed prior to rotation which resulted in insufficient lift and the subsequent tail strike.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The flight crew briefed the departure, completed the taxi-out and pre-departure checklist and entered the V-speeds (V1 was 139 knots and Vr was approximately 143 knots) into the flight management system (FMS) with both crewmember's primary flight display (PFD) displaying the V-speeds with the standard blue lines and no discrepancies noted. The captain entered the V2 speed (approximately 143 knots) into the flight control computer in the glare shield and entered 250 knots for the extended speed to 10,000 feet msl. The first officer did not recall being distracted during the checklist or before takeoff procedures. The flight crew requested and was cleared for departure on runway 04. The PF aligned the airplane on the runway and applied standard take-off power. The flight instruments were cross-checked at 80 knots and the V-speeds were correctly displayed on the PFD. The first officer checked the engine diagnostic page to observe the #2 engine vibrations. According to the first officer, when he looked back at the PFD, the V-speeds were not displayed, and V2 had reset to 100 knots. The first officer did not look at the speed index (correct raw speed data) on the left side of the PFD. The first officer called V1 rotate, and the captain responded to an aircraft pitch of approximately 12 degrees. The captain realized the airplane was not climbing or accelerating properly. The first officer realized the airspeed was approximately 120-125 knots (below V2) and called for the captain to lower the nose of the airplane. The captain lowered the nose, and executed a rejected take-off by pulling the throttles to idle. The flight control computer automatically applied maximum auto brakes, the airplane slowed, and the captain taxied the airplane off the runway. Neither flight crewmember recalled the aft end of the airplane strike the runway. The flight crew deplaned, entered the discrepancy "rejected T/O due to FMS speeds dumping and blue A/S line rolling back to 100. Rejected @ 120 knots Raw data still indicated properly." in the Aircraft Maintenance Log (AML) and departed the airport. The flight release weight and balance indicated the takeoff gross weight was 297,184 pounds. The takeoff center of gravity was 24.9. The DFDR revealed the following (1) The airplane became airborne for about 4 seconds. During the takeoff roll, pitch attitude reached 13.4 degrees airplane nose up with control column position recorded as 7.1 degree aft and elevator position recorded as 16.6 degree trailing edge up. (2) Pitch attitude decreased and was approximately 6 degrees upon touchdown of the left and right main landing gear, at which time the airplane experienced a vertical acceleration of 1.844 g's. (3) Airspeed was recorded as 114 knots when the nose gear initially left the ground. Airspeed continued to increase and was recorded as 131 knots. Following touchdown of the nose landing gear, airspeed reached its maximum recorded value of 138 knots. (4) Engine 1 and engine 2 thrust reversers were briefly unlocked before both were unlocked again and remained in that state. (5) Longitudinal acceleration reached -0.584 g's and lateral acceleration reached -0.151 g's during the rejected takeoff sequence. According to the operator's representative, the "test results for the Flight Control Computer, Flight Management Computer, Flight Warning Computer, ECAM, Flight Augmentation Computer, and Signal Generator Unit found no faults. Examination of the aircraft found no anomalies that would have prevented it from operating per design prior to the tail strike.

Quoted verbatim from the NTSB record.

Other Airbus A300 accidents

Date Aircraft Location Operator Outcome Died
28 Nov 2001 Airbus A300-600
N7055A
Lima, Peru
no coordinates
American Airlines Inc No injuries -
30 Jul 2001 Airbus A300-600
HZ-AJJ
Jeddah, Saudi Arabia
no coordinates
Saudi Arabian Airlines No injuries -
21 Jun 2005 Airbus A300-600
HS-TAO
Singapore, Singapore
no coordinates
Thai Airways International Ltd Unknown -
27 Nov 1998 Airbus A300-600 Jakarta, Indonesia
no coordinates
Korean Airlines Unknown -
20 Apr 1998 Airbus A300-600
N33069
Atlantic Ocean
no coordinates
American Airlines No injuries -
9 Jul 1998 Airbus A300
N70072
London, United Kingdom
no coordinates
American Airlines, Inc No injuries -

All 26 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
4 May 2002 Boeing A75SN1
N5805V
Georgetown, Texas, United States - Minor injuries -
17 Sep 2002 Cessna 188A
N9943G
Vincent, Texas, United States Elk Creek Spraying Service No injuries -
13 Jul 2002 Aero Commander CALLAIR A-9B
N7791V
El Paso, Texas, United States - Serious injuries -
16 Jan 2002 Bellanca 17-30
N7388V
Plainview, Texas, United States - No injuries -
17 Jan 2002 Cessna 340A
N339S
Temple, Texas, United States - Fatal 3
18 Jan 2002 Beechcraft C23
N6622X
Sinton, Texas, United States - Fatal 1

All 170,864 records in United States