No fatalities

2003 Boeing 747-300 Tail Scrape at Johannesburg International Airport (ZS-SAJ)

Johannesburg International Airport S26° 08’ 01” E 028° 14’ 32” at an elevation of 5558’ AMSL, ZA

On March 11, 2003, a Boeing B747-300 (registration ZS-SAJ) was involved in an aviation accident near Johannesburg International Airport S26° 08’ 01” E 028° 14’ 32” at an elevation of 5558’ AMSL, ZA. No fatalities were reported. Investigators recorded the probable cause as: The flight engineer unintentionally entered the incorrect weight into the hand-held performance computer, resulting in incorrect computed takeoff speeds that were checked by the pilot-in-command and set as bugs on the airspeed indicators. This summary draws on records from the South African Civil Aviation Authority (SACAA) Accident and Incident Investigations Division.

Sourcesthe South African Civil Aviation Authority (SACAA) Accident and Incident Investigations DivisionPrimary reportUpdated 2026-10-18Data APIEditorial standards
Aircraft registered ZS-SAJ
Aircraft registered ZS-SAJ. Photo: Aero Icarus from Zürich, Switzerland / CC BY-SA 2.0, via Wikimedia Commons

On 11 March 2003, a Boeing B747-300 (ZS-SAJ) experienced a tail scrape during takeoff from Johannesburg International Airport due to incorrect takeoff speeds entered into the performance computer. The aircraft returned safely with no injuries.

Incident Overview and Aircraft Details On 11 March 2003, a Boeing B747-300 with registration ZS-SAJ was scheduled to depart Johannesburg International Airport, South Africa, for Sao Paulo, Brazil, on an international scheduled flight. The aircraft had a total flying time of 20,335.25 hours. The pilot-in-command held a transport pilot's license, was 56 years old, and had 5,829.45 hours on type. The flight crew consisted of 5 people, with 15 other crew members and 137 passengers on board. ## Operational Context and Pre-Flight Issues The flight was initially delayed by air traffic control (ATC) because only one ATC radar sector was in use. During the pre-flight inspection, the auxiliary power unit (APU) failed to provide sufficient airflow for the cockpit and cabin and to start the engines. The crew planned to use a ground air cart to start one engine and then cross-bleed start the others. The expected 45-minute delay was reduced to 30 minutes when ATC issued start clearance. ## Weight and Speed Calculation Error The flight engineer obtained the load sheet but entered the zero fuel weight of 203,580 kg instead of the aircraft's takeoff weight of 324,456 kg into the hand-held performance computer. The computed takeoff speeds were then transferred to the takeoff cards. The pilot-in-command checked the speeds, as the first officer was busy, and both pilots set the relevant bugs on their airspeed indicators. These bugged speeds were incorrect for takeoff. ## Takeoff and Aftermath During the takeoff roll from Runway 03L, with engine power set at 1.42 EPR and 10° of flaps selected, the pilot-in-command called “ROTATE” at the speed set on the airspeed indicator. He sensed the aircraft felt nose-heavy and delayed rotation by 15 knots. As the aircraft became airborne, the pilot-in-command requested more thrust because the aircraft still felt “sluggish,” and the flight engineer called “sinking.” The pilot-in-command kept the nose down to gain more speed. The aircraft climbed away at a positive rate of climb before the landing gear was retracted. ATC notified the pilot that a tail scrape had occurred during takeoff. Fuel was dumped before the aircraft landed back at Johannesburg International Airport. The crew and passengers disembarked normally without any injuries.

Probable cause

The flight engineer unintentionally entered the incorrect weight into the hand-held performance computer, resulting in incorrect computed takeoff speeds that were checked by the pilot-in-command and set as bugs on the airspeed indicators. Several distractions on the flight deck and a sudden reduction in the expected ATC delay from 45 to 30 minutes contributed to the incident.

Frequently asked questions

What happened in the 11 Mar 2003 Boeing B747-300 accident near Johannesburg International Airport S26° 08’ 01” E 028° 14’ 32” at an elevation of 5558’ AMSL, ZA?

On 11 March 2003, a Boeing B747-300 (ZS-SAJ) experienced a tail scrape during takeoff from Johannesburg International Airport due to incorrect takeoff speeds entered into the performance computer. The aircraft returned safely with no injuries.

Were there any fatalities in the 11 Mar 2003 Boeing B747-300 accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 11 Mar 2003 involved a Boeing B747-300, registration ZS-SAJ, at Johannesburg International Airport S26° 08’ 01” E 028° 14’ 32” at an elevation of 5558’ AMSL, ZA.

What was the probable cause of the accident?

The flight engineer unintentionally entered the incorrect weight into the hand-held performance computer, resulting in incorrect computed takeoff speeds that were checked by the pilot-in-command and set as bugs on the airspeed indicators. Several distractions on the flight deck and a sudden reduction in the expected…